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.
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.
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.
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.
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.
Hung Mai is a Germany-based freelance consultant for Digital Operations & Transformation, working remotely with international B2B clients.
