What is this book about?
A primer on design thinking — its process, building blocks, and applications across diverse fields
Design thinking is a process for creative problem solving that originated in architecture and design but has spread far beyond those fields. Andrew Pressman's book is one of the most accessible introductions available — it is written for individuals, not teams, and requires no prior design training. The central argument is that anyone can learn to think like a designer, and that doing so leads to better, more innovative, more empathy-driven solutions to almost any problem.
The book is organised into two parts. Part 1 lays out the process itself in careful detail — the five building blocks that form the design thinking loop, and the tools and strategies (diagramming, reflection, presentation) that support it. Part 2 demonstrates the process in action through a series of real-world vignettes drawn from politics, business, health, law, and writing, each based on interviews Pressman conducted with practitioners who have applied design thinking meaningfully in their work.
A distinctive feature of the book is its insistence that design thinking is not a formula. The process should be customised to the problem at hand. Building blocks can be merged, skipped, reordered, or weighted differently depending on context. The goal is always an optimal solution — not a perfect one, which does not exist — that addresses the highest-priority objectives while satisfying as many stakeholder requirements as possible.
🔄 The Design Thinking Loop
The loop is non-linear. Building blocks can be combined, skipped, or weighted differently depending on the problem. Click any block to explore it in depth.
🧭 Six Defining Principles
🔁 Iteration Over Perfection
There is no single right answer. Solutions improve through successive loops of making, testing, and revising. The optimal solution — not the perfect one — is the goal.
🤝 Empathy Is Central
Deep understanding of stakeholders — their motivations, constraints, and unspoken needs — is what distinguishes design thinking from conventional analysis. You must immerse yourself in others' realities.
🎯 Define the Right Problem
Never accept problems at face value. The real problem is often masked. Rigorous analysis, probing questions, and contextual investigation are required to find the problem worth solving.
💥 Failure Is Information
Bad ideas and failed prototypes are valuable. They surface constraints, generate unexpected insights, and push thinking toward more innovative alternatives. IDEO's mantra: "Fail often to succeed sooner."
🌀 Embrace Ambiguity
Comfort with uncertainty is a core skill. You will not have all the information when you start. That's fine — design thinking is built to operate productively in incomplete information conditions.
✨ The Goose Bump Factor
Great design thinking reaches beyond the functional solution to something that stakeholders didn't know they needed — something that elicits an emotional response. Always look for this transcendence.
Chapter Navigator
Click any chapter to read a detailed summary with key insights and quotes
This opening chapter frames the book's central question: what exactly is design thinking, and how is it different from other problem-solving approaches? Pressman resists offering a single definition, acknowledging that there is no general agreement across disciplines. Instead, he offers five characterisations: DT is a process, a skill, a tool, a mindset, and a series of actions structured by a loop. He distils the process into five building blocks — information gathering, problem analysis, idea generation, synthesis through modelling, and critical evaluation — that form a non-linear loop to be traversed as many times as the problem requires.
The crucial insight of this chapter is that design thinking must be customised. A prescriptive step-by-step approach is itself a flaw. The building blocks can be cherry-picked, merged, reordered, or expanded. The process can be just as creative as the outcome it produces. Pressman also distinguishes DT from hypothesis testing and conventional research: unlike science problems, there is no single right answer, and solutions may actually change the initial question through the act of prototyping.
Sections
This is the book's most substantial chapter, walking through each of the five building blocks in depth. Information gathering is discussed through the lens of empathy — drawing on ethnographic methods and Clifford Geertz's "thick description" to argue for deep immersion in stakeholders' realities. Pressman provides detailed guidance on conducting effective interviews (preparation, rapport, active listening, probing questions, observation, avoiding leading questions). He also covers precedents (analysing prior solutions to similar problems) and context (the full environmental, social, and historical backdrop of the problem).
Problem analysis and definition challenges readers not to accept problems at face value. The right problem is often not the stated problem. Analysis should yield a clear, multi-dimensional understanding of root causes, stakeholder conflicts, and constraints before brainstorming begins. Idea generation is treated at length: brainstorming tips, the importance of withholding judgement, generating "wild and crazy" ideas, working in baby steps, using constraints as creative fuel, the "what if" game, and the danger of typical brainstorming mistakes. A distinctive concept is the goose bump factor — the magical intangible that separates a competent solution from a great one.
Synthesis through modelling covers prototyping — taking the best ideas to higher resolution. The prototype is both a design tool (a "conversation" between the thinker and the project) and a testing vehicle (to elicit the most constructive critique). Critical evaluation emphasises seeking diverse feedback, cultivating self-criticism, and responding constructively to challenges without becoming defensive.
Sections
This shorter chapter describes three supporting tools that advance the design thinking process. Diagramming is treated broadly — bubble diagrams, mind maps, flow charts, Post-its, outlines, and any visual representation of information that helps design thinkers understand problems and communicate ideas. Pressman argues that sketching is the most immediate brain-to-hand means of expression and quotes Donald Schön's concept of "reflective conversation with the situation." He cautions against over-reliance on digital tools in early stages.
Reflecting is perhaps the chapter's most charming section, organised around the metaphor of walking your dog. The creative pause — stepping away from intensive work to let ideas incubate — is essential. Sleep, walks, showers, coffee shops, and unstructured time all serve this function. "Time for reflection is crucial for making sense of all the information, and for discovering meaningful insights."
Presenting covers both verbal and graphic presentation skills. Pressman draws on Weld Coxe's view that the presentation is itself a design problem, and Roger Fisher and William Ury's concept of "principled negotiation" to frame stakeholder conversations not as battles to win but as collaborative processes of mutual enlightenment. Tips cover projecting confidence, grabbing the audience, speaking without jargon, and creating graphic focus.
Sections
This chapter argues that design thinking is a critical leadership tool in the political arena. Through interviews with two practitioners — former US Congressman and Ambassador Richard Swett, and Carmel City Councillor Victoria Beach — Pressman shows how design thinking can expand civic participation, break deadlocked debates, and create solutions that were previously unimaginable.
Swett describes how he co-authored the Congressional Accountability Act — landmark legislation requiring Congress to abide by the laws it passes — by literally approaching it "like designing a building": taking a blank piece of paper to all interested groups, listening to their designs, and then integrating and synthesising their input into alternative schemes for review. The process, entirely foreign to Congress at the time, ultimately passed 97-3 in the Senate and 433-3 in the House. He also describes using team-based management to transform morale at the US embassy in Denmark — replacing siloed agency structures with cross-agency project teams.
Beach's two vignettes illustrate different tactics. In the Flanders Mansion case, she broke a decade-long intractable dispute between pro-sale and pro-preservation factions by presenting newly uncovered facts that reframed the cost-benefit calculus, then proposing a third option — essentially, doing nothing — that neither side had previously considered. In a transportation board meeting, she secured a $20 million trail project not by advocating for it directly, but through a tactically timed procedural amendment that redirected the debate.
Vignettes
The book's richest application chapter, spanning six vignettes from a personal chef to a university president. Michael Tardif (Building Informatics Group) describes two examples: a "strategic plan as jigsaw puzzle" — implementing a technology plan non-linearly by inserting puzzle pieces opportunistically rather than following a linear sequence — and a business venture that arose from a Eureka moment: realising that building owners don't need the BIM model, they need the information inside it, structured in a form useful to facility managers from day one of occupancy.
Francesco Crocenzi (chef, Frankie's Table, Seattle) walks through the design thinking analogy in cooking: analysis and vision drive dish development, iteration and client feedback refine it, and the most important creative lesson is not to take criticism personally. Meredith Kauffman describes a pharmaceutical case where a designer embedded in an R&D team used a jury-rigged arthritic glove to generate empathy for elderly denture-adhesive users, ultimately identifying the real problem (over-application, not denture fit) and driving an innovative metered-dose delivery device.
James Barker (former Clemson University President) credits design thinking — especially visioning, listening, and diagramming — for transforming Clemson from ranked 74th to a top-25 public university, raising $1 billion in private funding, and managing the 2008 financial crisis with creativity. Diego Ruzzarin (Foodlosofia) describes the "fast-fail and iterative" approach to food innovation, including a case where reconnecting with lapsed adult cheese-snack consumers required abandoning the children's market entirely — a decision discovered through empathic interviews revealing that sticky fingers interfere with smartphone use. Scott Phillips (SearchLite) offers a masterclass on interview methodology as design thinking, using dinner-conversation dynamics, active listening, confirmation bias avoidance, and iterative question refinement.
Vignettes
This chapter examines the convergence of design thinking and medicine, framed by Peter Lloyd Jones's claim that training doctors to see the world through a designer's eyes improves clinical skills and empathy. Dr. Bon Ku leads the first design curriculum in US medical schools, at Thomas Jefferson University. He describes using design thinking to make the emergency department less stressful — having students conduct interviews, prototype app solutions, and map patient journeys to understand how people with different social circumstances navigate the healthcare system when suddenly ill. The central finding: "not all patients are the same," and treatment plans should be designed with that in mind.
The second vignette is more speculative but conceptually powerful. Pressman traces a case of cancer treatment innovation derived from a design-thinking mindset: reframing the question from "how do we destroy cancer cells?" to "what if there is a better means to achieve remission without destroying them?" This led to research on transforming cancer cells into healthy mature cells using retinoic acid — an approach inspired by the researcher's reading of Confucius on education versus punishment. The creative trigger came from an entirely unrelated domain.
Vignettes
Two lawyers demonstrate how design thinking transforms legal practice. Charles Heuer (The Heuer Law Group) argues that legal methodology is often too rigid: lawyers prepare complaints, list every legal wrong, and pursue all of them — spending $50 to protect against a $5 problem. Design thinking reframes this. When a client presents a problem, the first response should be: "Is that really the problem?" Heuer insists that identifying the right problem is as much a creative act as solving it. He also discusses "dialogue as iteration" — how successive rounds of conversation with adversaries progressively illuminate core interests.
Jay Wickersham (Noble, Wickersham & Heart LLP, Harvard law and architecture) identifies three ways design training enriches legal work: synthesising information from diverse sources (the opposite of legal training's narrowing impulse), visual and graphic thinking (translating legal complexity into simple diagrams), and the concept of alternatives. Wickersham never gives clients just one answer — he presents multiple alternatives with their pros and cons, because the final solution usually borrows from all of them and clients are more invested in solutions they've helped select. He also draws a powerful analogy: just as you don't jump to construction documents before concept design, you shouldn't move to a final legal agreement before doing concept-level work on the structure of the arrangement.
Vignettes
The final chapter treats writing as a design thinking process. Mark Childs (University of New Mexico, author of multiple award-winning books) offers the most fully theorised treatment: the draft is a prototype, and every draft is a test that may actually change the question being asked. He describes writing as iterative and non-linear — you start without knowing where you'll end up, and the act of writing itself reveals the real question. He advises splitting the mind into writer and editor modes, using trusted and untrusted reviewers at different stages, and understanding that closure is a matter of aesthetic judgement rather than objective completion.
Michael Tardif contributes a memorable metaphor: "rolling the snowball downhill." Don't start with Chapter 1, Page 1 — start with the easiest material and build momentum. This reframes writing from a daunting linear task into a non-linear accumulation of manageable wins, consistent with his strategic-plan-as-jigsaw-puzzle approach. Charles Linn (former Deputy Editor, Architectural Record) adds the importance of metaphor as a brainstorming tool in writing — finding an image that makes readers' imaginations "take a leap with you" — and underscores that early drafts are brush strokes, not final statements; infatuation with early writing must not block revision.
Vignettes
Core Concepts Explorer
Select a building block or concept to explore it in depth
Information Gathering
Building Block 1 of the DT loop. Design thinking begins with immersive discovery — deep research into the problem's context, stakeholders, and history. Pressman borrows from anthropology, journalism, and social science to describe this phase.
What it involves
- Empathy and ethnography: Spending time with stakeholders in their natural environment; going beyond what they consciously articulate to understand what drives and motivates them. Think of Clifford Geertz's "thick description."
- Effective interviews: The most important tool. Done well, an interview reveals emotional connections, unspoken problems, and creative triggers unavailable through any other method.
- Precedent analysis: Studying prior solutions to similar problems. Not to copy them, but to extract underlying principles that might transfer — or to understand what not to do. "Use the great idea but tweak and purposefully apply it."
- Context investigation: Every problem has a unique mosaic of physical, social, cultural, and historical factors. Without contextual knowledge, assumptions about solutions are likely to be wrong.
Interview: 8 tips from the book
- Do your homework. Form hypotheses about the issues before meeting. Prepare questions as background — not a script to read from.
- Establish rapport. Share your own story. Be genuine. Cultivate a respectful alliance where the stakeholder feels taken seriously.
- Listen actively. Process everything being said; test hypotheses by paraphrasing; discover what is said "between the lines."
- Formulate probing questions. Ask: Why did you do that? How did it work out? How do you feel? What did you expect? Dig deeply.
- Observe sensitively. Note body language, emotional state, environment, furnishings, artefacts. The surroundings reveal as much as the words.
- Maintain a sense of humour. It establishes rapport and helps stakeholders open up. Steve Martin on Carl Reiner: "a gentle way of speaking difficult truths."
- Don't interrupt. You could miss an important nuance. Silence is productive.
- Avoid leading questions and yes/no questions. Don't manipulate the interviewee toward the answer you want to hear.
Problem Analysis and Definition
Building Block 2. Perhaps counterintuitively, defining the right problem is itself a creative act. Design thinking insists that the stated problem is rarely the real problem — rigorous analysis is required to uncover what actually needs solving.
The core challenge
- Challenge every problem statement. The real problem may be masked by an immediately visible symptom. Stakeholders often misdiagnose their own situation.
- Ask the right questions. IBM in the 1960s framed the photocopying market question too narrowly ("copies from originals") and missed the larger opportunity of "copies of copies of copies."
- Reframe continuously. Continue the dialogue, diagnosis, and reframing throughout the process — not just at the start. Each loop of the DT cycle can produce new information that shifts the problem definition.
- Avoid the status quo. Even in the questions you ask initially, resist business-as-usual framing. The design-thinking mindset starts before any analysis.
Analytical tasks before idea generation
- Document specific and frequently expressed stakeholder comments, emphasising different sides of the problem
- Identify areas for further research to complement interviews
- Develop lists, diagrams, and images highlighting key context observations
- Formulate new questions about the validity of the initial problem statement
- Note unexpected patterns, relationships, or insights
- Eliminate extraneous material (carefully)
- Uncover fundamental causes of the problem
- Collapse an overwhelming problem into smaller, manageable components
- Filter information into general and specific categories for complex problems
- Set forth design criteria: constraints, challenges, objectives, hopes, and dreams
Idea Generation
Building Block 3. Once analysis is complete and knowledge internalised, "the real fun begins." This is the most creative phase — where imagination, epiphany, and structured brainstorming combine to generate a rich pool of ideas, good and bad alike.
Brainstorming essentials
- Do not judge ideas during the session. Evaluation comes after — not during — brainstorming. The natural tendency to evaluate is the biggest enemy of creativity here.
- Generate wild and crazy ideas. Standard and obvious solutions are fine, but quantity and imagination matter more than quality at this stage.
- Develop as many ideas as possible. Sheer quantity improves the odds of finding something special. Perfection is not the goal.
- Combine and build upon ideas. Synthesising, subdividing, and recombining ideas is part of the natural progression. Post-its under different headings help organise this.
The right attitude
✓ Embrace ambiguity
There will be many unknowns. New information will arrive mid-process. Expect it. Comfort with uncertainty is a fundamental design skill.
✓ Confidence in the process
Assume success. Initial ideas are especially delicate — protect them from premature criticism while they develop.
✓ Have fun
Approaching ideation as play unlocks creativity. If the work feels like play, you brainstorm more freely and take more risks.
✓ View constraints as fuel
"With a bit of creativity, problems can be transformed into unique assets." Constraints force more inventive solutions.
Brainstorming tips
- Withhold judgement — archive all ideas, even ones that seem bad
- Focus sessions on specific aspects, big picture, or process design
- Engage in trial, error, and refinement — take action; it provides a basis for further exploration
- Become immersed — ideas emerge as the issues are understood more deeply
- Do something different; take a risk
- Treat bad ideas and failure as opportunities, not embarrassments
- Play "what if" — develop questions before worrying about answers
- Be passionate — find personal connection to the problem
- Use words deliberately — vague words like "cluster," "layer," "intersect" can spark images
- Work in multiple scales simultaneously
The Goose Bump Factor
One feature that distinguishes great design thinking is striving to integrate a magical element — a critical intangible that separates a competent solution from a great one. Not all problems are amenable to this, but always look for the opportunity to transcend the practical problem. Honor the problem but also create something beyond the immediate utility of the solution — something that stakeholders might never have imagined. Reach for the greatest potential within the constraints, hopefully eliciting an emotional response. This is design thinking at its best.
Synthesis Through Modeling
Building Block 4. Take the best ideas from brainstorming to a higher degree of resolution by building a prototype — a model, draft, or operational demonstration of the idea. This phase involves convergent thinking: narrowing down from many ideas to the most promising ones.
Two goals of building a model
- Develop the idea into a coherent solution. Making things — whether a physical model, a narrative, a business model, or a draft — is crucial to innovation. Cogitating only gets you so far. "Sometimes it takes building a prototype to have that Eureka moment."
- Generate feedback through testing and evaluation. The model should be a close enough embodiment of the proposed solution to elicit the most constructive critique from stakeholders and peers.
What counts as a prototype?
A prototype or model is not necessarily an object. It can be:
- A strategy or business plan
- A written draft or narrative description
- An app, experience, or service flow
- A cardboard model, ripped apart and rebuilt
- A diagram, outline, or set of annotated Post-its
- A storyboard or journey map
- A spreadsheet or data structure
Key axioms during synthesis
- Consider stakeholders' perspectives at every step of prototype development
- Pursue several alternatives concurrently for critical evaluation — don't commit to one prematurely
- Responses to early prototypes may alter the direction of subsequent development — stay open
- Build quickly and keep the dialogue flowing; avoid striving for perfection in early iterations
- Do not underestimate the power of serendipity when making the prototype
- A functioning prototype is more persuasive than a brilliant idea on paper
Critical Evaluation
Building Block 5. Frequent conversations about the work — exposing it to criticism from diverse sources — amplify ideas, eliminate weak alternatives, and suggest new directions. Pressman argues that valid criticism is an opportunity, not a threat.
Why feedback matters
"When you have to articulate an idea and respond to criticism you are forced to think through more aspects of an issue, and ideas tend to become more concrete. On the other hand, if you keep something locked inside your head without having a dialogue, the reflection phase is neglected as you charge forward, with potential loss of opportunities and insights." — Madlen Simon
Responding well to criticism
- Avoid the natural propensity for defensiveness — resist it consciously
- Try to understand precisely what the critic is asserting; form a hypothesis and restate it back to them
- Extract the best of feedback and build on it; dismiss what is clearly off base
- Consider adjustment as an opportunity to make the project more sensitive and responsive — not as compromise
- Respond to stakeholder suggestions explicitly; show how their input was incorporated. This builds ownership ("sweat equity") in the solution
- Sometimes think of the project as a completely different assignment — this demonstrates that there are many valid approaches
The art of self-criticism
Be your own devil's advocate. Test the strength of initial ideas against the problem definition. Once their value is proven, continue testing to ensure coherent development. When critically reflecting on a solution, ensure that every decision relates to the bigger concept in some way. "Criticism can make us see familiar things from new perspectives, shake us out of our shopworn habits, and provoke us into thinking about problems we might otherwise overlook." — Christopher Mead
Tools and Strategies
Three supporting tools that advance the design thinking process: diagramming (visual thinking), reflecting (incubation), and presenting (communication and dialogue).
Diagramming
- Converting information into visual forms is analytically illuminating and inspires creativity
- Types include: bubble diagrams, mind maps, flow charts, decision trees, concept maps, outlines, Post-its, annotated sketches
- Sketching is the most immediate brain-to-hand means of expression (Donald Schön: "reflective conversation with the situation")
- Digital tools are powerful but may make you less flexible in early stages; rough freehand lines carry creative ambiguity
- The goal is exploration and idea capture — not how the diagram looks
Reflecting
- The creative pause is essential — step away after intensive work sessions to let ideas incubate
- Take a walk (the "dog walk" metaphor); leave the smartphone behind
- Ideas take time to grow; working on an unrelated task can yield insights later
- If frozen, come back to the problem at a later time from a different viewpoint, change medium, alter routine, vary environment
- Not everything has to be billable time: "Time for reflection is crucial for making sense of all the information"
Presenting
- Think of the presentation as a design problem: how do you tailor it for maximum reception by this audience?
- Show some of the process since inception; justify major design decisions
- Apply principled negotiation (Fisher and Ury): everyone is on the same team; the goal is mutual understanding, not winning
- Verbal: project confidence and passion; grab the audience; speak clearly without jargon; maintain eye contact
- Graphic: never let format overshadow content; annotate drawings; create a focal point; be judicious with colour
- Prepare a compelling take-away summary package
Empathy
Arguably the most important concept in the entire book. Empathy runs through every building block of design thinking — it is not a single phase but a continuous orientation toward understanding others' realities, motivations, and unspoken needs.
What empathy means in practice
- Spending time with stakeholders in their natural environment — not just talking to them
- Going beyond conscious wants to what really drives, excites, and motivates a person, group, or company
- Listening for emotional shifts in conversation — when you've touched on something someone feels deeply about
- Creating an emotional connection to the problem: "Once you get inside the minds of people or groups, the universe starts to open up"
- Assuming the role of stakeholder advocate — acting as a proxy for the user rather than speaking on their behalf without immersing yourself first
The pharmaceutical empathy example (Meredith Kauffman)
A designer embedded in a pharmaceutical R&D team made a jury-rigged gardening glove with hard plastic bits on the fingers to simulate arthritic hands. By wearing the glove while trying to use the denture adhesive product, the team felt — rather than just heard — the problem: the product was too viscous and too difficult to apply for the elderly consumers it was designed for. This led to an entirely new delivery mechanism (a metered-dose click device), and the recognition that the real problem was over-application — not the denture fit that everyone had assumed.
"The better we can get to know the people who will be using the spaces, solutions, or products that we design, the better problem solvers we can become."
Empathy and travel
Madlen Simon offers an unexpected application: design thinking has enhanced her travel experiences. "Now that I'm armed with empathy skills, I find that I'm much more able to reach out to people; to start conversations and learn a lot more about the place I'm visiting, rather than just walking around by myself. I'm really trying to see places through other people's eyes — that's an incredible way to enrich the travel experience."
Case Study Browser
Filter by field to explore all 14 real-world applications of design thinking from the book
Congressional Accountability Act
Co-authored landmark legislation by approaching it like designing a building — taking a blank piece of paper to all interested stakeholder groups and synthesising their inputs. Passed 97-3 in the Senate, 433-3 in the House.
US Embassy, Denmark — Team Restructuring
Transformed morale in a siloed 16-agency embassy by replacing individual agency structures with cross-agency project teams — modelled on architectural firm practice. Morale rose dramatically as staff found genuine problem-solving engagement.
Flanders Mansion, Carmel
Broke a decade-long dispute between pro-sale and pro-preservation factions by presenting newly uncovered facts and proposing a third option neither side had imagined: simply treat it as a "folly in the park" and stop spending money discussing it.
$20M Trail Project — Procedural Creativity
Secured approval for a major trail project not by advocating for it directly, but by proposing a "friendly amendment" at the last moment that redirected procedural debate and avoided a deadlocking subcommittee. The cause's advocates were briefly confused — but the project was funded.
Strategic Plan as Jigsaw Puzzle
Implemented a technology plan for a construction company non-linearly — inserting puzzle pieces opportunistically rather than following a linear rollout. The "jigsaw puzzle" metaphor gave staff a shared language for a messy but visionary process.
BIM Data: Eureka on Information Delivery
Discovered that building owners never use the BIM model — they want the information inside it, structured usefully for facility managers from day one of occupancy. This reframe launched an entirely new business venture.
Creativity in the Culinary Arts
Design thinking applied to cooking: analysis of flavour relationships drives dish creation; client feedback refines it; and dietary constraints (no salt, low cholesterol) become creative challenges. "All of this reinforces the story of design thinking."
Denture Adhesive Innovation
An embedded designer wore a jury-rigged arthritic glove to demonstrate that the real problem for elderly users wasn't denture fit but difficulty applying the adhesive. Led to a metered-dose click device. Empathy, not market research, drove the breakthrough.
Clemson University Transformation
Used visioning, listening, and diagramming to transform Clemson from ranked 74th to top-25, raise $1 billion, and navigate the 2008 financial crisis. Sketching — diagrams of overlapping and disconnected circles — drove key strategic insights.
Cheese Snack Fast-Fail
A shrinking cheese snack market was revived by abandoning the children's target audience entirely — discovered through interviews revealing that sticky fingers interfere with smartphone use. Empathic research, not conventional analytics, revealed the real barrier.
Dinner Conversation as Interview Method
SearchLite conducts 30-minute "dinner conversations" (not structured interviews) to discover market fit for university inventions. Active listening, confirmation-bias avoidance, iterative question refinement, and progressive referral to better experts are central to the method.
Medical Design Program — Thomas Jefferson University
The first US medical school design curriculum covering all four years. Students use design thinking to address overcrowding, patient stress, and provider frustration — including prototyping a text-reminder app and creating patient journey maps to understand social determinants of care.
Cancer Cell Transformation (Retinoic Acid)
A researcher reframed the cancer treatment question from "how do we destroy cancer cells?" to "what if we educate them?" — inspired by a passage in Confucius. Retinoic acid can transform certain cancer cells to healthy maturity. Creative trigger came from an entirely unrelated domain.
Problem Definition Before Legal Strategy
Argues that lawyers often pursue the stated legal problem without questioning whether it's the right one. Design thinking starts with "Is that really the problem?" — and uses research, reflection, and dialogue as iteration to uncover the issue worth solving. Wedding dancing video: unrelated detail discovered the real issue.
Alternatives and the Big Idea in Legal Practice
Harvard law + architecture. Always presents clients with multiple alternatives (with pros and cons) rather than a single "right" answer. Uses diagrams to translate legal complexity into simple visuals. Applies concept design before contract drafting. Maintains the "big idea" through all iterations.
Draft as Prototype
Every draft is a prototype to be tested. Writing iteratively reveals the real question you're working on — the act of writing itself changes what you think you're doing. Two-mode approach: pure writing mode, then editor mode. Not linear; not a math problem with a correct answer.
Rolling the Snowball Downhill
Don't start with Chapter 1, Page 1. Start with the easiest material; build momentum and knowledge before tackling harder sections. Quickly builds accomplishment and sharpens thinking. The process is messy and non-linear — but the jigsaw puzzle vision keeps it oriented.
Getting to the Aha Moment
"You don't necessarily know what the idea is; you know there is an idea somewhere but you have to try all these iterations in order to discover it." Early drafts are brush strokes. Metaphor is a key brainstorming tool — it makes readers' imaginations "take a leap with you."
Practical Toolkit
Actionable tools, templates, and techniques drawn directly from the book
Empathic Interview Framework
A structured approach to stakeholder interviews that goes beyond surface-level information to surface motivations, emotions, and unspoken needs.
- Before the interview: form hypotheses about the issues; prepare questions as imprinting, not a script
- Open with rapport-building: share your own story; find common ground; model the behaviour you want
- Listen actively: process what is said; paraphrase to invite clarification; note what is said "between the lines"
- Ask probing follow-ups: "Why did you do that?" "How did it work out?" "What did you expect?" "How do you feel?"
- Observe the environment: body language, emotional state, surroundings, artefacts — all are data
- After the interview: write your impressions immediately while still fresh; do not leave note-taking to memory
- Look for patterns across multiple interviews; use secondary research to validate or challenge what you heard
Problem Redefinition Checklist
Use this when the problem has been presented to you. Never proceed directly to solutions without working through these questions.
- Ask: "Is this really the problem?" What evidence supports the stated problem definition?
- Identify who stands to benefit or lose from different problem framings — whose definition is this?
- List all the underlying causes you can identify. Which is the root?
- Ask: "What would solving this look like in ten different ways?" (widens the solution space)
- Reframe the problem as a question: "How might we..." rather than "We need to..."
- Collapse the problem into smaller components; tackle the most salient one first
- Set design criteria: what are the constraints, challenges, and hopes? These become your evaluation framework
Brainstorming Session Guide
Run a productive individual or group brainstorming session using Pressman's principles and Alex Osborn's foundational techniques.
- Separate brainstorming time from evaluation time — never critique during generation
- Set a time limit (e.g., 20 minutes) and commit to generating as many ideas as possible — quantity over quality
- Use Post-its, index cards, or a whiteboard; allow free movement and physical arrangement of ideas
- Invite wild and crazy ideas explicitly — they often trigger the most innovative directions
- Combine, build upon, and recombine ideas as they accumulate
- After the session: review against the problem definition; categorise; identify the most promising for prototyping
- Archive all ideas — including bad ones. You may revisit them later in a new light
The Jigsaw Puzzle Method
For large complex projects where a linear implementation plan would be too rigid or disruptive. Based on Michael Tardif's strategic technology planning approach.
- Define a clear vision of what the "completed picture" looks like — the end state, in measurable terms
- Resist the urge to map out every detailed step before starting. You don't need all the pieces placed to make progress
- Identify opportunities to advance the vision opportunistically, inserting "puzzle pieces" wherever they fit
- Synthesise new information as it becomes available and adjust the approach — maintain the vision, not the plan
- Use the metaphor actively with your team: "What piece of the puzzle is that?" keeps everyone oriented
- Revisit the overall picture regularly to ensure the non-linear progress adds up to coherent progress
Presenting Alternatives
Rather than delivering a single "right" answer, present multiple alternatives with their pros and cons. Based on Jay Wickersham's legal practice approach — equally applicable to policy, business, and design.
- Generate at least 3 meaningfully different alternative approaches (not variations on the same idea)
- For each alternative, list its advantages, disadvantages, and trade-offs clearly
- Indicate which you recommend and why — but leave the choice visible
- Present alternatives visually where possible: a simple diagram often communicates what prose cannot
- Invite discussion: "Which elements from each option are most important to you?"
- Expect the final solution to borrow from multiple alternatives — this is the most common outcome
- Document how stakeholder input shaped the final direction; build ownership ("sweat equity")
Draft-as-Prototype Writing Process
Apply design thinking to writing. Based on Mark Childs's and Michael Tardif's approaches to non-linear, iterative writing as a design process.
- Start with the easiest material — not Chapter 1, Page 1. Build momentum by knocking off manageable sections first
- Put your internal editor away while writing. Use brackets, asterisks, or margin notes for unresolved questions — keep moving
- After a draft: switch to editor mode. Does it make logical sense? Emotional sense? Can readers follow the arguments?
- Test with a sympathetic reader first; only when stronger, expose to unsympathetic critique
- Understand critics' context — their agenda, expertise, and relationship to your target audience — before deciding how much weight to give their feedback
- Look for the aha moment: the insight that restructures everything. Be ready for early drafts to reveal that your real question is different from your starting one
- Closure is aesthetic, not algorithmic. Has the piece gelled? Does it have resonance? Trust your judgement
📣 Essential Quotations from the Book
The process can be just as creative and unique as the outcome. Keep your eyes open and free your imagination in response to the challenge at hand.
Never accept problems at face value — always challenge them to either affirm their validity or recast them after further investigation.
What you're really looking for in addition to the facts is the emotions. If you can put up sensitive antennae and listen for emotional shifts in the conversation, you can begin to know when you've touched on something that the person feels deeply about.
Design thinking has taught me to know when it is time for patience and when it is time for urgency.
Criticism can make us see familiar things from new perspectives, shake us out of our shopworn habits, and provoke us into thinking about problems we might otherwise overlook.
Design thinking amplifies the standard algorithms that we use.
Design thinking is not a luxury for society — it's a necessity.
The solution favors the prepared mind.
Ask AI About This Book
Use Google Gemini to ask any question about Design Thinking by Andrew Pressman
🔑 Gemini API Key
This companion uses Google Gemini to answer your questions. Get a free API key from Google AI Studio (aistudio.google.com), then paste it below. Your key is used only in your browser and is never stored.