Digital Customers, Product Design and Financial Inclusion

Introduction and Context

Digital banking has changed the relationship between financial institutions and their customers. Customers may now open accounts, transfer funds, borrow, save, insure assets, and obtain advice through mobile applications, websites, agents, cards, and digital payment channels. However, access to a digital channel does not automatically produce a good customer experience or genuine financial inclusion. A service may be technically available but unusable because it requires an expensive smartphone, reliable connectivity, advanced literacy, a formal identity document, or confidence in digital security.

Digital banking therefore requires more than technology deployment. It requires systematic understanding of customer needs, careful product design, accessible user experiences, responsible data practices, and controls that protect consumers. This chapter examines how banking professionals can map customer journeys, apply design thinking and agile development, evaluate user experience, and design trustworthy services for diverse and underserved populations.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain the characteristics and needs of digital banking customers.
2. Construct and interpret a customer journey map.
3. Apply design-thinking principles to financial-service problems.
4. Describe agile product development and the minimum viable product.
5. Evaluate usability, accessibility, trust, and inclusion.
6. Identify consumer-protection, ethical, and governance requirements.
7. Recommend responsible digital banking services for underserved customers.

1. Understanding Digital Banking Customers

A digital customer is not simply a person who uses an application. The term includes any customer whose interaction with a financial institution is substantially supported by digital technology. This may involve a smartphone, USSD, an ATM, a point-of-sale terminal, an agent device, a web portal, a call-centre system, or an automated decision engine.

Customers differ in income, age, education, language, disability, location, digital confidence, connectivity, and exposure to financial services. A product designed for an urban smartphone user may exclude a rural customer using a basic phone. Similarly, a highly secure authentication process may become a barrier for a customer who lacks stable biometric recognition or cannot remember complex passwords.

Important customer characteristics include:

• Financial capability: knowledge and confidence in managing money and understanding financial products.
• Digital capability: ability to operate devices, applications, authentication tools, and digital-payment processes.
• Access conditions: availability of devices, electricity, mobile networks, data, agents, and appropriate identification.
• Risk perception: beliefs about fraud, privacy, errors, debt, and the reliability of financial institutions.
• Life context: employment, household responsibilities, migration, disability, emergencies, and income volatility.
• Channel preference: the customer’s preferred combination of branch, agent, application, phone, ATM, and human support.

A useful distinction is between a customer’s stated need and underlying need. A customer may request a faster transfer, but the underlying need may be certainty that rent will arrive on time. Another customer may ask for a loan, while the underlying need is to manage irregular cash flow without falling into excessive debt. Effective product design investigates the underlying problem rather than merely implementing the requested feature.

Customer Segmentation

Segmentation groups customers with sufficiently similar needs or behaviours to support appropriate service design. Useful segmentation variables include:

Segmentation must not become unfair exclusion. Institutions should avoid using irrelevant or discriminatory characteristics to deny service. A segment is useful when it improves understanding and service quality, not when it creates unjustified barriers.

2. Customer Journey Mapping

A customer journey is the sequence of experiences through which a customer attempts to achieve a goal. A journey map represents the customer’s actions, questions, emotions, channels, barriers, and opportunities across that sequence. It differs from a process map: a process map focuses on internal activities, whereas a journey map focuses on the customer’s perspective.

A typical digital-account-opening journey may include:

1. Becoming aware of the service.
2. Comparing alternatives.
3. Downloading or accessing the service.
4. Registering and proving identity.
5. Setting authentication credentials.
6. Making an initial deposit or transaction.
7. Receiving confirmation and support.
8. Continuing to use, complain about, or abandon the service.

Components of a Journey Map

A practical journey map normally records:

• Customer goal: what the customer is trying to achieve.
• Stages: major steps in the experience.
• Touchpoints: application screens, messages, agents, branches, websites, or calls.
• Customer actions: what the customer does at each stage.
• Questions and expectations: what the customer needs to know.
• Emotions and pain points: confusion, anxiety, confidence, delay, or satisfaction.
• Backstage processes: verification, fraud screening, settlement, and complaint handling.
• Measures: completion rate, time, error rate, abandonment, complaints, and cost.
• Improvement opportunities: changes that could reduce effort or risk.

