Get the App

Chapter 9 of 9

Module 9: Practical Conversation Scenarios and Role-Plays

Apply what you’ve learned in realistic client scenarios across different industries and levels of blockchain maturity.

15 min readen

Step 1 – How This Practice Module Works

In this 15‑minute module, you will apply what you learned in Modules 7 and 8 to realistic client conversations about blockchain.

You will:

  • Walk through short, structured mock conversations with different client profiles
  • Practice adapting the depth of explanation to time limits and client knowledge
  • Learn to spot red flags and know when to recommend specialist advice (technical, legal, tax, compliance)
  • Practice closing conversations with clear, action‑oriented summaries

We will use scenario examples from:

  • Financial services (e.g., tokenization, stablecoins, DeFi)
  • Supply chain / provenance
  • SME owner thinking about accepting crypto or using blockchain
  • High‑net‑worth individual (HNI) with crypto and digital assets

> Throughout, remember the current landscape (as of early 2026):

> - Major regulations like the EU Markets in Crypto‑Assets Regulation (MiCA) started to apply in 2024–2025.

> - Many countries now have clearer rules on KYC/AML, stablecoins, and crypto taxation, but details vary by jurisdiction.

You will see scripts, decision prompts, and mini‑exercises you can reuse in your own practice.

Step 2 – A Simple Conversation Structure to Reuse

Before diving into role‑plays, anchor on a 4‑part structure (building on Module 7):

  1. Open & Frame (1–2 minutes)
  • Confirm the goal: “What would make this conversation useful for you?”
  • Timebox: “We have about 15 minutes; let’s focus on your top 1–2 questions.”
  1. Explore & Diagnose (5–8 minutes)
  • Ask open questions about:
  • Their business model / role
  • Their current pain points
  • Their experience with blockchain/crypto
  • Clarify constraints: time, budget, regulation, risk appetite.
  1. Respond & Co‑Design Options (5–10 minutes)
  • Connect one or two relevant blockchain use cases to their situation.
  • Use plain language and analogies (e.g., “shared spreadsheet that no one can secretly edit”).
  • Flag where specialist input is needed (e.g., MiCA compliance, tax treatment, smart contract audits).
  1. Close & Agree Next Steps (2–3 minutes)
  • Summarize: problem → options → key risks.
  • Propose 1–3 concrete next steps.
  • Confirm what you will do and what they will do.

You will now apply this structure to specific scenarios.

Step 3 – Scenario 1: Retail Bank Manager (Financial Services)

Scenario

You’re speaking with a product manager at a mid‑size retail bank. They’ve heard about tokenized deposits and stablecoins and want to know if the bank should “get into blockchain.” You have 15 minutes.

#### 1. Open & Frame (sample script)

> “Thanks for taking the time. In the next 15 minutes, what would you most like to understand about blockchain for your bank—payments, deposits, or something else?”

If they say: “We’re curious whether we should offer something like a stablecoin or tokenized deposits.”

You respond:

> “Great, let’s focus on how tokenized deposits and stablecoins work, what peers are doing, and the main regulatory and risk points you’d need to consider.”

#### 2. Explore & Diagnose – Key Questions

Ask 3–4 targeted questions:

  • Business goal: “What problem are you trying to solve—faster payments, lower costs, new products, or keeping up with competitors?”
  • Customer segment: “Is this more for retail customers, corporate clients, or internal treasury?”
  • Regulatory context: “Which jurisdictions do you operate in, and how closely are you following new crypto‑asset regulations like the EU’s MiCA or your local equivalent?”
  • Tech maturity: “Does your tech team already experiment with distributed ledgers, or would this be a first step?”

#### 3. Respond & Co‑Design (condensed explanation)

Use a simple, current explanation:

  • Tokenized deposits: “These are regular bank deposits represented as tokens on a ledger. They stay on your balance sheet and are regulated like normal deposits, but they can move more quickly between accounts or even across institutions that share a compatible network.”
  • Stablecoins: “These are usually tokens issued by non‑banks or banks, pegged to a currency like the euro or dollar. Under MiCA in the EU, they now face specific rules on reserves, governance, and disclosures.”

Then connect to their context:

> “Given you’re a regulated bank, tokenized deposits might align better with your existing license and risk controls, while offering some of the speed and programmability people associate with stablecoins.”

