Design Thinking and Human-Centred Innovation

Introduction

Entrepreneurial opportunities rarely begin with a complete product idea. They begin with an observation: a person is struggling, a process is inefficient, a service is inaccessible, or an important need is not being met. Design thinking provides a disciplined way to investigate these situations and develop solutions that are desirable to users, feasible to deliver and viable as a business.

Design thinking is an approach to innovation that combines empathy, problem investigation, creative generation of alternatives, experimentation and learning. It is not simply a process for making attractive products. It is a way of reducing uncertainty by studying real people and testing assumptions before committing substantial resources.

Human-centred innovation places people at the centre of analysis. It considers users, customers, employees, suppliers, regulators, communities and other stakeholders who may influence or be affected by a proposed solution. In entrepreneurship, this perspective is especially important because founders often begin with their own assumptions. A technically impressive solution may fail if it does not fit users’ behaviour, resources, culture or priorities.

Learning Objectives

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

1. Explain the meaning and value of design thinking and human-centred innovation.
2. Conduct basic empathy research using ethical qualitative methods.
3. Frame a broad situation as a focused, evidence-based problem statement.
4. Generate and select ideas using divergent and convergent thinking.
5. Build and test low-fidelity and higher-fidelity prototypes.
6. Use feedback and evidence to improve a proposed business solution.
7. Recognise ethical, practical and commercial limitations of design thinking.

1. Foundations of Design Thinking

1.1 Meaning and purpose

Design thinking is a human-centred problem-solving approach that seeks to understand people, redefine problems and develop solutions through experimentation. It is particularly useful when the problem is complex, the solution is uncertain and stakeholder needs are not fully understood.

A design-thinking project normally moves through five connected activities:

• Empathise: learn about stakeholders’ experiences, needs and constraints.
• Define: synthesise evidence into a clear opportunity or problem statement.
• Ideate: generate a wide range of possible responses.
• Prototype: create a representation that makes an idea tangible.
• Test: obtain evidence from stakeholders and revise the idea.

These activities should not be understood as a rigid, one-way sequence. Testing may reveal that the original problem was misunderstood, requiring further empathy research. Prototyping may expose a technical constraint that changes the definition of the problem. The process is therefore iterative.

1.2 Human-centred innovation and business opportunity

Human-centred innovation differs from product-centred thinking. Product-centred thinking asks, “What can we make?” Human-centred thinking asks, “What are people trying to accomplish, and what prevents them from doing it effectively?” This distinction helps entrepreneurs avoid developing solutions in search of a problem.

A promising opportunity commonly has three characteristics:

A fourth consideration is increasingly important: responsibility. A solution should not create unacceptable harm, exclusion, privacy risks or environmental damage merely because it is desirable and profitable.

1.3 Theories and influences

Design thinking draws on several traditions:

• Design practice: designers learn by making and revising rather than relying only on abstract planning.
• Systems thinking: a problem is examined within relationships among people, institutions, technologies and environments.
• Participatory design: affected stakeholders contribute to defining problems and shaping solutions.
• Lean experimentation: uncertain assumptions are tested with small, rapid experiments.
• Reflective practice: practitioners examine what they did, what they learned and how their assumptions influenced decisions.

The approach is compatible with business-model planning. Research may reveal a more specific customer segment; prototyping may clarify the value proposition; testing may challenge assumptions about channels, revenue or key activities.

2. Empathy Research

2.1 What empathy means in innovation

Empathy research is the systematic effort to understand stakeholders’ experiences from their perspective. It does not mean agreeing with every opinion or attempting to imitate another person’s life. It means investigating what people do, feel, value and struggle with in a particular context.

Researchers should distinguish among:

• Declared needs: what people say they want.
• Observed behaviour: what people actually do.
• Latent needs: needs that people may not articulate because they have adapted to an unsatisfactory situation.
• Constraints: limitations involving time, money, skills, infrastructure, trust, culture or regulation.