The map should include both successful and failed journeys. Customers who abandon onboarding, repeat an action, contact support, or experience a failed payment often reveal more important design problems than customers who complete the process without difficulty.

Example: Mapping a Person-to-Person Transfer

Journey mapping should not be treated as a one-time workshop. It is a living management tool. Transaction data, call-centre records, usability tests, complaints, and interviews should be used to update it.

3. Design Thinking for Financial Services

Design thinking is a human-centred approach to solving complex problems. It is often described through five connected activities: empathise, define, ideate, prototype, and test. These activities are iterative rather than strictly linear.

Empathise

The institution investigates customers’ circumstances through interviews, observation, diary studies, usability tests, and analysis of service data. Ethical research requires informed participation, protection of personal information, appropriate compensation, and sensitivity to vulnerable groups.

Researchers should distinguish what customers say from what they do. A customer may report that a process is easy because they do not wish to criticise an interviewer, while observed behaviour shows repeated errors. Research should therefore combine qualitative and quantitative evidence.

Define

Research findings are converted into a precise problem statement. A strong problem statement identifies the user, context, need, and consequence. For example:

A market trader who receives irregular income needs a simple way to separate business money from household money because unpredictable cash flow makes it difficult to know whether stock can be replenished.

The statement avoids prematurely specifying a solution. “Build a budgeting application” is a solution proposal, not a problem definition.

Ideate

Teams generate multiple possible responses before selecting one. Ideas may include goals-based savings, reminders, sub-accounts, agent-assisted deposits, cash-flow summaries, or flexible payment dates. Ideas should be evaluated against customer value, feasibility, financial sustainability, risk, accessibility, and regulatory requirements.

Prototype

A prototype is a representation used to learn. It may be a paper screen, clickable interface, scripted agent interaction, service blueprint, or limited technical release. Prototypes should be sufficiently realistic to reveal errors but inexpensive enough to change.

Test

Testing examines whether intended users can understand and complete tasks. A test should define the task, recruit representative participants, observe behaviour, record errors, and avoid leading questions. Findings are used to revise the concept. Successful testing does not prove that a product is safe or commercially viable; it only provides evidence about the tested experience.

4. Agile Product Development

Agile development manages product work through short cycles, frequent feedback, and incremental delivery. A cross-functional team may include product managers, designers, developers, operations staff, compliance specialists, risk officers, and customer-support representatives.

A product backlog lists desired capabilities and improvements. A user story expresses a requirement from the user’s perspective, commonly in the form:

As a [type of user], I want [capability], so that [benefit].

For example: “As a customer with limited connectivity, I want to see whether a payment succeeded without repeating it, so that I do not make a duplicate payment.”

Acceptance criteria specify what must be true for the story to be accepted. They should cover not only the happy path but also errors, accessibility, security, auditability, and customer support.

Minimum Viable Product

A minimum viable product, or MVP, is the smallest product that can provide meaningful value while generating valid learning. It is not a careless or incomplete product. Core legal, safety, security, privacy, accessibility, and consumer-protection requirements are not optional features that can be postponed merely because the release is described as an MVP.

A practical development cycle is:

1. Identify a customer problem.
2. Form a testable hypothesis.
3. Prioritise a safe, limited service.
4. Build and test a prototype.
5. Release to a controlled group where appropriate.
6. Measure outcomes and unintended effects.
7. Improve, scale, pause, or withdraw the service.

Agile methods must operate within governance. Speed cannot justify weak change control, undocumented decisions, inadequate testing, or the release of products that customers cannot understand.

5. User Experience and Accessibility

User experience, or UX, includes the customer’s perceptions and responses before, during, and after interaction with a service. It includes usefulness, ease of use, efficiency, trust, clarity, reliability, and emotional confidence.

