The Strategic Decision Framework - Should You Build a CBDC?
Learning Objectives
Apply a rigorous cost-benefit analysis framework to CBDC decisions
Distinguish between strong motivations (evidence-based) and weak motivations (that often lead to failure)
Evaluate whether CBDC solves problems that actually exist in a given context
Analyze the "do nothing" alternative and its true costs
Assess country-specific factors that influence CBDC viability
In the rush to announce CBDC initiatives, central banks typically skip the most important question: Should we do this at all?
- Expensive (hundreds of millions to develop and operate)
- Risky (technical failures, adoption failures, reputational damage)
- Disruptive (to banks, payment systems, monetary operations)
- Uncertain (no proven success model for retail adoption)
Yet the decision to proceed often happens without rigorous analysis. Political pressure ("other countries are doing it"), fear of missing out, and technology enthusiasm drive many CBDC initiatives—not evidence-based assessment of whether CBDC actually solves a problem worth solving.
This lesson provides the framework for making that decision properly.
Consider: if 137 countries are exploring CBDCs but only 3 have launched (with poor results), perhaps the right decision for most countries is not to proceed. That's a legitimate strategic choice—one that saves resources for higher-value initiatives.
The framework presented here doesn't assume CBDC is desirable. It helps decision-makers determine whether it is.
Every CBDC go/no-go decision should answer four questions in sequence:
CBDC DECISION FRAMEWORK
QUESTION 1: WHAT PROBLEM ARE WE SOLVING?
├── Is there a specific, articulated problem?
├── Is the problem significant (affects many people, large economic impact)?
├── Is the problem real (based on evidence, not assumption)?
└── If no clear problem → STOP (don't proceed)
QUESTION 2: CAN EXISTING SOLUTIONS SOLVE THIS PROBLEM?
├── Can private sector innovation address it?
├── Can regulatory intervention address it?
├── Can fast payment systems (non-CBDC) address it?
├── Can improved cash distribution address it?
└── If existing solutions adequate → STOP (CBDC unnecessary)
QUESTION 3: DO WE HAVE THE PREREQUISITES?
├── Digital identity infrastructure?
├── Telecommunications coverage?
├── Functioning banking system?
├── Legal framework capacity?
├── Technical expertise (or ability to acquire)?
├── Multi-year political commitment?
├── Adequate budget?
└── If missing 2+ prerequisites → STOP (not ready)
QUESTION 4: IS THE RISK/REWARD ACCEPTABLE?
├── What's the probability of success?
├── What's the cost of failure?
├── What's the opportunity cost?
├── What are the systemic risks?
└── If risk/reward unfavorable → STOP (pursue alternatives)
Most failed CBDC projects skipped one or more of these questions. They proceeded because "other countries are doing it" or because the technology seemed exciting—not because they had a clear problem with a clear CBDC solution.
The single most important predictor of CBDC success is whether it solves a genuine problem. This requires brutal honesty.
Strong Motivations (Evidence-Based):
FINANCIAL INCLUSION
├── Definition: Large unbanked population lacking access to financial services
├── Evidence required:
│ ├── Unbanked rate >20-30%
│ ├── Geographic/infrastructure barriers to banking
│ ├── Demonstrated demand for financial services
│ └── Existing solutions inadequate (mobile money not working)
├── Why CBDC might help:
│ ├── Lower KYC requirements for small amounts
│ ├── No bank account needed
│ └── Government-backed (theoretically trusted)
├── Reality check:
│ ├── Mobile money (M-Pesa) solved this in Kenya without CBDC
│ ├── Private fintechs serving unbanked profitably
│ └── CBDC still requires smartphone/connectivity
└── Strength as motivation: MEDIUM-HIGH (but alternatives exist)
PAYMENT SYSTEM RESILIENCE
├── Definition: Current payment infrastructure has single points of failure
├── Evidence required:
│ ├── Historical outages with economic impact
│ ├── Concentration risk in payment providers
│ └── Inadequate disaster recovery
├── Why CBDC might help:
│ ├── Alternative payment rail
│ ├── Government-controlled fallback
│ └── Potentially offline capability
├── Reality check:
│ ├── Multiple payment rails usually exist
│ ├── Resilience can be built into existing systems
│ └── CBDC adds new failure modes, not just redundancy
└── Strength as motivation: MEDIUM (usually better alternatives)
DECLINING CASH USAGE
├── Definition: Cash usage falling to levels threatening public money access
├── Evidence required:
│ ├── Cash transactions <15-20% and declining
│ ├── Bank branches/ATMs closing
│ └── Population segments losing access to payments
├── Why CBDC might help:
│ ├── Digital equivalent of cash
│ ├── Central bank liability (unlike private digital)
│ └── Accessible without bank account
├── Reality check:
│ ├── Sweden has 8% cash usage without CBDC crisis
│ ├── Private digital payments working for most
│ └── Those wanting cash often don't want digital
└── Strength as motivation: MEDIUM (real but overstated)
PRIVATE STABLECOIN THREAT
├── Definition: Private stablecoins gaining scale that threatens monetary sovereignty
├── Evidence required:
│ ├── Significant stablecoin usage domestically
│ ├── Currency substitution concerns
│ └── Regulatory gaps for stablecoins
├── Why CBDC might help:
│ ├── Government alternative to private digital currency
│ ├── Maintains central bank money relevance
│ └── Counter to dollar/stablecoin dominance
├── Reality check:
│ ├── Stablecoin regulation can address concerns
│ ├── CBDC competing with stablecoins is unproven
│ └── Users choose stablecoins for reasons CBDC may not solve
└── Strength as motivation: MEDIUM-HIGH (legitimate concern)
CROSS-BORDER PAYMENT EFFICIENCY
├── Definition: International payments slow, expensive, opaque
├── Evidence required:
│ ├── High remittance dependence
│ ├── Documented costs/delays
│ └── Economic impact of inefficiency
├── Why CBDC might help:
│ ├── Direct central bank to central bank settlement
│ ├── Faster finality
│ └── Lower intermediary costs
├── Reality check:
│ ├── Requires bilateral/multilateral agreements
│ ├── FX and compliance complexity remains
│ └── Correspondent banking improving (SWIFT gpi)
└── Strength as motivation: HIGH for wholesale, MEDIUM for retail
Weak Motivations (Often Lead to Failure):
"OTHER COUNTRIES ARE DOING IT"
├── Definition: Proceeding because of perceived peer pressure
├── Why it's weak:
│ ├── Other countries may be making mistakes
│ ├── Contexts differ dramatically
│ └── Following failure is still failure
├── Red flags:
│ ├── Can't articulate specific domestic problem
│ ├── References "global trend" rather than local need
│ └── Timeline driven by announcements, not readiness
└── Outcome prediction: High probability of stalled/abandoned project
BLOCKCHAIN/INNOVATION SIGNALING
├── Definition: Wanting to appear technologically progressive
├── Why it's weak:
│ ├── Innovation theater, not problem-solving
│ ├── Technology is means, not end
│ └── "Innovative" failures are still failures
├── Red flags:
│ ├── Heavy emphasis on technology features
│ ├── Little discussion of user benefits
│ └── Press release before feasibility study
└── Outcome prediction: Pilot that goes nowhere
COUNTERING CRYPTOCURRENCY
├── Definition: Responding to crypto with government alternative
├── Why it's weak:
│ ├── Crypto users want decentralization (CBDC is opposite)
│ ├── Crypto speculation not solved by CBDC
│ └── Different problems, different solutions
├── Red flags:
│ ├── Framing CBDC as "anti-crypto"
│ ├── Assuming crypto users will switch
│ └── No analysis of why people use crypto
└── Outcome prediction: Fails to capture target users
POLITICAL PRESSURE WITHOUT ANALYSIS
├── Definition: Leadership demands CBDC without clear rationale
├── Why it's weak:
│ ├── Political timelines ≠ implementation timelines
│ ├── Announcement ≠ achievement
│ └── Next administration may cancel
├── Red flags:
│ ├── Announcement before internal analysis
│ ├── Unrealistic timelines (months not years)
│ └── No sustained budget commitment
└── Outcome prediction: Announcement, then quiet abandonment
Before committing to CBDC, rigorously evaluate alternatives:
ALTERNATIVE EVALUATION MATRIX
ALTERNATIVE 1: FAST PAYMENT SYSTEMS
├── Examples: FedNow (US), UPI (India), Pix (Brazil), TIPS (EU)
├── What they solve:
│ ├── Real-time payments
│ ├── 24/7 availability
│ ├── Low-cost transfers
│ └── Instant settlement
├── What they don't solve:
│ ├── Not central bank money (bank deposits)
│ ├── No offline capability
│ └── Require bank account
├── CBDC advantage over this: Limited for most users
└── Countries where this is sufficient: Most developed economies
ALTERNATIVE 2: MOBILE MONEY REGULATION
├── Examples: M-Pesa (Kenya), bKash (Bangladesh), GCash (Philippines)
├── What they solve:
│ ├── Financial inclusion for unbanked
│ ├── Low-cost digital payments
│ ├── Agent network for cash in/out
│ └── Works on basic phones
├── What they don't solve:
│ ├── Private company (not central bank liability)
│ ├── Concentration risk
│ └── Cross-border complexity
├── CBDC advantage over this: Marginal (trust, stability)
└── Countries where this is sufficient: Most developing economies
ALTERNATIVE 3: STABLECOIN REGULATION
├── Examples: EU MiCA framework, Singapore regulations
├── What they solve:
│ ├── Private digital currency oversight
│ ├── Reserve requirements
│ ├── Consumer protection
│ └── Systemic risk mitigation
├── What they don't solve:
│ ├── Still private money
│ ├── Dollar-denominated (usually)
│ └── May not serve all populations
├── CBDC advantage over this: Monetary sovereignty
└── Countries where this is sufficient: Depends on policy goals
ALTERNATIVE 4: IMPROVED CASH DISTRIBUTION
├── Examples: ATM network expansion, cash back at retail
├── What they solve:
│ ├── Access to central bank money
│ ├── Financial inclusion (no tech required)
│ ├── Privacy
│ └── Offline by definition
├── What they don't solve:
│ ├── Cost of physical distribution
│ ├── Security concerns
│ └── Declining relevance in digital economy
├── CBDC advantage over this: Digital efficiency
└── Countries where this is sufficient: Those with privacy priority
Decision Rule: If any alternative adequately solves the identified problem at lower cost/risk than CBDC, pursue the alternative.
Even with a clear problem and no adequate alternatives, CBDC requires certain prerequisites. Missing multiple prerequisites strongly predicts failure.
CBDC PREREQUISITES CHECKLIST
- DIGITAL IDENTITY INFRASTRUCTURE
Why required: CBDC needs user identification
If missing: Cannot meet compliance requirements
Remediation time: 2-5 years
- TELECOMMUNICATIONS COVERAGE
Why required: CBDC is digital
If missing: Large population excluded
Remediation time: 3-7 years
- FUNCTIONING BANKING SYSTEM
Why required: Two-tier CBDC needs banks
If missing: One-tier adds enormous complexity
Remediation time: Varies (may not be fixable)
- LEGAL FRAMEWORK CAPACITY
Why required: CBDC needs legal basis
If missing: Legitimacy and liability unclear
Remediation time: 2-4 years
- TECHNICAL CAPACITY
Why required: CBDC is technology
If missing: Dependent on external parties
Remediation time: 1-3 years (can be bought)
- POLITICAL COMMITMENT
Why required: CBDC takes 4-6+ years
If missing: Project dies with political change
Remediation time: Cannot be engineered
- ADEQUATE BUDGET
Why required: CBDC is expensive
If missing: Project underdelivers or stalls
Remediation time: Subject to fiscal constraints
```
- 7/7 prerequisites: Ready to proceed
- 5-6 prerequisites: Proceed with remediation plan
- 3-4 prerequisites: Delay until prerequisites addressed
- <3 prerequisites: Do not proceed
Beyond universal prerequisites, certain country characteristics influence CBDC viability:
COUNTRY CHARACTERISTIC IMPACT ON CBDC
POPULATION SIZE
├── Large (>50M): Higher complexity but more resources
├── Medium (5-50M): Balanced
├── Small (<5M): Limited resources, small network effects
└── Implication: Smaller countries should consider partnership/shared platforms
ECONOMIC DEVELOPMENT
├── Advanced: Existing solutions often adequate
├── Emerging: Potentially strong case for inclusion
├── Developing: Prerequisites often missing
└── Implication: Sweet spot may be emerging economies
BANKING SECTOR CONCENTRATION
├── Highly concentrated: Easier coordination, higher resistance
├── Fragmented: Harder coordination, less resistance
└── Implication: Work with banking structure, not against it
CASH USAGE LEVELS
├── High cash (>50%): Bigger change required
├── Medium cash (20-50%): Balanced
├── Low cash (<20%): Is CBDC needed?
└── Implication: Extremely low cash may not need CBDC
TRUST IN GOVERNMENT
├── High trust: Adoption possible
├── Low trust: Adoption very difficult
└── Implication: Cannot proceed without trust foundation
DIGITAL PAYMENT MATURITY
├── Advanced (UPI, Alipay level): CBDC competes with success
├── Developing: More room for CBDC
├── Limited: Infrastructure gaps
└── Implication: Mature markets have harder adoption case
```
The default option—not building a CBDC—deserves explicit analysis. It's not failure to act; it's a strategic choice.
"DO NOTHING" SCENARIO ANALYSIS
FOR DEVELOPED ECONOMIES:
Digital payments work well (cards, fast payments)
Banking access universal or near-universal
Cash available for those who want it
Payment innovation ongoing (private sector)
Private digital payments continue improving
Stablecoins may fill some niches
Cash continues slow decline
Financial system continues functioning
Loss of direct central bank money access: Low impact
Private stablecoin growth: Manageable with regulation
Being "behind" other countries: Mostly perception
Missing efficiency gains: Minimal for consumers
Probability-weighted assessment:
"Do nothing" cost: LOW
CBDC cost (development + risk): HIGH
Recommendation: Proceed only with clear use case
FOR DEVELOPING ECONOMIES WITH HIGH UNBANKED:
Large population without financial services
Cash-based informal economy
High remittance dependence
Limited banking infrastructure
Private sector may not serve unprofitable populations
Financial inclusion relies on mobile money
Remittance costs remain high
Informal economy persists
Financial inclusion slower: MEDIUM-HIGH impact
Remittance costs persist: MEDIUM impact
Monetary policy transmission limited: MEDIUM impact
Digital economy development delayed: MEDIUM impact
Probability-weighted assessment:
"Do nothing" cost: MEDIUM-HIGH
CBDC cost (development + risk): HIGH
Recommendation: Proceed if prerequisites met
```
Resources devoted to CBDC cannot be used elsewhere. Consider alternatives:
OPPORTUNITY COST ANALYSIS
CBDC DEVELOPMENT COST: $100-200M over 4-5 years
CBDC OPERATING COST: $20-50M annually ongoing
WHAT ELSE COULD THIS BUY?
ALTERNATIVE 1: Fast Payment System Upgrade
├── Cost: $30-50M
├── Timeline: 1-2 years
├── Impact: Real-time payments for all
└── Risk: Lower than CBDC
ALTERNATIVE 2: Financial Inclusion Programs
├── Cost: $50-100M
├── Timeline: 2-3 years
├── Impact: Agent banking, mobile money support
└── Risk: Proven models exist
ALTERNATIVE 3: Payment System Resilience
├── Cost: $20-40M
├── Timeline: 1-2 years
├── Impact: Redundancy, disaster recovery
└── Risk: Low
ALTERNATIVE 4: Regulatory Modernization
├── Cost: $10-20M
├── Timeline: 2-3 years
├── Impact: Better oversight, consumer protection
└── Risk: Low
QUESTION: Do any of these deliver more value
with higher probability of success?
Often the answer is yes.
Use this matrix to structure the go/no-go decision:
CBDC GO/NO-GO DECISION MATRIX
STEP 1: PROBLEM DEFINITION
┌─────────────────────────────────────────────────────────────┐
│ Problem statement: │
│ __________________________________________________________ │
│ │
│ Evidence supporting problem: │
│ __________________________________________________________ │
│ │
│ Population affected: ______ (number or %) │
│ Economic impact: $______ annually │
│ │
│ Problem score (1-10): ______ │
│ If <5, STOP HERE. Problem not sufficient to justify CBDC. │
└─────────────────────────────────────────────────────────────┘
STEP 2: ALTERNATIVE ASSESSMENT
┌─────────────────────────────────────────────────────────────┐
│ Alternative 1: ________________ │
│ Can it solve problem? Y/N Cost: $______ Time: ______ │
│ │
│ Alternative 2: ________________ │
│ Can it solve problem? Y/N Cost: $______ Time: ______ │
│ │
│ Alternative 3: ________________ │
│ Can it solve problem? Y/N Cost: $______ Time: ______ │
│ │
│ Best alternative identified: ________________ │
│ CBDC advantage over alternative: ________________ │
│ │
│ Alternative adequacy score (1-10): ______ │
│ If >7, STOP HERE. Alternatives sufficient. │
└─────────────────────────────────────────────────────────────┘
STEP 3: PREREQUISITES CHECK
┌─────────────────────────────────────────────────────────────┐
│ □ Digital identity (Yes/No/Partial) │
│ □ Telecom coverage (Yes/No/Partial) │
│ □ Banking system (Yes/No/Partial) │
│ □ Legal framework (Yes/No/Partial) │
│ □ Technical capacity (Yes/No/Partial) │
│ □ Political commitment (Yes/No/Partial) │
│ □ Budget (Yes/No/Partial) │
│ │
│ Prerequisites met: ____/7 │
│ If <5, STOP HERE. Not ready for CBDC. │
└─────────────────────────────────────────────────────────────┘
STEP 4: RISK/REWARD ASSESSMENT
┌─────────────────────────────────────────────────────────────┐
│ Estimated development cost: $______ │
│ Estimated annual operating cost: $______ │
│ Probability of success: ______% │
│ Potential benefit if successful: $______ │
│ Expected value: $______ (benefit × probability - costs) │
│ │
│ Reputational risk of failure (1-10): ______ │
│ Systemic risk (bank disintermediation) (1-10): ______ │
│ Political risk (1-10): ______ │
│ │
│ Risk-adjusted score: ______ │
│ If unfavorable, STOP HERE. Risk/reward not acceptable. │
└─────────────────────────────────────────────────────────────┘
FINAL DECISION
┌─────────────────────────────────────────────────────────────┐
│ □ PROCEED - All criteria met, clear value proposition │
│ □ DELAY - Prerequisites incomplete, revisit in __ years │
│ □ PURSUE ALTERNATIVE - _____________ instead of CBDC │
│ □ DO NOTHING - No compelling case for action │
│ │
│ Decision rationale: │
│ __________________________________________________________ │
│ __________________________________________________________ │
└─────────────────────────────────────────────────────────────┘
Good Decision Process: European Central Bank
ECB DIGITAL EURO DECISION PROCESS
PROBLEM DEFINITION (2019-2021):
├── Identified: Cash usage declining, private alternatives growing
├── Evidence: Eurozone payment data, consumer surveys
├── Quantified: Cash <50% of POS transactions, declining trend
└── Articulated: Public access to central bank money at risk
ALTERNATIVE ASSESSMENT:
├── Considered: Improved cash distribution
├── Considered: Stablecoin regulation
├── Considered: SEPA Instant expansion
└── Conclusion: Alternatives address some, not all concerns
PREREQUISITES CHECK:
├── Digital identity: Varied across eurozone, improving
├── Telecom: Strong across eurozone
├── Banking: Robust, concerned about disintermediation
├── Legal: Requires EU legislation (acknowledged)
├── Technical: Strong capacity
├── Political: Coalition building underway
├── Budget: Significant resources committed
└── Conclusion: Prerequisites largely met, legal process needed
RISK/REWARD:
├── Extensive public consultation
├── Bank disintermediation mitigation (holding limits, no interest)
├── Privacy-first design principles
├── Phased approach with gates
└── Conclusion: Proceed to preparation phase
TIMELINE:
├── Investigation: 2021-2023 (2 years)
├── Preparation: 2023-2025 (2 years)
├── Development: 2025+ (if approved)
├── Launch: 2026+ (earliest)
└── Total: 5+ years from start to launch
VERDICT: Methodical, evidence-based, stakeholder-inclusive
Poor Decision Process: [Composite Example]
POOR CBDC DECISION PROCESS
PROBLEM DEFINITION:
├── Stated: "Modernize the financial system"
├── Evidence: None specific
├── Quantified: Not attempted
└── Red flag: No articulated problem to solve
ALTERNATIVE ASSESSMENT:
├── Considered: Nothing explicitly
├── Assumption: CBDC is the answer
└── Red flag: Solution before problem
PREREQUISITES CHECK:
├── Skipped entirely
└── Red flag: Proceeding without foundation
TRIGGER FOR DECISION:
├── "Other countries are doing it"
├── "Presidential directive"
├── "Blockchain opportunity"
└── Red flag: External pressure, not internal analysis
TIMELINE:
├── Announcement to launch: 12 months
└── Red flag: Impossibly fast
OUTCOME:
├── Announcement generates publicity
├── Hasty vendor selection
├── Technical problems
├── Adoption failure
├── Quiet abandonment
└── Resources wasted, credibility damaged
VERDICT: Announcement-driven, evidence-free, doomed from start
Countries with populations under 5 million face unique challenges:
SMALL ECONOMY CBDC CHALLENGES
SCALE ECONOMICS
├── Fixed costs spread over fewer users
├── Network effects harder to achieve
├── Vendor attention lower (small market)
└── Implication: Higher per-capita cost
LIMITED RESOURCES
├── Small central bank staff
├── Limited technical expertise
├── Budget constraints
└── Implication: Heavy vendor dependence
NETWORK EFFECTS
├── Fewer users = less utility
├── Fewer merchants = limited use cases
├── Critical mass harder to achieve
└── Implication: May never achieve adoption
1. Regional CBDC (share with neighbors)
1. Platform-as-a-Service
1. Focused use case
1. Don't proceed
CBDCs require sustained commitment across political cycles:
POLITICAL CYCLE RISK
TIMELINE REALITY:
├── CBDC development: 3-5 years minimum
├── CBDC maturation: 5-10 years
├── Election cycles: 2-5 years
└── Gap: Projects outlast governments
RISK SCENARIOS:
Scenario 1: Change in government
├── New government cancels project
├── Resources wasted
├── Example: US CBDC halt (2025)
Scenario 2: Change in priorities
├── Same government, different focus
├── Funding redirected
├── Project zombified (not killed, not resourced)
Scenario 3: Leadership change at central bank
├── New governor, different vision
├── Project deprioritized
├── Momentum lost
- Build cross-party support before starting
- Establish independent governance structure
- Create stakeholder coalition (banks, merchants)
- Demonstrate early wins
- Maintain public communication
REALITY CHECK:
Political risk cannot be eliminated
Projects lasting 5+ years WILL face political transitions
Plan for continuity or don't start
---
✅ Most CBDC motivations are weak: "Other countries doing it," blockchain enthusiasm, and vague modernization goals do not justify the cost and risk of CBDC development.
✅ Alternatives often suffice: Fast payment systems, mobile money, and regulatory improvements address many problems attributed to CBDC need at lower cost.
✅ Prerequisites matter: Countries that skipped prerequisites assessment (Nigeria, various Caribbean nations) experienced failures.
✅ "Do nothing" is valid: For many countries, especially developed economies with functioning payment systems, not building a CBDC is a defensible strategic choice.
⚠️ Whether any retail motivation is strong enough: Even the strongest motivations (financial inclusion, declining cash) have not produced successful retail CBDC adoption anywhere.
⚠️ Whether prerequisites are sufficient: Countries meeting all prerequisites may still fail due to behavior change challenges.
⚠️ Whether political commitment can be sustained: Multi-year projects face inherent political risk that no framework fully mitigates.
🔴 Proceeding without clear problem: CBDC-as-solution-seeking-problem produces expensive failures.
🔴 Ignoring alternatives: Failure to evaluate fast payments, mobile money, and regulatory options wastes resources on unnecessary complexity.
🔴 Skipping prerequisites: Building on inadequate foundations produces technical or operational failures.
🔴 Underestimating political risk: Projects that cannot survive political transitions are unlikely to succeed.
Most countries exploring CBDC should probably not proceed. The combination of unclear problems, adequate alternatives, missing prerequisites, and political risk means that "do nothing" or "pursue alternative" is often the rational choice. The decision framework in this lesson isn't designed to generate "proceed" decisions—it's designed to generate correct decisions, which often means stopping.
Assignment: Apply the CBDC decision framework to three countries—one developed, one emerging, and one developing economy—producing a recommendation memo for each.
Requirements:
- One developed economy (e.g., Canada, Australia, South Korea, UK)
- One emerging economy (e.g., Brazil, Indonesia, Mexico, Thailand)
- One developing economy (e.g., Kenya, Vietnam, Bangladesh, Philippines)
Part 2: For Each Country, Complete:
What specific problems might CBDC address?
What evidence supports these problems?
Quantify the impact where possible
Score problem severity (1-10)
What alternatives exist? (fast payments, mobile money, etc.)
How well do they address identified problems?
What's the gap, if any, that only CBDC fills?
Score alternative adequacy (1-10)
Evaluate each prerequisite (7 total)
Identify gaps and remediation timelines
Score overall readiness (prerequisites met out of 7)
Estimate costs (development, operating)
Assess probability of success
Evaluate risks (technical, political, reputational)
Calculate expected value (qualitative is acceptable)
Clear recommendation: Proceed / Delay / Pursue Alternative / Do Nothing
Rationale for recommendation
If proceeding: What conditions must be met?
If not proceeding: What would change the recommendation?
Problem definition rigor (20%)
Alternative evaluation thoroughness (20%)
Prerequisites assessment accuracy (20%)
Risk/reward analysis quality (20%)
Recommendation clarity and defensibility (20%)
Time investment: 3-4 hours
Value: Demonstrates ability to apply structured decision-making to CBDC strategy, a skill directly applicable to central bank advisory work.
Knowledge Check
Question 1 of 5Motivation Assessment
- BIS CBDC decision guide publications
- IMF CBDC Handbook chapters on policy decisions
- World Bank CBDC assessment frameworks
- ECB Digital Euro documentation (good process example)
- Various central bank CBDC assessment reports
- IMF Article IV consultations discussing CBDC
- Fast payment system documentation (UPI, FedNow, Pix)
- Mobile money research (GSMA reports)
- CPMI reports on payment system development
For Next Lesson:
Lesson 3 addresses stakeholder mapping and engagement strategy. Even with a clear problem and met prerequisites, CBDC fails without stakeholder alignment—especially banks, who fear disintermediation. We'll develop the comprehensive stakeholder engagement framework.
End of Lesson 2
Total words: ~5,400
Estimated completion time: 55 minutes reading + 3-4 hours for deliverable
Key Takeaways
Problem definition is paramount
: Without a clear, evidence-based problem that CBDC uniquely solves, don't proceed. "Other countries are doing it" and "blockchain innovation" are not valid reasons.
Alternatives deserve rigorous evaluation
: Fast payment systems, mobile money, and regulatory improvements solve many problems attributed to CBDC need. Evaluate them honestly before committing to CBDC complexity.
Prerequisites are non-negotiable
: Digital identity, telecom infrastructure, banking system readiness, legal framework, technical capacity, political commitment, and budget must be in place. Missing two or more is a stop signal.
"Do nothing" has value
: The opportunity cost of CBDC investment is real. Resources spent on a failed CBDC could fund successful alternatives. Not proceeding is a legitimate strategic choice.
Political sustainability matters
: Projects lasting 5+ years face political transitions. Without cross-party support and institutional resilience, even well-designed CBDCs fail. ---