For example, commuters may say they want a cheaper transport service, but observation may show that reliability and safety matter more than the lowest price.

2.2 Selecting research methods

No single method provides a complete picture. Suitable diploma-level methods include:

A semi-structured interview uses prepared themes but allows the participant to explain unexpected issues. Useful questions are open, specific and non-leading. “Tell me about the last time you handled this task” is generally more useful than “Would you use our proposed app?”

2.3 Planning an interview

A practical interview plan should specify:

1. The learning purpose: what uncertainty must be reduced?
2. The participant criteria: who has relevant experience?
3. Recruitment and consent procedures.
4. Topics and prompts rather than a rigid script.
5. Recording, storage and confidentiality arrangements.
6. The intended method of analysis.

Participants should understand the purpose of the research, how information will be used, whether participation is voluntary and whether they may withdraw. Sensitive information should not be collected unless it is necessary and appropriately protected.

2.4 Avoiding research bias

Entrepreneurs may unconsciously seek evidence that confirms their preferred idea. Common sources of bias include:

• asking leading questions;
• recruiting only friends or enthusiastic supporters;
• interpreting politeness as purchase intention;
• focusing on dramatic stories rather than recurring patterns;
• ignoring users who reject the proposed concept;
• treating a small convenience sample as representative of the entire market.

A useful discipline is to separate observation, interpretation and assumption. For example:

• Observation: “Four of six participants used a paper notebook to record stock.”
• Interpretation: “Digital stock tools may be inconvenient in their current setting.”
• Assumption: “A mobile tool would be adopted if it were simple and affordable.”

The third statement requires testing; it is not a research finding.

2.5 Synthesising findings

After research, raw notes should be organised into patterns. Common tools include:

• Affinity mapping: grouping observations that appear related.
• Persona: a carefully evidenced representation of a user type; it should not be a fictional stereotype.
• Journey map: a sequence of stages showing actions, thoughts, emotions, barriers and opportunities.
• Empathy map: a structured summary of what a stakeholder says, does, thinks and feels.
• Insight statement: an interpretation linking an observed behaviour to an underlying need or tension.

A useful insight explains more than a preference. For example: “Small food vendors avoid digital stock systems not because they reject technology, but because existing systems interrupt fast-paced work and require reliable connectivity.”

3. Defining the Right Problem

3.1 From symptoms to underlying problems

A symptom is an observable difficulty; a problem statement explains the unmet need without prematurely prescribing a solution. “Customers need a mobile application” is a solution assumption. “Customers need a faster and more trustworthy way to confirm delivery times” is a problem-oriented statement.

A strong problem frame is:

• based on evidence;
• focused on a specific stakeholder and context;
• broad enough to allow several solutions;
• narrow enough to guide action;
• free from an assumed technology or business model.

One useful structure is:

[Stakeholder] needs a way to [desired outcome] because [evidence-based insight], while [important constraint] must be considered.

3.2 “How might we?” questions

A “How might we?” question converts a problem into an invitation to explore. For example:

How might we help independent vendors check stock quickly during busy periods without requiring continuous internet access?

The wording should avoid embedding a particular answer. “How might we build a barcode app?” limits exploration too early, whereas “How might we reduce stock-recording effort?” permits paper, service, training, software or hybrid ideas.

3.3 Prioritising problems

When research identifies many needs, entrepreneurs can compare them using criteria such as severity, frequency, number of affected people, willingness to change, strategic fit, feasibility and ethical significance. These criteria should support judgement rather than create false numerical precision. A scoring matrix can make assumptions visible, but scores are not objective facts unless supported by reliable evidence.

4. Ideation and Concept Development

4.1 Divergent and convergent thinking

Divergent thinking expands the range of possibilities. Convergent thinking narrows options using evidence and criteria. Effective innovation alternates between the two. Premature evaluation can suppress creative possibilities, while endless ideation can delay learning and action.

Useful ideation techniques include:

