ToolStack
Design ThinkingConfluenceLimited native support

Using Confluence for Design Thinking

Deep native integration with Jira makes it the de facto documentation tool for teams already using Atlassian — Jira issues embed seamlessly in pages. When combined with Design Thinking, this makes Confluence a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Design Thinking works best in Confluence 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 Confluence

1

Create an Empathy and Research workspace

In Confluence, 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 Confluence. 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 Confluence, 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 Confluence. 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 Confluence features matter for Design Thinking

Confluence has 0 of 2 core Design Thinking features natively.

FeatureWhy it matters for Design ThinkingConfluence
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✗

Confluence at a glance

G2 Score
4.1 / 5
Reviews
4k+
Free Tier
Yes
Starting Price
Free
Full Confluence review →Confluence website

Explore Design Thinking

Design Thinking full guide →

Confluence with other methodologies

Confluence for Scrum →Confluence for Kanban →Confluence for SAFe (Scaled Agile Framework) →Confluence for Shape Up →Confluence for OKRs (Objectives & Key Results) →Confluence for Jobs-to-Be-Done (JTBD) →Confluence for Lean Startup →Confluence for Dual-Track Agile →Confluence for LeSS (Large-Scale Scrum) →Confluence for Spotify Model →Confluence for Extreme Programming (XP) →Confluence for Crystal Methods →Confluence for Feature-Driven Development (FDD) →Confluence for DSDM (Agile Business Consortium) →Confluence for Six Sigma for Product →Confluence for Lean Product Development →Confluence for Discovery-Driven Planning →Confluence for Opportunity Solution Tree →Confluence for User Story Mapping →Confluence for Impact Mapping →Confluence for Kano Model →Confluence for RICE Scoring →Confluence for MoSCoW Prioritisation →Confluence for Value Proposition Canvas →Confluence for Business Model Canvas →Confluence for Wardley Mapping →Confluence for Customer Journey Mapping →Confluence for Event Storming →Confluence for Domain-Driven Design for PMs →Confluence for Continuous Discovery →Confluence for Product-Led Growth →Confluence for North Star Framework →Confluence for Goal Tree (Theory of Constraints) →Confluence for GIST Planning →