Design Thinking Process: From an Assumption to a Tested Idea

A design-thinking framework and practical process, illustrated through a library booking problem and prototype.

A library installs a new online booking page, yet many study rooms remain empty while visitors say they cannot find a place to work. The team initially proposes a more prominent “Book now” button. Before changing the page, it needs to learn whether visitors have seen the button, understood the booking rules or abandoned the process for another reason.

A design-led process begins with that uncertainty. A framework for design thinking connects observation, problem definition, ideas, prototypes and tests so a team can examine its assumptions before investing in a finished solution. The library example below is hypothetical; its purpose is to show how evidence can change the question a team is trying to answer.

Design thinking framework: a flexible sequence

One design thinking definition describes an approach to solving problems through attention to people’s experiences, experimentation and revision. Stanford’s d.school toolkit groups its methods into five modes: empathize, define, ideate, prototype and test. These names provide a useful structure, but the work need not proceed through them once in a rigid order.

What is the design thinking process in practice? It is a cycle in which a team learns about a situation, frames a problem, makes an idea tangible and uses observations to decide what to change next. A test might send the team back to the problem statement, while an interview might reveal a constraint that makes a promising idea impractical.

The design thinking framework is useful when the problem is not yet well understood and the people affected can help reveal what is happening. It is less useful to treat the steps as a guarantee that any idea will succeed. A team still needs to consider costs, accessibility, operational constraints and evidence beyond the first few conversations.

Observe the experience before prescribing a fix

The hypothetical library team begins by speaking with visitors who tried to find a room, as well as staff who answer booking questions. With permission, it watches people attempt to reserve a space on their own devices. It also reviews existing booking records to see when rooms are reserved and whether reservations are used. Each source answers a different question: an interview can reveal a concern, an observation can show where someone hesitates, and records can show a broader pattern.

The team asks visitors to describe a recent attempt rather than asking whether they would like a larger button. One visitor explains that the trip to the library takes thirty minutes and that availability can change before arrival. Another finds the calendar but cannot tell whether a room requires a minimum group size. Staff report that some people reserve a room as insurance and do not cancel when their plans change.

These observations challenge the initial assumption. The button may still need improvement, but the more consequential problem appears to be uncertainty about access and availability. The team should also note who was not reached: visitors with limited internet access or people who stopped using the library may have different experiences. A handful of interviews offers directions for further inquiry, not a representative estimate of how often each issue occurs.

Define a problem that can guide choices

The team turns its notes into a working statement: “Visitors planning a trip need a reliable way to understand room availability and the conditions for using a space, because an apparently available room may not be usable when they arrive.” This formulation identifies people, a need and an observed obstacle without prescribing a particular interface.

A good problem statement is narrow enough to guide the next test. “Make the library better” does not suggest what to observe; “Make the button blue” has already chosen a solution. The revised statement allows the team to consider both the online information and the way unused reservations are handled.

The team separates observations from assumptions. It observed that some visitors were unsure about group-size rules; it has not yet established that unclear rules cause most abandoned bookings. It can check available records and ask a broader set of visitors. If records do not capture abandonment, the team may need another way to learn rather than inventing a precise figure.

One of the design thinking principles at work here is to make the problem open to revision. The statement is a working explanation, not a permanent verdict. If later tests show that visitors understand the rules but cannot reach the library during opening hours, the team should reconsider the scope of the problem and the people who need to be involved.

Generate and compare possible responses

The team sketches several ideas: clarify eligibility next to each room, provide a short confirmation of availability before a trip, release reservations that are not checked in after a grace period, or let staff help visitors reserve by phone. The alternatives address different parts of the experience and impose different costs. A check-in rule, for example, might improve availability while disadvantaging a person delayed by an accessible transit service.

The design thinking methodology asks the team to explore possibilities before committing, but a long list is not evidence that an idea works. The team compares options against the need, accessibility, staff capacity and the library’s existing rules. It also asks which assumption is both consequential and uncertain. If visitors do not understand eligibility, clearer wording could help; if they understand it but cannot rely on availability, wording alone will have little effect.

The team chooses to test two modest interventions together: a clear eligibility summary and a confirmation step shortly before a reservation. It records the risk that a confirmation requirement might cause visitors to lose a space unfairly. A separate phone route is retained as an alternative to investigate with people who cannot readily use the website.

Prototype the part that needs an answer

A prototype is a representation of an idea that lets people interact with it before the full solution is built. For the first test, the team creates a paper calendar and sample confirmation messages. A staff member plays the role of the system, showing the next page when a participant makes a choice. This is inexpensive and allows wording or timing to change between rounds, while the team keeps track of which version each participant saw.

The team asks visitors to complete a realistic task: “You need a quiet room for two people tomorrow afternoon. Find out whether you can use one and reserve it.” It watches where they look, what they infer and whether they notice the confirmation requirement. A neutral follow-up such as “What would you expect to happen next?” reveals more than “Is this easy?”

The prototype does not prove that the eventual online system will work. A paper test cannot establish whether a message will be delivered reliably or whether the reservation database can release a room safely. It can, however, reveal whether the proposed information and sequence make sense before the team pays to implement them. The d.school’s testing guidance similarly treats a prototype as a way to elicit feedback rather than merely defend a finished idea.

Test, revise, and test again

In the hypothetical test, several visitors understand the eligibility summary but assume the confirmation message is optional. One visitor explains that a phone may be unavailable during a work shift. Staff point out that automatically releasing a reservation could lead to an avoidable dispute at the desk. These observations weaken the proposed confirmation rule even though the clearer room information appears promising.

Using the design thinking model, the team revises its prototype: instead of requiring every visitor to respond to a message, it explores a reminder with an easy cancellation option and a separate check-in process. It also tests whether the room page states eligibility clearly without the facilitator’s explanation. The next round should include visitors with different access needs and a realistic account of staff workload.

The desing thinking approach becomes valuable when learning changes a decision. Here the first test did not merely polish a button: it exposed a risk in the new solution and sent the team back to consider alternatives. Before a wider launch, the library would still need to check technical reliability, operating costs and whether the change improves actual room access over time.

A warning sign is a team that can name every stage but cannot say what observation changed its next decision. Returning to the people affected, identifying the uncertain assumption and testing a specific alternative can restore the connection between the process and the problem it is meant to solve.