Common UX measures include:

• Task-completion rate.
• Time required to complete a task.
• Error and retry rate.
• Abandonment rate.
• Repeat-contact rate.
• Complaint volume and resolution time.
• Customer satisfaction or perceived effort.
• Successful use by different customer groups.

A single score cannot fully represent UX. A high satisfaction score may conceal customers who never completed onboarding. Metrics should therefore be interpreted by segment, channel, task, and outcome.

Accessibility

Accessibility means that people with different abilities can perceive, understand, navigate, and use a service. Relevant considerations include:

• Text that can be enlarged without losing meaning.
• Adequate colour contrast and non-colour indicators.
• Screen-reader-compatible labels.
• Clear focus order and keyboard operation where relevant.
• Captions and transcripts for audio or video.
• Plain language and local-language support.
• Sufficient time to read and complete tasks.
• Alternatives to biometrics when recognition fails.
• Support for customers with motor, visual, hearing, cognitive, or speech disabilities.
• Accessible physical agents, ATMs, and payment points.

Accessibility is broader than application design. An accessible application is of limited value if registration requires an inaccessible branch, customer support cannot handle speech or hearing differences, or agents discriminate against customers who need assistance.

Inclusive Design

Inclusive design begins with diverse users rather than designing for an assumed “average” customer. Testing should include people with low literacy, older people, people with disabilities, low-income customers, minority-language speakers, and customers using low-end devices or intermittent connectivity. Human assistance and alternative channels should remain available when automation is unsuitable.

6. Trust, Consumer Protection and Responsible Design

Trust is a condition for adoption and continued use. It is built through reliable performance, understandable communication, fair treatment, privacy protection, effective redress, and visible accountability.

Transparency and Informed Choice

Customers should receive clear information about fees, exchange rates, limits, interest, penalties, data use, eligibility, and the consequences of missed payments. Important information should not be hidden in lengthy terms and conditions. A confirmation screen should show the recipient, amount, total charge, and likely timing before an irreversible transaction is authorised.

Security and Fraud Protection

Security controls should be proportionate to risk and usable by legitimate customers. Relevant controls include strong authentication, transaction monitoring, device and session management, encryption, secure software development, staff training, and incident response. Customers should be warned that institutions will not request passwords or one-time codes through suspicious channels.

Security design must also handle errors fairly. If a transaction is delayed or duplicated, the customer needs a clear status, a reference number, and a route to resolution. A failed message must not encourage the customer to repeat a payment without explaining whether the first attempt reached the payment system.

Privacy and Data Governance

Responsible data governance includes purpose limitation, data minimisation, accuracy, retention controls, access restrictions, customer rights, and secure deletion where applicable. Consent should be meaningful and separate from confusing bundles of unrelated permissions. Institutions should explain automated decisions and provide a channel for review when a customer is rejected or restricted.

Fairness and Responsible Automation

Artificial intelligence and automated scoring can support fraud detection, service personalisation, credit assessment, and customer support. They can also reproduce historical discrimination, create opaque decisions, or disadvantage customers with limited digital records. Governance should include:

• A defined purpose and lawful basis.
• Data-quality and bias assessment.
• Human oversight for significant decisions.
• Monitoring for disparate outcomes.
• Explainable customer communication.
• Appeals and correction mechanisms.
• Security against manipulation and data leakage.

An automated decision should be evaluated by its real-world effect, not only by predictive accuracy. A model that reduces losses but wrongly excludes a large group may be unacceptable if less harmful alternatives exist.

7. Financial Inclusion and Exclusion Risks

Financial inclusion means that individuals and businesses can access and use useful, affordable, responsible financial services that meet their needs. Inclusion involves more than account ownership. It includes regular use, suitability, safety, affordability, and positive outcomes.

Barriers may be:

