Internal Stakeholder Management

Who matters for digital asset treasury initiatives:

Stakeholder Inventory:

STAKEHOLDER IDENTIFICATION:

PRIMARY STAKEHOLDERS (Direct decision authority):

CFO / Finance Leadership
├── Role: Ultimate approval authority for treasury
├── Interest: Financial performance, risk management
├── Typical concern: "Does the business case hold up?"
└── Priority: CRITICAL

CEO / Executive Committee
├── Role: Strategic and reputational oversight
├── Interest: Strategic alignment, risk
├── Typical concern: "Is this consistent with who we are?"
└── Priority: HIGH

Board / Audit Committee
├── Role: Governance oversight
├── Interest: Risk, compliance, strategy
├── Typical concern: "Are we managing risk appropriately?"
└── Priority: HIGH (for formal approval)

SECONDARY STAKEHOLDERS (Influence decision):

General Counsel / Legal
├── Role: Legal and regulatory oversight
├── Interest: Legal risk, compliance
├── Typical concern: "Are we exposed legally?"
└── Priority: HIGH

Chief Information Security Officer (CISO)
├── Role: Security oversight
├── Interest: Security risk, data protection
├── Typical concern: "Does this create security vulnerabilities?"
└── Priority: HIGH

Controller / Chief Accounting Officer
├── Role: Accounting and reporting
├── Interest: Accounting treatment, audit
├── Typical concern: "How do we account for this?"
└── Priority: MEDIUM-HIGH

TERTIARY STAKEHOLDERS (Affected by decision):

IT Leadership
├── Role: Technology implementation
├── Interest: Integration, resources
├── Typical concern: "Can we support this?"
└── Priority: MEDIUM

Internal Audit
├── Role: Control assurance
├── Interest: Auditability, controls
├── Typical concern: "Can we audit this?"
└── Priority: MEDIUM

Investor Relations
├── Role: External communication
├── Interest: Market perception
├── Typical concern: "What will investors think?"
└── Priority: MEDIUM

Operations / Business Units
├── Role: Use the solution
├── Interest: Operational efficiency
├── Typical concern: "Will this actually work?"
└── Priority: MEDIUM
```

Mapping influence, interest, and disposition:

Analysis Framework:

STAKEHOLDER ANALYSIS MATRIX:

DIMENSION DEFINITIONS:

INFLUENCE: Ability to affect decision outcome
├── High: Can approve, veto, or significantly sway
├── Medium: Input sought, voice heard
├── Low: Informed but not consulted

INTEREST: Level of concern with this initiative
├── High: Directly affected, engaged, cares deeply
├── Medium: Somewhat affected, moderate concern
├── Low: Peripherally affected, limited concern

DISPOSITION: Current attitude toward initiative
├── Supportive: Generally favorable, likely advocate
├── Neutral: No strong view, open to persuasion
├── Skeptical: Doubts or concerns, needs convincing
├── Opposed: Actively resistant, may obstruct

STAKEHOLDER MAP:

Stakeholder Influence Interest Disposition Strategy
────────────────────────────────────────────────────────────────────
CFO High High Supportive Collaborate
CEO High Medium Neutral Engage
General Counsel High High Skeptical Address concerns
CISO High High Opposed Convert or neutralize
Controller Medium High Neutral Educate
IT Leadership Medium Medium Supportive Engage
Internal Audit Medium Medium Neutral Inform
Investor Relations Medium Medium Skeptical Address concerns
Business Units Low Medium Supportive Keep informed

STAKEHOLDER QUADRANT:

HIGH INFLUENCE
│
┌─────────────────────┼─────────────────────┐
│ │ │
│ MANAGE CLOSELY │ KEEP SATISFIED │
│ CFO, CEO, GC, CISO │ Board, ExCom │
│ │ │
H ──├─────────────────────┼─────────────────────┤
I │ │ │
G │ KEEP INFORMED │ MONITOR │
H │ Controller, IT, │ (peripheral │
│ Internal Audit │ stakeholders) │
I │ │ │
N └─────────────────────┼─────────────────────┘
T │
E LOW INFLUENCE
R
E
S
T
```

