Open opportunity
There is an important need, but no bounded use case yet.
Takeoff · 21 days
Turn a vague opportunity into a tested system.
We observe the real work, bound the challenge and design the accelerator worth testing first.
- 21 days
- Real challenge
- Assigned coach
Takeoff · 21 days
- Understand
- Design
- Activate
When it fits
Does this path fit?
Check where it helps and where another intervention would be more appropriate.
When clarity is needed before committing to a larger transformation.
Takeoff reduces uncertainty through a small, observable intervention.
Fragmented work
The team recognizes friction but does not yet agree on its cause.
Pending decision
Own evidence is needed before investing in a broader solution.
A shortcut around context, permissions or accountability.
Predetermined purchase
We do not use diagnosis to justify a tool that was already selected.
Abstract challenge
Without an observable workflow, decision or deliverable, there is no honest test.
Blocked access
Without owners or authorized information, access must be resolved first.
Active diagnosis
We look for lost value while the work is happening.
Diagnosis tests narratives against decisions, documents and exceptions.
Outcome
What the workflow must produce, for whom and to which standard.
Friction
Where waiting, rework, ambiguity or lost context appears.
Conditions
Which data, permissions, tools and reviews bound the intervention.
Ambassador Coach
One assigned person connects the challenge, test and decision.
The coach facilitates the process and preserves traceability; the team owns the outcome.
Observe
Joins agreed work moments and makes assumptions and blockers visible.
Challenge
Turns preferences into hypotheses and requests evidence before consolidation.
Transfer
Documents criteria and prepares the owner who continues after day 21.
Three moments
Understand, design and decide in 21 days.
Each moment produces what the next one needs.
Frame
Days 1–5 · Agree on challenge, outcome, owners, constraints and starting point.
Test
Days 6–15 · Design the accelerator and test it on authorized cases.
Decide
Days 16–21 · Review evidence, refine and recommend closure, extension or rejection.
Deliverables
Four pieces for the next decision.
Exact content adapts to the challenge; traceability is mandatory.
Challenge summary
Outcome, scope, owners, assumptions and limits.
Operating map
Current workflow, friction and prioritized opportunities.
Accelerator design
Inputs, output, controls and acceptance criteria; includes a prototype when access allows.
Progress decision
Evidence, open issues and recommendation to close or move into Traction.
Entry and close
Takeoff starts with access and ends with a defensible decision.
To begin
- Challenge and owner identified
- Work examples available
- Permissions and reviewers agreed
To close
- Starting point documented
- Accelerator defined and test recorded
- Decision, owner and next step explicit
Boundaries
- No quantitative outcome is promised
- Nothing is deployed without authorization
- Missing evidence is never invented
Frequently asked questions
What you need to know before moving forward.
Do we receive a working accelerator?
With access, data and authorization, it includes an operable test. Otherwise, a verifiable specification with explicit dependencies.
What can an accelerator be?
An instruction, assistant, workflow or standard that reduces specific friction with controls.
Must we choose technology first?
No. We first bound the case and requirements, then select a compatible option.
What happens on day 21?
We decide whether the case moves to Traction, needs another test or closes. Continuation is not forced.
First horizon
Clarify the challenge before scaling the investment.
One conversation confirms the case, access and evidence that can be produced in 21 days.