• Economic: fees, minimum balances, data costs, or expensive devices.
• Geographic: weak networks, distance from agents, or limited electricity.
• Documentation-related: lack of formal identity or address evidence.
• Capability-related: low literacy, low digital confidence, or unfamiliarity with finance.
• Social: gender restrictions, discrimination, language barriers, or lack of privacy.
• Trust-related: fear of fraud, hidden charges, or misuse of personal data.
• Design-related: inaccessible interfaces, complex authentication, or poor error recovery.

Designing Inclusive Services

An inclusive service may combine digital and human channels. Examples include:

• Low-bandwidth or USSD access for basic transactions.
• Agent networks for cash-in, cash-out, registration assistance, and education.
• Transparent, low-value accounts with proportionate requirements.
• Local-language instructions and voice support.
• Flexible authentication alternatives.
• Fee structures that are understandable and affordable.
• Small-value savings tools that support irregular income.
• Accessible complaint and dispute-resolution mechanisms.
• Offline or delayed-synchronisation capabilities where technically and safely possible.

Proportionality is important. Controls should manage genuine risks without excluding low-risk or low-income customers unnecessarily. Simplified onboarding must still comply with applicable identification, anti-money-laundering, and counter-terrorist-financing obligations.

8. Measuring Product Success Responsibly

A product should be assessed through a balanced scorecard rather than adoption alone. Useful dimensions include:

A basic completion rate can be calculated as follows:

The measure is meaningful only when “started journey” and “successfully completed” are defined consistently. It should be reported by customer segment and channel. A high overall rate may conceal a very low rate for customers using assistive technology or low-connectivity channels.

A complaint-resolution rate may be expressed as:

This does not measure whether the resolution was fair or satisfactory. Institutions should therefore combine quantitative measures with case reviews and customer feedback.

9. Applied Case: Inclusive Digital Savings for Market Traders

The following is an illustrative case, not a report of a named institution.

Background

A financial institution observes that many market traders hold transaction accounts but maintain low balances and frequently borrow at high cost before restocking. Traders receive income in small, irregular amounts and often mix household funds with business cash. Most use basic smartphones, while some rely on agents.

Problem

Interviews reveal that traders do not necessarily need a complex financial-planning application. They need a trusted and simple way to reserve money for stock, understand available business cash, and access help when a digital transaction fails. Some are concerned that automatic deductions might remove money needed for food or transport.

Analysis

Journey mapping identifies several pain points: account-opening language is too technical; savings goals require regular fixed contributions; the application does not work reliably during network interruptions; and confirmation messages do not clearly distinguish a successful transaction from a pending one. Women traders also report difficulty obtaining private time to complete lengthy registration processes.

The institution defines a design hypothesis: if traders can create flexible, labelled savings pockets with visible balances and clear withdrawal rules, then they will be more likely to reserve business funds without perceiving the service as an uncontrollable commitment.

Approach and Solution

The team develops a limited service with the following features:

1. A simple business-savings pocket that permits irregular deposits.
2. Plain-language explanations of access, fees, and withdrawal conditions.
3. Agent-assisted onboarding and a low-bandwidth channel.
4. A confirmation message showing amount, balance, status, and reference number.
5. Alternative authentication and assisted recovery.
6. A human complaint route for disputed or pending transactions.
7. Testing with traders using different devices, languages, ages, and abilities.

The service is piloted with a controlled group. The institution measures activation, repeated deposits, failed transactions, complaints, withdrawal patterns, and outcomes for customers using agents compared with those using the application.

Outcome

The pilot shows improved understanding of balances and fewer accidental repeat payments. However, some customers misunderstand the term “available balance,” and agent training is inconsistent. The institution revises the language, improves agent supervision, and delays wider deployment until complaint handling is reliable.

Learning Points

The case demonstrates that inclusion is a service-system issue, not merely an application feature. Customer research changed the problem definition; journey mapping exposed operational weaknesses; agile testing reduced the cost of correction; and responsible design required transparency, alternatives, human support, and measurement of harm as well as adoption.

10. Challenges and Limitations