Flag specialist advice:

> “To move beyond experimentation, you’d need regulatory and legal input on how tokenized deposits fit your license, and a risk review on operational resilience and cybersecurity.”

#### 4. Close & Next Steps (sample closing)

> “Let me quickly recap: you’re exploring blockchain mainly to improve payment speed and stay competitive. We discussed tokenized deposits as a bank‑friendly way to experiment, and we noted that MiCA‑style rules and your local regulations will shape what’s possible.”

>

> “A practical next step could be: (1) run a small internal workshop with your product, compliance, and tech teams to map use cases; (2) identify one pilot, like tokenized internal transfers; and (3) bring in regulatory and legal experts to check alignment with your license. If you’d like, I can help design that workshop and prepare a short briefing on regulatory considerations.”

Step 4 – Practice: Tailoring Depth to Time and Knowledge

Imagine the same retail bank manager scenario, but with two variations.

Variation A – 5 minutes only, low technical knowledge

They say: “I only have 5 minutes and I’m not technical. Should we care about blockchain at all?”

Your task: Write 2–3 sentences that:

  1. Acknowledge the time limit
  2. Give one simple reason they should care
  3. Offer one clear next step

> ✍️ Pause and draft your 2–3 sentence response before reading further.

---

Variation B – 30 minutes, high technical knowledge

They say: “We’ve already built a proof‑of‑concept on a permissioned blockchain. I want to debate trade‑offs between public and private networks under current regulations.”

Your task: List 3 topics you would prioritize in that deeper conversation, given today’s environment (e.g., MiCA in the EU, stricter AML expectations, data protection rules like GDPR in Europe).

> ✍️ Write down your 3 topics. Think: interoperability, compliance, data privacy, custody, or on/off‑ramp risks.

After you’ve written your answers, compare them to this quick self‑check:

  • Did you adjust complexity (no jargon in A; more nuance in B)?
  • Did you respect the time constraint (1 key point in A; structured agenda in B)?
  • Did you include a specific next step in both cases?

Step 5 – Scenario 2: Supply Chain Manager (Provenance & Tracking)

Scenario

You’re meeting a supply chain manager at a food company. They’re under pressure from retailers and regulators to prove product origin and quality. They’ve heard about blockchain traceability platforms.

#### 1. Open & Frame

> “To make this useful, should we focus more on the business case for traceability, the technical architecture, or data and compliance issues like product recalls and audits?”

#### 2. Explore & Diagnose – Key Questions

  • Current process: “How do you track batches today—spreadsheets, ERP, specialized software?”
  • Pain points: “Where do errors, disputes, or delays typically occur?”
  • Stakeholders: “How many different organizations need to trust the data—farmers, logistics, distributors, retailers?”
  • Data sensitivity: “Are there trade secrets or personal data (e.g., small farmers’ identities) that must be protected?”

#### 3. Respond & Co‑Design (visual description)

Use a simple visual metaphor:

> “Imagine a shared, time‑stamped logbook that each participant writes to when they handle a batch: harvest, processing, shipping, storage, retail. No one can quietly rewrite old pages without everyone noticing.”

Then add nuance:

  • Blockchain does not guarantee truth of input data; it guarantees integrity of records once written.
  • You still need off‑chain controls: inspections, IoT sensors, audits.
  • For sensitive data, you can store hashes or references on‑chain and keep full data off‑chain.

#### 4. Red Flags & Specialist Advice

Call out red flags:

  • Data protection: If operating in or with the EU, consider GDPR (e.g., right to erasure vs. immutable ledgers).

→ Recommend data protection / privacy counsel.

  • Competition / antitrust: Sharing data among competitors may trigger antitrust questions.

→ Recommend competition law advice.

  • Vendor lock‑in & interoperability: Proprietary platforms that are hard to exit.

→ Involve technical architects to assess standards.

#### 5. Close & Next Steps (sample closing)

> “We’ve identified that your main problems are batch‑level visibility and dispute resolution with logistics partners. Blockchain can help create a shared, tamper‑evident record, but it doesn’t fix bad data or poor processes on its own.”

>

> “Next steps could be: (1) map a single high‑value product line and its data flows; (2) run a small pilot with 2–3 key partners; and (3) involve your legal/privacy team early to review data‑sharing and GDPR implications. I can help draft a one‑page pilot outline you can share internally.”

