UX Framework

What it is

A usability method where participants navigate a text-only website structure to test findability. Evaluates information architecture without visual distractions.

How to use

Checklist:

• Digital tool (Optimal Workshop, FigJam)
• Text-based sitemap hierarchy
• 5-8 realistic tasks (e.g., 'Find next-day delivery costs')
• Post-task questionnaire
• Recruiting screener

Time:

• Prep: 1-2 hours (build tree + tasks)
• Test: 10-15 mins per participant
• Analysis: 1-3 hours

Participants:

• 15-50 users (remote)
• Minimum: 10 for reliable data

Steps:

1. Build your tree:

• Convert site structure to text hierarchy:

• 'You need to return damaged trainers. Where would you start?'

• Participants navigate the tree to complete tasks
• No images/icons - pure text only

• Success rate: % correct paths
• Directness: Optimal path vs. detours
• Time on task

• Rename confusing labels (e.g., 'Services' → 'Support')
• Restructure deep hierarchies (e.g., reduce 5 levels → 3)

Tips & Variations

Do:

• Test early (before visual design)
• Use open phrasing: 'How would you find…?' not 'Click on X'
• Pilot test with colleagues first

Avoid:

• Jargon (e.g., 'SKU lookup' → 'Find product code')
• Trees > 4 levels deep
• Leading tasks ('Go to Help Centre > Returns')

Variations:

• Reverse tree test: Show a category, ask 'What would you expect here?'
• Hybrid: Combine with card sorting to build the tree

Why this method

Pros

• Exposes labelling issues cheaply (e.g., 'FAQ' vs 'Help')
• Validates navigation before development
• Quantifies findability (statistically reliable)

Cons

• Misses behavioural context (no clicks/scrolls)
• Artificial without visual cues
• Poor for testing transaction flows (e.g., checkout)

Find out more

• UK: Tree Testing Guide
• Nielsen Norman Group: Tree Testing Essentials