Design methods have limitations. Customers may not accurately remember past behaviour, research participants may not represent non-users, and prototype success may not predict behaviour under financial stress. Journey maps can oversimplify complex household decisions. Agile teams may prioritise visible features over infrastructure, accessibility, or compliance. Metrics can create harmful incentives if employees are rewarded only for registrations or transaction volume.

Digital inclusion can also create new risks. Customers may become dependent on a single platform, lose access during outages, or be exposed to phishing and social engineering. Personalised marketing may encourage unnecessary borrowing. Data-driven targeting can reinforce exclusion. Institutions must therefore evaluate both intended benefits and unintended consequences.

11. Best-Practice Checklist

A responsible digital banking product should:

• Begin with a clearly evidenced customer problem.
• Include representative users in research and testing.
• Map the complete journey, including failure and complaint paths.
• State fees, risks, data use, and transaction status plainly.
• Design for low bandwidth, disability, language diversity, and human assistance.
• Build security, privacy, auditability, and consumer protection into the product from the start.
• Use agile iteration without bypassing governance.
• Monitor outcomes by customer segment.
• Provide effective redress and escalation.
• Test for exclusion, unfairness, fraud, and harmful financial outcomes.
• Retire or redesign services that cause unacceptable harm.

Chapter Summary

Digital banking product design begins with understanding customers in their real social, financial, and technological contexts. Customer segmentation supports relevant design, while customer journey mapping reveals actions, emotions, touchpoints, operational dependencies, and failure points. Design thinking provides an iterative human-centred process of empathising, defining, ideating, prototyping, and testing. Agile development converts validated learning into incremental releases, but speed must remain subject to security, privacy, accessibility, compliance, and consumer-protection controls.

User experience includes usefulness, clarity, reliability, effort, and trust. Accessibility requires services to be usable by people with different abilities, languages, devices, and levels of digital capability. Financial inclusion requires affordable, suitable, safe, and genuinely usable services, often combining digital channels with agents and human support. Responsible products provide transparency, secure authentication, privacy governance, fair automated decisions, effective complaints handling, and meaningful redress. Success should be measured through balanced indicators covering reach, usability, value, inclusion, safety, and sustainability rather than adoption alone.

Key Terms

Digital customer: A customer whose financial interaction is substantially supported by digital technology.

Customer journey: The sequence of experiences through which a customer attempts to achieve a goal.

Journey map: A visual or structured representation of customer actions, touchpoints, emotions, barriers, and opportunities.

Touchpoint: Any interaction between a customer and an institution or service.

Design thinking: An iterative, human-centred approach involving research, problem definition, ideation, prototyping, and testing.

Prototype: A representation used to learn about a proposed product or service.

Agile development: An incremental approach based on short cycles, collaboration, feedback, and continuous improvement.

Product backlog: A prioritised list of product requirements, improvements, and defects.

User story: A requirement expressed from the perspective of a user and the benefit sought.

Minimum viable product: The smallest safe product that provides value and generates valid learning.

User experience: The perceptions and responses arising from a customer’s interaction with a service.

Accessibility: The capacity of people with different abilities to perceive, understand, navigate, and use a service.

Inclusive design: Designing with and for diverse users rather than an assumed average user.

Financial inclusion: Access to and effective use of useful, affordable, suitable, and responsible financial services.

Consumer protection: Measures that promote fair treatment, transparency, privacy, security, and redress.

Redress: A remedy or resolution available to a customer who has suffered an error, loss, or unfair treatment.

Data minimisation: Collecting and retaining only the personal data necessary for a defined purpose.

Responsible automation: Use of automated systems with appropriate fairness, transparency, oversight, security, and appeal mechanisms.

Completion rate: The percentage of started journeys that are successfully completed under a defined measurement rule.

Service blueprint: A representation linking customer actions with front-stage interactions and backstage organisational processes.

Review Questions

Short Answer Questions

1. What is the difference between a customer journey map and an internal process map?
2. Name the five commonly used activities in design thinking.
3. Why should an MVP not postpone security and consumer-protection requirements?
4. Identify four barriers to financial inclusion.
5. What is the purpose of a complaint and redress mechanism?

