Design Thinking and Human-Centered Innovation

Introduction and Context

Entrepreneurial product development begins with an uncertain proposition: a team believes that a particular group of people has an important problem and that a new product, service, or business model might address it. The central risk is not merely technical failure. A product can be technically sophisticated and commercially unsuccessful if it solves the wrong problem, imposes unacceptable costs, excludes important users, or does not fit the social and organizational context in which it will be used.

Design thinking and human-centered innovation provide approaches for reducing this uncertainty. They place people’s experiences, goals, constraints, and capabilities at the center of opportunity discovery and concept development. Rather than treating innovation as a linear sequence from idea to product, these approaches view it as an iterative process of learning, framing, imagining, making, and testing.

Design thinking is not a universal recipe or a guarantee of innovation. It is a disciplined set of practices for investigating situations, making assumptions visible, generating alternatives, and learning through interaction with users and stakeholders. Human-centered innovation extends this orientation by considering not only individual users but also communities, institutions, workers, affected non-users, and broader social and environmental consequences.

For entrepreneurs, this chapter is especially important because early-stage ventures operate with limited resources and incomplete information. Well-designed research and prototypes can reveal weak assumptions before substantial capital is committed. At the same time, entrepreneurial teams must avoid confusing positive user reactions with evidence of willingness to adopt, pay, or change behavior. Human-centered methods are therefore most effective when combined with business-model analysis, technical feasibility assessment, and ethical judgment.

Learning Objectives

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

1. Explain the principles and process logic of design thinking and human-centered innovation.
2. Conduct empathetic inquiry while recognizing bias, power, privacy, and representation issues.
3. Define a product problem as a meaningful, evidence-based opportunity rather than as a premature solution.
4. Apply divergent and convergent thinking to generate and select product concepts.
5. Plan and facilitate co-design activities with users and stakeholders.
6. Use inclusive design principles to address differences in ability, language, culture, age, resources, and context.
7. Develop defensible concept-selection criteria and evaluate early concepts.
8. Critically assess the limitations and ethical implications of human-centered innovation.

1. Foundations of Design Thinking

1.1 From solution-first to problem-informed innovation

A solution-first approach begins with a technology or product idea and searches for a problem it might address. This can be appropriate when a genuine technical breakthrough creates new possibilities, but it often encourages confirmation bias: the team selectively notices evidence supporting its initial idea. A problem-informed approach begins by investigating needs, practices, and constraints, then asks what kinds of interventions might create value.

Design thinking is commonly described through the activities of empathize, define, ideate, prototype, and test. These labels are useful reminders, but they should not be interpreted as rigid stages. Teams may return to research after testing, redefine the problem during ideation, or prototype before the problem is fully understood. The process is iterative because learning changes the design question itself.

The process contains two complementary movements:

• Expansion, or divergence, increases the range of observations, interpretations, possibilities, and concepts.
• Reduction, or convergence, narrows that range by applying evidence, criteria, constraints, and judgment.

Premature convergence produces familiar ideas and hides alternatives. Uncontrolled divergence produces attractive possibilities without decisions. Effective innovation alternates deliberately between both modes.

1.2 Human-centered innovation as a systems perspective

A user is not always the only relevant human actor. For example, a hospital device may be used by a patient, operated by a nurse, purchased by a procurement department, maintained by technicians, and regulated by a public authority. A design that satisfies one actor while increasing risks or workload for others is not genuinely human-centered.

Human-centered innovation therefore examines:

• Direct users: people who interact with the product.
• Indirect users: people affected by its outputs or consequences.
• Purchasers and decision-makers: people who authorize adoption or payment.
• Service providers and maintainers: people who install, repair, train, or support it.
• Non-users and vulnerable groups: people excluded, burdened, or harmed by the design.
• Environmental and community stakeholders: people affected by resource use, waste, infrastructure, or social change.

This perspective links user experience to organizational systems, markets, regulation, culture, and sustainability. A desirable product must also be feasible to deliver and viable within an appropriate business model. These dimensions are related but distinct: users may desire a product that cannot be manufactured, or a technically feasible product may lack a viable route to adoption.

