Process
A structured delivery model that reduces ambiguity before it becomes rework.
Delivery system
Five stages
The depth changes with the project, but each stage has a concrete result, a client responsibility and a condition for moving forward.
A shared problem model: audience, current journey, constraints, evidence gaps and the decision that needs to improve.
Client participation
Provide existing materials, access to relevant non-secret systems/data, and the people who understand the current workflow.
Move forward when
Move forward when the problem and evidence gaps are clear enough to define scope without guessing.
Approved scope, information architecture, system boundaries, ownership and acceptance criteria for the first useful release.
Client participation
Review priorities, confirm business rules and identify who can approve content, pricing, permissions or other consequential states.
Move forward when
Move forward when the build team can explain what is in scope, what is not, who owns each rule and how completion will be judged.
Working experience, integrations and operating workflow implemented against the agreed acceptance model.
Client participation
Answer bounded domain questions, review decision points that need business approval and provide timely access to approved content or systems.
Move forward when
Move forward when the critical path is complete enough to validate end-to-end behavior rather than isolated screens.
Release evidence for critical paths, content/state checks, acceptance conditions and a known recovery or rollback route.
Client participation
Review acceptance evidence and approve release where business or operational authority is required.
Move forward when
Release only when blocking defects are resolved or explicitly accepted and recovery is understood.
A prioritized next-decision list grounded in real usage, analytics, operational evidence and unresolved constraints.
Client participation
Share business outcomes and operational feedback that analytics alone cannot explain.
Move forward when
Choose the next change only when the evidence supports a useful question—not because a backlog needs filling.
Release principle
What was actually checked?
Which system or rule decides?
What happens if the release fails?
Next step
