Human-Centered Design and the Design Thinking Process

Introduction

Entrepreneurial opportunities rarely arrive as clearly defined problems with obvious solutions. They emerge from uncertain situations involving people, technologies, institutions, markets, and social expectations. A technically impressive product may fail because it solves the wrong problem, is difficult to use, is unaffordable, or creates unacceptable social or environmental consequences. Human-centered design addresses this challenge by beginning with people’s experiences and by treating innovation as a process of learning, framing, creating, and revising.

Design thinking is a practical approach to innovation that combines user research, problem framing, creative generation, experimentation, and reflection. It is especially valuable in entrepreneurship because new ventures operate with incomplete information. Rather than investing heavily in an untested assumption, entrepreneurs can use relatively inexpensive prototypes and user feedback to reduce uncertainty.

Human-centered design does not mean simply asking users what product they want. People may not be able to articulate latent needs, may describe current solutions rather than desired outcomes, or may behave differently from what they report. Designers therefore study actual contexts, interpret evidence, and work collaboratively with stakeholders. The objective is not only desirability, but also a solution that can be feasible, viable, and responsible.

Learning Objectives

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

1. Explain human-centered design and distinguish it from product-centered innovation.
2. Apply the empathize, define, ideate, prototype, and test stages appropriately.
3. Relate the design thinking process to the Double Diamond model.
4. Explain iteration, abductive reasoning, ambiguity, and systems thinking in design work.
5. Evaluate concepts using desirability, feasibility, viability, and responsibility.
6. Apply design thinking to an entrepreneurial opportunity while recognizing ethical and practical limitations.

1. Human-Centered Design as an Innovation Discipline

Human-centered design is an approach in which the needs, capabilities, limitations, values, and lived experiences of affected people guide the development of products, services, processes, and business models. It is broader than interface design. A redesigned public-transport service, a digital health platform, and a new food-delivery business can all be investigated through human-centered design.

Several principles distinguish this approach:

• Context matters. People use solutions within physical, social, cultural, economic, and organizational environments.
• Needs are deeper than requests. A request is an expressed preference; a need concerns an underlying goal, difficulty, or desired outcome.
• Evidence is provisional. Interviews, observations, and experiments produce useful but incomplete evidence.
• Design is collaborative. Users, employees, technical specialists, managers, community representatives, and regulators may all hold relevant knowledge.
• Learning precedes commitment. Early experimentation should test important assumptions before major resources are committed.
• Consequences matter. A design should be assessed for inclusion, safety, privacy, environmental effects, and distribution of benefits and harms.

A product-centered process often begins with a technology and searches for a market. A human-centered process begins with a situation and asks: What are people trying to accomplish? What prevents them from doing so? Who else is affected? What solution could create value without imposing disproportionate costs?

Human-centered design is not identical to design thinking. Design thinking is a family of problem-solving practices and mindsets; human-centered design is the commitment to place human experiences and interests at the center of inquiry and evaluation. In practice, the two are closely connected.

2. The Double Diamond and the Design Thinking Process

The Design Council’s Double Diamond represents four broad movements: discover, define, develop, and deliver. The two diamonds show that innovation involves alternating between expanding and narrowing attention. The first diamond concerns understanding the problem; the second concerns developing and selecting a response.

Figure: The Double Diamond alternates between divergent exploration and convergent decision-making.

The five-stage design thinking sequence commonly used in entrepreneurial education is empathize, define, ideate, prototype, and test. These stages map onto the Double Diamond but should not be treated as a rigid or purely linear sequence.

Divergence expands the range of possibilities. Convergence selects, prioritizes, or frames possibilities. Premature convergence occurs when a team selects a familiar solution before understanding the problem. Unfocused divergence occurs when a team generates ideas without criteria or learning objectives. Effective design alternates between both modes.

3. Empathize: Investigating Experience

Empathy in design is disciplined inquiry, not merely sympathy. The designer seeks to understand what people do, say, think, feel, and value in a particular context. Useful methods include semi-structured interviews, contextual observation, diary studies, shadowing, participatory workshops, analysis of complaints and support records, and review of existing research.

A strong interview uses open questions such as “Tell me about the last time you…,” “What happened next?” and “What made that difficult?” It avoids leading questions such as “Would you use our convenient app?” Interviews should investigate actual past behavior rather than relying only on imagined future intentions.

Observation can reveal workarounds, interruptions, accessibility barriers, and informal practices that participants do not mention. Researchers should record descriptive evidence separately from interpretation. For example:

• Observation: “The customer looked at the printed form for 40 seconds and asked the employee where to sign.”
• Interpretation: “The form may be difficult to navigate.”