Long Answer Questions

1. Explain how customer segmentation can improve digital banking product design while avoiding unfair exclusion.
2. Describe the stages of constructing and using a customer journey map for digital account opening.
3. Discuss the relationship between usability, accessibility, and trust in digital banking.
4. Explain how agile development can be governed responsibly in a regulated financial institution.
5. Discuss how privacy, fairness, and human oversight should be addressed when AI is used in financial services.

Analytical / Application Questions

1. A bank has a high overall account-registration rate but very low completion among older customers and customers using screen readers. Analyse possible causes and recommend a research and design response.
2. Design an inclusive digital savings service for customers with irregular income and intermittent connectivity. Specify channels, safeguards, measures, and complaint processes.
3. A payment application displays “transaction failed” even when the payment may be pending. Analyse the customer, operational, fraud, and consumer-protection risks, and propose an improved journey.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a customer journey map from an internal process map?

A. A journey map focuses on customer experience, while a process map focuses on internal activities.

B. A journey map contains only financial data, while a process map contains only customer emotions.

C. A journey map is used after launch, while a process map is used only before launch.

D. A journey map excludes failed interactions, while a process map includes them.

Correct Answer: A. A journey map focuses on customer experience, while a process map focuses on internal activities.

Question 2

Which design-thinking activity converts research findings into a clearly framed customer problem?

A. Ideate

B. Define

C. Prototype

D. Test

Correct Answer: B. Define

Question 3

Which feature is most appropriate for an inclusive digital banking service in a low-connectivity environment?

A. A high-resolution video tutorial required before every transaction

B. A low-bandwidth channel combined with clear transaction status messages

C. A requirement to use the newest smartphone operating system

D. A policy that removes all human support

Correct Answer: B. A low-bandwidth channel combined with clear transaction status messages

Question 4

An institution starts 2,000 customer journeys and 1,500 are completed successfully. What is the completion rate?

A. 25%

B. 50%

C. 75%

D. 80%

Correct Answer: C. 75%

Question 5

Which statement about a minimum viable product is correct?

A. It may omit legal and security controls until commercial success is proven.

B. It is the smallest safe product that provides value and generates learning.

C. It must contain every feature requested by customers.

D. It is a prototype that cannot be used by real customers.

Correct Answer: B. It is the smallest safe product that provides value and generates learning.

Question 6

Which practice best supports responsible automated credit decisions?

A. Using the model without monitoring after deployment

B. Hiding the decision reason to prevent customer questions

C. Providing oversight, fairness monitoring, explanations, and an appeal route

D. Using as many personal variables as possible regardless of relevance

Correct Answer: C. Providing oversight, fairness monitoring, explanations, and an appeal route

Question 7

Which measure most directly evaluates whether complaints are handled within the institution’s stated standard?

A. Resolution rate within the stated service standard

B. Number of application downloads

C. Average customer age

D. Total number of product features

Correct Answer: A. Resolution rate within the stated service standard

Question 8

Which is an example of accessibility rather than merely visual design?

A. Adding decorative animation to the home screen

B. Providing screen-reader labels and alternatives when biometric authentication fails

C. Increasing the number of promotional banners

D. Reducing the size of confirmation text

Correct Answer: B. Providing screen-reader labels and alternatives when biometric authentication fails

Question 9

Why should a payment service clearly distinguish a failed transaction from a pending transaction?

A. To encourage customers to repeat transactions immediately

B. To reduce the need for transaction records

C. To prevent duplicate payments and reduce uncertainty

D. To eliminate the need for complaint handling

Correct Answer: C. To prevent duplicate payments and reduce uncertainty

Question 10

Which outcome best represents financial inclusion?

A. A customer receives an account but cannot afford or use it safely

B. A service is available only through an expensive smartphone

C. Customers can access and effectively use suitable, affordable, safe financial services

D. A bank increases registrations without measuring customer outcomes

Correct Answer: C. Customers can access and effectively use suitable, affordable, safe financial services