ToolStack
Design ThinkingLoomLimited native support

Using Loom for Design Thinking

Fastest way to communicate complex ideas asynchronously — record screen + camera in seconds with zero setup. When combined with Design Thinking, this makes Loom a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Design Thinking works best in Loom when you leverage its core workflow features to implement the framework's key practices directly in the tool your team already lives in.

About Design Thinking

Design Thinking is a human-centred problem-solving process: Empathise → Define → Ideate → Prototype → Test. It emphasises understanding user needs deeply before jumping to solutions.

Empathise: conduct deep user research before defining the problem
Define: synthesise research into a clear problem statement (HMW)
Ideate: generate divergent solutions before evaluating any
Prototype and test: build low-fidelity representations to validate with real users

How to set up Design Thinking in Loom

1

Create an Empathy and Research workspace

In Loom, create a project named "User Research". Each card represents one research session. In the card, log: participant context, key observations, direct quotes, and emotional signals. Use labels for: observation type (Pain, Gain, Context), urgency, and user segment.

2

Define the problem (HMW statements)

Create a "HMW Statements" list in Loom. After every research synthesis session, generate 5–10 HMW statements and add them as cards. Use card reactions or a voting session (sticky notes on a video call) to identify the top 3 to take into ideation.

3

Run an ideation sprint in the tool

In Loom, create an "Ideation" board or list for each HMW statement. Team members add solution ideas as cards — no filtering or evaluation during this phase. After ideation, hold a dot-voting session: each team member marks their top 3 ideas. The highest-voted ideas with the best feasibility/impact balance move to prototyping.

4

Track prototypes and test cycles

Create a "Prototypes" project in Loom. Each card tracks one prototype with fields for: hypothesis, test method, participant count, and outcome. After testing, record whether the prototype validated or invalidated the hypothesis. Link back to the original HMW card for traceability.

Which Loom features matter for Design Thinking

Loom has 0 of 2 core Design Thinking features natively.

FeatureWhy it matters for Design ThinkingLoom
User Feedback ManagementCapturing and organising research and feedback
Idea ManagementDivergent ideation and opportunity management
Custom WorkflowsCustom stage definitions matching your process
Custom FieldsTracking methodology-specific metadata
RoadmappingStrategic planning and PI/initiative mapping

Loom at a glance

G2 Score
4.7 / 5
Reviews
3k+
Free Tier
Yes
Starting Price
Free
Full Loom review →Loom website

Explore Design Thinking

Design Thinking full guide →

Loom with other methodologies

Loom for ScrumLoom for KanbanLoom for SAFe (Scaled Agile Framework)Loom for Shape UpLoom for OKRs (Objectives & Key Results)Loom for Jobs-to-Be-Done (JTBD)Loom for Lean StartupLoom for Dual-Track AgileLoom for LeSS (Large-Scale Scrum)Loom for Spotify ModelLoom for Extreme Programming (XP)Loom for Crystal MethodsLoom for Feature-Driven Development (FDD)Loom for DSDM (Agile Business Consortium)Loom for Six Sigma for ProductLoom for Lean Product DevelopmentLoom for Discovery-Driven PlanningLoom for Opportunity Solution TreeLoom for User Story MappingLoom for Impact MappingLoom for Kano ModelLoom for RICE ScoringLoom for MoSCoW PrioritisationLoom for Value Proposition CanvasLoom for Business Model CanvasLoom for Wardley MappingLoom for Customer Journey MappingLoom for Event StormingLoom for Domain-Driven Design for PMsLoom for Continuous DiscoveryLoom for Product-Led GrowthLoom for North Star FrameworkLoom for Goal Tree (Theory of Constraints)Loom for GIST Planning