Identifying allies and building support:

Coalition Framework:

COALITION BUILDING:

STAKEHOLDER CATEGORIES:

Champions (Build on):
├── Definition: Influential supporters
├── Strategy: Engage early, leverage influence
├── Actions: Share information, ask for advocacy
└── Goal: Activate their support for initiative

Allies (Nurture):
├── Definition: Supporters with limited influence
├── Strategy: Keep engaged, prepare to mobilize
├── Actions: Regular updates, seek input
└── Goal: Create groundswell of support

Fence-sitters (Convert):
├── Definition: Neutral, persuadable
├── Strategy: Educate, address concerns, demonstrate value
├── Actions: One-on-one discussions, tailored information
└── Goal: Move to ally or champion

Skeptics (Neutralize or convert):
├── Definition: Concerned but open-minded
├── Strategy: Understand concerns, address substantively
├── Actions: Deep engagement, proof points, reassurance
└── Goal: Convert to fence-sitter or neutralize objections

Opponents (Manage):
├── Definition: Actively resistant
├── Strategy: Understand root cause, work around if can't convert
├── Actions: Address concerns if reasonable, escalate if not
└── Goal: Prevent blocking or convert to skeptic

COALITION BUILDING SEQUENCE:

Step 1: Secure sponsor
├── Identify executive champion (typically CFO)
├── Ensure genuine support, not just tolerance
├── Agree on roles and support expected
└── Output: Committed sponsor

Step 2: Build core team support
├── Engage treasury team
├── Engage IT partners
├── Address operational concerns
└── Output: Internal team aligned

Step 3: Neutralize high-influence skeptics
├── Identify who could block
├── Engage early, understand concerns
├── Address concerns substantively
└── Output: Objections addressed or contained

Step 4: Expand coalition
├── Engage fence-sitters
├── Demonstrate progress and support
├── Build momentum
└── Output: Broad coalition of support

Step 5: Formalize approval
├── Present with coalition visible
├── Handle remaining objections
├── Secure formal approval
└── Output: Approved initiative

---

What stakeholders say vs. what they actually worry about:

Concern Analysis:

CONCERN ANALYSIS:

THE REALITY: Stakeholders often don't voice their real concerns

STATED CONCERN           POSSIBLE UNSTATED CONCERN
────────────────────────────────────────────────────────────────
"Is this legal?"         "Will I be blamed if something goes wrong?"

"The risk is too high"   "I don't understand this and that scares me"

"We should wait"         "I don't want to be associated with crypto"

"The numbers don't       "I don't believe the numbers and don't know
work"                    how to evaluate them"

"What about security?"   "I've seen crypto hack headlines and assume
                         we'll be hacked"

"This isn't strategic"   "I think crypto is a fad/scam"

"Our board won't         "I don't want to explain this to the board"
approve"

UNDERSTANDING REAL CONCERNS:

Approach:
├── Listen more than talk
├── Ask probing questions
├── Observe body language and tone
├── Note what's NOT said
└── Give permission to share concerns

Questions to surface real concerns:
├── "What would need to be true for you to be comfortable?"
├── "What's your biggest worry about this?"
├── "If this went wrong, what would concern you most?"
├── "What would you need to see to feel confident?"
└── "What questions would you expect from [their stakeholder]?"