2. Empathy: Understanding People in Context

Empathy in design does not mean guessing what another person feels or claiming to share that person’s experience. It means developing an informed understanding of how people interpret situations, pursue goals, experience constraints, and adapt their behavior. The objective is not emotional performance but better evidence and more responsible judgment.

2.1 Research methods

A mixed-method approach is often appropriate because each method reveals different aspects of experience.

Interview questions should invite concrete accounts rather than demand opinions about an imagined future. “Tell me about the last time you…,” “What happened next?,” and “What made that difficult?” are generally more informative than “Would you use our proposed product?” The latter tends to produce polite or speculative answers.

Observation should focus on sequences, interruptions, tools, workarounds, and environmental conditions. An entrepreneur studying food-delivery workers, for example, should examine how weather, traffic, phone battery, building access, and payment procedures shape the work. A brief interview alone may not reveal these interacting constraints.

2.2 Sampling and research quality

Early design research does not necessarily require statistically representative samples, but it does require purposeful coverage of relevant variation. Participants may differ by age, ability, income, language, geography, digital access, experience, and authority. Recruiting only enthusiastic early adopters can create a misleadingly positive picture.

A research plan should specify:

1. The decision the research will inform.
2. The populations and contexts that matter to that decision.
3. Inclusion and exclusion criteria.
4. Recruitment channels and possible selection bias.
5. Data-collection procedures and consent requirements.
6. How observations will be recorded, coded, compared, and interpreted.
7. How contradictory or disconfirming evidence will be handled.

Researchers should distinguish observations from interpretations and assumptions. “The participant used a paper notebook after the app failed” is an observation. “The participant dislikes digital tools” is an interpretation. “Users will pay for offline functionality” is an assumption requiring further evidence.

2.3 Empathy artifacts

Empathy maps organize evidence under headings such as says, does, thinks, and feels. They can help teams notice discrepancies—for example, a person may say that convenience matters but repeatedly choose a slower option because it feels safer. Personas are evidence-based representations of meaningful user patterns, not fictional stereotypes. A strong persona includes goals, behaviors, context, barriers, and relevant quotes or evidence; it should not reduce a population to a name and a photograph.

Journey maps represent experiences over time, including stages, actions, emotions, pain points, backstage processes, and opportunities. They are valuable because dissatisfaction may be produced by a sequence rather than a single interaction. However, a journey map is an analytical model, not an objective portrait. Teams should record whose journey is represented and where evidence is uncertain.

3. Defining the Right Problem

3.1 From symptoms to opportunity statements

A problem statement identifies a meaningful gap between a current situation and a desired one. It should be specific enough to guide design and open enough to permit multiple solutions. A useful structure is:

[Relevant group] needs a way to [desired progress] because [evidence-based insight or constraint].

For example: “First-year university students living off campus need a low-effort way to identify affordable, trustworthy evening meals because limited cooking facilities and irregular schedules make existing planning routines unreliable.” This statement does not prescribe an app, meal box, or restaurant marketplace.

A weak statement often embeds a solution: “Students need a mobile app that recommends meals.” Such wording narrows exploration before the need and context have been established.

3.2 Jobs, needs, and outcomes

The jobs-to-be-done perspective asks what progress a person is trying to make in a situation. A job may be functional, emotional, and social. “Commute to work” is functional; “feel in control of an unpredictable commute” is emotional; “arrive as a reliable colleague” is social. This framework helps teams move beyond demographic descriptions toward situational needs.

Needs should not be treated as simple preferences. A user may request a faster process, while deeper investigation reveals a need for confidence, error recovery, or protection from embarrassment. Entrepreneurs should preserve the user’s stated experience while testing the interpretation rather than replacing it with an unsupported theory.

3.3 Reframing and the “How might we?” question

“How might we?” questions convert a problem into an invitation for exploration. Effective questions are neither so broad that anything qualifies nor so narrow that only one solution remains possible. Compare:

• Too broad: “How might we improve education?”
• Too narrow: “How might we add a chatbot to the course website?”
• More useful: “How might we help working students obtain timely feedback when they cannot attend scheduled support sessions?”