• brainstorming with a clear problem frame;
• brainwriting, where participants record ideas independently;
• “What if?” prompts;
• analogy, using solutions from another industry;
• SCAMPER: substitute, combine, adapt, modify, put to another use, eliminate and rearrange;
• co-creation workshops with stakeholders;
• worst-possible-idea exercises to expose hidden assumptions.

A rule such as “defer judgement during generation” does not mean that every idea should eventually be implemented. Evaluation occurs after a sufficiently broad set of alternatives has been produced.

4.2 Selecting concepts

Concept selection should consider stakeholder value, evidence, feasibility, cost, risk, inclusiveness, environmental consequences and fit with the intended business model. A concept may be attractive but difficult to deliver; another may be feasible but irrelevant to users.

Before selecting a concept, teams should describe it clearly:

• target stakeholder and context;
• problem addressed;
• proposed experience or outcome;
• major activities and resources;
• assumptions requiring testing;
• possible revenue or funding logic.

The selected concept is not a final decision. It is a learning proposition.

5. Prototyping

5.1 Purpose of prototypes

A prototype is an intentionally incomplete representation used to learn. It may be a sketch, paper interface, role-play, storyboard, physical model, service script, landing page, spreadsheet or manual “concierge” service. The appropriate prototype depends on the uncertainty being investigated.

A prototype should answer a question. Examples include:

• Will users understand the proposed sequence?
• Which information do they need first?
• Will they trust this service provider?
• Can the process be completed within an acceptable time?
• Will a customer pay, subscribe, refer others or change behaviour?

5.2 Fidelity and cost

Low-fidelity prototypes are quick and inexpensive. They are suitable for exploring structure, language and workflow. High-fidelity prototypes resemble the proposed product more closely and are useful for testing interaction, performance or credibility, but they require more time and may cause stakeholders to focus on cosmetic detail.

A prototype should be only as detailed as necessary to obtain useful evidence. Building a complete application before testing whether the problem matters is usually poor entrepreneurial practice.

5.3 Service prototyping

Many entrepreneurial offerings are services rather than physical products. Service prototypes may include:

• a customer journey storyboard;
• a role-play between customer and provider;
• a service blueprint showing front-stage and back-stage activities;
• sample messages and forms;
• a manual process that imitates a future automated system.

Service blueprints can reveal failures that a customer interface conceals, such as unclear staff responsibilities, unavailable data or unrealistic response times.

6. Testing and Iteration

6.1 Testing as learning

Testing is not a sales presentation. The purpose is to discover whether the prototype supports the intended user outcome and to identify barriers. Participants should be asked to perform realistic tasks where possible. Their behaviour, hesitation, questions and workarounds may be more informative than general statements of approval.

A basic test cycle is:

1. State the assumption.
2. Define observable evidence.
3. Prepare the smallest credible test.
4. Conduct the test with appropriate participants.
5. Record findings without over-interpreting them.
6. Decide whether to persevere, modify, narrow, combine or abandon the concept.

For example, an assumption may be: “First-time users can schedule a collection without assistance.” Evidence might include task completion, errors, time taken and requests for help. The entrepreneur must define in advance what result would justify revision.

6.2 Feedback quality

Useful feedback is specific, contextual and connected to behaviour. “I like it” is weak evidence of adoption. Better questions include:

• What would you do next?
• What part was confusing?
• What would prevent you from using this in real life?
• What do you use currently?
• What would you stop doing if this existed?

Testing should include non-users, sceptical users and stakeholders involved in delivery. A solution can satisfy the direct customer while creating unacceptable workload for employees or suppliers.

6.3 Iteration and pivoting

Iteration means improving a concept in response to evidence. A pivot is a substantial change in one or more core assumptions, such as the customer segment, problem, value proposition, channel or revenue model. Iteration should not become endless modification without a clear learning objective. Teams should maintain a decision log showing evidence, interpretation and the resulting change.

7. Integrating Design Thinking with Business Model Planning

