Stakeholder Mapping & Engagement Strategy

Not all stakeholders have equal influence. Understanding the hierarchy helps prioritize engagement:

TIER 1: CRITICAL STAKEHOLDERS
Can single-handedly kill the project
├── Commercial Banks
├── Political Leadership
└── Central Bank Leadership (internal)

TIER 2: ESSENTIAL STAKEHOLDERS
Strongly influence success/failure
├── Payment Service Providers
├── Merchants (large and small)
├── General Public
└── Financial Regulators (other than CB)

TIER 3: IMPORTANT STAKEHOLDERS
Significant influence on outcomes
├── Fintech Companies
├── Technology Vendors
├── Media
├── Civil Society Organizations
└── Academic/Research Community

TIER 4: CONTEXTUAL STAKEHOLDERS
Influence specific aspects
├── International Organizations (IMF, BIS)
├── Other Central Banks
├── Telecommunications Companies
├── Consumer Protection Agencies
└── Law Enforcement
```

Commercial Banks

Banks are the most critical—and often most resistant—stakeholder group. Their relationship with CBDC is existential.

COMMERCIAL BANKS - COMPLETE PROFILE

WHAT THEY WANT:
├── Maintain customer deposits
├── Preserve customer relationships
├── Continue earning on payment services
├── Avoid disintermediation
└── Remain relevant in digital future

WHAT THEY FEAR:
├── Deposit flight to CBDC
│   └── "If customers hold CBDC instead of deposits,
│       we lose our funding base"
├── Digital bank runs
│   └── "CBDC enables instant, massive withdrawals—
│       faster than we can respond"
├── Loss of customer data
│   └── "If payments bypass us, we lose insights"
├── Irrelevance
│   └── "If central bank serves customers directly,
│       what's our role?"
└── Increased costs
    └── "Integration, compliance, new systems"

THEIR POWER:
├── Control retail distribution infrastructure
├── Have customer relationships
├── Political lobbying influence
├── Can passively resist (don't promote)
├── Technical integration required
└── Without them, CBDC cannot reach users

ENGAGEMENT STRATEGY:
├── Make them partners, not victims
├── Two-tier architecture (they distribute)
├── Holding limits on CBDC (protect deposits)
├── No/negative interest on CBDC (deposits more attractive)
├── Bank-branded wallets (preserve relationship)
├── Revenue sharing opportunities
├── Early involvement in design
└── Address concerns before they become opposition

The bank disintermediation fear deserves special attention:

BANK DISINTERMEDIATION ANALYSIS

THE FEAR:
If people can hold central bank money directly,
why hold deposits at commercial banks?

THE MATH:
├── Bank deposits: $X trillion
├── Assumed CBDC adoption: Y%
├── Deposit outflow: $X × Y% = $Z
├── Impact on bank funding: Significant
└── Impact on credit availability: Potentially severe

REALITY CHECK:
├── CBDC designs include holding limits ($2K-$10K typically)
├── CBDC typically pays 0% or negative interest
├── Bank deposits earn interest, provide credit access
├── Convenience of existing bank relationship
└── Most users won't maximize CBDC holdings

1. Holding limits (cap CBDC per person)
2. No interest on CBDC (or negative)
3. Banks remain distribution layer
4. Maintain bank account requirement
5. Waterfall design (excess auto-converts to deposit)

BOTTOM LINE:
Fear is manageable with proper design
But banks must be convinced, not ignored

Political Leadership

Politicians control funding, legal frameworks, and can terminate projects.

POLITICAL LEADERSHIP - COMPLETE PROFILE

WHAT THEY WANT:
├── Economic success stories
├── Voter approval
├── Modernization narrative
├── International standing
└── Legacy achievements

WHAT THEY FEAR:
├── Blame for failures
│   └── "CBDC crash" headlines
├── Privacy backlash
│   └── "Surveillance state" accusations
├── Bank sector opposition
│   └── Powerful lobbying, campaign donations
├── Public resistance
│   └── Protest potential
└── Wasted resources
    └── Opportunity cost criticism

THEIR POWER:
├── Approve/deny funding
├── Pass/block enabling legislation
├── Appoint central bank leadership
├── Set government policy
├── Control public narrative
└── Can terminate project at any time

ENGAGEMENT STRATEGY:
├── Build cross-party support
│   └── Don't make CBDC a partisan issue
├── Clear success metrics
│   └── Define what success looks like
├── Risk management visibility
│   └── Show you've considered what could go wrong
├── Regular communication
│   └── No surprises
├── Quick wins
│   └── Demonstrate progress milestones
├── Privacy-first positioning
│   └── Preempt surveillance concerns
└── Manage expectations
    └── Realistic timelines

Central Bank Leadership (Internal)

Often overlooked: internal alignment within the central bank.

CENTRAL BANK INTERNAL - COMPLETE PROFILE

WHAT THEY WANT:
├── Institutional credibility
├── Policy effectiveness
├── Operational excellence
├── Staff career development
└── International recognition

WHAT THEY FEAR:
├── Failure reflecting on institution
├── Scope creep and distraction
├── Resource competition with core functions
├── Staff burnout/turnover
└── Technology failures

INTERNAL DYNAMICS:
├── Monetary policy department
│   └── Concern: Does CBDC complicate our job?
├── Banking supervision
│   └── Concern: New risks to supervise
├── Payment systems
│   └── Opportunity: This is our domain
├── IT/Technology
│   └── Concern: Can we build/maintain this?
├── Legal
│   └── Concern: Liability, authority questions
└── Research/Economics
    └── Opportunity: Cutting-edge work

ENGAGEMENT STRATEGY:
├── Senior leadership sponsorship
├── Cross-departmental steering committee
├── Clear governance structure
├── Dedicated team (not part-time)
├── Career development opportunities
├── External expertise where needed
└── Communication across departments

Payment Service Providers (PSPs)

PSPs (card networks, payment processors, digital wallets) have mixed interests.

PAYMENT SERVICE PROVIDERS - COMPLETE PROFILE

WHAT THEY WANT:
├── Continue earning transaction fees
├── Maintain customer relationships
├── Access to CBDC infrastructure
├── Level playing field with banks
└── Innovation opportunities

WHAT THEY FEAR:
├── CBDC as competitor
├── Banks getting preferential access
├── Fee compression
├── Regulatory complexity
└── Market restructuring

THEIR POWER:
├── Control significant payment infrastructure
├── Have technology expertise
├── Customer relationships in certain segments
├── Can innovate around CBDC
└── Lobbying influence

ENGAGEMENT STRATEGY:
├── Define clear role in ecosystem
├── API access for integration
├── Competitive neutrality (banks vs. PSPs)
├── Acknowledge value they provide
└── Co-development opportunities

Merchants

Without merchants accepting CBDC, users have nowhere to spend it.

MERCHANTS - COMPLETE PROFILE

LARGE MERCHANTS (Retail chains, major businesses):
├── What they want:
│   ├── Lower payment processing fees
│   ├── Faster settlement
│   ├── Reduced chargebacks
│   └── Customer convenience
├── What they fear:
│   ├── Integration costs
│   ├── Another payment method to support
│   ├── Customer confusion
│   └── Training requirements
├── Their power:
│   ├── High-volume acceptance validates CBDC
│   ├── Can negotiate terms
│   └── Influence smaller merchants
└── Strategy: Early partnership, fee incentives, easy integration

SMALL MERCHANTS (Local shops, informal sector):
├── What they want:
│   ├── Simple solutions
│   ├── Low/no costs
│   ├── Cash-like immediacy
│   └── Customer convenience
├── What they fear:
│   ├── Technology complexity
│   ├── Hardware requirements
│   ├── Training burden
│   └── Reporting/tax visibility
├── Their power:
│   ├── Ubiquity matters for everyday transactions
│   ├── Informal economy significant
│   └── Public-facing adoption signal
└── Strategy: App-based acceptance, QR codes, zero fees initially

General Public

Ultimately, CBDC succeeds or fails based on public adoption.

GENERAL PUBLIC - COMPLETE PROFILE

WHAT THEY WANT:
├── Payment methods that work
├── Convenience (no new learning)
├── Security
├── Privacy
└── Perhaps: Lower costs, faster transfers

WHAT THEY FEAR:
├── Government surveillance
├── Losing financial privacy
├── Technology complexity
├── Losing access to cash
├── Account freezes/control
└── "Big Brother" associations

THEIR POWER:
├── Non-adoption = failure
├── Public opinion influences politicians
├── Media amplifies concerns
└── Voting power on CBDC-related issues

SEGMENTS TO CONSIDER:
├── Tech-savvy early adopters
│   └── Easier to reach, smaller group
├── Mainstream users
│   └── Need clear value proposition
├── Cash-preferring population
│   └── Privacy concerns, digital reluctance
├── Unbanked/underbanked
│   └── Target segment for inclusion goal
└── Elderly/digitally excluded
    └── Accessibility requirements

ENGAGEMENT STRATEGY:
├── Clear value proposition (why change?)
├── Privacy safeguards (visible, credible)
├── Education campaign (not marketing)
├── Gradual introduction (no forced adoption)
├── Cash coexistence (not replacement)
└── Feedback mechanisms

TIER 3 STAKEHOLDER SUMMARY

FINTECH COMPANIES:
├── Want: API access, level playing field, innovation space
├── Fear: Exclusion, over-regulation, bank favoritism
├── Power: Innovation pressure, talent pool, agility
└── Strategy: Developer program, sandbox access, clear rules

TECHNOLOGY VENDORS:
├── Want: Contracts, long-term relationships, reference cases
├── Fear: Scope changes, payment delays, unrealistic requirements
├── Power: Technical delivery capability
└── Strategy: Clear requirements, fair procurement, partnership model

MEDIA:
├── Want: Stories, accountability, access
├── Fear: Missing important developments
├── Power: Shape public narrative, amplify concerns
└── Strategy: Transparency, proactive communication, backgrounding

CIVIL SOCIETY:
├── Want: Privacy protection, financial inclusion, accountability
├── Fear: Surveillance state, exclusion, government overreach
├── Power: Public advocacy, legal challenges, reputation impact
└── Strategy: Early engagement, advisory roles, address concerns

ACADEMIA:
├── Want: Research access, intellectual engagement, funding
├── Fear: Being ignored, uninformed policy
├── Power: Expert analysis, legitimacy provision
└── Strategy: Research partnerships, advisory roles, data access
```

