Three plausible project situations showing how strategy, content, design, and launch evidence connect. These are not claimed clients or performance outcomes.
Situation: respected work arrives through referrals, but the site cannot explain fit. Direction: map the audience decision, build a proof inventory, organise services by situation, and create a qualification handoff. Evidence: a positioning sentence, service responsibilities, content ownership, and a testable enquiry path.
Situation: events, stories, resources, and archives compete in one inherited menu. Direction: create audience routes, programme relationships, accessible event patterns, and an editorial model. Evidence: route responsibilities, representative templates, keyboard flows, and a publishing rehearsal.
Situation: an ageing site contains valuable routes and undocumented dependencies. Direction: inventory, keep/merge/archive decisions, redirect mapping, baseline capture, and staged release. Evidence: route tests, migration exceptions, rollback conditions, and post-launch review.
Situation: products exist but comparison and care information are inconsistent. Direction: model catalogue relationships, define decision evidence, make states accessible, and document transaction boundaries. Evidence: representative catalogue flow, integration responsibilities, and failure handling.