Information architecture research · PUBLIC RESEARCH BRIEF
Optimal WorkshopWhen is navigation evidence strong enough to change the structure?
Optimal Workshop describes card sorting, tree testing, first-click testing, surveys, interviews and other usability methods. Its guidance distinguishes generative card sorting from evaluative tree testing: one helps reveal how people group information, while the other tests whether they can find it in a proposed hierarchy. Combining them can be useful, but the methods answer different questions.
Updated 2026-10-22 · Simulation results not yet generatedCHANGE ONE THING. LEARN WHAT MATTERS.
Three questions for the GTM team.
If first-click results look strong but tree-test paths reveal confusion, which task, label or participant evidence should determine the next revision?
Set up this study →How should teams handle meaningful minority mental models without creating a navigation structure that is internally inconsistent for everyone?
Set up this study →PROPOSED AUDIENCE
Who should weigh in?
North American UX researchers, information architects, content designers, product designers, product managers and digital teams evaluating Optimal Workshop. Include people designing and approving website or product navigation. Proposed audience only; no Optimal Workshop study, participant response or customer workspace is included.
TWO TIME HORIZONS
Trial today. A habit tomorrow?
Near term · 0–90 days
Over 0–90 days, test fictional content sets and hierarchies containing ambiguous labels, overlapping categories and known findability failures. Compare method sequencing, segment interpretation, task realism, revision quality and confidence calibration.
Longer term · 3–12 months
Over 3–12 months, follow approved navigation decisions across content growth and product change. Study label drift, new-category pressure, returning-user habits and whether prelaunch task performance matches live search and navigation behavior.
What would make the result actionable?
Use versioned trees, seeded ambiguity, synthetic card sorts, known task paths and blinded information-architecture review. Validate changes with relevant participants and live findability evidence; do not equate preference with successful navigation.
A Gather simulation returns hypothetical customer reactions. Quantifying revenue, traffic or retention needs actual business inputs and validation against observed behavior.