Teams should create several alternative framings and examine their consequences. A problem framed as “reducing waiting time” may produce a scheduling solution; framed as “reducing uncertainty during waiting” it may produce communication or reassurance. Reframing is not manipulation: the new frame must remain grounded in evidence and stakeholder interests.

4. Ideation and Concept Generation

4.1 Divergent thinking

Divergent thinking seeks quantity, variety, and unexpected combinations before evaluation. Brainstorming is only one technique. Other methods include:

• Brainwriting: participants record ideas independently before sharing, reducing dominance by vocal members.
• SCAMPER: substitute, combine, adapt, modify, put to another use, eliminate, and reverse.
• Analogy: examine how another industry or natural system addresses a comparable challenge.
• Worst possible idea: deliberately generate bad ideas to expose hidden assumptions and loosen evaluation anxiety.
• Constraint variation: ask how the concept would work with no electricity, one minute of user time, zero training, or a very small budget.
• Role-based ideation: generate ideas from the perspective of a user, maintainer, regulator, or excluded person.

Ideation sessions need a clear challenge, relevant evidence, time limits, and explicit norms. Defer judgment during generation, build on others’ ideas, make concepts visible, and seek variation rather than merely repeating refinements of the first idea.

4.2 Convergent thinking

Convergence is more than voting. It involves defining criteria, examining evidence, identifying risks, and deciding what should be learned next. Useful criteria include:

• Importance of the problem.
• Strength of evidence for user need.
• Potential value to users and other stakeholders.
• Technical and operational feasibility.
• Economic viability and route to adoption.
• Strategic fit with the venture.
• Inclusiveness and accessibility.
• Ethical, legal, privacy, and environmental risk.
• Learning value of a prototype.

A simple weighted decision matrix can structure discussion. If concept j receives a score sᵢⱼ from 1 to 5 on criterion i, and criterion i has weight wᵢ, the weighted score is:

Here, n is the number of criteria, weights are nonnegative, and the weights should sum to 1 if the score is intended to remain on the same 1–5 scale. The result is a prioritization aid, not an objective truth. Scores are judgments and should be accompanied by evidence, confidence levels, and unresolved questions. A concept with a lower total may deserve testing if it addresses a severe risk or offers high learning value.

For example, suppose a team assigns weights of 0.35 to user value, 0.25 to feasibility, 0.20 to viability, and 0.20 to inclusion. Concept A scores 5, 3, 2, and 4 respectively. Its score is:

The arithmetic is correct, but the decision remains provisional. The low viability score might reflect an untested pricing assumption rather than a fundamental weakness.

5. Co-Design and Collaborative Innovation

Co-design involves users and stakeholders as active contributors to framing, imagining, making, or evaluating solutions. It differs from conventional research in which participants only provide information, and from consultation in which designers retain nearly all decision authority.

5.1 Designing a co-design session

A productive session should establish:

1. A clearly bounded design challenge.
2. Participants with relevant and varied experiences.
3. Accessible materials and communication formats.
4. Activities that move from individual reflection to group exchange.
5. Facilitation that manages status and power differences.
6. A transparent explanation of how contributions will influence decisions.
7. Appropriate compensation and recognition.
8. A plan for documenting and returning results.

A typical sequence may include individual mapping of a current experience, small-group identification of barriers, creation of alternative concepts, construction of rough prototypes, and structured critique. Participants should be free to disagree. Consensus can conceal minority concerns, particularly when professionals or organizational leaders are present.

5.2 Power, participation, and ownership

Participation is not automatically empowering. Organizations may invite people to generate ideas while retaining the right to reject them without explanation. Participants may also disclose knowledge that is later commercialized without fair recognition or benefit. Ethical co-design requires clarity about purpose, decision rights, data use, confidentiality, intellectual property, and compensation.

The facilitator should ask whose knowledge is treated as authoritative, who speaks most, who performs unpaid labor, and who bears the risks of implementation. In community settings, it may be appropriate to establish shared governance, local review, or benefit-sharing arrangements rather than treating participants as temporary sources of insight.

6. Prototyping as Learning