Step 6 – Quick Check: Spotting When to Call in Specialists

Use this quiz to test your ability to recognize when a client needs deeper expertise.

A supply chain client wants to store detailed supplier identities and quality certificates for EU farmers directly on a public blockchain. What is the MOST appropriate immediate response?

  1. Encourage them to proceed, since public blockchains improve transparency for all stakeholders.
  2. Explain that immutable public records may conflict with data protection rules (like GDPR) and recommend involving privacy/legal experts before designing the solution.
  3. Suggest encrypting all data and assure them that encryption alone fully solves any privacy concerns.
Show Answer

Answer: B) Explain that immutable public records may conflict with data protection rules (like GDPR) and recommend involving privacy/legal experts before designing the solution.

Option 2 is correct. Public, immutable storage of personal or sensitive data can conflict with data protection regimes such as GDPR (e.g., right to erasure, data minimization). You should flag this risk and recommend involving privacy/legal experts. Option 1 ignores regulatory risk; option 3 overstates what encryption can solve, since issues like lawful access, key management, and data minimization still apply.

Step 7 – Scenario 3: SME Owner & High‑Net‑Worth Individual

Part A – SME Owner Considering Crypto Payments

A small e‑commerce owner asks: “Should I accept crypto payments? My customers keep asking.”

#### Explore (3–4 questions)

  • “Where are your customers located?” (jurisdictions affect tax and regulation)
  • “What payment issues are you facing now—fees, chargebacks, access?”
  • “How comfortable are you with price volatility and managing wallets or exchanges?”
  • “Do you already have an accountant or tax advisor familiar with crypto?”

#### Respond (balanced overview)

  • Pros: access to some new customers; potentially lower fees; faster cross‑border settlement.
  • Cons: price volatility (unless using regulated stablecoins); operational risk (managing keys, scams); tax and accounting complexity (e.g., capital gains on conversions in many countries as of 2026).

Flag specialists:

> “Before implementing this, you should talk to your accountant or a tax advisor familiar with crypto in your country, and possibly your payment service provider or bank about compliance and reporting.”

Sample closing:

> “Given your size and current payment options, a low‑risk next step might be to pilot crypto payments only for a small product line, using a reputable payment processor that converts to fiat immediately. Let’s list 2–3 providers and questions you should ask them about fees, KYC/AML, and settlement.”

---

Part B – High‑Net‑Worth Individual (HNI) with Crypto Assets

A high‑net‑worth individual says: “I hold several million in crypto across exchanges and self‑custody. I want to optimize returns and minimize tax. What should I do?”

Your role is not to give financial, legal, or tax advice unless you are licensed and authorized.

Instead, you:

  1. Clarify goals & risk tolerance
  • “Is your priority long‑term preservation, yield, or speculative growth?”
  • “How comfortable are you with locking assets in DeFi protocols or lending platforms?”
  1. Outline risk categories (high level)
  • Custody risk: centralized exchanges vs. self‑custody; key management.
  • Counterparty & protocol risk: hacks, smart contract bugs, governance failures.
  • Regulatory & tax risk: treatment of staking, lending, and capital gains.
  1. Draw a clear boundary

> “I can help you understand the types of risks and questions to ask, but I can’t advise on specific investments or tax strategies. For that, you should speak with a licensed investment advisor and a tax specialist with up‑to‑date crypto experience in your jurisdiction.”

  1. Value‑add without overstepping
  • Help them prepare questions for their advisors (e.g., how MiCA‑style rules, local securities laws, or new tax guidance affect them).
  • Suggest they review exchange and custodian risk disclosures and consider diversification of custody.

This scenario trains you to recognize and respect professional boundaries while still being helpful.

Step 8 – Micro Role‑Play: Choosing Your Response

Read the client statement and choose how you would respond first.

Client statement

> “My friend made huge returns using DeFi protocols. I’m thinking of moving all my savings into similar platforms. You understand blockchain—can you tell me which protocols are safest and how to avoid tax?”

Task 1 – Draft your first sentence

Write one sentence that:

  • Acknowledges their interest
  • Gently sets expectations about your role

> ✍️ Example starter: “I’m glad you asked before making big moves, and I can explain the types of risks involved, but I can’t recommend specific investments or give tax advice.”

