"How many roads must a man walk down, before you can call him a man?" - Bob Dylan
This is what we've been waiting for - actual results from actual users. Now, we just need to figure out what the data means.
Luckily, the basic results from tree tests are usually easy to understand - easier, say, than a typical open card sort. And if we're using tree-testing software, the results have already been summarized and visualized, ready for us to discover how well our tree(s) performed.
Backing up raw data, removing garbage, updating correct answers
Publishing via the tool, sharing logins, uploading results to the cloud
Overall success rate, directness, speed, and overall score
Where they went, clicked first, backtracked, slowed down, gave up, etc.
Looking for clusters of right and wrong answers
Filtering results using survey questions, and comparing them
What they are, how to spot, why they happen, how to get rid of them