A prototype is a representation created to explore an idea and obtain learning. It may be a sketch, storyboard, role-play, paper interface, physical model, service enactment, landing page, or functional technical artifact. The appropriate fidelity depends on the question.

• To test information structure, use a paper or clickable screen prototype.
• To test a service sequence, use role-play or a concierge simulation.
• To test physical form, use a low-cost mock-up.
• To test technical performance, create a focused functional prototype.
• To test willingness to act, use a realistic but ethically transparent behavioral experiment.

High fidelity is not always better. A polished prototype can cause participants to focus on visual details and hesitate to criticize the underlying concept. Low fidelity makes change inexpensive and signals that critique is welcome. However, a prototype must be realistic enough to elicit the behavior or judgment being studied.

Testing should begin with explicit hypotheses. For instance: “People who manage medication for an older relative will be able to identify the next required action within 30 seconds without assistance.” The team must define what counts as evidence, recruit appropriate participants, observe behavior, and distinguish usability findings from market validation. A successful task does not prove demand, and a stated intention to buy does not prove payment behavior.

7. Inclusive Design and Accessibility

Inclusive design seeks products that can be used by people with diverse abilities, identities, languages, resources, and contexts. It is broader than compliance with accessibility regulation, although legal compliance is a minimum obligation in many sectors.

Important dimensions include:

• Visual, auditory, motor, cognitive, and speech differences.
• Temporary impairments, such as injury or fatigue.
• Situational constraints, such as glare, noise, one-handed use, or poor connectivity.
• Language, literacy, cultural expectations, and digital confidence.
• Economic constraints, device ownership, and data costs.
• Age, privacy concerns, safety, and power relationships.

Inclusive design should occur at discovery, not only at final testing. A team that recruits diverse participants early can identify assumptions about language, dexterity, household structure, or internet access before they become expensive to remove.

Designers should provide multiple ways to perceive information, operate a product, and recover from error. Clear language, adequate contrast, keyboard or alternative input support, captions, adjustable text, confirmation before irreversible actions, and offline or low-bandwidth pathways are common practices. The relevant standard depends on the product and jurisdiction; teams should consult applicable accessibility laws and technical standards rather than assuming that a generic checklist is sufficient.

A critical caution is that inclusive design does not mean designing one average product for everyone. It often means providing flexibility and choice. Nor should designers place responsibility on users to overcome inaccessible systems through assistive workarounds when the product itself can be improved.

8. An Integrated Venture Workflow

A graduate-level entrepreneurial team can organize the work as a sequence of decision loops:

1. Frame the opportunity: identify the system, stakeholders, uncertainty, and initial assumptions.
2. Investigate context: conduct ethical, purposeful research across relevant user groups and situations.
3. Synthesize evidence: cluster observations, compare cases, identify tensions, and document confidence.
4. Define and reframe: create several problem statements and select a provisional focus.
5. Generate concepts: use divergent methods individually and collectively.
6. Select learning priorities: assess value, feasibility, viability, inclusion, risk, and uncertainty.
7. Prototype the riskiest assumption: choose the least expensive credible representation.
8. Test and interpret: observe behavior, seek disconfirming evidence, and revise the frame or concept.
9. Decide the next investment: persevere, pivot, pause, or abandon based on learning.

This workflow should connect to entrepreneurial evidence. Discovery evidence concerns the problem and context; desirability evidence concerns perceived and demonstrated value; feasibility evidence concerns technical and operational performance; viability evidence concerns adoption, revenue, cost, and strategic fit. No single interview or prototype answers all four questions.

Illustrative Case: Reimagining Medication Support for Older Adults

Background

The following is a fictional illustrative case. A graduate venture team is exploring a product for older adults who take several prescription medicines at home. The initial idea is a smartphone application that sends reminders.

Problem investigation

The team interviews older adults, family caregivers, pharmacists, and home-care workers, and observes medication preparation in several households. They discover that missed doses are only one part of the problem. Participants also confuse changes in dosage, worry about taking medicines at the wrong time, and struggle to obtain timely clarification. Some older adults do not use smartphones; others share devices with family members. Caregivers value reassurance but do not want constant surveillance.

