Tool

Your first 90 days, dated.

Pick a start date and whether the environment is prepared. The plan dates every week and gate, and says whether a live release is realistic.

Environment

WeekStartsPhaseOutput and decision
Week 1FrameObserve the work
Current workflow, eligible users, task volumes, baseline sample, exceptions and the accountable owner.
Week 2FrameResolve the constraints
Sources, definitions, access path and dependency owners. Open model risk, third-party, privacy and security reviews now.
Week 3FrameAgree the target
Architecture, measures, acceptance criteria, evaluation plan, operating owner and the plan. Frame gate.
Week 4ProveEstablish the dependencies
Scoped access, owned product contracts, approved definitions and the identity used for each dependency.
Week 5ProveConnect the request
Read interfaces, retrieval where needed, typed tools and a correlated trace.
Week 6ProveEvaluate
Representative, refusal, hostile and broken-dependency cases on the real path.
Week 7ProvePrice the outcome
Cost per completed useful task, review effort included.
Week 8ProveDecide
Prove decision: proceed, reshape or stop, with reasons.
Week 9BuildOwned products and interfaces
Contracts versioned, release pipeline in place.
Week 10BuildControls and monitoring
Enforcement, limits, alerts and the switch-off route.
Week 11BuildSupport and recovery
Runbook, incident route, recovery test.
Week 12BuildReadiness review
Release evidence for the actual state; in an unprepared environment this is the readiness review.
Week 13ReviewDay-90 decision
Expand, continue, reshape or stop, with funding, owners and the next review date.

Companion to The 90-Day First Governed Capability. Everything you enter stays in this browser.

Next step

Plan the first 90 days together.

Frame takes two to three weeks and starts with the people who do the work.