Design thinking contributes evidence to business-model decisions. Research helps define customer segments and their jobs, pains and desired gains. Prototypes test elements of the value proposition. Service experiments reveal key activities, partners and resources. Payment or commitment tests provide stronger evidence for revenue assumptions than compliments alone.

A business model should therefore be treated as a set of hypotheses. Examples include:

The aim is not to prove every statement with absolute certainty. It is to reduce the most consequential uncertainties before major investment.

8. Illustrative Case: FreshRoute Market Service

The following is a fictional illustrative case.

Background

FreshRoute is a proposed service for small urban food vendors who purchase fresh produce from wholesale markets. The founding team initially planned a mobile application that would allow vendors to compare prices and place orders.

Problem investigation

The team interviewed eight vendors, observed purchasing activity at two markets and spoke with three delivery drivers. Vendors frequently changed orders because prices and availability shifted during the morning. Several used messaging applications, but many had unreliable data connections. The central difficulty was not merely finding prices; it was making quick, trustworthy purchasing decisions while serving customers.

The team recorded the following evidence:

• vendors valued reliable availability more than a long list of suppliers;
• purchasing decisions were often made under time pressure;
• some vendors preferred voice messages or trusted personal contacts;
• delivery coordination created additional uncertainty;
• participants were interested in the outcome but did not request a complex application.

Problem frame

The team reframed the opportunity as follows:

Small food vendors need a fast and trustworthy way to confirm available produce and coordinate delivery during busy purchasing periods, despite variable connectivity and changing prices.

This frame allowed non-digital and hybrid solutions to remain possible.

Ideation and prototype

The team generated concepts including a full marketplace, a daily SMS bulletin, a verified supplier group, a call-centre ordering service and a hybrid system combining messaging with a human coordinator. It created a low-fidelity service prototype: vendors sent a structured message, a coordinator confirmed availability by phone, and a driver provided a delivery window.

Testing

Six vendors used the service for one week. Four completed repeat orders. Two stopped using it because the delivery window was too uncertain. Interviews showed that vendors preferred a smaller list of verified products over a large catalogue. The team therefore changed the service promise from “compare every market price” to “secure reliable availability and delivery for selected high-demand items.”

Outcome

The prototype did not prove long-term profitability, but it reduced two important uncertainties: whether vendors would delegate purchasing information to the service and whether a human-supported process could fit their workflow. The team still needed to test supplier economics, delivery costs, pricing and operational capacity.

Learning points

1. The initial product idea was not the same as the underlying need.
2. Observation revealed time pressure and connectivity constraints that interviews alone might have missed.
3. A low-technology prototype produced valuable evidence.
4. User enthusiasm was less informative than repeat behaviour.
5. The revised value proposition was narrower but more credible.

9. Ethics, Inclusion and Governance

Human-centred innovation creates responsibilities as well as opportunities. Entrepreneurs should consider the following:

Consent and privacy

Participants should provide informed consent. Personal information should be collected only for a legitimate purpose, stored securely and retained for an appropriate period. Recordings and quotations should be anonymised where possible.

Vulnerable stakeholders

Children, people with disabilities, economically dependent workers and marginalised communities may require adapted recruitment, communication and consent procedures. Their participation should not become tokenistic or extractive.

Accessibility and inclusion

A solution should be tested across relevant differences in language, literacy, disability, income, age, gender, location and access to devices or connectivity. Designing for a typical user can exclude those with the greatest need.

Power and representation

Researchers often control how stakeholder experiences are interpreted. Teams should explain how findings were synthesised and avoid presenting a few voices as representative of an entire community. Where feasible, stakeholders should be invited to review interpretations.

Algorithmic and AI systems

Artificial intelligence may support transcription, pattern finding, translation, ideation or prototype generation. However, AI-generated summaries can omit context, reproduce bias or expose confidential information. Human review is essential. Teams should not upload identifiable interview data to tools that do not provide appropriate privacy protections. If an AI-enabled product affects access to credit, employment, healthcare or essential services, fairness, explainability, accountability and regulatory requirements require particular attention.

