Capstone — A 90-Day DMBOK Adoption Plan

Capstone — A 90-Day DMBOK Adoption Plan

One domain, three KAs, four measurable deliverables — the smallest plan that's still real.

Why it matters

Big-bang DMBOK rollouts almost always die. The pattern that works: pick one high-value domain, ship a thin slice across three KAs, publish the number, then expand. This lesson is the template.

Going deeper

The capstone plan template, in one page:

Domain: <one>

Sponsor: <exec name> — Accountable

Outcome by day 90:

• Governance — domain charter signed, owner + steward + custodian named, exception workflow live.
• Metadata — top 20 datasets in the catalog with owner + business definition + freshness signal.
• Quality — six-dimension scorecard for the top 5 datasets, alert routing live, one closed loop demonstrated.

Number to publish: <e.g. analyst time-to-find for canonical X reduced from <24h to <10min>

Day-90 review: demo + ask for the next domain's funding.

Three KAs, not eleven. One domain, not the enterprise. One number, not a slide deck. Anything bigger dies in committee.

A 90-day adoption plan is building a model railway, not a national network.

You'd never start a national rail network by laying track simultaneously in every city. You'd build a working scale model in one room, prove it runs, demonstrate the signalling, then propose the next section. The proof is the model — not the PowerPoint of a future country.

Same with DMBOK: ship one domain, three KAs, a measurable scoreboard, a demo. Funding for the next domain becomes a formality; without the demo it becomes a philosophical debate.