Stakeholder engagement must be sequenced strategically. Early mistakes create opposition that persists throughout the project.

RECOMMENDED ENGAGEMENT SEQUENCE

PHASE 1: INTERNAL ALIGNMENT (Months 1-6)
┌─────────────────────────────────────────────────────────────┐
│ Priority: Build internal coalition before external exposure │
│ │
│ Actions: │
│ ├── Central bank executive alignment │
│ ├── Cross-departmental working group formation │
│ ├── Treasury/Finance Ministry coordination │
│ ├── Initial legal authority assessment │
│ └── Develop external engagement strategy │
│ │
│ Key output: Internal decision to proceed and engage │
└─────────────────────────────────────────────────────────────┘

PHASE 2: CORE COALITION (Months 6-12)
┌─────────────────────────────────────────────────────────────┐
│ Priority: Secure critical stakeholder buy-in │
│ │
│ Actions: │
│ ├── Confidential bank association engagement │
│ ├── Major bank individual meetings │
│ ├── Political leadership briefings │
│ ├── Preliminary design consultation │
│ └── Address bank disintermediation concerns │
│ │
│ Key output: Bank support (or non-opposition) │
└─────────────────────────────────────────────────────────────┘

PHASE 3: EXPANDED CIRCLE (Months 12-18)
┌─────────────────────────────────────────────────────────────┐
│ Priority: Build broader support base │
│ │
│ Actions: │
│ ├── Payment service provider engagement │
│ ├── Major merchant consultation │
│ ├── Telecommunications partnership │
│ ├── Consumer protection agency briefing │
│ └── International organization coordination │
│ │
│ Key output: Ecosystem partnerships established │
└─────────────────────────────────────────────────────────────┘