10. Challenges and Limitations

Design thinking is valuable but not automatically successful. Important limitations include:

• research with a small sample may miss market differences;
• users may describe aspirations rather than actual future behaviour;
• rapid workshops can oversimplify structural problems;
• creativity techniques do not guarantee commercially viable ideas;
• teams may prototype the visible interface while ignoring operations;
• iteration can consume resources without clear decision criteria;
• organisations may celebrate empathy language while retaining top-down decisions;
• some problems require policy, infrastructure or collective action rather than a new product.

Design thinking should therefore be combined with market analysis, technical assessment, financial planning, legal review and responsible governance. It is a method for improving judgement under uncertainty, not a substitute for judgement.

Best-Practice Checklist

Before progressing from an early concept, an entrepreneurial team should be able to answer:

• Who has the problem, and what evidence supports that claim?
• What do stakeholders currently do instead?
• Which constraints shape their behaviour?
• What assumption is the prototype intended to test?
• What observable result would change the team’s decision?
• Have relevant non-users and delivery stakeholders been included?
• Is the concept accessible, safe and ethically acceptable?
• What must be true for the business model to work?
• Which uncertainty should be tested next?

Chapter Summary

Design thinking is an iterative approach to innovation that begins with understanding stakeholders rather than assuming a product requirement. Its central activities are empathy, problem definition, ideation, prototyping and testing. These activities interact rather than follow a rigid linear sequence.

Empathy research combines interviews, observation and other methods to distinguish stated preferences from actual behaviour, latent needs and contextual constraints. Findings must be synthesised carefully, with observations separated from interpretations and assumptions. A strong problem frame identifies a stakeholder, desired outcome, evidence-based insight and relevant constraint without prescribing a solution.

Ideation uses divergent thinking to generate alternatives and convergent thinking to evaluate them. Prototypes make assumptions visible and should be designed around specific learning questions. Testing is strongest when it examines realistic behaviour and includes clear evidence criteria. Iteration and pivoting allow entrepreneurs to revise customer segments, value propositions, channels or operating assumptions.

Human-centred innovation supports business-model planning by providing evidence about customer needs, value propositions, delivery processes and willingness to commit. Ethical practice requires informed consent, privacy protection, inclusion, accessibility and responsible use of technology. Design thinking is not a guarantee of success; it must be combined with commercial, technical, financial and regulatory analysis.

Key Terms

Design thinking: A human-centred, iterative approach to understanding problems and developing solutions.

Human-centred innovation: Innovation guided by the experiences, needs and rights of affected stakeholders.

Empathy research: Investigation of stakeholders’ experiences, behaviours, motivations and constraints.

Latent need: An important need that a stakeholder may not explicitly articulate.

Contextual inquiry: Research combining observation with questions in the setting where an activity occurs.

Insight: An evidence-based interpretation that explains a meaningful behaviour or tension.

Affinity mapping: Grouping research observations to identify patterns.

Persona: An evidence-based representation of a relevant stakeholder type.

Journey map: A visual or written account of experiences across stages of an activity.

Problem frame: A focused description of an unmet need and its context.

How might we question: An open formulation that invites possible solutions to a defined challenge.

Divergent thinking: Expanding the number and variety of possible ideas.

Convergent thinking: Narrowing alternatives using evidence and decision criteria.

Prototype: An incomplete representation created to learn about an idea.

Low-fidelity prototype: A quick, inexpensive representation used for early exploration.

Service blueprint: A representation of customer-facing and behind-the-scenes service activities.

Iteration: Repeated improvement based on evidence and feedback.

Pivot: A substantial change to a key business or problem assumption.

Value proposition: The promised benefit or outcome offered to a defined customer segment.

Stakeholder: A person or group that affects or is affected by an activity or solution.

Review Questions

Short Answer Questions

