Strategic Architect Framework: Microsoft CSA Training Program

Module 04: Influence Workbook

Leading Through Friction: Influence Without Authority
The core question: Can you drive alignment when you have no direct control? This workbook applies the M04 frameworks, Triangulation, Developer Coalition, and Executive Pivot, to a real engagement where alignment is currently stalled.
Customer / Engagement
Stalled decision

Section A: Alignment Diagnosis

Before applying any framework, diagnose the nature of the stall. Different stall types require different influence approaches.

Stall TypeSignalIs this what you're facing?
Authority gap: no one has clear sign-off powerDecision bounces between stakeholders; everyone defers to someone elseYes / No
Information gap: decision-maker lacks confidence in the data"We need to see more analysis" or "Let's wait for the vendor comparison"Yes / No
Political conflict: two stakeholders have competing goalsMeetings produce agreement that is quietly reversed afterwardYes / No
Trust gap: sponsor can't bring the skeptic alongA specific person's concerns are cited repeatedly; that person isn't engagedYes / No
Risk aversion: decision-maker fears being wrong more than staying still"We're not ready" or "Let's revisit in Q3" with no defined triggerYes / No
Primary stall type and why

Section B: Triangulation Map

Triangulation builds alignment by connecting multiple stakeholders laterally rather than vertically through a single sponsor. Map the current influence topology and identify where lateral connections are missing.

Who is your current primary sponsor?
Who is the key skeptic or blocker your sponsor cannot reach?

Triangulation Targets

Identify 2–3 stakeholders who already trust you (or could) and who have credibility with the skeptic. A successful triangulation works through those relationships, not around the skeptic directly.

Potential Bridge StakeholderTheir relationship to the skepticYour relationship with themMessage / framing for this person

Section C: Developer Coalition

When the engineering team has influence over a skeptical executive, building their conviction in the solution creates a ground-up endorsement that bypasses the authority gap. The Developer Coalition is a peer-to-peer influence play.

C1. Identify the Coalition

List the technical practitioners who will work with this solution. These are the people who can generate an organic endorsement if they believe in the approach.

C2. Design the Coalition-Building Moment

What experience will make these practitioners genuine advocates, not just technically literate? A sandbox, a prototype, a reference customer call, a hands-on lab?

C3. The Coalition's Voice

How will the coalition's endorsement reach the skeptical decision-maker? Write the specific scenario, who says what to whom, in what meeting or channel.

Section D: Executive Pivot

The Executive Pivot is used when the deal needs to move up the authority chain when your current sponsor doesn't have the authority to end the stall. It is not an escalation; it is a strategic reframe delivered to a new audience.

D1. Is an Executive Pivot appropriate here?

D2. The Executive Pivot Message

The pivot message is not a project status briefing. It is a strategic framing of the decision in terms the executive cares about (risk, competitive position, capital allocation). Write it in 3 sentences: context, cost of the stall, and the decision needed.

Section E: Influence Plan

Sequence the moves. Which framework goes first, who executes each step, and what is the minimum viable outcome at each step?

#Move (framework)Who executesTarget audienceBy whenSuccess signal
1
2
3
4