The team separates evidence from interpretation. Evidence includes observed uncertainty after prescription changes, repeated calls to pharmacies, and the use of handwritten notes. An early interpretation is that users need reminders. Further research suggests a broader need: confidence in managing changing instructions while preserving autonomy and privacy.

Reframing

The initial statement, “Older adults need a medication reminder app,” is replaced with: “People managing multiple medicines at home need a clear and trustworthy way to understand current instructions and obtain help when instructions change, without requiring continuous digital monitoring.”

This framing permits several solutions: a pharmacist-linked printed schedule, a voice-based service, a caregiver coordination process, packaging redesign, or a digital tool with offline and privacy-preserving features.

Ideation and selection

The team generates twenty-six concepts. They reject none during initial generation. During convergence, they compare concepts using user value, feasibility, viability, inclusion, and privacy risk. The highest-scoring concept combines a pharmacist-verified medication summary, large-print instructions, optional voice access, and a process for reporting changes. A smartphone reminder alone scores well on convenience but poorly on access, trust, and prescription-change risk.

Prototyping and testing

The first prototype is not a functioning app. It is a paper medication summary and a role-play in which a pharmacist updates an instruction. Participants are asked to identify what changed and what action is required. Testing reveals that color coding is unreliable for participants with visual limitations and that the phrase “as directed” creates uncertainty. The team replaces color-only cues with text, symbols, and explicit timing language.

A later prototype tests a voice interaction and caregiver permission controls. Participants appreciate optional support but object to automatic sharing of medication information. The team therefore makes sharing opt-in, displays who can access information, and includes an easy revocation process.

Outcome and learning points

The team does not yet have proof of clinical effectiveness or commercial viability. It has, however, reduced several risks and identified requirements for clinical review, data protection, accessibility testing, and a partnership model with pharmacies. The case demonstrates that empathy can transform the problem, co-design can reveal trust and power concerns, and low-fidelity prototypes can produce valuable learning before expensive software development.

Challenges, Limitations, and Governance

Design thinking is sometimes criticized for being superficial, excessively optimistic, or detached from structural analysis. These criticisms are justified when teams use colorful workshops instead of rigorous inquiry, treat individual preference as the whole problem, or assume that creativity can overcome political and economic constraints.

Important limitations include:

• Representation bias: a small, convenient sample may exclude people most affected by the problem.
• Researcher interpretation: framing, coding, and synthesis reflect the team’s assumptions.
• False consensus: workshops may reward confidence rather than knowledge.
• Novelty bias: teams may prefer unusual ideas even when simpler solutions are more effective.
• Pilot distortion: participants may behave differently when observed or when a service is free.
• Power asymmetry: organizations may extract knowledge without sharing decision-making or benefits.
• Scale effects: a solution that works for a few users may create costs, exclusion, or risks at scale.
• Commercial pressure: teams may ignore evidence that threatens the preferred business model.

Ethical practice requires informed consent, proportional data collection, secure storage, privacy protection, and special care with vulnerable participants. Sensitive research should avoid collecting identifiable information unless necessary. Teams should explain whether participation affects access to services, how recordings will be used, and whether participants can withdraw. In regulated domains such as health, finance, education, and employment, product development may require professional review, formal risk management, and compliance with sector-specific law.

AI can support transcription, clustering, translation, accessibility adaptation, and rapid generation of alternative concepts. It can also reproduce stereotypes, expose confidential data, fabricate plausible but unsupported insights, and make participation less transparent. Teams using AI should disclose its role where relevant, protect research data, retain human review, test outputs across demographic groups, and avoid treating generated personas or summaries as evidence. AI-generated concepts remain hypotheses requiring human-centered validation.

Contemporary Developments and Best Practices

Contemporary human-centered innovation increasingly combines service design, systems thinking, participatory research, behavioral science, sustainability, and digital experimentation. Climate impact and resource constraints require teams to ask not only whether a product is desirable but also what materials, energy, labor, data infrastructure, and disposal systems it depends upon. Circular approaches examine repair, reuse, modularity, remanufacture, and end-of-life recovery.

Best practices for entrepreneurial teams include:

