Six phases. Weekly evidence.
Rigorous enough for high-value international work, flexible enough to keep moving. You always know who owns the outcome and what the next decision is.
A real working session — a wall or large screen covered in sitemap, wireframes and printed decisions, two people mid-discussion, seen from behind so faces are not the subject. Documentary, not staged. Should look like work rather than a stock meeting.
Save as /public/img/process-wall.webpUnderstand
Discovery with the people who actually decide. We are looking for the commercial truth behind the brief, the constraints nobody mentioned, and what success would have to look like to be worth doing.
Outputs · Discovery, constraints, success measures
Define
Positioning, audience journeys, scope and the technical roadmap. You approve the problem and the priorities here — before anything visual exists to argue about.
Outputs · Positioning, journeys, scope, technical roadmap
Design
Interface system and prototypes. The important interactions and the risky technical bits get tested now, while changing them is cheap.
Outputs · Interface system, prototypes, motion direction
Engineer
Frontend, CMS, integrations and analytics, built against agreed performance and accessibility budgets rather than measured against them afterwards.
Outputs · Frontend, CMS, integrations, analytics
Prove
Device QA, Core Web Vitals, WCAG 2.2 AA on core journeys, security review and structured acceptance testing. We break it deliberately before your customers do it by accident.
Outputs · Device QA, accessibility, performance, security
Launch & evolve
Deployment, monitoring, training and a prioritised improvement backlog. The measurement plan is agreed before release, not invented after it.
Outputs · Deployment, monitoring, optimisation backlog
- Weekly working session with the people who decide
- A decision log covering approved scope, assumptions and changes
- Progress shown as working artefacts, not status percentages
- Formal gates at strategy, design, build completion and launch readiness
- Documentation, access and training designed into delivery — no black-box build
Every material request is classified as a clarification, a correction, a scope trade, or a scope addition. Additions get an impact statement covering cost, timeline and dependencies before work begins.
That is not bureaucracy — it is what stops three people building against three different assumptions, which is how quality actually dies on a project.
Bring us the challenge