Not every transformation needs a 90-day plan immediately. Most fail earlier — because the mandate, value logic, decision rights, and execution constraints are still implicit. Mopud starts where drift actually begins: readiness, then mid-transformation health, then 90-day execution design when you’re ready to lock the operating model.
Transformation Readiness
Before you “start executing”, Mopud tests whether the transformation is structurally ready — problem clarity, value logic, stakeholder alignment, and decision ownership.
Mid-Transformation Health Check
When everything “looks fine” but feels off — Mopud exposes drift signals across governance, decision latency, unresolved dependencies, adoption reality, and reporting truth.
90-Day Execution Plan
When readiness is strong enough (or the risk is understood), Mopud turns intent into an execution boundary: what gets done, in what order, with which decisions locked early.
UC3 — 90-day execution plan
How Mopud produces the 90-day plan (Step 0 → Step 3)
These are the same execution-plan steps you already have — presented on a lighter surface so it reads as a framework, not a long black article.
Execution baseline for transformation
Bounded inputs → fixed baseline (no hidden assumptions)
You answer a small set of uncomfortable but bounded questions about why this transformation exists, what must not break, and where resistance is likely.
You provide
Mopud generates
Most users realise their “problem statement” is doing political work — not analytical work.
90-day intent
Strategic intent in the first 90 days — with explicit trade-offs
Intent is converted into a clear narrative with explicit trade-offs — the version that can survive senior scrutiny.
You provide
Mopud generates
This is often where “alignment” starts to crack — productively.
Execution architecture
Execution design under pressure — decision rights and escalation clarity
You define how execution will behave under pressure — not how it should behave on slides.
You provide
Mopud generates
Most transformations fail here because execution architecture is assumed rather than designed.
90-day design
90-day transformation plan — sequencing, triggers, and “must not break”
Clarity is translated into a focused 90-day plan — with sequencing, risks, and explicit “must not break” elements.
Mopud generates
Reality check
The goal is a plan that survives pressure — not a plan that looks good.
Use this whenever you revise earlier answers after seeing outputs.
