Skills Track: Sections 4.1, 4.2, and 4.3 are the complete academic foundation for every student. They apply to business, employment, education, public service, and community life. Optional Venture Track boxes, added after the academic manuscript is complete, illustrate tactical business-launch applications. Instructor-managed assignments are published separately.
Learning Objectives
By the end of this module, you should understand how people move from an evidence-informed understanding of a problem to several possible ways of addressing it. You will learn why design thinking is not simply making something attractive, why creativity can be practiced rather than awaited, and why the first solution that occurs to us often deserves more examination before we commit to it. You'll explore how to reframe problems, generate alternatives, and make careful choices using human needs, organizational realities, and ethical responsibilities.
You'll also learn to distinguish a sketch, a prototype, a minimum viable product, and a pilot. These tools help us make ideas easier to understand and examine, but they answer different questions and do not automatically prove that an offering is safe, useful, or financially viable. You'll practice interpreting feedback, noticing accessibility barriers, and deciding what should change when a design doesn't work as expected. Through examples from workplaces, consumer products, healthcare, and community life, you'll see that creative problem-solving is a professional capability—not a privilege reserved for inventors or startup founders. The goal is to leave with better judgment about what to create, what to question, and what to learn next.
Before We Begin: The Difference Between a Good Answer and a Better Question
Imagine you're trying to cross a river. You stand on one bank, look at the opposite shore, and decide that you need a bridge. Maybe you begin estimating how long the bridge should be, what materials it would require, and how much it might cost. Those are responsible questions if a bridge is the right answer. But suppose a nearby ferry already operates most of the day, and people are frustrated primarily because they cannot find its schedule. Perhaps the problem is not the absence of a bridge. Perhaps it is the absence of reliable information. A beautiful bridge could solve the wrong problem at enormous expense.
In Module 1, you practiced noticing opportunities. In Module 2, you learned why a person's actual experience matters more than our interpretation of that experience. In Module 3, you examined how an organization creates, delivers, and sustains value through a coordinated system—not simply an attractive idea. These lessons prepare us for a change in perspective. We no longer begin by asking what product we want to make. We begin by asking what improvement people need, what other explanations are possible, and how many responsible ways that improvement might be achieved.
Remember Elena, the fictional community-college student who works in a health clinic. She first noticed that some patients struggled with appointment reminders. After listening to people and reviewing nonidentifying, permitted workflow information, she realized that the challenges were not all the same. Some instructions were confusing; some patients had limited transportation; others faced shift schedules or caregiving responsibilities. Module 3 helped her see that any proposed improvement would depend on clinic staff, communication channels, costs, privacy, and dependable follow-through. She now has a better understanding of the situation—but she still doesn't know what to design.
One idea is to rewrite reminder messages. Another is to give people a simple checklist of what to bring. A third is to clarify how patients can ask for scheduling help. A fourth is to improve the clinic's handoff between registration and the care team. These are not interchangeable. Each responds to a different part of the experience, creates different obligations for the clinic, and needs different kinds of evidence. Elena's task is not to find an impressive idea and defend it. Her task is to explore possibilities, make them understandable, and discover what each might actually accomplish.
This is where design thinking and prototyping become valuable. The tools may sound specialized, but the underlying habit is familiar: when something matters and the answer is uncertain, we think carefully, try a small representation, pay attention, and improve. A teacher does this while redesigning a classroom exercise. A mechanic does it while investigating an intermittent repair problem. A parent does it while organizing a routine that actually works for a family. The tools become more powerful when we learn to use them deliberately.
4.1.1 Human-Centered Design
4.1.1.1 Design begins with someone's experience
What makes a solution good? We often answer by describing its features: it is fast, modern, affordable, automated, or innovative. But features are not the same as benefits. A new hospital kiosk may be faster at recording information while making the experience harder for patients who cannot easily read the screen. A workplace dashboard may display more data while leaving employees less certain about what they should do. A new app may be technically impressive and still ask people to download something they do not need. A solution earns its value through the improvement it makes in real life, not through the number of technologies it contains.
Human-centered design begins with a serious effort to understand the people affected by a proposed solution and the context in which they will use it. It involves more than imagining what an average customer might prefer. We consider the person's goals, constraints, habits, physical environment, language, abilities, priorities, and relationship to the organization. We also consider the employees or partners who must deliver the service. When a new process helps one group but transfers an impossible workload to another, the design may fail as a system. This is why the business-model perspective from Module 3 remains relevant even as we begin exploring specific solutions.
Tim Brown (2008), writing about design thinking, argued that design belongs much earlier in innovation than the final work of making a product attractive. It can shape the product, the service surrounding it, and the broader system through which value is delivered. For a beginning student, the practical insight is that appearance is one small part of design. The deeper question is how people's experiences will change if the proposed idea becomes real. That question applies to the layout of a classroom, a scheduling policy, an online form, or a new business service.
4.1.1.2 Five useful modes—not five mandatory steps
Design thinking is often introduced using five familiar modes: empathize, define, ideate, prototype, and test. Empathizing means seeking to understand people's experiences rather than assuming that our own perspective is sufficient. Defining means developing a useful description of the challenge. Ideating means creating several plausible approaches. Prototyping means making an aspect of an idea tangible enough to examine. Testing means observing and learning from a person's interaction with a representation of the proposed solution. The Stanford d.school describes these as flexible modes of practice, not a fixed checklist that must always be completed in the same order (Stanford d.school, n.d.).
A common misconception is that a design team must finish understanding customers, write a perfect problem statement, generate ideas, select one, build it, and never return to the earlier work. Real problems rarely cooperate with such a neat sequence. When you sketch a concept, you may discover that you do not understand an important user need. When someone attempts a paper simulation, you may realize that the original problem statement was incomplete. When you discuss technical constraints, you may need to revisit what is realistically possible. Moving backward is not necessarily a failure of planning; it may be the mechanism by which understanding improves.
Think of the five modes as tools kept in a well-organized toolbox. You wouldn't use a wrench simply because a wrench appears third on a checklist. You would use it when the task calls for it. Similarly, a team uncertain about what customers mean may need more observation. A team with many ideas but no basis for comparison needs clearer criteria. A team arguing about whether a process will confuse users may benefit from a simple prototype. The point is to choose the next useful way to learn, not to perform a ritual called design thinking.
| Design mode | Central question | An accessible example |
|---|---|---|
| Empathize | What is happening for the people affected? | Listen to students describe a confusing registration process. |
| Define | What problem or desired outcome should we address? | Clarify whether confusion is about course choices, deadlines, or terminology. |
| Ideate | What different approaches might help? | Consider clearer instructions, guided advising, redesigned forms, or simpler terminology. |
| Prototype | How can we make one idea visible without fully implementing it? | Create a paper version of a revised registration screen. |
| Test | What happens when someone tries it? | Observe where a volunteer becomes confused without coaching them through the answer. |
4.1.1.3 Human-centered does not mean the customer always dictates the answer
People have valuable knowledge about their experiences, but they are not obligated to diagnose every underlying cause or invent the best solution. A patient may accurately describe confusion while lacking visibility into clinical rules. A student may want an instant approval process while the institution must satisfy financial-aid or accreditation requirements. A consumer may ask for a lower price without knowing the minimum costs of delivering a safe service. Human-centered design takes people's experiences seriously while also recognizing expertise, organizational responsibilities, and legitimate constraints.
This balance helps us avoid two opposite mistakes. The first is designing from the organization's perspective alone: “We know what's best; customers will adjust.” The second is treating every stated preference as a nonnegotiable specification: “Someone asked for it, so we must build it.” A stronger approach asks what underlying benefit is needed, what boundaries cannot responsibly be ignored, and what alternative paths might produce that benefit. The International Organization for Standardization's human-centered design guidance for interactive systems emphasizes understanding users, tasks, and environments while involving users and evaluating designs throughout development (ISO, 2019).
For Elena's clinic, this means she can treat patient difficulties as central without assuming that any proposed change is permissible. A paper reminder sample can be discussed without accessing real medical records. A hypothetical scheduling flow can be examined by staff before anyone uses it with patients. Medical, accessibility, privacy, language, and operational experts may need to review later versions. The people who will live with a change deserve a voice in shaping it, but their experiences must be connected with the expertise required to make the change safe and reliable.
4.1.2 Framing and Reframing Problems
4.1.2.1 Why the first problem statement can trap us
Imagine a college supervisor saying, “Our problem is that students don't read emails.” The statement sounds specific, but it contains an explanation before any investigation has occurred. It assumes that email is the correct communication channel, that messages are understandable, and that students have reliable access and enough time to act. Suppose students do read the emails but do not understand an unfamiliar financial-aid term. Suppose a message arrives after a critical deadline. Suppose an important instruction is buried beneath five paragraphs of routine information. A design team that accepts “students don't read emails” as settled truth may spend months designing more eye-catching subject lines when the real problem is different.
A problem frame is the way we define the situation we are trying to improve. Frames influence what information we notice, which people we consult, and which possible answers appear reasonable. Kees Dorst (2011) explains that reframing is a central part of design reasoning because different interpretations of a situation can open different pathways for action. This is not permission to ignore evidence and invent a more convenient story. It is a reminder that the evidence may support several plausible explanations, each of which deserves examination before we commit resources.
Consider how the phrase “We need a better reminder app” frames Elena's clinic problem. It already contains a product choice. “Patients need clearer appointment instructions” is broader but still assumes understanding is the chief barrier. “Some patients encounter preventable obstacles between scheduling an appointment and arriving prepared for care” creates more space for investigation. It makes no promise that a single message or technology will address transportation, scheduling, language, and paperwork problems. Good framing often feels less exciting at first because it removes premature certainty. That can be an advantage.
4.1.2.2 Symptoms, causes, constraints, and consequences
A symptom is something we can observe, such as long wait times or repeated questions. A cause is a condition that helps produce that symptom. A constraint limits what changes are possible, and a consequence is the effect experienced when the situation persists. These terms are related but not interchangeable. Imagine an auto-repair shop where customers complain that updates arrive late. Delayed updates are a symptom. An unclear handoff between technicians and the front desk might be one cause. Customer privacy requirements and limited staff availability may be constraints. Lost trust and unnecessary calls may be consequences. Calling the symptom a cause can lead to a solution that treats only the surface.
One practical method for exploring causes is to ask “Why?” several times, while recognizing that repeating the question does not prove the final answer. Why do customers call repeatedly? Because they do not know the status of repairs. Why don't they know? Because the update is recorded in a place the front desk does not routinely check. Why is the information there? Because two teams use different workflows. The sequence reveals possibilities worth verifying, not a universal law of cause and effect. Multiple causes can coexist; some may be outside the organization's immediate control.
When working with human problems, the distinction also protects against blaming people. “Patients fail to follow instructions” presents the person as the problem. “The instructions require unfamiliar terminology and are difficult to retrieve on a phone” directs attention toward conditions that may be improved. Sometimes individual choices matter, but a design team should not use those choices as an excuse to avoid examining the environment it has created. A productive problem statement makes the affected person's situation understandable without turning a human being into a defect that needs correction.
4.1.2.3 Turning a complaint into a productive design challenge
Design teams often use a How might we…? question to convert a supported problem description into an invitation to explore alternatives. The word how asks us to consider possible approaches; might reminds us that no single answer has been proven; we invites collaboration instead of assuming one expert must solve everything. These questions are helpful when they are neither so narrow that the answer is already chosen nor so broad that no one can act on them. “How might we make every aspect of healthcare perfect?” is inspiring but unusable. “How might we create a blue reminder button?” is testable but prematurely fixes a solution.
A better question for one part of Elena's problem could be: “How might we help patients understand what they need to bring to an appointment, using communication they can realistically access?” That frame gives a design team several directions: clearer language, a short checklist, an accessible message format, staff confirmation, or a better place to find the information later. It also leaves open the possibility that patients need a human conversation rather than another message. The question can change as the team learns more.
A useful test of the frame is to imagine three very different solutions. If your question permits only one, it may already be a disguised answer. If it could cover almost anything, it probably needs a clearer person, situation, or desired outcome. This discipline matters in any career. A restaurant manager might ask how to reduce uncertainty for waiting guests rather than simply how to make servers move faster. A teacher might ask how to make expectations clearer rather than how to make students work harder. Reframing often changes the quality of the next conversation before a single product is built.
4.1.3 Divergent and Convergent Thinking
4.1.3.1 Why the first good idea is a dangerous stopping point
The first plausible solution to a frustrating problem can feel like a discovery. We experience relief because uncertainty has been replaced by a concrete plan. Yet this feeling can narrow our imagination at exactly the moment we most need alternatives. If Elena's first idea is a new reminder template, she may spend hours improving word choices while overlooking the option of changing the timing of reminders, offering a callback route, or redesigning the registration handoff. Her initial idea might still prove valuable. The mistake would be selecting it before comparing it with other paths to the same outcome.
Divergent thinking means deliberately generating different possibilities without immediately forcing a winner. Convergent thinking means comparing, combining, refining, and selecting among possibilities using relevant criteria. The two are complementary, not competing personality types. You do not have to be an artistic genius to practice divergence, and you do not have to be a financial analyst to practice convergence. In one stage you make room for options; in the other you make disciplined choices. IDEO describes this rhythm as creating choices and making choices, repeated throughout design work rather than performed only once (IDEO, n.d.-a).
There is research behind the value of exploring more than one representation. In an experiment involving novice designers creating online advertisements, Dow and colleagues (2010) compared parallel prototypes with prototypes developed one at a time. In that context, producing and comparing multiple versions was associated with stronger evaluated design outcomes and more diverse ideas. That result does not mean every project should generate dozens of designs or that the study proves a universal formula. It does give us a reason to challenge a familiar habit: polishing one answer can become a substitute for asking whether a different answer would be better.
4.1.3.2 Divergence needs a clear question, not an empty room
Telling a group to “be creative” often produces silence or the same three ideas everyone already knew. People need a useful challenge, enough information to understand it, and permission to explore alternatives without immediate ridicule. A well-framed question creates boundaries that stimulate rather than eliminate imagination. “How might we make a service more accessible to students who work evenings?” is more productive than “Invent something innovative.” It names the people and condition while leaving open changes in timing, communication, delivery, staffing, and partnerships.
Divergence works better when participants can think from more than one perspective. A student who has worked in hospitality may understand the emotional cost of unpredictable waiting. Someone with experience in healthcare may notice confidentiality constraints. A parent might see that a supposed convenience still requires childcare. A person with a disability might identify a barrier that other participants overlook. Diversity of experience does not automatically create good ideas, but it can expose assumptions that would otherwise remain invisible. Design teams should create conditions in which people can contribute without being interrupted or treated as spokespersons for everyone in a group.
Imagine three directions for the clinic. One approach improves written information. Another improves conversations between patients and staff. A third changes the scheduling workflow so that important constraints are identified earlier. Each can be subdivided, combined, or rejected based on evidence. The goal is not to accumulate imaginative objects on a whiteboard. It is to expand the range of responsible ways the underlying need might be met. When we later choose, we want confidence that we considered more than our first instinct.
4.1.3.3 Convergence is judgment under constraints
After broad exploration, a team must make choices. Time and money are limited; technical expertise is uneven; safety and privacy obligations cannot be suspended; and a proposed change may burden staff already struggling to keep up. Convergence does not mean selecting the idea that receives the loudest applause. It means making the reasoning behind a choice visible. Criteria might include the importance of the user need, likely accessibility, ease of learning, resource requirements, foreseeable risks, and compatibility with a coherent delivery system.
A simple comparison table can help, but numbers should not create false precision. A team may rate three ideas from one to five on usability or cost, yet those ratings are still judgments unless backed by evidence. Two ideas that receive the same total may have radically different implications. A concept with excellent convenience but unacceptable privacy risk should not win because its average score is high. Responsible design therefore includes nonnegotiable boundaries, such as safety, legal requirements, and respect for people, alongside preferences such as speed and aesthetics.
We can also combine ideas rather than assume there must be one winner. A clear checklist and a staff callback option may work better together than separately. Or the team may decide that a process change is more promising than a new technology. Convergence should lead to the next responsible learning step, not an announcement that the final answer has been discovered. This is especially important for students new to entrepreneurship. Selecting a concept for a prototype is a provisional choice; it is not a declaration that future evidence must support it.
Sketch Three Solutions Before Choosing One
Sam, the prospective bicycle-repair founder we met in earlier Venture Track companions, has heard that bicycle commuters face disruptive repair delays. He could immediately invest in a mobile repair van. But what if that is only one possible way to reduce the disruption? A founder's early tactical skill is learning to turn a supported problem into three genuinely different offers before spending money on the first.
| Concept | What the first customer actually receives | Capability that would be needed | Biggest unknown |
|---|---|---|---|
| Scheduled mobile repair | Qualified repair at an approved worksite or home location | Skills, transport, tools, parts, safe on-site work | Which repairs are practical and worth the travel time? |
| Workplace pickup partnership | Bikes collected and returned through an authorized partner | Reliable handoffs, secure storage, partner agreement | Would employers and riders trust the arrangement? |
| Diagnostic and referral service | Transparent assessment and connection to an appropriate repair provider | Technical judgment, trustworthy partners, clear scope | Would customers value coordination instead of direct repair? |
How a founder uses this: First write one sentence describing the customer's actual problem; then sketch a customer journey for each concept. Do not evaluate the drawings for visual polish. Compare whether each approach would reduce the relevant disruption, how it could be delivered, what safety or liability concerns arise, and which assumption would be most useful to investigate. A simple three-column page is enough for the first pass.
The launch insight
A business idea should be a considered response to a problem—not a commitment that prevents better responses from being discovered. Sam might ultimately launch mobile repair, but comparing alternatives can reveal a narrower, safer, or more viable starting model. A good founder becomes capable of changing the solution while staying committed to the customer's need.
4.1.4 Ideation Methods
4.1.4.1 Brainstorming is a starting point, not a magic technique
A familiar classroom image of creativity involves people sitting around a table calling out ideas while someone writes them on a board. That is brainstorming, and it can be useful. But anyone who has participated in a group knows the difficulties. One confident speaker may dominate. Others may hesitate because their ideas seem unfinished. A participant may forget an idea while waiting to speak. The group may settle quickly on something that feels familiar, socially acceptable, or easy to explain. Creating an enthusiastic atmosphere does not automatically solve these problems.
Research on group idea generation suggests that how ideas are shared and processed influences results. Paulus and Yang (2000) studied forms of brainwriting, in which participants generate and exchange ideas in writing, and found that well-designed sharing and reflection conditions can improve idea generation in their experimental setting. Their work is useful here because it complicates a popular assumption: the most creative meeting is not necessarily the loudest one. Giving people time to think independently, review others' contributions, and add connections can create more room for meaningful participation.
One accessible approach is to let individuals write several ideas silently before sharing them. Then each participant contributes an idea without immediately defending it, and the group builds on or combines ideas before evaluating them. This sequence can reduce the tendency for early opinions to dominate. It is not a guarantee of better results in every team, and the facilitator still needs to make space for people with different communication styles and accessibility needs. But it reminds us that creativity can be organized. We do not have to wait for the most confident person to have an inspiration.
4.1.4.2 Mind maps, analogies, and SCAMPER
A mind map places a central challenge in the middle of a page and uses branches to explore related experiences, causes, people, resources, and possible responses. For a campus food-access problem, branches might include class schedules, transportation, available kitchens, storage, affordability, dietary needs, and time. Connections among branches can reveal opportunities that a simple product list misses. A map is not evidence by itself, but it can help students organize a complex problem and recognize that solutions often involve more than one contributing factor.
Analogies encourage us to look outside the immediate situation. How does a library manage borrowed resources? How does a concert venue guide people through a crowded entrance? How does a warehouse signal that an item is ready? A clinic may learn from an airport's wayfinding principles without copying an airport's security procedures. A restaurant might learn from a repair shop's service updates without inheriting its entire business model. Analogies are useful when they illuminate a mechanism—such as clear status information or predictable handoffs—rather than when they encourage superficial copying.
SCAMPER is a structured set of prompts often used to reshape an existing idea: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse or Rearrange. Consider a complicated course-registration form. Could unfamiliar words be substituted with clearer language? Could two repetitive steps be combined? Could an existing calendar tool be adapted to show deadlines? Could confusing choices be eliminated without removing necessary information? Could the order of the process be rearranged so that students receive essential guidance earlier? SCAMPER does not make each suggestion good. It provides directions for thinking that might otherwise be missed.
| Method | When it is useful | Question to keep in mind |
|---|---|---|
| Brainwriting | When all team members need space to contribute | Are we hearing from people who prefer to think before speaking? |
| Brainstorming | When a team needs rapid shared exploration | Are early comments shutting down unusual ideas? |
| Mind mapping | When a challenge has many related parts | Which connections or overlooked conditions are emerging? |
| Analogy | When a team is trapped in familiar solutions | What mechanism could transfer from another setting? |
| SCAMPER | When redesigning an existing process or offering | Which assumption could we change, remove, or reverse? |
| AI-supported ideation | When exploring alternative concepts or organizing themes | What invented claims, missing perspectives, or hidden biases must we check? |
4.1.4.3 Using AI as a creative partner without outsourcing judgment
Generative AI can produce many ideas quickly. Give it a description of a problem and it may offer a list of possible services, features, names, or processes. For an inexperienced student, that can feel like an enormous creative advantage. But volume is not the same as insight. An AI system can propose an elegant solution to a problem it has not observed, recommend a feature that violates a workplace requirement, or confidently describe customer behavior for which no supporting evidence exists. It may reproduce familiar market assumptions while overlooking people who are poorly represented in its training data.
A better use is to ask AI to help expand or challenge your own evidence-informed thinking. You might provide a fictional, nonidentifying scenario and ask for three approaches that use different resources: one process change, one human-support change, and one technology-assisted change. Then ask what assumptions each makes, what might go wrong, and which people may face barriers. This turns AI into an ideation aid rather than a judge of customer reality. It also protects the skill we are trying to learn: the ability to distinguish a plausible idea from a defensible conclusion.
Sensitive customer, patient, student, or employee information should not be entered into public AI tools without appropriate authorization and safeguards. AI-generated designs also require attention to accessibility, intellectual-property considerations, and whether automated recommendations could create unequal treatment. The designer remains responsible for asking who benefits, who may be harmed, and what evidence supports the proposal. As IDEO's contemporary design guidance emphasizes, questions about what we should create belong alongside what technology makes possible (IDEO, n.d.-b).
4.1.5 Evaluating Ideas Responsibly
4.1.5.1 The three lenses: desirable, feasible, and viable
A creative idea can be appealing and still fail to improve people's lives. Another may solve an important problem but depend on technology the organization does not possess. A third may be buildable but require costs that the intended users or organization cannot sustain. Design teams therefore often consider three connected lenses: desirability, whether a meaningful group of people needs or values the result; feasibility, whether the idea can be made and delivered with available or attainable capabilities; and viability, whether the arrangement can continue under realistic economic and organizational conditions. IDEO uses these lenses to help organizations examine promising innovations (IDEO, n.d.-a).
The lenses overlap with Module 3's business-model thinking, but they ask us to study a solution more closely. Suppose Elena's clinic considers translating reminder materials into several languages. Patients may benefit, establishing a reason to investigate desirability. Feasibility involves qualified translation, accurate medical instructions, accessible formats, and a reliable process for updates. Viability includes how changes will be maintained, who owns the content, and whether the clinic can support the work. No one lens is enough. A highly desirable change can become harmful if implemented with inaccurate information, while a technically easy change may be pointless if it addresses a problem nobody experiences.
In many settings, a fourth question deserves its own place: responsibility. Can the idea be pursued without unacceptable harm, exclusion, privacy violations, or misleading claims? An idea does not become ethical because it performs well on the other three dimensions. The proper goal is not to choose the most exciting proposal and assume the difficult issues will disappear later. It is to discover which concepts deserve responsible examination and what conditions must be satisfied before they could be used in the real world.
4.1.5.2 Accessibility is a source of insight, not a finishing touch
Consider a kitchen utensil that requires strong hands to grip its narrow handle. For someone with arthritis, the difficulty may be painful and immediate. For a child, someone with an injury, or a person carrying several things, it may simply be frustrating. If designers assume that every person uses a product in the same way, they may treat these experiences as exceptions. But taking different abilities seriously can reveal a better design that serves more people. The same principle applies to a website that cannot be navigated by keyboard, an instructional video without captions, or a service that requires a phone call during standard work hours.
In digital contexts, accessibility is not merely a vague preference. The Web Content Accessibility Guidelines (WCAG) provide testable criteria for improving access for people with a range of disabilities (World Wide Web Consortium [W3C], 2024). The details of compliance belong with people qualified to implement and review them, but introductory students should understand the underlying responsibility: a service is not fully designed if significant groups cannot meaningfully use it. Accessibility often affects usability for many people, although one improvement does not automatically solve every need.
An inclusive process also changes whose feedback counts. Testing a form only with highly confident technology users may conceal difficulties experienced by people using assistive technologies, older devices, or low-bandwidth connections. A product demonstration held only in English may not reveal language barriers relevant to the actual service population. Inclusion is therefore both an ethical commitment and an evidence-quality issue. A designer who never encounters different users may confuse familiarity with usability.
4.1.5.3 Unintended consequences and the courage to choose less
Even a well-intentioned design can create new problems. A workplace app that simplifies scheduling for supervisors might make employees feel continuously monitored. A self-service kiosk might shorten average queues while leaving people who need assistance waiting longer. A school reminder system might reduce missed deadlines while generating so many messages that students begin ignoring all of them. The relevant question is not whether a design has any risk—nearly every change does—but whether the risks are understood, proportionate, and responsibly managed.
This is where design thinking benefits from the caution introduced in earlier modules. An organization should examine whose time is saved, whose labor increases, whose privacy may be affected, and which assumptions still need evidence. It can be entrepreneurial to decide not to automate a process, not to deploy a prototype, or not to promise a feature the organization cannot support. Good design may simplify rather than expand. A clearer instruction or better handoff can be more valuable than a sophisticated platform if it addresses the verified need more dependably.
The purpose of evaluating ideas is not to drain creativity of excitement. It is to connect creative possibility with care for the people who will live with the outcome. Tim Brown's (2008) discussion of design thinking and the human-centered principles in ISO 9241-210 both point toward a broader view of design than styling a finished object. We are shaping experiences and systems. That makes responsible judgment an essential part of creative skill.
Entrepreneur-in-Action
OXO Good Grips: When the Handle Was the Problem
In the late 1980s, entrepreneur Sam Farber noticed that his wife, Betsey, who had arthritis, struggled with an everyday kitchen peeler. The problem was not that people lacked vegetable peelers. It was that familiar kitchen tools could be uncomfortable or difficult to use, particularly for someone with limited grip strength. That distinction may sound small, but it changes the design challenge. Instead of asking how to market another kitchen utensil, a designer can ask how a tool might remain comfortable and controllable for people whose hands work differently.
Farber worked with Smart Design to develop the line that became OXO Good Grips. The designers explored handles with larger, softer, nonslip forms. The Museum of Modern Art describes how the handle design was developed for broad ease of use rather than for one narrow group. Smithsonian collections document the original line of utensils introduced in 1990 and the way the design responded to challenges associated with arthritis (Museum of Modern Art [MoMA], n.d.; National Museum of American History, n.d.). This history is meaningful partly because the object remained ordinary. It was still a kitchen tool; the innovation was a more thoughtful relationship between the tool and the person holding it.
A popular version of entrepreneurship imagines that the winning idea must be technologically spectacular or entirely new. OXO offers another possibility: a familiar object can become substantially more useful when someone changes the problem frame. Betsey Farber's experience was not simply a niche inconvenience to be ignored. It was a source of design insight that could make a common task easier for a wider group of people. The company history does not prove that every accessibility-centered invention will succeed commercially, but it illustrates why observation, empathy, and disciplined design belong together.
Think about it: What product, school process, or workplace routine do people tolerate because they assume its inconvenience is inevitable? How might the design question change if you began with someone who finds it especially difficult to use?
Emerging practices
Creativity in an AI-Saturated World
As generative AI makes it easier to produce polished images, interfaces, text, and even working software, the scarce capability may increasingly be the judgment to choose what deserves to exist. A student can now generate twenty designs in the time it once took to sketch two, but that speed also makes it easier to confuse abundance with understanding. Effective design teams will need to document where ideas came from, consider intellectual-property and privacy issues, include people whose perspectives are missing from generated examples, and evaluate actual use rather than approving the most impressive-looking output. The foundational advantage remains human-centered inquiry: better questions, broader perspectives, and more responsible choices.
References
Sources cited in this section. The full Module 4 reference list closes section 4.3.
Brown, T. (2008). Design thinking. Harvard Business Review, 86(6), 84–92, 141. https://hbr.org/2008/06/design-thinking
Dorst, K. (2011). The core of ‘design thinking’ and its application. Design Studies, 32(6), 521–532. https://doi.org/10.1016/j.destud.2011.07.006
Dow, S. P., Glassco, A., Kass, J., Schwarz, M., Schwartz, D. L., & Klemmer, S. R. (2010). Parallel prototyping leads to better design results, more divergence, and increased self-efficacy. ACM Transactions on Computer-Human Interaction, 17(4), Article 18, 1–24. https://doi.org/10.1145/1879831.1879836
IDEO. (n.d.-a). The design thinking process. https://designthinking.ideo.com/process
IDEO. (n.d.-b). Design thinking at IDEO. https://www.ideo.com/methodology/design-thinking
International Organization for Standardization. (2019). Ergonomics of human-system interaction—Part 210: Human-centred design for interactive systems (ISO Standard No. 9241-210:2019). https://www.iso.org/standard/77520.html
Museum of Modern Art. (n.d.). Smart Design, New York. Good Grips paring knife. 1989. https://www.moma.org/collection/works/3754
National Museum of American History. (n.d.). OXO Good Grips carrot peeler. Smithsonian Institution. https://americanhistory.si.edu/collections/object/nmah_1417719
Paulus, P. B., & Yang, H.-C. (2000). Idea generation in groups: A basis for creativity in organizations. Organizational Behavior and Human Decision Processes, 82(1), 76–87. https://doi.org/10.1006/obhd.2000.2888
Stanford d.school. (n.d.). Design thinking bootleg. https://dschool.stanford.edu/tools/design-thinking-bootleg
World Wide Web Consortium. (2024). Web content accessibility guidelines (WCAG) 2.2 (W3C Recommendation, December 12, 2024). https://www.w3.org/TR/WCAG22/