Design thinking is a non-linear, iterative process used by teams to understand users, challenge assumptions, redefine problems, and create innovative solutions. While the philosophy is deeply human-centered, the practical execution relies heavily on structured frameworks. Templates act as the scaffolding for this process, ensuring that collective creativity does not devolve into chaotic brainstorming.

To move effectively through the five stages—Empathize, Define, Ideate, Prototype, and Test—innovation leaders utilize specific artifacts to organize insights and spark breakthroughs. This resource provides a deep dive into the most effective design thinking templates, complete with practical implementation strategies derived from real-world workshop facilitation.

Quick Reference: Core Templates by Phase

Phase Core Templates Primary Goal
Empathize Empathy Map, Persona, Journey Map Build deep user understanding.
Define POV Statement, HMW Questions Narrow down to a solvable problem.
Ideate SCAMPER, Brainwriting, Priority Matrix Generate and filter creative ideas.
Prototype Storyboard, Prototype Brief, Service Blueprint Make ideas tangible for testing.
Test Feedback Capture Grid, Testing Script Gather actionable user feedback.

The Empathize Phase: Mapping the Human Experience

The first stage of design thinking focuses on setting aside your own assumptions to gain insight into users and their needs. In our experience, teams often rush this phase, leading to "solutions looking for a problem." High-quality empathy templates force teams to confront the reality of the user's life.

1. The Empathy Map

The Empathy Map is a visual tool divided into four quadrants: Says, Thinks, Does, and Feels. It helps teams synthesize observations from user research and interviews.

  • Practical Use: After conducting user interviews, gather the team to fill this out.
  • The "Experience" Insight: In professional workshops, the "Feels" quadrant is the hardest to fill but the most valuable. Don't just list "happy" or "sad." Look for the tension. For example, a user might say they find a software easy to use but do reach for their phone to use a calculator. This contradiction suggests an underlying anxiety or lack of trust in the system's accuracy.

2. User Persona Template

A persona is a fictional but data-driven representation of a user segment. It should include a name, bio, core goals, frustrations, and technical proficiency.

  • Avoid the Trap: Many teams create "marketing personas" based on demographics (age, location). Design thinking personas must be "task-based." Focus on the user's motivation and barriers to completing a specific job.

3. Customer Journey Map

This template visualizes the process a person goes through to accomplish a goal. It plots the user's actions against a timeline, noting touchpoints and emotional highs and lows.

  • How to leverage it: Look for the "valleys" (emotional lows). These are your primary opportunities for innovation. If a doctor's appointment booking journey has a massive emotional drop at the "filling out paper forms" stage, that’s where you start designing.

The Define Phase: Crafting the Strategic Focus

In the Define phase, you synthesize your empathy findings into a clear problem statement. This is where you move from "understanding the world" to "deciding how to change it."

4. Point of View (POV) Statement

