Example scenario
A nonprofit website has grown around internal structures rather than visitor needs. Program information is difficult to navigate, important supporter journeys are unclear, and routine updates require more technical effort than the team can sustain.
Proposed approach
Start with stakeholder and content discovery, then organize the site around priority visitor tasks. Create accessible components and plain-language page patterns, establish a manageable publishing workflow, and define performance, search, and measurement checks before launch.
How success would be measured
- Visitors can complete agreed program, contact, and support journeys in usability reviews
- Priority templates pass the agreed accessibility checks
- Staff can publish and update routine content through a documented workflow
- Core pages meet agreed performance and search-readiness baselines
- Analytics capture the agreed visitor journeys without presenting outcomes