PHASE 4: PUBLIC ENGAGEMENT (Months 18-24)
┌─────────────────────────────────────────────────────────────┐
│ Priority: Build public awareness and acceptance │
│ │
│ Actions: │
│ ├── Civil society consultation │
│ ├── Public consultation process │
│ ├── Media engagement │
│ ├── Academic community outreach │
│ └── User education development │
│ │
│ Key output: Public understanding and general acceptance │
└─────────────────────────────────────────────────────────────┘

PHASE 5: ECOSYSTEM DEVELOPMENT (Months 24+)
┌─────────────────────────────────────────────────────────────┐
│ Priority: Build adoption infrastructure │
│ │
│ Actions: │
│ ├── Fintech developer program │
│ ├── Small merchant outreach │
│ ├── Community organization partnerships │
│ ├── Ongoing feedback mechanisms │
│ └── Continuous engagement refinement │
│ │
│ Key output: Ready ecosystem for pilot launch │
└─────────────────────────────────────────────────────────────┘
```

SEQUENCING RATIONALE

WHY INTERNAL FIRST:
├── Can't engage externally without clear internal position
├── Mixed messages destroy credibility
├── Legal authority must be confirmed
└── Resource commitment must be secured

WHY BANKS BEFORE PUBLIC:
├── Banks will learn regardless—better to engage proactively
├── Their concerns inform design decisions
├── Opposition from banks kills projects
├── Media will ask banks for comment

WHY CONFIDENTIAL INITIALLY:
├── Allows honest conversation about concerns
├── Avoids premature public debate
├── Enables design iteration based on feedback
└── Announcement after coalition built is stronger

COMMON MISTAKES:
├── Public announcement before bank engagement
│ └── Creates defensive opposition
├── Ignoring civil society until they object
│ └── Late engagement looks like hiding something
├── Media strategy after negative coverage
│ └── Reactive positioning is weak
└── Assuming silence means acceptance
└── Passive stakeholders can become active opponents
```