1. What is meant by human-centred innovation?
2. Distinguish between a declared need and a latent need.
3. Why should a problem statement avoid prescribing a particular technology?
4. What is the purpose of a prototype?
5. State two ethical responsibilities in empathy research.

Long Answer Questions

1. Explain the five connected activities of design thinking and show why the process is iterative.
2. Compare interviews, observation and focus groups as empathy-research methods.
3. Explain how divergent and convergent thinking contribute to concept development.
4. Discuss how design thinking can improve business-model planning.
5. Evaluate the limitations of design thinking as an approach to entrepreneurship.

Analytical / Application Questions

1. A student team wants to create an app for small retailers but has conducted no research. Develop an empathy-research plan and identify three assumptions that should be tested.
2. Convert the statement “Students need an online platform for affordable meals” into a stronger problem frame and explain what evidence would be required.
3. Design a low-fidelity prototype and test plan for a service that helps local residents reduce household food waste. Specify the learning question, participants, evidence and possible decisions.

Multiple Choice Questions with Answers

Question 1

Which activity in design thinking focuses primarily on understanding stakeholders’ experiences and constraints?

A. Empathise

B. Ideate

C. Prototype

D. Scale

Correct Answer: A. Empathise

Question 2

Which statement is an example of a problem frame rather than a solution assumption?

A. Customers need a mobile application.

B. Customers need a faster way to confirm trustworthy delivery times.

C. Customers need a barcode scanner.

D. Customers need an artificial-intelligence chatbot.

Correct Answer: B. Customers need a faster way to confirm trustworthy delivery times.

Question 3

What is the main purpose of a prototype?

A. To demonstrate that the final business will be profitable

B. To create an attractive finished product

C. To learn about a specific assumption or user need

D. To replace all market research

Correct Answer: C. To learn about a specific assumption or user need

Question 4

Which research method is most directly concerned with seeing behaviour in its natural context?

A. Observation

B. Brainstorming

C. Financial forecasting

D. Concept scoring

Correct Answer: A. Observation

Question 5

What is the principal difference between divergent and convergent thinking?

A. Divergent thinking evaluates costs, while convergent thinking conducts interviews.

B. Divergent thinking generates alternatives, while convergent thinking narrows them.

C. Divergent thinking builds prototypes, while convergent thinking writes consent forms.

D. Divergent thinking is quantitative, while convergent thinking is always qualitative.

Correct Answer: B. Divergent thinking generates alternatives, while convergent thinking narrows them.

Question 6

Which interview question is least leading?

A. You agree that this service would save time, don’t you?

B. Would you definitely buy this application?

C. Why do you dislike current suppliers?

D. Tell me about the last time you completed this task.

Correct Answer: D. Tell me about the last time you completed this task.

Question 7

A team changes its target customer and value proposition after evidence disproves its original assumptions. This is best described as a:

A. Pivot

B. Persona

C. Journey map

D. Benchmark

Correct Answer: A. Pivot

Question 8

Which evidence is generally stronger than a participant merely saying that an idea is interesting?

A. A polite smile during a presentation

B. A request for more colours in the interface

C. Repeat use or a concrete commitment in a realistic test

D. The founder’s personal enthusiasm

Correct Answer: C. Repeat use or a concrete commitment in a realistic test

Question 9

Which consideration is part of responsible human-centred innovation?

A. Collecting as much personal data as possible

B. Testing only with highly enthusiastic friends

C. Ignoring users who cannot access the technology

D. Protecting privacy and considering accessibility

Correct Answer: D. Protecting privacy and considering accessibility

Question 10

Why should an entrepreneur test a manual service before building a complex automated system?

A. Manual testing can reduce uncertainty about the need and workflow at lower cost.

B. Manual services are always more profitable than automated systems.

C. Automation is never appropriate for entrepreneurial ventures.

D. Users cannot evaluate digital prototypes.

Correct Answer: A. Manual testing can reduce uncertainty about the need and workflow at lower cost.