1. Start with a decision and uncertainty, not with a workshop technique.
2. Recruit for relevant diversity, including people likely to be overlooked.
3. Record evidence, interpretations, assumptions, and confidence separately.
4. Use multiple methods and actively seek disconfirming evidence.
5. Frame problems without embedding a premature solution.
6. Alternate divergence and convergence deliberately.
7. Make selection criteria explicit and revisit them when evidence changes.
8. Prototype the riskiest assumption at the lowest credible fidelity.
9. Treat accessibility, privacy, safety, and sustainability as design requirements.
10. Compensate participants fairly and clarify ownership and data use.
11. Test behavior and context, not only stated preference.
12. Connect human-centered evidence to technical, economic, and regulatory analysis.

Chapter Summary

Design thinking is an iterative approach to innovation that alternates between expanding possibilities and narrowing them through evidence and judgment. Human-centered innovation broadens the focus from direct users to all people and systems affected by a product. Empathy requires contextual inquiry rather than speculation; interviews, observation, diaries, surveys, and participatory methods each provide different evidence.

A strong problem statement describes a meaningful need without prescribing a solution. Reframing and “How might we?” questions support exploration while remaining grounded in evidence. Divergent ideation generates variety, whereas convergence applies criteria such as value, feasibility, viability, inclusion, risk, and learning potential. Weighted decision matrices can structure discussion but cannot eliminate judgment or uncertainty.

Co-design makes users and stakeholders active contributors, yet participation must address power, compensation, ownership, privacy, and decision rights. Prototypes are learning instruments whose fidelity should match the question being investigated. Inclusive design considers disability, language, culture, resources, connectivity, and situational constraints from the beginning. Finally, design thinking has limitations: it can reproduce bias, create false confidence, or ignore structural and ethical issues. Its greatest value emerges when it is integrated with business, technical, regulatory, and sustainability analysis.

Key Terms

Design thinking: An iterative approach to understanding needs, framing problems, generating possibilities, prototyping, and learning through testing.

Human-centered innovation: Innovation that considers people’s experiences, capabilities, goals, relationships, and broader consequences.

Empathy: Evidence-based understanding of people’s experiences and contexts rather than projection or assumption.

Divergent thinking: Expanding the range of interpretations, possibilities, or concepts.

Convergent thinking: Narrowing alternatives through criteria, evidence, constraints, and judgment.

Problem statement: A focused description of a meaningful gap between a current and desired situation.

Reframing: Deliberately changing the interpretation or wording of a problem to reveal alternative opportunities.

Jobs to be done: The functional, emotional, and social progress a person seeks in a particular situation.

Contextual inquiry: Research that combines questioning with observation of people in their real environment.

Persona: An evidence-based representation of a meaningful pattern of users and circumstances.

Journey map: A representation of experiences, actions, emotions, barriers, and interactions across time.

Co-design: Collaborative design in which users or stakeholders actively contribute to framing, creating, or evaluating solutions.

Prototype: A representation used to explore an idea and generate learning.

Fidelity: The degree to which a prototype resembles the intended product or experience.

Inclusive design: Designing for diversity in ability, identity, language, resources, and context.

Accessibility: The extent to which a product or service can be used by people with diverse abilities.

Assumption: A proposition treated as true but requiring evidence or validation.

Decision matrix: A structured comparison of alternatives against weighted or unweighted criteria.

Confirmation bias: The tendency to seek or interpret evidence in ways that support existing beliefs.

Stakeholder: A person or group that affects, uses, purchases, delivers, regulates, or is affected by an innovation.

Review Questions

Short Answer Questions

1. Why should design thinking be understood as iterative rather than strictly linear?
2. Distinguish an observation from an interpretation and an assumption.
3. What makes a problem statement solution-neutral?
4. Explain the difference between divergent and convergent thinking.
5. Why is low-fidelity prototyping often useful in early product development?

Long Answer Questions