Every CBDC project faces resistance. Anticipating and addressing it proactively is essential.

RESISTANCE SOURCES AND PATTERNS

COMMERCIAL BANK RESISTANCE

Passive resistance:
├── Not promoting CBDC to customers
├── Making onboarding difficult
├── Providing minimal support
├── Not investing in integration
└── Effect: Low adoption despite technical success

Active resistance:
├── Public opposition statements
├── Political lobbying against CBDC
├── Media campaigns highlighting risks
├── Legal challenges
└── Effect: Project delays, scope reduction, or termination

Root cause: Fear of disintermediation
Solution: Design that protects bank role

POLITICAL RESISTANCE

Same-party resistance:
├── Concerns about resource allocation
├── Competing priorities
├── Risk aversion
└── Solution: Clear value proposition, risk management

Opposition-party resistance:
├── Criticizing government initiative
├── Privacy/surveillance narrative
├── "Waste of money" narrative
└── Solution: Cross-party consultation, pre-empt concerns

Root cause: Political risk/opportunity calculation
Solution: Build broad coalition, manage expectations

PUBLIC RESISTANCE

Privacy-based:
├── "Government will track all my spending"
├── "Social credit score" fears
├── "Bank accounts can be frozen"
└── Solution: Privacy-first design, safeguards, transparency

Inertia-based:
├── "Current payments work fine"
├── "Why should I change?"
├── "Too complicated"
└── Solution: Clear value proposition, simplicity, incentives

Distrust-based:
├── "Government can't manage technology"
├── "It will crash and I'll lose money"
├── "Another failed project"
└── Solution: Demonstrated competence, pilot success, guarantees

CIVIL SOCIETY RESISTANCE

Principled opposition:
├── Financial surveillance concerns
├── Exclusion of vulnerable populations
├── Government overreach concerns
└── Solution: Address concerns in design, advisory roles

