cMAP Cloud Strategy Executive Briefing
Narration transcript

Slide 1 — We know the road
Four enterprise programs already walked the road to Department of Defense cloud at scale. The swim lanes, the gates, the interdependencies — that ground is known. What a mission organization needs from us is not discovery. It is focus.

Slide 2 — Three questions
Every engagement answers three questions. What can you leverage — the capabilities already trustworthy enough to carry forward. What has to be established before the rest can move. And what to sequence first, so the program stays consumable rather than overwhelming.

Slide 3 — One researched map
Underneath all of it sits one researched map: transformation, production operations, and authorization sequencing, anchored in Department standards and the programs that proved them. It does not change from client to client. That is exactly what makes it trustworthy.

Slide 4 — Three overlays
What changes is what we draw on top of it. Where you are now, derived from your own evidence. The transformation workstreams that move you — the work, its sequence, and who does it at what speed. And day-two operations: the shared and mission services that keep the result running, and whose they are.

Slide 5 — Four ways to get there
A capability you do not have yet can be built, contracted, acquired as a service, or joined — inherited as a tenant of a program that already runs it. Joining trades years of building for onboarding, against a consumption premium and the obligations of tenancy. We put all four on one screen, with what you would still own the morning after.

Slide 6 — The Phase Zero promise
And we hold to one promise. We describe where you stand today, on the estate you actually have. Cloud-native capabilities with no on-premise equivalent have no current position to describe. They are the scope of your program, and the starting point for the work.

Slide 7 — Day two comes first
Migration is an event. Operating is a posture. The cloud is a different operating model in kind, not in degree — so before any workload moves, one question needs a name attached to it. Who owns the incident at zero three hundred?

Slide 8 — The day-two operating concept
The piece most plans skip is the day-two operating concept: who runs what, once it is running. Shared services can be yours, acquired, or inherited from a larger program you join — and each of those puts the accountability in a different place. Mission services sit on top of them, inside an authorization boundary somebody has to own. Naming that early is what keeps the second year from surprising you.

Slide 9 — Six weeks, light on your calendar
Six focused weeks, and light on your calendar. Four named points of contact. One or two interviews per owner. Sponsor reviews in weeks one, five, and six. Your people provide context and access — not a new program to staff.

Slide 10 — A I readiness, inside the strategy
A I readiness runs through those same service domains, in three lenses: enable, govern, and sustain. It is awareness, not certification. A posture inside the cloud strategy — never a separate report.

Slide 11 — What Phase Zero scopes
Phase Zero is scoped with the foresight to feed the work that follows. Application profiling, against the six migration patterns. Zero trust and R M F: what control evidence you have, and what is missing. The authorization path, and where an interim authority to test could open a bounded lane. And optionally, an A I capture session on one bounded opportunity. Phase Zero scopes and sequences all four. It does not perform them — that work belongs to the phase that follows, run by the teams you choose.

Slide 12 — A bounded next step
The next step is deliberately bounded: a focused scoping conversation, and a fixed-scope estimate after it. Evidence informs; named individuals with authority decide. The engagement establishes the starting point — your Authorizing Official owns every decision that follows.