1. Explain how empathy research can influence the framing of an entrepreneurial opportunity. Discuss the strengths and limitations of at least three research methods.
2. Describe a complete design-thinking workflow for developing a new product, including the relationship between user value, feasibility, viability, and inclusion.
3. Discuss co-design as both a design method and a power relationship. What responsibilities do organizations have toward participants?
4. Explain inclusive design and analyze why accessibility should be addressed during discovery rather than only during final testing.
5. Critically evaluate the limitations of design thinking in addressing complex social or structural problems.

Analytical / Application Questions

1. A team wants to develop an app for informal caregivers but has interviewed only digitally confident adults aged 25–40. Identify the main threats to the research and propose a revised sampling and inquiry plan.
2. Using the weighted-score formula in this chapter, evaluate two hypothetical concepts with criteria for user value, feasibility, viability, and inclusion. Explain why the numerical result should not be treated as an automatic decision.
3. Select a familiar service and create three alternative “How might we?” questions: one too broad, one too narrow, and one appropriately framed. Justify your evaluation and identify a prototype for testing the riskiest assumption.

Multiple Choice Questions with Answers

Question 1

Which statement best describes human-centered innovation?

A. It focuses exclusively on the direct purchaser of a product.

B. It considers users, affected stakeholders, context, and broader consequences.

C. It requires that every product be designed through a workshop.

D. It replaces technical and financial analysis with empathy research.

Correct Answer: B. It considers users, affected stakeholders, context, and broader consequences.

Question 2

Which research question is most likely to elicit useful evidence about actual behavior?

A. Would you use our proposed application?

B. Do you think this product is innovative?

C. Tell me about the last time you encountered this situation.

D. Would you pay any price for a better solution?

Correct Answer: C. Tell me about the last time you encountered this situation.

Question 3

What is the main purpose of a solution-neutral problem statement?

A. To guarantee that the first concept will succeed.

B. To prevent the team from exploring multiple solutions.

C. To describe a need without prematurely prescribing an answer.

D. To eliminate the need for user research.

Correct Answer: C. To describe a need without prematurely prescribing an answer.

Question 4

Which activity is primarily divergent?

A. Ranking concepts against fixed criteria.

B. Generating many alternative concepts before evaluation.

C. Selecting the concept with the lowest technical risk.

D. Calculating a weighted decision score.

Correct Answer: B. Generating many alternative concepts before evaluation.

Question 5

In the formula S_j = ∑_i=1ⁿ w_i s_ij, what does w_i represent?

A. The score of concept j on criterion i.

B. The number of concepts being evaluated.

C. The weight assigned to criterion i.

D. The total score of all concepts.

Correct Answer: C. The weight assigned to criterion i.

Question 6

Why might a team choose a low-fidelity prototype?

A. It guarantees accurate market demand.

B. It makes changes inexpensive and encourages critique.

C. It removes the need to define a testing hypothesis.

D. It always provides better technical performance data.

Correct Answer: B. It makes changes inexpensive and encourages critique.

Question 7

Which practice best supports inclusive design?

A. Recruiting only expert users to simplify research.

B. Addressing accessibility only after launch.

C. Including variation in ability, language, resources, and context from discovery onward.

D. Designing for an assumed average user.

Correct Answer: C. Including variation in ability, language, resources, and context from discovery onward.

Question 8

What is a significant ethical concern in co-design?

A. Participants may generate too many ideas.

B. Organizations may extract knowledge without fair recognition or decision rights.

C. Prototypes may be lower in fidelity.

D. Teams may use both interviews and observation.

Correct Answer: B. Organizations may extract knowledge without fair recognition or decision rights.

Question 9

A prototype test shows that participants can complete a task. What does this finding establish most directly?

A. The product will be profitable.

B. The product has passed all regulatory requirements.

C. The tested interaction or assumption has produced the observed behavior under the test conditions.

D. All target users will adopt the product.

Correct Answer: C. The tested interaction or assumption has produced the observed behavior under the test conditions.

Question 10

Which statement about a weighted decision matrix is most accurate?

A. It converts subjective judgments into objective facts.

B. It is useful for structuring comparison but depends on the chosen criteria, weights, and evidence.

C. It should be used before any problem research.

D. It always selects the concept with the greatest social benefit.

Correct Answer: B. It is useful for structuring comparison but depends on the chosen criteria, weights, and evidence.