Activist opposition:
├── Organized campaigns
├── Media engagement
├── Legal challenges
└── Solution: Early engagement, transparency, compromise where possible
```

Nigeria's eNaira provides a comprehensive case study in stakeholder management failure:

NIGERIA ENAIRA - STAKEHOLDER FAILURE ANALYSIS

BANK ENGAGEMENT FAILURE:
├── What happened:
│ ├── Limited bank consultation
│ ├── Banks saw eNaira as threat
│ ├── No clear role for banks defined
│ └── Banks provided minimal support
├── Consequence:
│ ├── Limited distribution
│ ├── ATM integration absent
│ └── Customer support lacking
└── Lesson: Banks as passive participants guarantees failure

POLITICAL APPROACH FAILURE:
├── What happened:
│ ├── Presidential mandate drove timeline
│ ├── Rush to be "first in Africa"
│ ├── Launch before readiness
│ └── Political considerations over technical
├── Consequence:
│ ├── Inadequate infrastructure
│ ├── Poor user experience
│ └── Credibility damage
└── Lesson: Political timelines ≠ technical timelines

PUBLIC TRUST FAILURE:
├── What happened:
│ ├── Currency demonetization (naira redesign)
│ ├── Cash withdrawal limits
│ ├── Perceived forced adoption
│ └── Surveillance concerns unaddressed
├── Consequence:
│ ├── Public backlash, protests
│ ├── Black market for cash
│ ├── Trust destruction
│ └── 98.5% wallet abandonment
└── Lesson: Coercion destroys trust and adoption

MERCHANT ENGAGEMENT FAILURE:
├── What happened:
│ ├── Minimal merchant outreach
│ ├── No incentives for acceptance
│ ├── Integration complexity
│ └── Chicken-and-egg unsolved
├── Consequence:
│ ├── Nowhere to spend eNaira
│ ├── No reason to acquire eNaira
│ └── Self-reinforcing non-adoption
└── Lesson: Merchant network before user acquisition

CIVIL SOCIETY FAILURE:
├── What happened:
│ ├── Limited consultation
│ ├── Privacy concerns dismissed
│ ├── Perceived government overreach
│ └── Opposition mobilized
├── Consequence:
│ ├── Organized resistance
│ ├── Media coverage of concerns
│ └── Public distrust amplified
└── Lesson: Engagement beats dismissal
```

RESISTANCE MITIGATION FRAMEWORK

STRATEGY 1: PREEMPTIVE ENGAGEMENT
├── Engage stakeholders before they form opposition
├── Address concerns in design phase
├── Create advisory/consultation structures
├── Show concerns are heard and considered
└── Effect: Prevents opposition from solidifying

STRATEGY 2: COALITION BUILDING
├── Identify stakeholders who benefit
├── Organize supporters proactively
├── Balance opposition with support
├── Create stakeholder advisory groups
└── Effect: Opposition faces counter-voices

STRATEGY 3: DESIGN ACCOMMODATION
├── Modify design to address legitimate concerns
├── Holding limits for banks
├── Privacy tiers for public
├── Clear roles for payment providers
└── Effect: Removes basis for opposition

STRATEGY 4: COMMUNICATION STRATEGY
├── Proactive narrative
├── Address concerns before they're raised
├── Transparency about trade-offs
├── Regular updates
└── Effect: Shapes conversation, reduces uncertainty

STRATEGY 5: INCREMENTAL APPROACH
├── Pilot before full launch
├── Demonstrate success before scaling
├── Build credibility through achievement
├── Allow course correction
└── Effect: Reduces risk perception

STRATEGY 6: POLITICAL INSULATION
├── Cross-party support
├── Independent governance
├── Clear metrics (not political spin)
├── Long-term commitment structures
└── Effect: Survives political changes
```

Success requires not just avoiding opposition but building active support.

COALITION BUILDING FRAMEWORK

IDENTIFY BENEFICIARIES:
├── Who gains from CBDC?
├── Financial inclusion advocates
├── Technology innovators
├── Efficiency seekers
├── Anti-fraud interests
└── Map their influence and voice

ORGANIZE SUPPORTERS:
├── Create formal advisory structures
├── Regular engagement and updates
├── Amplify supportive voices
├── Coordinate messaging
└── Build momentum

NEUTRALIZE OPPOSITION:
├── Engage early and substantively
├── Address concerns in design
├── Find common ground
├── Offer concessions where possible
└── Isolate unreasonable opposition

MAINTAIN COALITION:
├── Regular communication
├── Demonstrate progress
├── Share credit for success
├── Address emerging concerns
└── Evolve relationships
```

The European Central Bank's Digital Euro project demonstrates sophisticated coalition building:

ECB DIGITAL EURO - COALITION ANALYSIS

INTERNAL COALITION:
├── Governing Council alignment
├── Cross-departmental involvement
├── Clear decision-making structure
└── Multi-year resource commitment

