Status — In synthesis
Workflow-based versus feature-based navigation
Question
Does organising the site around workflows rather than capabilities help readers find relevant material?
Hypothesis
People arrive with an outcome in mind, not a capability name, so workflow-first navigation should shorten the path to relevant content.
Who it concerns
First-time visitors with a product problem.
Intervention
Workflows are a top-level section; the Platform page explains capabilities but links out to workflows constantly.
What would be observed
- Which section first-time reviewers open after the homepage
- Whether they can name a relevant workflow unprompted
What would count as a useful signal
Reviewers describe the site in terms of what it helps them build rather than what it contains.
Notes
Homepage currently leads with guides; worth testing workflows-first.
information architecturenavigation
This entry records a design intention. It does not report measured results, traffic, rankings, or customer outcomes.