This distinction reduces the risk of presenting assumptions as facts. Researchers should also recruit participants who represent relevant variation, including differences in age, ability, income, technical confidence, language, and frequency of use. A convenient sample may be efficient for early exploration but can conceal the experiences of less visible groups.

Common synthesis tools include:

• Persona: A research-based representation of a meaningful user pattern, not a fictional stereotype.
• Journey map: A visual account of stages, actions, emotions, barriers, and opportunities across an experience.
• Empathy map: A structured summary of what a participant says, thinks, does, and feels.
• Affinity diagram: A method for grouping observations and identifying recurring themes.
• Stakeholder map: A representation of actors, relationships, influence, and affected interests.

Empathy research has ethical requirements. Participants should understand the purpose of the research, how data will be used, and whether participation is voluntary. Sensitive information should be minimized, securely stored, and anonymized where possible. Researchers should avoid extracting stories from vulnerable communities without returning value or representing their experiences accurately.

4. Define: Framing the Right Problem

The define stage converts a broad field of observations into a focused, evidence-informed design challenge. It is an interpretive activity: the team decides which patterns matter and how they should be expressed. A useful problem statement identifies a population, a meaningful need, and the context without prescribing a particular solution.

A weak statement is: “We need an artificial-intelligence appointment app.” It assumes a technology and ignores the underlying problem. A stronger statement is: “People with unpredictable work schedules need a simpler way to reschedule essential appointments without waiting on hold.” The second statement leaves room for several possible solutions.

A point-of-view statement may follow this structure:

[A particular user] needs [a meaningful need] because [an insight grounded in evidence].

A “How might we…?” question can then open the problem for ideation: “How might we help people with unpredictable schedules change appointments with less time and anxiety?” Such questions should be neither so broad that anything qualifies nor so narrow that only one solution is possible.

Problem framing involves judgment. Teams should compare alternative frames and ask:

1. Whose problem is being described?
2. What evidence supports the frame?
3. What assumptions are embedded in it?
4. Who benefits or loses if this frame is adopted?
5. Is the proposed scope appropriate to the team’s authority and resources?

A design brief commonly records the target context, desired outcome, constraints, stakeholders, evidence gaps, and evaluation criteria. Constraints are not always obstacles. Budget limits, safety standards, accessibility requirements, and environmental boundaries can stimulate more responsible creativity.

5. Ideate: Generating and Selecting Possibilities

Ideation is not a competition to produce one brilliant idea. It is a structured effort to create alternatives before evaluating them. Individual generation can be followed by group development. Useful techniques include brainstorming, brainwriting, sketching, analogy, “worst possible idea,” forced connections, morphological analysis, and co-design workshops.

Effective ideation rules include deferring judgment during generation, building on others’ contributions, making ideas visible, and seeking quantity and variety early. Teams should deliberately include ideas that change the process, business model, communication, physical environment, or institutional arrangement—not only ideas that add features to an existing product.

After divergence, concepts can be screened against criteria such as user value, technical possibility, economic potential, time, risk, accessibility, environmental impact, and legal acceptability. A simple weighted decision model may be useful, provided that the weights and scores are treated as judgments rather than objective facts. For concept j, a team might calculate:

Here, S_j is the weighted score of concept j; w_i is the importance weight for criterion i; and r_ij is the rating of concept j on criterion i. Ratings must use a defined scale, such as 1–5. The method assumes criteria are sufficiently distinct and that additive compensation is acceptable—for example, a high market score may offset a lower technical score. It should not override non-negotiable constraints such as safety or legal compliance.

6. Prototype: Making Ideas Testable

A prototype is an intentional, limited representation of a proposed experience or system. Its value lies in the questions it makes possible, not in its polish. A paper interface can test navigation; a storyboard can test a service sequence; a role play can test staff responsibilities; a landing page can test whether a value proposition attracts interest; and a functional minimum viable product can test repeated use under realistic conditions.

Prototype fidelity should match the learning objective. High fidelity is not automatically better. It can waste resources, make people reluctant to criticize, and create the illusion that unresolved assumptions have been validated. A useful prototype is designed around a hypothesis:

We believe that [target user] will [behavior] because [value proposition]. We will observe [indicator] to learn whether this assumption is credible.

For example, an entrepreneur might hypothesize that freelance workers will reserve shared childcare in advance if cancellation terms are transparent. A prototype could be a clickable booking flow tested with realistic scenarios, not a fully engineered platform.

Prototyping also supports communication among stakeholders. Different disciplines often interpret abstract descriptions differently; a tangible representation exposes disagreements early. In service design, prototypes should include frontstage interactions visible to customers and backstage activities required to deliver the service.