BANK COALITION:
├── Euro Retail Payments Board engagement
├── Bank industry consultation
├── Design addressing disintermediation
│ ├── Holding limits
│ ├── No interest
│ └── Bank distribution role
└── Ongoing dialogue, not one-time consultation

POLITICAL COALITION:
├── European Parliament briefings
├── Member state consultations
├── Finance ministry engagement
└── Legislative process engagement

PUBLIC COALITION:
├── Public consultation process
│ └── 8,000+ responses analyzed
├── Privacy focus (responding to #1 concern)
├── Use case research
└── Transparent communication of findings

CIVIL SOCIETY COALITION:
├── Privacy advocacy engagement
├── Consumer group consultation
├── Academic partnerships
└── Transparency about trade-offs

RESULT:
├── Broad acceptance of preparation phase
├── No major opposition emerged
├── Legitimate debate on design questions
├── Path to potential implementation
└── Model for other central banks
```

✅ Banks can kill CBDC projects: No successful CBDC has launched without bank cooperation. Bank opposition or passive resistance correlates strongly with adoption failure.

✅ Forced adoption backfires: Nigeria's cash restrictions to promote eNaira created public backlash and deeper trust problems. Coercion destroys the trust CBDC needs.

✅ Early engagement beats late damage control: Projects that engaged stakeholders early (ECB) face less opposition than those that announced first and engaged later.

✅ Coalition building takes time: Meaningful stakeholder engagement requires 18-24 months before public announcement. Shortcuts create problems.

⚠️ Whether opposition can be permanently neutralized: Even successful engagement may leave latent opposition that emerges later.

⚠️ Whether public acceptance is achievable: Despite engagement, public adoption of retail CBDC remains unproven anywhere.

⚠️ Whether political support can be sustained: Multi-year projects face political transitions regardless of coalition building.

🔴 Treating stakeholders as obstacles: Viewing engagement as box-checking rather than genuine dialogue creates adversaries.

🔴 Assuming technical success means project success: A working CBDC that nobody uses is a failure. Technology without stakeholder support is worthless.

🔴 Underestimating bank influence: Banks have political connections, resources, and distribution infrastructure. They must be partners.

🔴 Ignoring civil society: Privacy advocates and consumer groups can mobilize public opposition rapidly.

Stakeholder engagement is not a phase of CBDC implementation—it is the implementation. Technology is a commodity; stakeholder support is the scarce resource. Central banks that excel at stakeholder management can succeed with adequate technology. Central banks that excel at technology but fail at stakeholder management will fail overall.

Assignment: Create a comprehensive stakeholder engagement plan for a hypothetical CBDC implementation in a country of your choice.

Requirements:

Part 1: Stakeholder Mapping (3-4 pages)

• Name the specific organizations/entities
• Assess their current position (supportive, neutral, opposed, unknown)
• Evaluate their influence (high, medium, low)
• Identify their key interests and concerns
• Note any relationships between stakeholders

Part 2: Engagement Strategy by Stakeholder (3-4 pages)

• Key messages (what do they need to hear?)

• Engagement format (meetings, working groups, consultations)

• Anticipated objections and responses

• Concessions/accommodations you'd offer

• Success metrics for engagement

• Engagement approach summary

• Key concerns to address

• Role in CBDC ecosystem

Part 3: Engagement Timeline (1-2 pages)

• Month-by-month stakeholder engagement activities
• Key milestones and decision points
• Phase transitions and gates
• Public communication timing

Part 4: Risk Assessment (1 page)

• Three stakeholders most likely to become opponents

• Warning signs of emerging opposition

• Mitigation strategies for each

• Stakeholder identification completeness (25%)

• Engagement strategy sophistication (25%)

• Timeline realism and sequencing logic (25%)

• Risk assessment quality (25%)

Time investment: 3-4 hours
Value: Creates reusable framework for CBDC stakeholder engagement applicable to any jurisdiction.

For Next Lesson:
Lesson 4 examines the critical retail vs. wholesale CBDC decision. This design choice shapes every subsequent stakeholder relationship and implementation strategy. We'll analyze why wholesale CBDC is progressing while retail struggles, and how to make this fundamental decision.

End of Lesson 3

Total words: ~5,600
Estimated completion time: 60 minutes reading + 3-4 hours for deliverable