From C-level vision to a running system in 90 days
Strategy is cheap; running systems are not. The gap between them is a sequence, and the sequence fits in a quarter.
Most transformation initiatives die in the gap between the deck and the doing. Closing it is less about ambition and more about a disciplined cadence.
Why initiatives stall between deck and doing
The deck is approved, the budget exists, and then weeks pass in meetings about scope. The gap is rarely a lack of will. It is the lack of a sequence that turns intent into the next concrete step. Here is one that fits in a quarter.
Weeks 1–2: Audit
Map what actually exists: the tools, the data, the manual steps, the leaks. The goal is not a report. It is a shared, honest picture of the current state that everyone agrees on before anything changes.
- Outcome: one current-state map the whole team signs off on
- Decision: which two or three problems are in scope, and which are explicitly not
- Risk: an audit that turns into a blame exercise, so keep it about flows, not people
Weeks 3–4: Architecture
Design the target state on paper. Structure before tooling: define the flows, the owners, and the measurable outputs first. Tool choices fall out of this almost automatically.
- Outcome: target flows with a named owner and one measure for each
- Decision: what to build, what to buy, what to leave alone
- Risk: designing for the ideal case and ignoring the exceptions that make up half the work
Weeks 5–10: Build
Implement in thin, shippable slices. Each one runs end-to-end before the next begins, so value lands continuously instead of in one risky launch.
- Outcome: a working slice every one to two weeks, used by real people
- Decision: what gets cut when a slice takes longer than planned
- Risk: building five things halfway instead of one thing completely
Nothing ships that cannot be measured, and nothing is "done" until someone other than the builder can run it.
Weeks 11–12: Hand-off
Document, train, and step back. A transformation that depends on you is a dependency, not a result. The win is a system the team owns and keeps running after the engagement ends.
What you need from leadership in week one
- Access to systems and data, granted in days and not weeks
- One decision-maker who can settle scope questions quickly
- A budget that is clear before the audit, not after it
- Agreement that the team's time for this work is protected
How to tell around week six that it is drifting
- Slices are finished but nobody uses them
- The scope list has grown without anything leaving it
- Owners named in week four are no longer in the room
- Measures exist but nobody looks at them
Any one of these is a signal to stop and reset the plan, not to push harder.
Hand-off checklist
- Every flow has a written description a new colleague could follow
- Owners know how to change, pause, and monitor what they own
- Access and credentials sit with the team, not with you
- There is a clear path for questions after the engagement ends
Hung Mai is a Germany-based freelance consultant for Digital Operations & Transformation, working remotely with international B2B clients.
