/
Chapter 14 - key points

Chapter 14 - key points


Most trees will need revisions after testing. If these are more than minor tweaks, they should be re-tested to confirm that they fix the observed problems.

Re-testing results in a better structure, shows that the organization is willing to try out ideas, and lets the project team “prove” that their final design is better than previous ones.

In general, we discard trees (or elements) that didn’t perform well, and pursue those that did, documenting our rationale as we go.


Next:  Chapter 15 - Special considerations

Related content

14 - Revising and retesting
14 - Revising and retesting
More like this
Revising trees
More like this
How many rounds of testing?
How many rounds of testing?
More like this
When are we done?
When are we done?
More like this
The design phase: going deep
The design phase: going deep
More like this
Rewording and replacing tasks
Rewording and replacing tasks
More like this


Copyright © 2024 Dave O'Brien

This guide is covered by a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.