- Duration: 60 minutes
- Prerequisites: M03: Architecture Tradeoffs; M06: Radical Transparency
- Primary Metric: Jargon-Free Test
- Frameworks: 3 (Analogous Pitch, Hero’s Journey, 30-Second Elevator Vision)
The QBR where the sponsor went cold
Six months into a multi-year program, the sponsoring CIO has stopped opening the architecture decks. The sponsor is not technically lost: they are narratively lost. The story has become a list of milestones, and they cannot remember why they cared. The Elevator Vision is what re-anchors them in 30 seconds; the Hero’s Journey rewrite is what re-engages them for the next two quarters.
The first executive briefing: a CEO or CFO who was not in the technical reviews
A new executive enters the room. They have 15 minutes. Their team has been telling them you are too deep in the technical detail. The Analogous Pitch is the only tool that lands inside that window. A CSA who tries to brief a CFO using architecture diagrams gets a polite nod and never gets the second meeting.
The internal Microsoft review: pod lead, PMM, or strategic account team
The CSA has 5 minutes to explain why a complex engagement matters strategically. The audience is internal, but the discipline is identical: business outcome first, jargon limited, and a hero (the customer) the audience can root for. CSAs who cannot pass this test internally cannot pass it externally either.
Common Misconceptions About This Module
- "Storytelling is the soft skill of architecture." Storytelling is the hardest measurable skill in this program. The Jargon-Free Test fails objectively when the architect cannot deliver the Vision under 30 seconds with 5 or fewer acronyms. There is nothing soft about a stopwatch.
- "A good analogy is one the architect finds clever." A good analogy is one the customer hears once and can repeat to their CFO without coaching. The test is not whether you like the analogy: it is whether the customer redeploys it. If they do not redeploy it, it failed.
- "The Hero’s Journey is for the architect to feel inspired." No. It is a structural device that forces the customer into the protagonist seat. Architects who use it as motivational scaffolding for their own pitch instinct produce stories where Microsoft is the hero. That story is not just unhelpful: it is corrosive to the advisor relationship.
- "You build the narrative after the technical work is done." The narrative drives the technical work. If you cannot tell the 30-second story before the design begins, the design will not coalesce around an outcome: it will sprawl into features. The Vision is a forcing function for design discipline.
- "Jargon-Free Test means dumbed down." The Jargon-Free Test produces a sharper, more decision-supporting message than a jargon-rich one. Acronyms are mostly a sign that the architect has not finished thinking. Removing them is not simplification; it is precision.
Analogous Pitch
Explain complex technology through a mental model the audience already holds. Azure API Management becomes “an air traffic controller for your application requests.” Zero-trust security becomes “a club that checks ID at every room, not just the front door.” The best analogies are drawn from the customer’s own industry: not from technology, not from sports, not from your last customer. The discipline is a four-step structure: (1) name the source domain, (2) map the mechanic, (3) state the consequence, (4) hand it back to the customer to redeploy. Skipping step 4 is where most analogies fail.
The audience is not loading a new mental model when you analogize: they are extending one they already have. The cognitive cost is near zero, which is exactly why the Analogous Pitch lands inside the 15-minute executive window when a technical brief would not. The handback in step 4 is what makes the analogy travel: when the customer can repeat it to their CFO without you in the room, the message has gone operational.
The first time a non-technical executive enters the room. Whenever you catch yourself explaining a Microsoft acronym with more Microsoft acronyms. As a recovery move when a peer’s analogy from a different industry has confused the audience. Avoid analogies that require the audience to know the source domain: an oil-and-gas customer should not have to learn airline operations to understand your point.
Hero’s Journey
In every transformation story, the customer is the hero. Your role is the guide: Yoda, not Luke; Gandalf, not Frodo. The Hero’s Journey applied to architecture: ordinary world (current state and its pain) → call to adventure (the burning platform or the opportunity) → trials (migration complexity, change management, technical debt) → guide appears (you, with a framework and a track record) → transformation (the future state) → new normal (what the customer can now do that they could not before). Never make yourself or Microsoft the hero of this story.
The pattern is wired into the audience before you arrive. They have been absorbing it for their entire lives in every story they have ever cared about. When you place the customer in the protagonist seat, they recognize the shape of the narrative without conscious effort: and recognize themselves as the agent of change. Stories where Microsoft is the hero produce a polite distance; stories where the customer is the hero produce commitment.
Opening of an executive business review. Re-engagement of a sponsor who has gone cold mid-program. The first 90 seconds of any QBR. Avoid in highly technical implementation reviews: the structure works at the executive layer, not at the engineering layer. Also avoid when the customer is in crisis; the call-to-adventure beat will land as tone-deaf.
30-Second Elevator Vision
A precision discipline: one sentence on the current state, one on the future state, one on the cost of not moving, one on what you are proposing. Under 30 seconds. Under 5 acronyms. Opens with business impact, not technical description. This is the hardest skill in the program to master and the one with the highest executive leverage. If you cannot deliver this from memory without notes, you do not yet understand your own recommendation well enough to be trusted with it.
The 30-second constraint is a forcing function on the architect, not a courtesy to the executive. Most stalled engagements are stalled because the architect has not yet found the through-line; the Vision exposes that gap to the architect before it embarrasses them in front of a sponsor. A Vision that cannot be delivered in 30 seconds is a recommendation that has not finished baking.
Any moment a senior executive enters or re-enters the room. Open the QBR with it. Open the steering committee with it. Use it as your private internal test before any major design review: if you cannot deliver the Vision cleanly, the design is not ready to present. Do not use it as the closing slide; the Vision is an opening move, not a wrap-up.
From a stalled $9M modernization to a board-approved transformation in one quarter: three narrative moves stacked end to end
Situation
National freight forwarder. CIO Patricia Donovan inherited a $9M Azure modernization program from a predecessor. The program had been running for 18 months. The technical work was credible; the executive sponsorship had quietly evaporated. The CFO Steven Yu had stopped attending steering committees. Patricia’s board had a single question for the next review: "Why are we still spending on this?" The architect was asked to lead the next QBR: not to defend the program, but to decide whether it should continue.
Move 1: Diagnose the gap as narrative, not technical
The architect spent two days in discovery and concluded that nothing technical had broken. Every milestone was on track. The gap was that no one in the room could answer the question "what is this for?" in plain language. Patricia could repeat the program objectives, but the language was acronym-heavy and feature-listed. Steven could not. That was the diagnosis: this was a Module 07 problem, not a Module 03 problem.
Move 2: Open the QBR with a 30-Second Elevator Vision
Architect’s opening, on the whiteboard with no slide deck visible: "Today, your dispatchers can route trucks against last week’s data. By Q3 next year, they will route against the actual road conditions in front of the truck. The cost of not moving is that your largest customer’s on-time-delivery commitments will fall below their contractual floor in 14 months. We are proposing to make Westmark the first freight forwarder in your tier with real-time route optimization." Four sentences. 28 seconds. Two acronyms. Steven leaned forward. The room was back.
Move 3: Reframe with an Analogous Pitch the customer could redeploy
When the CFO asked how the integration architecture worked, the architect said: "Think of your current state as having a logistics hub for trucks, but no logistics hub for the data the trucks generate. We’re building the same kind of hub for data: the dispatch model you already use, applied to the system you don’t yet have." Steven repeated that sentence to his board the following Tuesday. Verbatim. The architect was not in the room. That is the redeployment test, passed.
Move 4: Restage the program as a Hero’s Journey with Westmark as protagonist
The architect rewrote the program narrative for the board: "Westmark’s ordinary world was a routing system that worked when freight volumes were predictable. The call to adventure was the 2023 disruption that broke that predictability. The trial is rebuilding the route logic without breaking your dispatch operation. We are the guide. The new normal is dispatchers who route the way Patricia’s team has always wanted to route: against reality, not against last week." Microsoft is the guide. Westmark is the hero. That was the structural change.
Move 5: Hold the line on the Vision through the next three QBRs
The discipline that produced the durable change was not the first delivery: it was that the architect opened every subsequent steering committee with the same Elevator Vision. Same four sentences. Same 28 seconds. The repetition is what made the message survive sponsor turnover six months later when Steven moved to a new role.
Outcome
The board approved the remaining program scope and added a $3.4M follow-on phase before the QBR ended. Steven, three weeks before transitioning to a new company, named the architect personally to his successor as the only vendor relationship he wanted preserved. Twelve months later the program landed on schedule. Patricia’s phrase in the post-go-live executive briefing: "This was the first program I’ve sponsored where the story didn’t change every quarter." That sentence is the Jargon-Free Test passed at the highest level: the story was simple enough to remain stable across 14 months of executive churn.
An Analogous Pitch sourced from the customer’s own industry: generators vs. the power grid
Situation
Mid-market commercial insurer. The architect was explaining the move from on-premises capacity planning to elastic cloud capacity to the CFO Daniel Reeves. The previous architect had used a generic data center analogy. Daniel had nodded politely and moved on. The architect needed an analogy that came from inside Daniel’s world: not from technology.
Move
Architect, in the next session: "Today your insurance operation is like a hospital that runs on its own backup generators: you size them for the worst hurricane day, you fuel them year-round, and they sit idle 95% of the time. We’re proposing you connect to the grid. Your peak capacity is unlimited, you only pay for what you draw, and the generator on the roof becomes a backup, not a way of life. The pricing model is the meter, not the fuel truck." Four-step structure: source domain (hospital generators), mechanic (idle 95%), consequence (unlimited peak, pay-as-you-go), handback (the meter, not the fuel truck).
Outcome
Daniel used the “meter, not the fuel truck” phrase three times in the following month: with his CEO, with the board treasurer, and in the quarterly all-hands. The architect was not in any of those rooms. The Analogous Pitch had become a self-propagating message, which is the highest-leverage outcome the framework can produce. The cloud capacity SOW was approved without further executive escalation.
Recovery from the wrong analogy: when a sports metaphor misfired in a healthcare room
Situation
Regional hospital network. The architect, in the first executive briefing, opened with a basketball analogy: “think of zero-trust like a defense that picks up its mark at full court instead of waiting at the basket.” The CIO Anita Shah, who did not follow basketball, mentally checked out for the next twelve minutes. The architect had violated the customer-domain rule.
Move
Two days later, the architect requested a 20-minute follow-up and opened: "I want to redo something from Tuesday. Zero-trust is closer to your medication-administration protocol than it is to anything else: you don’t check the patient’s wristband once at admission, you check it at every dose. Same identity, same chart, same nurse, doesn’t matter: the wristband is scanned every time. That’s zero-trust. We’re asking your network to behave the way your med-pass already does."
Outcome
Anita repeated the wristband analogy in the very next sentence: the cleanest possible signal that the message had landed and was redeployable. The architect’s recovery move did more for the relationship than the original delivery would have. Anita raised the architect’s recovery in a Microsoft executive briefing six months later as the moment she decided the engagement was worth her personal sponsorship.
A Hero’s Journey rewrite that re-engaged a sponsor 14 months into a stalled program
Situation
Outdoor retail chain. The COO Jen Marquez had stopped opening the program decks. The deck told a feature story: 14 milestones across three workstreams, each a Microsoft service in a deployment plan. Jen could not remember why she had funded the program; she could not articulate it to her CEO; the program was on the chopping block at the next budget cycle.
Move
Architect rewrote the opening slide as a single Hero’s Journey paragraph: "Northpath sold gear to people who showed up at your stores. The world changed and they started buying online from competitors who could tell them whether the boot was in stock 40 miles away. Northpath’s call to adventure was that shift. The trial is having one inventory truth across 217 stores and an e-commerce site that has never agreed with each other. Microsoft is the guide. Northpath’s new normal is being the brand that knows where every boot is in real time: the brand the next outdoor generation defaults to." The 14-milestone plan became context, not foreground.
Outcome
Jen forwarded the rewritten paragraph to her CEO without changing a word and asked for it to be added to the board pre-read. The program was protected in the budget cycle. More important: every steering committee for the next four months opened with that paragraph. The narrative had become the through-line. The architect’s lesson: when a sponsor goes cold, do not add detail: subtract it, and rebuild the protagonist.
Co-authoring the Elevator Vision with the sponsor in real time
Situation
Mid-market mutual insurer. CFO Margaret Liu, a year into a digital transformation, asked the architect at the end of a steering committee: "How would you describe what we’re building: if you had 30 seconds and someone who didn’t know what an API is?" Margaret was not testing the architect; she was asking because she had to brief her board the next morning and could not get her own version under 90 seconds.
Move
Architect, on the whiteboard: "Cardinal’s policy systems were built for a world where members called you. They now expect you to know them before they call. Without this program, your retention curves bend the wrong way over the next four years. We’re building the bridge between the policy data you already own and the conversations your members already expect." Then the move that mattered: the architect handed the marker to Margaret and said "now you say it back, in your words. We will iterate it together until it sounds like you." They iterated four times in 12 minutes.
Outcome
Margaret’s board version was tighter than the architect’s original. She delivered it the next morning in 26 seconds. The architect’s lesson: the Elevator Vision is most powerful when the sponsor takes ownership of the language. The architect’s job is not to deliver a perfect Vision: it is to leave behind one the sponsor will deliver themselves when the architect is not in the room.
When the Vision exposed a recommendation that should not have been made
Situation
The architect was preparing a recommendation for an industrial-IoT platform deployment. Internal review only: one week before the customer presentation. The architect tried to draft the 30-Second Elevator Vision and could not get past sentence two. The current state was clear; the future state was generic; the cost of not moving was something the architect could not quantify; the recommendation was a feature list dressed as a vision.
Move
Rather than push through, the architect treated the failed Vision as the diagnosis. "If I cannot say it in four sentences, I have not finished thinking." The architect halted the presentation prep, returned to the customer for two more discovery sessions, and discovered the actual business outcome was operator-safety-related: not the productivity story the original recommendation had been built around. The recommendation was rebuilt. The new Vision came in at 24 seconds.
Outcome
The customer approved the rebuilt recommendation. More importantly, the architect avoided presenting a feature-list pitch that would have produced a polite stall and a quiet cancellation. The Elevator Vision had served as a private quality gate: the most valuable use of the framework, and the one that never appears in a customer-facing artifact. Architects who use the Vision only for delivery miss its highest-leverage use, which is internal.
Hero’s Journey Mapping
Take a real or fictional cloud migration story and map each stage of the Hero’s Journey to specific customer milestones. Then write the verbal version you would use to open an executive business review.
- Choose a cloud migration story (real, sanitized, or fictional). Write one sentence for each Hero’s Journey stage: ordinary world, call to adventure, trials, guide appears, transformation, new normal.
- Check your sentences: is the customer the hero in every sentence? Is the vendor or the technology the hero in any of them? If so, rewrite.
- Write the 2-minute verbal version you would use to open an executive business review. The customer should recognize themselves in the story by sentence two. You should appear as a supporting character, not the protagonist.
- Deliver it to a peer. Ask: did you feel like the hero of that story, or like someone being pitched to?
| Stage | One sentence |
|---|---|
| Ordinary world | Brookline Outfitters built a $400M outdoor brand on the assumption that their stores would always be the buying channel. |
| Call to adventure | In 2024, online sessions outpaced store visits 4-to-1: and 38% of those online customers abandoned because the inventory data was wrong. |
| Trials | 217 stores running on three legacy POS systems, none of which agreed with the e-commerce database in real time, and a peak-season margin that could not absorb the cost of a bad migration. |
| Guide appears | A reference architecture proven across four other tier-2 outdoor retailers, paired with a phased rollout that protected the November freeze window. |
| Transformation | One inventory truth across stores, web, and the mobile app: updated in the same minute the customer asks the question. |
| New normal | Brookline becomes the brand that always knows where the boot is, in the size you wear, before you ask: the brand the next outdoor generation defaults to. |
What to notice: Microsoft is mentioned exactly zero times in the six sentences. Brookline is the agent in every clause. The technology is the means, not the protagonist. A peer test: "did you feel like the hero of that story?": lands clean only when the architect has actively resisted the instinct to put the platform in the protagonist seat.
Common failure: "Microsoft helps Brookline modernize." That sentence makes Microsoft the hero in 4 words. Rewrite: "Brookline modernizes with a guide whose reference architecture has already worked four times." Same fact, different protagonist.
Analogous Pitch Workshop
Build analogies that work without technical context. The test: if someone from the customer’s industry heard this analogy, would they understand it immediately and would they be able to repeat it?
- For each of the following technologies, write two analogies: one using a sports metaphor, one using a metaphor from a specific industry (healthcare, manufacturing, finance: pick one). Apply the four-step structure: source domain → mechanic → consequence → handback.
- Azure API Management
- Microsoft Entra ID (identity platform)
- Azure Service Bus
- Filter rule: the analogy cannot use any of these words: cloud, server, network, authentication, failover, or any technology brand name.
- Present your best analogy for each technology to a peer. Ask: could a CFO in that industry use this analogy to explain the technology to their board? Would they want to?
- Identify the one analogy that failed. What made it fail? Was it using the wrong source domain, or was the technology itself not well understood?
Failing version (technology echoes): "Service Bus is a message broker that decouples your producers from your consumers, allowing asynchronous processing and durable delivery." → The CFO hears five technical nouns in fifteen seconds. The analogy is technology explained with technology, which is not an analogy at all.
Passing version (four-step, customer-domain):
- Source domain: "Think of your kitchen during a Saturday rush. The expediter doesn’t hand each ticket to a specific cook: tickets go on the rail, and whichever cook is free pulls the next one."
- Mechanic: "That rail is doing two things: it’s holding the order so it doesn’t get lost if a cook steps away, and it’s decoupling the speed of the dining room from the speed of the kitchen."
- Consequence: "On a quiet Tuesday the rail is empty and you don’t care it exists. On Mother’s Day with a 90-minute wait, that rail is the only thing keeping the kitchen from collapsing."
- Handback: "Service Bus is the kitchen ticket rail for your applications. When you tell your operators ‘the system held up under peak,’ what you mean is the rail held up. Now: how would you explain that to your COO?"
What to notice: the handback in step 4 is non-optional. It is the move that confirms the analogy traveled. If the CFO cannot redeploy it in their own words, the analogy did not land: it was just well-received.
Common failure: stopping after step 3. The architect feels good. The analogy never gets used by the customer. The architect is confused six weeks later why the message did not propagate.
Elevator Vision Drill
Write and memorize your 30-Second Elevator Vision for a specific customer scenario. The time constraint and the no-notes constraint are both mandatory.
- Choose a specific cloud migration scenario (real or from the module folder). Write your Elevator Vision using the four-sentence structure: current state, future state, cost of not moving, what you propose.
- Count your acronyms. If you have more than 5, rewrite. If any sentence opens with a technology name instead of a business outcome, rewrite.
- Time yourself reading it aloud. If it exceeds 30 seconds, cut. Every word that is not load-bearing is a word that dilutes the impact.
- Put the paper down. Deliver it from memory. Do this three times in a row, with a 60-second gap between each delivery.
- On the third delivery: have a peer time you and count your acronyms. Report the results.
| Sentence | Architect’s draft | Margaret’s rewrite (delivered) |
|---|---|---|
| 1. Current state | Cardinal’s policy administration platform was built for an era when members called us. | Today our members expect us to know them before they pick up the phone: and we don’t. |
| 2. Future state | By Q3 we will have unified the policy data with the member-engagement platform. | By Q3 every conversation a member has with Cardinal starts with us already knowing what they need. |
| 3. Cost of not moving | Without this work, retention curves degrade. | If we don’t do this, we lose the next generation of members to carriers who already do. |
| 4. What we propose | We’re proposing an integration architecture connecting policy systems to the engagement layer. | We’re building the bridge between the data we already own and the conversations our members already expect. |
Stopwatch: Margaret’s version delivered in 26 seconds. Three acronyms became zero. Every sentence opens with the customer or with a member outcome: never with a technology noun.
What to notice: the architect’s draft was technically accurate and would have failed the Jargon-Free Test. Margaret’s version is what got delivered to her board because it was hers. The architect’s job was not to write the perfect Vision: it was to leave behind a Vision the sponsor would carry. The handover from architect-language to sponsor-language is the move that produces durable executive sponsorship.
Common drill failure: writing the Vision and reading it from notes during the drill. The drill only works under the no-notes constraint. The third memorized delivery is what reveals which sentences are load-bearing and which are filler.
The Jargon-Free Test for this module is narrative: you pass when your story moves a non-technical executive to action: not just to agreement. Rate yourself on delivered performance, not on written exercises.
Narrative self-assessment runs hot. Architects who read and write fluently tend to over-rate their own delivery. The frameworks are testable on stopwatch and on redeployment: rate against those, not against how the room felt.
Mistake 1: Confusing warmth in the room with the Jargon-Free Test passed.
A peer hugging your delivery is not the same as a CFO redeploying your analogy. The Jargon-Free Test is mechanical: count acronyms, time the Vision, watch the customer’s next sentence. If the customer’s next sentence does not include your language, the test was not passed: even if everyone smiled. Rate Developing if you do not have a captured instance of customer redeployment within the same meeting.
Mistake 2: Skipping step 4 of the Analogous Pitch and calling it a Ready.
The handback is non-optional. Most architects deliver steps 1–3 cleanly, get a polite acknowledgment, and conclude the analogy worked. The framework defines “worked” as: the customer used the analogy themselves in the next minute, or in the next room they walked into. If you cannot point to that, the move was a presentation, not a pitch. Rate Developing.
Mistake 3: Counting an Elevator Vision read from notes as a Ready.
The framework is named “30-Second Elevator Vision” for a reason: the elevator does not let you bring slides. The skill is the from-memory delivery under time pressure. Reading from a card is not the skill being tested: it is the prep for the skill. Rate Ready only if a peer has timed your third memorized delivery and confirmed both the duration and the acronym count. Anything less is Developing.
Mistake 4: Vision with a soft outcome.
“We will modernize their platform” is not a Vision: it is a deliverable. The Vision sentence on future state must describe a specific, externally visible business outcome (“dispatchers route against real road conditions,” “every member conversation starts with us already knowing them”). If your future-state sentence describes work-product, not customer-experience, the Vision has not been finished. Rate Developing until the sentence describes the world the customer’s customer experiences.
The when-in-doubt rule: if the most senior person in the room cannot repeat your through-line back to you in their words, you have not passed Module 07: regardless of how the meeting felt. Narrative competence is measured by whether the message survives the architect leaving the room, not by whether it was well-received while the architect was in it.