RED FLAGS (Indicating unstated concerns):
├── Repeated objections to different specific issues
├── Moving goalposts (new objection after addressing previous)
├── Vague discomfort that can't be pinpointed
├── Deferring to others ("ask Legal")
├── Requesting more analysis/information repeatedly
└── Strong reaction disproportionate to stated reason
```

Typical stakeholder patterns and responses:

Archetype Framework:

STAKEHOLDER ARCHETYPES:

ARCHETYPE 1: THE SKEPTICAL TRADITIONALIST

Profile:
├── Prefers established approaches
├── Views digital assets as speculative/risky
├── Values stability over innovation
└── Often: Finance leadership, legal, risk

Indicators:
├── "Why fix what isn't broken?"
├── "We've never done this before"
├── References to crypto crashes/scandals
└── Requests for extensive due diligence

Engagement approach:
├── Emphasize risk management and controls
├── Frame as evolution, not revolution
├── Provide extensive documentation
├── Offer conservative pilot approach
├── Reference peer adoption
└── Allow time to process

ARCHETYPE 2: THE CAREER PROTECTOR

Profile:
├── Primary concern is personal risk
├── Worried about being blamed if it fails
├── Risk-averse for career reasons
└── Often: Any level, especially mid-career

Indicators:
├── "What if something goes wrong?"
├── Asks who else is doing this
├── Wants extensive documentation
├── Defers to others
└── Focuses on downside scenarios

Engagement approach:
├── De-risk the initiative (pilot, limited scope)
├── Provide cover (industry examples, expert opinions)
├── Document decision process thoroughly
├── Offer exit ramps
├── Share accountability widely
└── Emphasize controls and governance

ARCHETYPE 3: THE UNINFORMED SKEPTIC

Profile:
├── Doesn't understand digital assets
├── Knowledge from headlines/media
├── Confuses speculation with treasury use
└── Often: Executives outside finance/tech

Indicators:
├── Confuses XRP with Bitcoin speculation
├── References irrelevant crypto events
├── Basic misconceptions
└── Fear-based objections

Engagement approach:
├── Educate patiently, without condescension
├── Distinguish speculation from treasury use
├── Use analogies to familiar concepts
├── Provide simple explanations
├── Give time to learn
└── Avoid jargon

ARCHETYPE 4: THE CAUTIOUS SUPPORTER

Profile:
├── Sees potential but worried about execution
├── Wants to support but needs reassurance
├── Concerned about operational risks
└── Often: Operations, IT, team members

Indicators:
├── "I like the idea, but..."
├── Asks detailed operational questions
├── Worried about workload/resources
└── Wants to see plan before committing

Engagement approach:
├── Address specific operational concerns
├── Provide detailed implementation plan
├── Ensure adequate resources
├── Involve in planning
├── Start with limited scope
└── Demonstrate quick wins

ARCHETYPE 5: THE ENTHUSIASTIC ADVOCATE

Profile:
├── Excited about digital assets
├── May oversell or understate risks
├── Could create backlash from over-enthusiasm
└── Often: Tech-forward, younger, innovation roles

Indicators:
├── Pushes for faster/broader implementation
├── Minimizes risks
├── Uses crypto jargon freely
├── May alienate traditionalists

Engagement approach:
├── Channel enthusiasm productively
├── Coach on organizational dynamics
├── Use as champion but manage messaging
├── Ensure realistic expectations
└── Help them understand other perspectives

What each function cares about:

Functional Concerns:

FUNCTIONAL STAKEHOLDER PERSPECTIVES:

LEGAL / GENERAL COUNSEL:

Primary concerns:
├── Regulatory compliance
├── Contractual protections
├── Litigation risk
├── Corporate governance
└── Fiduciary duty

Questions they'll ask:
├── "What's the regulatory status?"
├── "How are we protected contractually?"
├── "What's our liability exposure?"
├── "Have peers done this?"
└── "What could we be sued for?"

What they need:
├── Regulatory analysis
├── Contract review findings
├── Risk mitigation measures
├── Precedent/comparables
└── Clear governance structure

CISO / SECURITY:

Primary concerns:
├── Cybersecurity risk
├── Data protection
├── Key management
├── Vendor security
└── Incident response

Questions they'll ask:
├── "How are keys secured?"
├── "What if there's a breach?"
├── "How are vendors vetted?"
├── "What's the attack surface?"
└── "Can we audit security?"

What they need:
├── Security architecture
├── Vendor SOC reports
├── Key management procedures
├── Incident response plan
└── Security assessment findings

CONTROLLER / ACCOUNTING:

Primary concerns:
├── Accounting treatment
├── Audit readiness
├── Financial reporting
├── Internal controls
└── Tax implications

Questions they'll ask:
├── "How do we account for this?"
├── "Can we audit the transactions?"
├── "What's the fair value process?"
├── "How does this affect financials?"
└── "What are the tax implications?"

What they need:
├── Accounting policy
├── Control documentation
├── Audit trail evidence
├── Tax analysis
└── Reporting procedures

INVESTOR RELATIONS:

Primary concerns:
├── Market perception
├── Analyst reaction
├── Disclosure requirements
├── Reputation
└── ESG considerations

Questions they'll ask:
├── "What will analysts think?"
├── "Do we need to disclose?"
├── "How do we message this?"
├── "What if media picks it up?"
└── "What are peers saying?"

What they need:
├── Disclosure analysis
├── Messaging guidance
├── Peer comparables
├── Q&A preparation
└── Communication plan

---

How you describe it matters:

Framing Framework:

FRAMING STRATEGIES:

EFFECTIVE FRAMING:

Frame as treasury efficiency:
├── "A new approach to cross-border payments"
├── "Treasury settlement optimization"
├── "Working capital improvement initiative"
└── NOT "cryptocurrency project"

Frame as risk-managed innovation:
├── "Piloted approach with clear controls"
├── "Limited initial scope with expansion based on results"
├── "Proven technology with institutional adoption"
└── NOT "cutting-edge blockchain experiment"

Frame as competitive necessity:
├── "Industry-adopted approach to payment efficiency"
├── "Peers including [X] have implemented"
├── "Cost disadvantage if we don't adapt"
└── NOT "first-mover opportunity"

FRAMING BY AUDIENCE:

For CFO/Finance:
├── Lead with economics and risk
├── "35% cost reduction with controlled risk profile"
├── Provide quantitative analysis
└── Discuss risk management rigorously

For Legal:
├── Lead with compliance and protection
├── "Compliant approach with regulatory clarity"
├── Reference legal analysis
└── Emphasize contractual protections

For Security:
├── Lead with security architecture
├── "Institutional-grade security with qualified custody"
├── Detail security controls
└── Reference SOC reports and audits

For Board:
├── Lead with strategic fit and governance
├── "Measured approach to treasury modernization"
├── Emphasize oversight and controls
└── Provide peer context

FRAMING DON'TS:

Avoid:
├── Cryptocurrency/crypto (use "digital assets")
├── Blockchain hype language
├── Technical jargon
├── Comparison to retail crypto trading
├── Speculative framing
└── Defensive/apologetic tone
```

