Methodology
Three sprints. One system.
A single URL you can share with procurement, the board or a venture partner — how we think, how long it takes, and what you hold in your hands at each gate.
Why sprints
Traditional consulting often optimises for deliverable weight and billable continuity. That can leave clients with impressive documents and unchanged behaviour. Sprints invert the incentive: time-boxed phases, explicit outputs, and go / no-go decisions baked into the calendar.
Structured sprints also reduce political drag. When everyone knows what week three must produce, debates narrow to substance — not survival.
Sprint 01
Scoping
Weeks 1–3 · Decision clarity
We interview stakeholders, map the real decision chain (not the org chart), review existing evidence and pressure-test assumptions. Workshops are tight and outcome-oriented.
Who is involved: executive sponsor, programme lead, 6–10 subject experts as needed.
What you receive: problem statement, hypothesis set, success metrics draft, risk register, written recommendation on whether to proceed to prototype.
Pricing approach: fixed sprint fee scoped after a discovery call — no open-ended discovery billing.
Sprint 02
Prototype
Weeks 4–8 · Evidence under uncertainty
We build the smallest set of prototypes — service blueprints, venture narratives, clickable flows, partner pilots — that let you learn before you scale capital or reputation.
Who is involved: product or venture lead, field or operations representatives, compliance where relevant.
What you receive: prototype artefacts, test protocol, findings memo, explicit scale / pivot / stop recommendation.
Pricing approach: fixed sprint fee; out-of-pocket research incentives billed transparently.
Sprint 03
Execution
Weeks 9–12 · Operating reality
We install the minimum viable operating system: cadence, dashboards where useful, escalation paths and ownership maps — so the work survives the week we are not in the building.
Who is involved: COO / programme office, team leads, sometimes HR or finance for incentive alignment.
What you receive: playbooks, workshop recordings, handover checklist, 30/60/90-day review template.
Pricing approach: fixed sprint fee; optional light retainer scoped separately if needed.
How it connects
Scoping
Commit to the problem before the build.
Prototype
Learn cheaply where uncertainty is highest.
Execution
Make the organisation capable of running the bet.
What you get across all three
- Written decision artefacts at each gate — not oral tradition.
- Shared language between strategy, product and operations.
- Explicit kill criteria so political fear does not smother honest signals.
- A partner accountable for the arc, not only the workshop room.
Is this right for you?
Ideal clients bring a sponsor with budget authority, a problem that matters on a twelve-month horizon, and willingness to assign internal time to sprints — not only to us. If you need a vendor to “own delivery” indefinitely without organisational change, we are rarely the fit.
Begin a sprint
Start with Scoping. We will tell you honestly if the moment is wrong.