Memo Office of the CVP, Microsoft Copilot Studio + Power Platform

Ryan's story. Modular. At scale.

Without ever lowering the bar.

Begin reading
00 The Question, the Moonshot

How would you frame the AI Moonshot for the exec office in terms of the specific ambition + constraint recipe we talk about with customers so often?

Ryan's story.
Modular. At scale.

Without ever lowering the bar.

JFK in 1962 gave the cleanest ambition-and-constraint statement ever delivered. Specific outcome. Hard deadline. No hedge. We need the same shape.

Ambition

Any of the 1,382 people in Ryan's org who carry a piece of his narrative can deliver a Ryan-quality story in hours, not weeks. Ryan himself ships keynotes in a fraction of the current cycle.

Constraint

The quality bar never drops. If Ryan wouldn't put it on stage, it doesn't ship. Full stop.

01 The Problem

Every event starts from zero.

Ryan briefs. We script. We rebuild. Slides decay between events. The team can't reliably carry his voice. Others reinvent the wheel or freelance their own decks.

That's the internal cost. The external cost is worse. A single Fortune 1000 CIO can hear our story from a dozen mouths in a dozen versions. Monday's pitch sounds nothing like Thursday's. Coherence is leaking out the door, not just inside the building. And the surface area is getting bigger: the CAP business is now the Copilot and Agents Platform, housing Microsoft Copilot Studio, Power Platform, and Dynamics 365.

Story is treated like a project. It should be a program.

Fig. 01 Today vs. Tomorrow — value per event
QUALITY · REUSE EC One EPPC Ignite AMA M365 Con MVP Summit Build resets to ~zero between events library gets smarter with every event Today — bespoke each time Tomorrow — each event compounds
Every event spike is wasted effort if the next event can't reuse it.
A note · two weeks ago

This isn't a new observation. At the May All Hands, Steve was asked about exactly this pattern — fragmented work, declining coherence, everyone vibing their own thing while the quality bar quietly drops. He acknowledged it in front of the org.

This isn't the first time I've heard this concern. Speed can fragment thinking. If everyone is vibing independently without shared critique, systems thinking, or collaboration, coherence suffers.

— Steve Gustavson · May All Hands Q&A

What's missing is structure.
StoryOps is the structural answer for narrative.

02 The Stakes

Why this can't wait.

1,382
people now report up to Ryan. Story load doubled.
20+
keynotes per year, 45 to 60 minutes each, currently bespoke every time.
#1
Copilot Studio leads the platform play. Narrative drift is a strategic risk.
Ryan's time
is the binding constraint. Every hour of rework is an hour not spent on the bets that matter.
03 The Solution

Treat story as a program.

Build it once. Compose it forever. Improve it continuously.

A program means a loop. We build the engine. The field uses it. Feedback returns. The engine sharpens. Run that long enough and the program runs itself.

Fig. 06 The self-sustaining loop
feedback arms the field 01 Make we build the engine 02 Deliver field ships · customers respond
Two halves. One loop. The engine arms the field; the field teaches the engine. We own the engine. We become our own customer success story.

Six moves get us there. Each one is a thing you can fund, staff, and measure. None of them require a re-org.

03.1

Strategy

Story as program, not artifact. Decouple what stays from what moves.

Foundation

Ryan's canonical narrative, the System of Work POV, the Copilot Studio + Power Platform arc.

Cadence Quarterly

Modules

Product, Proof, Customer, Demo, POV. Composable units that snap together for any event shape.

Cadence Weekly

Custom

Per-event tailoring, audience hooks, EC One leave-behinds. The last 10% that earns the standing ovation.

Cadence Per event

Every event becomes an act of composition, not creation.

Fig. 02 The Story Stack
Foundation canonical narrative · POV · arc QUARTERLY Modules product · proof · customer · demo · POV WEEKLY Custom per-event tailoring · leave-behinds PER EVENT composition
Three layers, three different velocities. The bottom is stable. The top is fast. The middle does the real work.
03.2

Audiences

Design for who's on the receiving end. Four roles, anchored to Microsoft's own taxonomy. Same story, same arc, tuned to the job each one walked in trying to do.

01

Leadership

Execs · CIOs · business unit owners

Job to be done

"Help me decide whether to bet on this — and give me the story I'll repeat upward."

Needs
Cost clarity. Risk visibility. Strategic alignment.
Wants
A narrative they can defend in their own room.
Expects
Business impact, not feature theater.
02

IT admin

Platform admins · security · governance leads

Job to be done

"Help me let people build, without losing the floor under us."

Needs
Governance, observability, cost containment.
Wants
Guardrails on day one. One control plane.
Expects
To say yes without becoming the bottleneck.
03

Maker

Citizen developers · BAs · Power Platform builders

Job to be done

"Help me turn a business idea into a working agent before the moment passes."

Needs
Templates that work. Evals that prove quality.
Wants
Speed from concept to live, with confidence intact.
Expects
Low-code to mean high-quality, not low-bar.
04

Developer

Pro-code engineers · solution architects

Job to be done

"Help me ship production-grade agents that extend the stack we already run."

Needs
Real architecture. Runtime story. Enterprise readiness.
Wants
Deep hooks. APIs, SDKs, extension points.
Expects
The platform not to box them in.
Every role walks away with
  • Log line
  • Elevator pitch
  • Slide modules
  • Demo
  • Talking points
  • Leave-behind