7. Test: Learning, Not Merely Validating

Testing involves presenting a prototype to appropriate participants, observing behavior, asking focused questions, and deciding what to change. A test should be designed around uncertainty. If the major risk is whether users understand an instruction, a usability test is appropriate. If the major risk is whether a business model can operate profitably, conversations with customers must be supplemented by operational and financial analysis.

Test participants should receive enough context to act naturally but not so much guidance that the team performs the task for them. Researchers should distinguish between:

• what participants say they would do;
• what they attempt to do;
• what they actually complete; and
• what they do repeatedly in a realistic setting.

A failed test is not necessarily a failed project. It may reveal that the prototype was confusing, the participant group was inappropriate, the task was unrealistic, or the underlying assumption was false. The team should record the evidence, revise its interpretation, and determine whether to persevere, pivot, or stop.

Useful measures may include completion rate, time on task, error frequency, retention, willingness to pay, or qualitative confidence. No single measure proves product success. A participant’s positive opinion does not establish demand, and a successful prototype interaction does not establish technical feasibility or financial viability.

8. Iteration, Abductive Reasoning, and Ambiguity

Design thinking is iterative because new evidence changes the team’s understanding. Iteration may involve refining a feature, changing a user segment, reframing the problem, replacing a business model, or abandoning the idea. The best iteration is not the one that produces the most versions; it is the one that converts important uncertainty into useful learning at reasonable cost.

Design reasoning combines three forms of inference:

• Deduction: applying a general rule to a case.
• Induction: generalizing a pattern from cases.
• Abduction: proposing the most plausible explanation or opportunity for observed evidence.

If several customers abandon a complicated registration process, the team may abductively infer that perceived effort—not lack of interest—is limiting adoption. This is a hypothesis, not a fact. It must be tested against alternative explanations such as price, trust, accessibility, or lack of need.

Ambiguity is unavoidable because early information is incomplete and meanings are contested. Rather than eliminating ambiguity immediately, designers can make it explicit through assumption logs, alternative problem statements, decision records, and experiments. Teams should identify which assumptions are both important and uncertain. These deserve early testing.

A useful distinction is between desirability risk (whether people value the solution), feasibility risk (whether it can be built and delivered), viability risk (whether it can sustain an organization), and responsibility risk (whether it causes unacceptable harm or injustice). Testing should address all four, not only user preference.

9. Systems Thinking and the Wider Context

A product or service is part of a system. Systems thinking examines relationships, feedback, dependencies, delays, unintended consequences, and boundaries. For example, a ride-sharing platform affects passengers, drivers, traffic patterns, public transport, regulators, neighborhoods, and emissions. Optimizing convenience for one user group may create costs elsewhere.

Tools such as stakeholder maps, system maps, causal-loop diagrams, value-network maps, and service blueprints help teams see beyond the immediate interface. Designers should ask:

• What inputs, processes, outputs, and feedback loops shape the experience?
• Which actors have power to enable or obstruct the solution?
• What happens when adoption increases substantially?
• Which costs are visible to the customer, and which are externalized?
• Could the solution reinforce exclusion or dependency?

Systems thinking is particularly important for entrepreneurial ventures whose success can alter behavior at scale. A food-delivery service may create convenience but also increase packaging waste and precarious labor. A responsible design response may require changes to partnerships, incentives, pricing, logistics, and governance rather than a new app feature.

10. Evaluating Concepts: Four Complementary Criteria

A promising concept should be evaluated across four dimensions:

These criteria are related but not interchangeable. A desirable solution can be infeasible; a viable business can be irresponsible; a feasible technology can lack demand. Responsibility should not be treated as an optional fourth-stage adjustment. It should influence research, ideation, prototyping, and launch decisions from the beginning.

Entrepreneurs may use a concept portfolio rather than selecting a single idea too early. One concept may maximize near-term feasibility, while another offers greater long-term potential but requires further technical research. Explicit criteria make such trade-offs visible and open to challenge.

11. Illustrative Case: Redesigning Appointment Access

Background

The following is a fictional illustrative case. A small entrepreneurial team notices that patients at a community health clinic frequently miss appointments or spend long periods waiting on the telephone to reschedule. The team initially proposes an artificial-intelligence chatbot.

Problem and analysis

During the empathize stage, the team conducts interviews with patients and staff, observes reception workflows, and reviews anonymized appointment records. It learns that the problem is not simply telephone waiting. Patients have irregular work schedules, some share phones with family members, several speak languages other than English, and staff must protect confidential information. Some patients also fear that cancelling an appointment will make it difficult to obtain another one.

