What you get in three weeks
The Production Sprint leaves a folder a decision-maker can act on: as-is, to-be, controls, evidence, and a ninety-day path.
Part of Product Offers (6)
If the output is only slides, you bought theatre.
The Production Sprint is built around a folder a decision-maker can act on.
In the pack (typical)
- Kick-off pack and RACI for one workflow
- As-is map — people, systems, tickets, evidence gaps
- To-be operating model — dual control, gates, exceptions
- Requirements and use cases (when the thick pack applies)
- Architecture views — context, sequences, components, data/control flow
- Control matrix mapped to that workflow
- Evidence-plane design on your systems
- 90-day production path, SOP outlines, go-live checklist
- Executive one-pager for CCO or board
Exact composition is in the Production Sprint brief. Samples of shape (not a paid client case) live under Work.
What “done” means
- Named workflow has a clear to-be.
- CCO can point to control + evidence model.
- 90-day path is accepted or explicitly deferred with owners.
Not: “we aligned stakeholders.” Not: “platform roadmap.”
After the sprint
Optional: Production Build, Integration SI, Operator Lab, fractional Production Owner. None of those are forced. None replace the deposit-backed sprint.
Next step: Open the sample pack. If the shape is wrong for you, do not force a fit call.
Fence: Implementation folder. Not a software licence. Not custody.