What to communicate and when:

Phase-Based Communication:

COMMUNICATION BY PHASE:

PHASE 1: EXPLORATION (Before formal proposal)

Audience: Sponsor, key influencers
Purpose: Test waters, build support, surface concerns
Content:
├── Concept overview
├── Initial business case outline
├── Industry trends and peer activity
└── Request for feedback/input

Channels:
├── One-on-one conversations
├── Informal discussions
├── Working sessions
└── NOT formal presentations yet

Outcome: Coalition forming, concerns identified

PHASE 2: PROPOSAL (Seeking approval)

Audience: Decision makers, influencers, affected parties
Purpose: Gain approval to proceed
Content:
├── Formal business case
├── Risk analysis
├── Implementation plan
├── Decision options
└── Resource requirements

Channels:
├── Formal presentation
├── Written business case
├── Supporting documentation
└── Q&A sessions

Outcome: Approval decision

PHASE 3: IMPLEMENTATION (Pilot execution)

Audience: Stakeholders, project team, broader organization
Purpose: Keep informed, maintain support, manage expectations
Content:
├── Progress updates
├── Milestone achievements
├── Issues and resolutions
├── Preliminary results
└── Changes to plan

Channels:
├── Regular status reports
├── Steering committee updates
├── Team meetings
└── Informal check-ins

Outcome: Stakeholders remain supportive, informed

PHASE 4: EVALUATION (Pilot complete)

Audience: Decision makers, all stakeholders
Purpose: Share results, seek continuation/expansion decision
Content:
├── Results vs. objectives
├── Lessons learned
├── Recommendation for next phase
├── Updated business case
└── Risk assessment update