The team reframes the challenge as: “How might we help patients change appointments through a trustworthy, accessible process while reducing avoidable staff workload?” This frame does not assume that a chatbot is the answer.

Approach

The team ideates several options: multilingual text messaging, a call-back queue, evening scheduling sessions, a staff-assisted web form, and a chatbot. It prototypes a multilingual text flow and a staff dashboard using paper screens and role play. Testing reveals that participants understand the messages but want confirmation that their new appointment is secure. Staff identify a risk that automated messages could be sent to a shared phone.

The team therefore adds identity-verification safeguards, clear consent procedures, a human escalation route, and a printed alternative for people without reliable mobile access. It pilots the service with a small group rather than immediately automating all scheduling.

Outcome

The pilot produces evidence that rescheduling becomes easier for some patients and that staff workload can be reduced for routine changes. However, the team discovers that complex clinical appointments still require human judgment. The venture therefore adopts a hybrid service rather than a fully automated chatbot.

Learning points

1. The initial technology idea was not the same as the underlying need.
2. Observation exposed operational and privacy constraints.
3. Prototypes tested service logic before software investment.
4. Responsibility shaped the design rather than being added after development.
5. The final opportunity was a coordinated service, not merely an application.

12. Professional Practice, Technology, and AI

Digital tools can support transcription, clustering, simulation, rapid prototyping, accessibility testing, and analysis of large volumes of feedback. Generative AI can produce alternative concepts, personas, interface drafts, or research questions. However, AI-generated outputs may reproduce stereotypes, invent evidence, expose confidential data, or encourage superficial agreement. Human researchers remain responsible for consent, interpretation, verification, and decisions.

Teams should document when AI is used, avoid entering identifiable participant data into unapproved systems, check outputs against primary evidence, and include affected communities in evaluation. Automation should not remove meaningful human choice in high-stakes settings such as health, employment, credit, or education without appropriate safeguards and accountability.

Employability in design-oriented entrepreneurship depends on more than creativity. Graduates should be able to conduct ethical research, facilitate collaboration, communicate uncertainty, create and evaluate prototypes, interpret evidence, manage stakeholders, and explain trade-offs. They should also know when design methods are insufficient and when legal, clinical, engineering, financial, or social-science expertise is required.

13. Challenges and Limitations

Design thinking is useful but not universally sufficient. Common limitations include:

• Method theatre: teams use sticky notes and workshops without changing decisions or evidence quality.
• Sampling bias: vocal or accessible participants dominate the definition of the problem.
• Overconfidence in empathy: a short interview is treated as complete understanding.
• Novelty bias: new concepts are preferred over reliable existing solutions.
• Weak economic analysis: enthusiasm is mistaken for a sustainable business model.
• Power imbalance: organizations define problems for communities rather than with them.
• Scaling failure: a prototype works in a controlled setting but fails under real operational conditions.
• Ethical displacement: harms are discussed but subordinated to growth targets.

The remedy is not to abandon design thinking. It is to combine it with sound research methods, domain expertise, financial analysis, engineering validation, accessibility practice, and governance. Design thinking should be understood as a flexible problem-framing and learning approach, not as a guarantee of innovation success.

Chapter Summary

Human-centered design places people’s lived experiences, goals, capabilities, and risks at the center of innovation. The design thinking process uses empathize, define, ideate, prototype, and test activities to investigate needs, frame opportunities, generate alternatives, make assumptions visible, and learn through evidence. The Double Diamond explains the movement between divergent exploration and convergent focus across problem and solution spaces.

Design work is iterative, abductive, and conducted under ambiguity. Teams should distinguish observations from interpretations, test important assumptions early, and use systems thinking to understand stakeholders, dependencies, feedback, and unintended consequences. Concepts should be assessed through desirability, feasibility, viability, and responsibility. Ethical research, inclusion, privacy, accessibility, and environmental consequences are integral to the process. For entrepreneurs, the central value of design thinking is not a prescribed sequence of workshops but a disciplined way to reduce uncertainty while creating solutions that people value and organizations can responsibly deliver.

Key Terms

Human-centered design: An approach that guides design decisions through people’s experiences, needs, capabilities, and interests.

Design thinking: A set of mindsets and practices for framing problems, generating possibilities, experimenting, and learning.

Double Diamond: A model showing divergent and convergent movements through discover, define, develop, and deliver.

Empathy: Informed understanding of people’s experiences and perspectives in context.

Problem framing: Defining which situation, need, population, and boundaries will be addressed.

Persona: A research-based representation of a recurring user pattern.

Journey map: A representation of stages and experiences across an interaction or service.

Ideation: Structured generation of alternative concepts.

