Design Thinking
Human-centered problem solving
Design Thinking is a human-centered approach to innovation that starts with deep empathy for users before defining problems, generating ideas, and prototyping solutions. It's iterative and non-linear — teams frequently loop back from testing to earlier stages as they learn. Used both for new product development and for reframing existing problems.
Developed at the Stanford d.school and popularised by IDEO. Tim Brown (IDEO CEO) formalised the framework in the 2000s.
Use Design Thinking when
- ✓You're facing a complex, ambiguous problem where the right question isn't obvious
- ✓Teams are too close to the problem and need fresh empathy with users
- ✓Cross-functional teams need a shared problem-solving language
- ✓Stakeholders need to experience user research firsthand before committing to a direction
Avoid it when
- ✗You have a well-defined problem and just need to execute — Design Thinking is discovery, not delivery
- ✗Time constraints preclude proper empathy research
Key Concepts
Observe and interview users in their context. Suspend assumptions. Understand the problem from their perspective, not yours.
Synthesise empathy research into a problem statement (Point of View). "User X needs Y because Z."
Generate many possible solutions before evaluating any. Diverge before converging. Quantity over quality in this phase.
Build rough, cheap representations of your best ideas. The goal is to learn, not to impress.
Get prototypes in front of users. Observe behaviour, not just opinions. Feed learnings back into earlier stages.
A question format that reframes problems as opportunities. "How might we help users X without Y?"
How it works
Contextual interviews, observation, diary studies. Output: user journey maps, empathy maps, raw quotes.
Affinity mapping of research findings. Synthesis into a clear POV problem statement.
Brainstorming sessions (Crazy 8s, SCAMPER, reverse brainstorming). Converge on the most promising ideas.
Paper sketches, wireframes, clickable prototypes, or service blueprints. Aim for the minimum fidelity that tests the key assumption.
Structured usability sessions or guerrilla testing. Capture observations, not just user opinions.
Tools that support Design Thinking
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Browser-based with no installation required — runs on any OS and enables instant sharing via URL, removing friction for cross-functional collaboration with PMs, engineers, and stakeholders
Best-in-class infinite canvas experience — the gold standard for collaborative whiteboarding with real-time multiplayer editing
Dominant platform for source control and collaboration — used by 100M+ developers, making it the de facto standard for open-source and most commercial software teams
Frequently Asked Questions
Design Thinking is a broader problem-solving framework that includes UX research methods but also covers problem framing, ideation, and prototyping. UX research is one input to Design Thinking, not the whole framework.
A Google Design Sprint (Jake Knapp) runs the full cycle in 5 days. A full design research project might take 4–6 weeks. Many teams run a lightweight version — 2 days of interviews, 1 day of synthesis, half-day ideation.