Channels:
├── Formal presentation
├── Written evaluation report
├── Decision meeting
└── Broader communication of outcomes

Outcome: Decision on program future

PHASE 5: ONGOING OPERATIONS

Audience: Relevant stakeholders
Purpose: Maintain awareness, demonstrate success, manage issues
Content:
├── Periodic performance reporting
├── Material issues/changes
├── Annual reviews
└── Success stories

Channels:
├── Regular reporting (monthly/quarterly)
├── Exception reporting as needed
├── Annual review presentations
└── Integration into normal treasury reporting

Outcome: Digital assets normalized as treasury tool

Managing resistance and objections:

Conversation Framework:

HANDLING RESISTANCE:

GENERAL APPROACH:

Do:
├── Listen fully before responding
├── Acknowledge concerns as valid
├── Ask clarifying questions
├── Address substance, not defensively
├── Offer to follow up with information
└── Thank them for raising concerns

Don't:
├── Get defensive
├── Dismiss concerns
├── Over-promise or minimize risk
├── Make it personal
├── Force immediate resolution
└── Go around them (usually backfires)

OBJECTION HANDLING:

Objection: "This is too risky"

Response approach:
├── Acknowledge: "Risk management is crucial for treasury"
├── Clarify: "Can you help me understand which specific
│ risks concern you most?"
├── Address: Respond to specific risks with mitigation
├── Reframe: "Our approach is designed to manage those
│ risks through [specific measures]"
└── Verify: "Does that address your concern, or is there
more we should discuss?"

Objection: "We should wait and see"

Response approach:
├── Acknowledge: "Timing is an important consideration"
├── Explore: "What would you want to see before moving
│ forward?"
├── Provide: Information on current state (peer adoption,
│ regulatory clarity, technology maturity)
├── Cost: "Waiting has costs too—[quantify if possible]"
└── Offer: "A limited pilot would let us learn while
managing exposure"

Objection: "The board will never approve"

Response approach:
├── Explore: "What do you think their concerns would be?"
├── Prepare: "Let's develop the materials that would
│ address those concerns"
├── Offer: "Would you be willing to socialize the concept
│ before a formal proposal?"
├── Reference: Comparable companies with board approval
└── Sequence: "We could seek CFO approval first, then
board if needed"

WHEN RESISTANCE PERSISTS:

If stakeholder remains opposed:
├── Understand: Is this fundamental or addressable?
├── Escalate: Can sponsor help resolve?
├── Work around: Can initiative proceed without them?
├── Accommodate: Can scope be adjusted to address concern?
├── Accept: Some opposition may be immovable

Document:
├── Concerns raised
├── Responses provided
├── Outcome of discussions
└── Rationale for proceeding (if applicable)

---

Keeping stakeholders aligned:

Expectation Management:

EXPECTATION MANAGEMENT:

PRINCIPLES:

Under-promise, over-deliver:
├── Conservative projections
├── Acknowledge uncertainty
├── Celebrate exceeding expectations
└── Never promise what you can't deliver

Communicate early and often:
├── Bad news travels fast—get ahead of it
├── Regular updates even when nothing notable
├── No surprises for senior stakeholders
└── Frequency appropriate to phase

Be transparent about challenges:
├── Acknowledge when things aren't working
├── Explain what you're doing about it
├── Don't hide problems hoping they'll resolve
└── Stakeholders respect honesty

MANAGING SPECIFIC EXPECTATIONS:

Financial expectations:
├── Present as ranges, not point estimates
├── Track against conservative case
├── Explain variances promptly
├── Don't chase optimistic projections
└── Celebrate meeting conservative targets

Timeline expectations:
├── Build in buffer
├── Identify dependencies and risks
├── Communicate delays as soon as known
├── Explain impact and recovery plan
└── Reset expectations clearly when needed

Risk expectations:
├── Be clear about what could go wrong
├── Don't minimize to get approval
├── Report issues when they occur
├── Show how risk is being managed
└── Adjust if risk profile changes