All of it lives in one library. Carriers pull what they need, tuned to the room they're standing in. The freelancing stops.

Done right, we become our own customer success story. The pitch becomes the proof.

03.3

Program

StoryOps is the operating system for narrative across the office of the CVP. One library. One voice. Tiered access. Clear ownership. To work, it has to sit close to product reality: design, product management, and the creative systems shaping how CAP shows up in the world.

Story Architect

Lance

Owns the stack, the standards, and Ryan's keynotes while staying integrated with product design, PM, and the field signals that keep the story true.

Product + Creative Bridge

Lance · Design · PM · Creative Visual Studio

Connects product truth to the creative system: motion design, iconography, branding, visual language, and the narratives spanning Copilot Studio, Power Platform, Dynamics 365, and the broader Copilot and Agents Platform.

Module Owners

Named per slice

Own freshness of their slice — product, proof, customer, demo, POV.

Approvers

Ryan

Sign off on Foundation, and on any module Ryan will personally deliver.

Carriers

The 1,382

Pull from the library by tier, with guardrails. They can self-serve without going off-message.

Fig. 03 Concentric ownership — Ryan at the center
CARRIERS · 1,382 MODULE OWNERS ARCHITECT · APPROVERS RYAN the voice
The closer to Ryan, the higher the standard. The farther out, the more self-serve. Every ring touches the next.
03.4

Guidelines

Three pillars. Every deck is measured against them.

V

Voice

How Ryan tells a story. The opening move. The pivot. The close. Catalog them, name them, teach them.

V

Visual

Density, motion, typography, iconography, and brand behavior. The rules that make a slide feel like Ryan made it, even when he didn't.

V

Velocity

When to self-serve. When to escalate. When to wait for the Architect. The decision tree that protects the bar.

03.5

Tooling

Built on the platform we sell. Designed for thoughtful use, not token volume. We dogfood what we're asking customers to buy.

Copilot Studio

Story Brief Agent

Reads the event request. Pulls relevant modules. Drafts a script outline. Surfaces customer stories that match the audience.

Power Apps · Power Pages

Intake

One door for every story request. Auto-routes by tier. No more DMs, no more side decks, no more forgotten asks.

SharePoint · PPT · metadata

Module Library

Tagged, searchable, versioned. Single source. The library that lets the agent actually find what it needs.

Power Pages

Leave-Behind Builder

EC One outputs become custom micro-sites with a video message from Ryan. Not a PDF the customer forwards once and forgets.

Nothing ships into a void. Every event teaches the next one.

Fig. 04 The closed loop — intake to telemetry
Intake Agent Designer Ship Telemetry feeds the library
What ships gets measured. What gets measured feeds back into the library. The library is alive.
03.6

Rollout & Governance

Thirty days. Five sprints. Listen first, then build. Nursery protected from the franchise.

  1. 01Wk 1

    Listen

    Stakeholder interviews with Ryan, his leadership team, and our key partners in marketing. Twelve to fifteen conversations. The standard discovery move before any project that matters. Pain catalog out the other end. Voice patterns documented before we touch a slide.

  2. 02Wk 1–2

    Audit

    Dedicated time on every active asset across the org. What's working. What's drifting. What's worth salvaging into Modules. The piecemeal review I've been doing for months finally gets a real lens — and a deadline.

  3. 03Wk 2–3

    Foundation

    Lock the canonical narrative. Lock the visual standards. Ryan signs off. The bar becomes something people can point at instead of guess at. Nothing ships outside the keynote tier until this is in place.

  4. 04Wk 3–4

    Compose

    Module library seeded with first-pass Product, Proof, Customer, Demo, POV. Intake door opens. Tier 2 events move to composition where timing and readiness allow.

  5. 05Wk 4+

    Carriers + Agent

    First Carriers onboard to self-serve with guardrails. Story Brief Agent dev kicks off in Copilot Studio — we start dogfooding the platform we sell. These two continue past day 30. Month 1 closes with proof, not promise.

Governance

  • Foundation changes require Ryan sign-off.
  • Module changes require Module Owner sign-off, audited weekly.
  • Self-serve access expands by tier.
  • Quarterly story review with Ryan. The bar gets recalibrated.
04 Expected Results

What changes when this ships.

Same three layers as today. Different proportions. Today every event starts at the top and rebuilds down. Tomorrow it starts at the bottom and composes up.

Fig. 05 Inversion — the 70 / 20 / 10 flip
TODAY custom-first · library starves 70% Custom 20% Modules 10% Foundation TOMORROW foundation-first · library compounds 10% Custom 20% Modules 70% Foundation Foundation Modules Custom
Most decks today are 70% rebuilt. The fix isn't more output. It's a different ratio.
1day
to first draft. Down from five to seven.
60%+
reuse rate on Tier 2 events. Up from under twenty.
1 story.
Every audience.
Coherence stops leaking out the door. 1,382 carriers, four roles, one Microsoft.
Hours back
to Ryan.
For the bets that matter.
05 Closing

StoryOps is how the office of the CVP turns story into a program.

Build it once. Compose it forever. Improve it continuously.

Lance Garcia
Story Architect · Office of the CVP
Microsoft Copilot Studio + Power Platform
Back to top