...
| Tip |
|---|
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. |
| Tip |
|---|
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. |
| Tip |
|---|
In In general, we discard trees (or elements) that didn’t perform well, and pursue those that did, documenting our rationale as we go. |
| Tip |
|---|
Testing alternative trees makes this iterative approach much more powerful. |
| Tip |
|---|
When When re-testing, we should also revise tasks that were not clear in the first round, or which needs rewording (or different correct answers) because of our tree changes. |
| Tip |
|---|
We We ideally want fresh participants for the follow-up test, but may have to settle for previous participants if our pool is small. |
| Tip |
|---|
We’re “done” when our success rate is high (>70%) and there are no more useful revisions we can make to the tree. |
...