EXPECTATION ALIGNMENT CHECKPOINTS:

Before approval:
├── Confirm shared understanding of objectives
├── Confirm understanding of risks
├── Confirm success criteria
└── Document agreements

During implementation:
├── Regular progress check-ins
├── Confirm continued alignment
├── Surface changes promptly
└── Reconfirm support

At evaluation:
├── Review against agreed criteria
├── Discuss honestly what worked/didn't
├── Agree on next phase expectations
└── Document decisions
```

Communicating wins effectively:

Success Communication:

SUCCESS STORYTELLING:

WHY IT MATTERS:
├── Builds confidence in the initiative
├── Justifies continued investment
├── Recognizes team contributions
├── Creates positive association with digital assets
└── Makes future initiatives easier

WHAT TO COMMUNICATE:

Quantitative wins:
├── Cost savings achieved (with context)
├── Efficiency improvements (time, resources)
├── Performance vs. projections
├── Volume and activity growth
└── Risk metrics within tolerance

Qualitative wins:
├── Smooth operations
├── Positive user feedback
├── Audit success
├── Regulatory compliance
└── Team capability development

STORYTELLING PRINCIPLES:

Be credible:
├── Accurate numbers, verified
├── Acknowledge what didn't work
├── Don't over-claim
└── Context that makes claims meaningful

Be relevant:
├── Connect to stakeholder priorities
├── "We saved $X" vs. "Treasury efficiency improved"
├── Different wins resonate with different audiences
└── Tailor the story

Be memorable:
├── Simple, clear headline
├── Concrete example or anecdote
├── Visual if possible
├── Repeat key message

COMMUNICATION CHANNELS:

Internal:
├── Executive updates
├── Treasury team meetings
├── Company newsletter (if appropriate)
├── Town halls (if appropriate)
└── One-on-one with key stakeholders

External (if appropriate):
├── Annual report (if material)
├── Investor presentations (if relevant)
├── Industry conferences
├── Case studies (with care)
└── Generally: Low profile is safer
```

When things don't go as planned:

Setback Management:

MANAGING SETBACKS:

TYPES OF SETBACKS:

Operational issues:
├── Transaction failures
├── System outages
├── Reconciliation problems
├── Provider issues

Financial shortfalls:
├── Savings below projection
├── Unexpected costs
├── Volatility impacts

Timeline delays:
├── Implementation taking longer
├── Dependencies not met
├── Resource constraints

External events:
├── Negative crypto news
├── Regulatory developments
├── Provider problems

RESPONSE FRAMEWORK:

Step 1: Assess
├── What happened?
├── What's the impact?
├── What's the root cause?
├── What are the options?

Step 2: Communicate
├── Notify appropriate stakeholders promptly
├── Factual, not defensive
├── Include impact assessment
├── Include response plan

Step 3: Address
├── Implement response plan
├── Monitor effectiveness
├── Adjust as needed
└── Document actions taken

Step 4: Learn
├── Root cause analysis
├── Preventive measures identified
├── Process improvements
├── Knowledge captured

COMMUNICATION TEMPLATE (Setback):

Subject: [Initiative] Status Update - [Issue]

Summary: [Brief description of issue]

Impact: [What is affected and how]

Root cause: [What caused this—if known]