Prototype: A limited representation created to explore or test an idea.

Minimum viable product: A deliberately limited offering used to learn about a business or user assumption.

Iteration: Repeated modification based on learning and evidence.

Abduction: Inference of a plausible explanation or opportunity from observations.

Ambiguity: A condition in which meaning, causes, or solutions are not yet clear.

Systems thinking: Analysis of relationships, feedback, dependencies, and consequences within a wider system.

Desirability: The extent to which relevant people value and choose a solution.

Feasibility: The extent to which a solution can be technically and operationally delivered.

Viability: The extent to which a solution can create sustainable economic value.

Responsibility: Attention to ethical, social, environmental, legal, and safety consequences.

Stakeholder: A person or group that affects or is affected by a design.

Service blueprint: A map connecting customer-facing interactions with backstage processes and support activities.

Review Questions

Short Answer Questions

1. What is the principal difference between human-centered design and product-centered innovation?
2. What are divergence and convergence in the Double Diamond?
3. Why should observations be separated from interpretations during research?
4. What is the purpose of a prototype?
5. Name and briefly explain the four criteria for evaluating a concept.

Long Answer Questions

1. Explain the five stages of design thinking and show how they relate to the Double Diamond.
2. Discuss how ethical considerations should influence empathize, prototype, and test activities.
3. Explain abductive reasoning and ambiguity in entrepreneurial design work.
4. Analyze how systems thinking can reveal consequences that a user-centered interface analysis might miss.
5. Critically evaluate the limitations of design thinking as an approach to innovation.

Analytical / Application Questions

1. A university wants to reduce student queues at its financial-aid office. Develop a research plan, a problem statement, and two prototype ideas. Identify the assumptions each prototype would test.
2. Evaluate a proposed food-delivery platform using desirability, feasibility, viability, and responsibility. State what evidence would be needed before launch.
3. A team’s prototype receives enthusiastic interview feedback but no one returns to use it. Use abductive reasoning to propose three possible explanations and design a test that distinguishes among them.

Multiple Choice Questions with Answers

Question 1

Which activity best represents the empathize stage?

A. Selecting a final business model

B. Observing users in their actual context

C. Writing production software

D. Ranking concepts by revenue potential

Correct Answer: B. Observing users in their actual context

Question 2

In the Double Diamond, divergence primarily involves:

A. Expanding the range of evidence or possibilities

B. Approving a single solution

C. Calculating financial statements

D. Eliminating stakeholder involvement

Correct Answer: A. Expanding the range of evidence or possibilities

Question 3

Which problem statement is least solution-prescriptive?

A. We need an AI chatbot for appointments

B. We need a mobile app with push notifications

C. Patients need a trustworthy way to change appointments

D. We need facial recognition at reception

Correct Answer: C. Patients need a trustworthy way to change appointments

Question 4

What is the main purpose of an early prototype?

A. To prove that the final product is complete

B. To make assumptions tangible and learn cheaply

C. To prevent users from criticizing an idea

D. To replace all technical validation

Correct Answer: B. To make assumptions tangible and learn cheaply

Question 5

Abductive reasoning is best described as:

A. Applying a rule with certainty to a case

B. Counting every possible user response

C. Proposing a plausible explanation for observed evidence

D. Selecting the cheapest available technology

Correct Answer: C. Proposing a plausible explanation for observed evidence

Question 6

Which criterion asks whether an organization can technically and operationally deliver a concept?

A. Desirability

B. Feasibility

C. Viability

D. Responsibility

Correct Answer: B. Feasibility

Question 7

Why is systems thinking important in entrepreneurial design?

A. It limits analysis to the immediate user interface

B. It identifies relationships and unintended consequences

C. It guarantees that every stakeholder will agree

D. It removes the need for prototyping

Correct Answer: B. It identifies relationships and unintended consequences

Question 8

A team discovers that a prototype works in a workshop but fails under real operating conditions. Which issue is most directly illustrated?

A. Scaling and contextual validity

B. Successful convergence

C. Excessive participant consent

D. Complete feasibility

Correct Answer: A. Scaling and contextual validity

Question 9

Which practice is most appropriate when using generative AI in design research?

A. Treating generated personas as empirical evidence

B. Uploading identifiable participant data to any public tool

C. Verifying outputs against research evidence and protecting privacy

D. Allowing AI to make final high-stakes decisions without review

Correct Answer: C. Verifying outputs against research evidence and protecting privacy

Question 10

A concept receives ratings of 4 and 2 on two equally weighted criteria using a 1–5 scale. Its weighted score is:

A. 2

B. 3

C. 4

D. 6

Correct Answer: B. 3