Strategic Architect Framework: Microsoft CSA Training Program
Module 06: Radical Transparency & The Trusted Advisor
Facilitator Deck Outline: ~60 minutes
Deck purpose: Build the courage and skill to deliver difficult information proactively, and the framework to do it in a way that strengthens rather than damages the customer relationship.
Opening (Slides 1–3)
01Title
M06: Radical Transparency: The Trusted Advisor Posture
Module title and session framing
Core question: "What is the hardest thing you haven't told your customer, and why haven't you told them?"
02Opening Scenario
The Migration That Was Going to Slip
Three weeks from go-live: architect sees an integration complexity the implementation team has not flagged
VP of Operations expects on-time delivery; account team says "don't complicate things"
The architect can stay quiet and hope it resolves or deliver the difficult news Tuesday morning, with options, before there are no options left
Discussion: what does the Trusted Advisor do?
This is a values question before it is a skills question. Establish the values position first: the Trusted Advisor delivers difficult information early, because that is what being trustworthy means.
03Concept
The Credibility Paradox
Withholding difficult information protects the short-term relationship and destroys the long-term one
Delivering difficult information costs the short-term relationship and builds the long-term one
The architect who stays quiet to protect the deal loses the deal: six months later, when the problem surfaces, along with the fact that they knew
The architect who delivers the difficult news with options earns a customer for life because no one else told them the truth
Timeline diagram: two paths from "difficult information exists." Path A (stay quiet): deal closes → problem surfaces → trust collapses. Path B (deliver): relationship tension → options explored → problem solved → trust deepens.
Credibility: The customer believes what you say is accurate
Reliability: The customer believes you will do what you say
Intimacy: The customer believes you understand their specific context, not just the generic category
Self-Orientation: The degree to which the customer believes your recommendations serve their interest vs. yours. Self-Orientation is the denominator: it can destroy all the numerator value
Formula card: (C + R + I) ÷ S. Annotate: "Most architects score high on C, moderate on R and I, and damage their score on S without knowing it."
05Framework
Framework 2: The Anti-Pitch
The Anti-Pitch is the moment a Trusted Advisor tells a customer something that reduces the immediate sale to protect the customer's long-term interest
Four Anti-Pitch scenarios: architecture flaw before sign-off; project that should stop; competitor has a better product for this use case; budget should be spent differently
Delivering an Anti-Pitch without a path forward is a problem deposit. Delivering it with options is trusted advisory.
Structure: (1) Acknowledge what the customer has built / decided, (2) Name the concern clearly, (3) Provide a path forward
06Framework
Framework 3: The Red/Amber/Green Update Protocol
Status updates are the most common opportunity to practice radical transparency, and the most commonly missed
Green = on track; Amber = risk identified, mitigation in progress; Red = cannot proceed without a decision
Red Update structure: Status (one sentence) → Root Cause → Customer Impact → Options A/B/C (C = "no change") → Recommendation → Decision required by [date]
The Red Update is delivered before Thursday afternoon when there are still options. "Waiting to be sure" is the pattern that turns Green into Red overnight.
Red Update template card: six sections labeled and color-coded. The "Options" section shows three rows: Option A, B, and C (labeled "no change: what happens if we do nothing"). This is the section most architects skip.
07Framework
Framework 4: The Information Timing Test
Before deciding whether and when to share difficult information, answer three questions: (1) Does the customer need this to make a good decision? (2) Will they find out anyway? (3) Is there still time to act on it?
If any answer is yes: disclose now, with options
The only valid reason to delay is that you need 24–48 hours to verify the information before raising a false alarm
"I need to validate this before I say anything" is professional. "I'm going to wait and see" is not.
Exercises (Slides 8–10)
08Exercise
The Anti-Pitch Role Play: Scenario 1
Customer has designed an architecture they are proud of, and it has a fundamental flaw at scale
Account team has asked the architect not to "complicate things": the deal is close to signed
Participant plays the architect; partner plays the customer (emotionally invested in their design)
Task: open the difficult conversation: acknowledge the design, name the flaw, provide a path forward. You have 3 minutes.
Debrief question: did the architect separate the concern from a judgment about the customer's competence? The flaw is in the architecture, not the customer. Conflating them is the most common failure mode.
09Exercise
Draft a Red Update: Live
Each participant identifies a real or fictional scenario where a Red Update is needed
Draft the update using the 6-section structure from M06_Red_Update_Template.pdf
Pair review: does the update include three genuine options, including the "no change" option? Is the recommendation unambiguous?
The test: could the customer make a decision based on this update without calling you first?
10Close
Application: Before the Next Hard Conversation
Identify one piece of difficult information you have not yet shared with a current customer, and apply the Information Timing Test
Draft the Anti-Pitch or Red Update before the next customer meeting
Score your Trusted Advisor formula for your current primary engagement, which dimension is your weakest?
Prepare the path forward before the conversation: never deliver the problem without the options