Response: [What we're doing about it]

Timeline: [When it will be resolved]

Support needed: [If any]

Next update: [When you'll provide next update]

STAKEHOLDER REACTIONS:

If stakeholder overreacts:
├── Stay calm, don't match energy
├── Acknowledge their concern
├── Provide perspective (context, proportion)
├── Focus on resolution
└── Follow up with additional information

If stakeholder loses confidence:
├── Understand what specifically concerns them
├── Provide reassurance based on facts
├── Offer additional controls if appropriate
├── Demonstrate responsiveness
└── Rebuild trust through actions over time

---

✅ Stakeholder dynamics affect outcomes: Sound business cases fail without stakeholder management

✅ Early engagement matters: Surfacing and addressing concerns early prevents blocking later

✅ Framing influences reception: How you describe the initiative affects stakeholder reactions

✅ Different stakeholders need different approaches: One-size-fits-all communication fails

⚠️ How to handle immovable opponents: Sometimes stakeholders can't be converted

⚠️ Organizational culture impact: Approaches work differently in different cultures

⚠️ Timing considerations: When to push vs. when to wait varies by situation

⚠️ External event impact: Crypto news can change stakeholder attitudes overnight

🔴 Ignoring stakeholders: Proceeding without addressing concerns leads to project failure

🔴 Over-promising: Creating expectations that can't be met destroys credibility

🔴 Going around opponents: Usually backfires and creates lasting enemies

🔴 Hiding problems: Small issues become big crises when concealed

Digital asset treasury initiatives succeed or fail based on stakeholder management as much as business fundamentals. Executives have emotional reactions to "cryptocurrency" that pure logic won't overcome. Early, thoughtful engagement—understanding real concerns, building coalitions, framing appropriately, and communicating consistently—creates conditions for success. This is not manipulation; it's bringing people along on a journey that requires trust and confidence.

---

Assignment: Develop a comprehensive stakeholder management plan for a digital asset treasury initiative at your organization.

Requirements:

Part 1: Stakeholder Mapping (25%)

STAKEHOLDER MAP:

Stakeholder          Role              Influence   Interest   Disposition
────────────────────────────────────────────────────────────────────────────
________________    ______________    _________   ________   _____________
________________    ______________    _________   ________   _____________
________________    ______________    _________   ________   _____________
________________    ______________    _________   ________   _____________
________________    ______________    _________   ________   _____________
________________    ______________    _________   ________   _____________

COALITION ASSESSMENT:

Champions: _________________________________
Allies: ____________________________________
Fence-sitters: _____________________________
Skeptics: __________________________________
Opponents: _________________________________
```

Part 2: Concern Analysis (25%)

CONCERN ANALYSIS:

For each key stakeholder:

Stakeholder: _________________________________

Stated concerns:
├── _________________________________________
├── _________________________________________
└── _________________________________________

Likely unstated concerns:
├── _________________________________________
├── _________________________________________
└── _________________________________________

What they need to feel comfortable:
├── _________________________________________
├── _________________________________________
└── _________________________________________

Engagement approach:

---

---

---

[Repeat for top 4-5 stakeholders]
```

Part 3: Communication Plan (25%)

COMMUNICATION PLAN:

PHASE 1: EXPLORATION
├── Audience: ________________________________
├── Key messages: ____________________________
├── Channels: ________________________________
└── Timeline: ________________________________

PHASE 2: PROPOSAL
├── Audience: ________________________________
├── Key messages: ____________________________
├── Channels: ________________________________
└── Timeline: ________________________________

PHASE 3: IMPLEMENTATION
├── Audience: ________________________________
├── Key messages: ____________________________
├── Channels: ________________________________
├── Frequency: _______________________________
└── Timeline: ________________________________

FRAMING GUIDANCE:

How we describe the initiative:

---

Language to use:
├── _________________________________________
├── _________________________________________
└── _________________________________________

Language to avoid:
├── _________________________________________
├── _________________________________________
└── _________________________________________
```

Part 4: Objection Responses (15%)

OBJECTION RESPONSE GUIDE:

Objection 1: "_________________________________"
Response approach:
________________________________________________
________________________________________________

Objection 2: "_________________________________"
Response approach:
________________________________________________
________________________________________________

Objection 3: "_________________________________"
Response approach:
________________________________________________
________________________________________________

Part 5: Setback Management (10%)

SETBACK RESPONSE PLAN:

If financial results disappoint:
├── Communication: ___________________________
├── Response: ________________________________
└── Stakeholder management: __________________

If operational issues occur:
├── Communication: ___________________________
├── Response: ________________________________
└── Stakeholder management: __________________

If negative crypto news breaks:
├── Communication: ___________________________
├── Response: ________________________________
└── Stakeholder management: __________________

• Completeness of stakeholder mapping (25%)
• Quality of concern analysis (25%)
• Thoughtfulness of communication plan (25%)
• Practicality of objection responses (15%)
• Realism of setback management (10%)

Time investment: 4-5 hours
Value: This deliverable provides the stakeholder management infrastructure needed to navigate internal dynamics—often the deciding factor in initiative success or failure.

---

1. Stakeholder Mapping:

A CISO is classified as "High Influence, High Interest, Opposed" to a digital asset initiative. What is the appropriate engagement strategy?

A) Ignore them and work around through the CFO
B) Engage early, understand concerns, and address substantively with technical detail
C) Wait until formal proposal to address their concerns
D) Reduce their influence by excluding them from discussions

Correct Answer: B

Explanation: High influence + opposed = potential project blocker. The correct strategy is early engagement to understand specific concerns (likely security-related) and address them substantively with technical detail (SOC reports, security architecture, key management procedures). Option A (working around) usually backfires and creates an enemy. Option C (waiting) allows opposition to solidify. Option D (excluding) is ethically problematic and practically counterproductive.

---

2. Unstated Concerns:

A stakeholder repeatedly raises new objections after previous ones are addressed. According to the framework, what does this likely indicate?

A) The stakeholder is deliberately obstructing
B) The business case needs more work
C) There are unstated concerns not being addressed
D) The stakeholder needs more technical education

Correct Answer: C

Explanation: "Moving goalposts"—raising new objections after previous ones are addressed—is a red flag indicating unstated concerns. The stated objections are proxies for something else (career risk, discomfort with the technology, etc.). The approach is to probe for real concerns with questions like "What would need to be true for you to be comfortable?" rather than continuing to address surface objections.

---

3. Framing:

Which framing is most likely to succeed with a skeptical executive audience?

A) "This cutting-edge blockchain technology will revolutionize our treasury"
B) "A measured approach to treasury settlement optimization"
C) "Our competitors are all using cryptocurrency and we're falling behind"
D) "Bitcoin and Ethereum have proven digital assets are the future"

Correct Answer: B

Explanation: "Measured approach to treasury settlement optimization" frames the initiative as risk-managed treasury efficiency, using neutral language. Option A uses hype language that triggers skepticism. Option C creates fear without substance and conflates with cryptocurrency speculation. Option D references assets unrelated to the use case and reinforces speculative associations.

---

4. Setback Communication:

A pilot experiences lower-than-projected cost savings (25% vs. 35% projected). What is the appropriate stakeholder communication approach?

A) Wait to see if results improve before communicating
B) Communicate promptly, honestly, with context and response plan
C) Highlight other positive metrics to distract from the shortfall
D) Revise projections retroactively to show success

Correct Answer: B

Explanation: Prompt, honest communication with context and response plan maintains credibility. The communication should acknowledge the shortfall, provide context (what's driving it, was the projection reasonable), and describe response (can anything be optimized, is the remaining benefit still valuable). Option A (waiting) risks being seen as hiding problems. Option C (distraction) undermines trust. Option D (revising retroactively) destroys credibility.

---

5. Coalition Building:

In the coalition building sequence, why is "neutralize high-influence skeptics" prioritized before "expand coalition"?

A) Skeptics are more important than supporters
B) Skeptics may block the initiative if not addressed, making broader coalition irrelevant
C) It's easier to convert skeptics than build new allies
D) Coalition expansion should wait until all objections are resolved

Correct Answer: B

Explanation: High-influence skeptics can block an initiative regardless of how many allies you have. Addressing their concerns before expanding the coalition ensures the initiative won't be blocked when it reaches decision-making. If you build a broad coalition but a single high-influence skeptic vetoes, the coalition was wasted effort. The sequence is: secure sponsor → build core team → neutralize blockers → expand coalition → seek approval.

---

For Next Lesson:
Reflect on industry trends and future developments in digital asset treasury before Lesson 14, where we'll examine the evolving landscape and emerging opportunities.

---

End of Lesson 13

Total words: ~6,300
Estimated completion time: 50 minutes reading + 4-5 hours for deliverable