Task 2 – List 3 follow‑up questions you would ask to understand their situation (e.g., time horizon, risk tolerance, jurisdiction).

Self‑check: Did you…

  • Avoid promising specific investment or tax outcomes?
  • Offer value by discussing risk categories and questions rather than specific protocols?
  • Implicitly or explicitly recommend they speak to licensed professionals?

Step 9 – Closing Every Conversation with Clear Next Steps

A strong closing does three things:

  1. Summarizes the discussion in plain language
  • Problem → options → key risks/constraints.
  1. Assigns ownership
  • What you will do (e.g., send a summary, share resources, connect them with experts).
  • What they will do (e.g., talk to legal, gather internal data, decide on pilot scope).
  1. Confirms timing & boundaries
  • “I’ll send you a 1‑page summary by Friday.”
  • “For detailed tax implications, your next step is to meet with your tax advisor.”

---

Reusable 3‑sentence closing template

You can adapt this template in almost any blockchain‑related conversation:

> 1. Recap: “To recap, you’re mainly trying to [business goal], and we explored [option A] and [option B] using blockchain, along with key risks around [regulation / data / security].”

> 2. Next steps: “Your next steps are to [client actions], while I will [your actions].”

> 3. Boundary & timing: “For deeper questions on [legal / tax / investment], the right people to speak with are [type of specialist]; I’ll send you a short summary and resource list by [time].”

Practice filling this in for one scenario from earlier (bank manager, supply chain manager, SME owner, or HNI).

Step 10 – Quick Term & Skill Review

Flip the cards (mentally) to review key ideas before you finish.

Scenario-based practice
Using realistic client situations to rehearse conversations, apply frameworks, and build confidence in explaining blockchain opportunities, risks, and next steps.
Adapting depth of explanation
Adjusting how detailed and technical your explanation is based on the client’s knowledge, role, goals, and time constraints.
Red flag (in client conversations)
A signal that a topic goes beyond your expertise or authority (e.g., detailed tax planning, investment recommendations, complex regulatory interpretations) and requires a specialist.
Specialist advice (who to involve)
Technical architects, smart contract auditors, information security experts, regulatory/compliance officers, lawyers (e.g., MiCA/GDPR/antitrust), and tax or investment advisors, depending on the issue.
Action-oriented summary
A closing recap that clearly states what was discussed, key options and risks, and assigns concrete next steps with owners and (ideally) timelines.

Key Terms

KYC/AML
Know Your Customer / Anti-Money Laundering. Regulatory requirements that financial and many crypto service providers must follow to verify customer identities and monitor transactions for suspicious activity.
Stablecoin
A crypto-asset designed to maintain a stable value relative to a reference asset (often a fiat currency). Under modern regulations like MiCA, many stablecoins must meet strict reserve, governance, and disclosure requirements.
Tokenized deposit
A digital token on a ledger that represents a claim on a bank deposit. It remains on the bank’s balance sheet and is regulated like a traditional deposit, but can move and settle using blockchain infrastructure.
Smart contract audit
A security and correctness review of blockchain-based code by specialized auditors, aimed at identifying vulnerabilities, logical errors, and compliance issues before deployment.
Action-oriented closing
A conversation ending that summarizes key points, clarifies decisions or open questions, and specifies who will do what next, by when, often including referrals to specialists where needed.
Custody (of digital assets)
How crypto-assets are held and controlled, including who holds the private keys (user vs. custodian) and the associated security, legal, and operational risks.
DeFi (Decentralized Finance)
A set of financial services (lending, trading, derivatives, etc.) built on public blockchains using smart contracts, typically without traditional intermediaries. DeFi carries specific technical, market, and regulatory risks.
GDPR (General Data Protection Regulation)
The EU’s data protection framework, in force since 2018, which sets strict rules on personal data processing, including rights to access, rectify, and erase data—creating tensions with immutable blockchain records.
MiCA (Markets in Crypto-Assets Regulation)
A comprehensive EU regulation that began to apply from 2024 onward, creating a harmonized framework for crypto-asset issuance and service providers, including rules for stablecoins, disclosures, and licensing.
Traceability / provenance (in supply chains)
The ability to track the origin, movement, and transformation of goods through the supply chain. Blockchain can provide a tamper-evident record of events, but does not guarantee the truthfulness of input data.