The POV template uses a simple formula: [User] needs to [User's Need] because [Surprising Insight].

  • The Nuance: A strong POV avoids naming a solution.
    • Weak: "Mothers need an app to track kids' chores." (Prescribes an app).
    • Strong: "Busy mothers need a way to delegate household tasks without feeling like a 'nagger' because they value family harmony over a perfectly clean house." (Opens up multiple solution paths).

5. "How Might We" (HMW) Questions

HMW questions are the bridge between the problem and the solution. They take the insights from your POV and turn them into generative prompts.

  • The Goldilocks Rule: HMW questions shouldn't be too broad ("How might we fix healthcare?") or too narrow ("How might we design a red button for the checkout page?"). Aim for a middle ground that allows for a variety of creative answers.

6. Problem Statement Canvas

This is a more comprehensive template that asks: Who has the problem? What is the problem? Where does it happen? Why does it matter?

  • Facilitator Tip: When we run these sessions for enterprise clients, we use the Problem Statement Canvas to align stakeholders who have different departmental priorities. It forces everyone to agree on the "What" before arguing about the "How."

The Ideate Phase: Expanding and Converging Ideas

Now that the problem is defined, it’s time to generate solutions. The goal here is volume over quality initially, followed by rigorous filtering.

7. SCAMPER Template

SCAMPER is a checklist that helps you think of new ideas by modifying existing ones. It stands for:

  • Substitute (What can be replaced?)
  • Combine (Can two features merge?)
  • Adapt (How can we use this in a different context?)
  • Modify (Can we change the shape or scale?)
  • Put to another use (Can this solve a different problem?)
  • Eliminate (What can we remove?)
  • Reverse (What if we did the opposite?)

8. Brainwriting (6-3-5 Method)

Traditional brainstorming often suffers from "loudest voice in the room" syndrome. Brainwriting is a silent, structured template. Six people write three ideas on a sheet in five minutes, then pass it to the next person who builds on those ideas.

  • Why it works: In our testing with remote teams using digital whiteboards like Miro or FigJam, brainwriting consistently produces 300% more diverse ideas than verbal brainstorming.

9. Impact vs. Effort Prioritization Matrix

After generating 50+ ideas, you need to filter them. This 2x2 grid plots ideas based on the value they provide to the user (Impact) versus the resources required to build them (Effort).

  • Quick Wins: High Impact, Low Effort.
  • Strategic Initiatives: High Impact, High Effort.
  • Fill-ins: Low Impact, Low Effort.
  • Thankless Tasks: Low Impact, High Effort (Avoid these!).

The Prototype Phase: Making Thinking Tangible

Prototyping is about "thinking with your hands." The goal is not to build a finished product but to create a representation that can be tested.

10. Storyboard Template

Borrowed from the film industry, a storyboard is a series of sketches showing how a user discovers, interacts with, and benefits from your solution.

  • The Secret Sauce: Don't focus on the UI of the app. Focus on the context. Show where the user is (on a crowded bus?), what they are feeling (stressed?), and how the solution changes their situation.

11. Prototype Brief

Before building, use this template to define:

  • What question are we trying to answer?

  • What assumption are we testing?

  • What level of fidelity is required (Paper? Clickable mockup? Roleplay?)?

  • Expert Observation: We've seen teams spend weeks building a high-fidelity Figma prototype when a simple paper sketch could have invalidated their core assumption in ten minutes. The Prototype Brief keeps you lean.

12. Service Blueprint

For complex solutions involving multiple people and processes (like a hospital check-in or a hotel stay), a Service Blueprint maps out what the customer sees (front stage) and what happens behind the scenes (back stage).

The Test Phase: Learning from Interaction

Testing is the stage where you put your prototype in front of real users and listen. It is not about "selling" your idea; it's about being proven wrong.

13. User Testing Feedback Capture Grid

Divide a canvas into four quadrants:

  • (+) What worked? (Positive feedback)
  • (\triangle) What could be improved? (Constructive criticism)
  • (?) Questions raised (Things the user didn't understand)
  • (Idea) New ideas (Suggestions from the user)

14. User Testing Script

Consistency is key to getting valid data. A script template includes a warm-up, specific tasks for the user to perform (using the "Think Aloud" method), and post-test debrief questions.

15. The "I Like, I Wish, What If" Template

This is a constructive feedback framework used during internal team critiques. It keeps feedback focused on growth rather than ego.

  • "I like how simple the navigation is..."
  • "I wish there was a way to undo the last action..."
  • "What if we used voice commands for this part?"

How to Choose the Right Tools for Your Templates

While paper and sticky notes are the traditional tools of design thinking, digital collaboration has become the standard. Based on our practical experience, here is how to select your stack:

  1. Miro/Mural: Best for infinite canvas workshops and pre-built design thinking libraries. Use these for Empathy Mapping and Ideation.
  2. FigJam: Excellent for teams already using Figma for design. It allows for a seamless transition from "Sticky Note Ideation" to "UI Prototyping."
  3. Canva: Best for creating polished versions of your personas or journey maps to share with stakeholders who weren't in the workshop.

Conclusion: Templates Channel the Thinking

Design thinking templates are not "busy work." They are cognitive tools designed to reduce bias, encourage empathy, and force clarity. However, the most successful teams recognize that the template is just the starting point. The real value lies in the conversations triggered by the quadrants and the insights found between the lines of a journey map.

Whether you are a solo founder trying to find product-market fit or an innovation lead at a Fortune 500 company, these 15 templates provide the structure needed to navigate the "fuzzy front end" of innovation. Start small, be willing to iterate on your own process, and always keep the user at the center of the canvas.

FAQ

How do I facilitate a design thinking workshop remotely? Use a digital whiteboard and set clear time limits (Timeboxing) for each template. Ensure everyone has "edit" access and encourage the use of emojis and comments to keep energy high.

Can I skip the Empathize phase if I already know my users? Almost never. In our experience, what teams "know" are often outdated assumptions or anecdotal evidence. Even a 30-minute empathy mapping session can reveal new friction points in the current user experience.

What is the most common mistake in using design thinking templates? Treating them as a "checklist" to be completed. A template is a conversation starter. If the team is just filling in boxes to get it over with, you won't get the "Surprising Insight" needed for a breakthrough POV.