itk-rose-bud-thorn

name	itk-rose-bud-thorn
description	Visually categorize positive (rose), potential (bud), or negative (thorn) aspects of a topic (e.g., system, product, process).
intent	Help quickly identify problems and opportunities to produce a structured summary of each. Constructively discuss difficult topics, such as “what’s not working well.” Build shared understanding among the team to analyze issues.
type	component
phase	evaluate
outcome	evaluate
difficulty	beginner
group_size	4+ people
time_required	45+ minutes
best_for	["Sprint retrospectives to surface systemic friction and emerging opportunities before committing to the next roadmap cycle","Early discovery sessions where stakeholders disagree on what's working and where the product should head next","Post-launch reviews to categorize what delighted users, what shows promise, and what needs immediate fixing","Stakeholder workshops aligning cross-functional teams on a legacy system's strengths and pain points before modernization","Quarterly product health checks that need a fast, low-friction way to inventory wins, bets, and risks"]
sources	["MITRE Innovation Toolkit (ITK)","https://itk.mitre.org/toolkit-tools/rose-bud-thorn/"]

Rose, Bud, Thorn

What Is It

Visually categorize positive (rose), potential (bud), or negative (thorn) aspects of a topic (e.g., system, product, process).

Why Use It

Help quickly identify problems and opportunities to produce a structured summary of each. Constructively discuss difficult topics, such as “what’s not working well.” Build shared understanding among the team to analyze issues.

When to Use It

When clarifying different facets of the challenge or opportunity and identifying areas needing further evaluation and exploration.

How to Do It

1. Identify a topic for analysis. Possibilities include systems, products, processes, organizations, etc.
2. Pull together a diverse group of stakeholders, users, and subject matter experts.
3. Pass out red (rose), green (bud), and blue (thorn) sticky notes to participants and have them write the strengths, opportunities, and challenges associated with the topic. If colored sticky notes are not available, use red, green, and blue markers with plain sticky notes, or use a whiteboard with colored markers. Optional: Use the Rose, Bud, Thorn worksheet as your guide.
4. Encourage participants to generate multiple issues, insights, or ideas, but to capture only one per sticky note.
5. Group the colored sticky notes on a whiteboard or similar surface according to rose, bud, and thorn.
6. If desired, participants can group or cluster items further by priority or related themes and give each group a title.

Key Concepts

Rose — A current strength or positive aspect that is working well and worth preserving. Identifying roses prevents teams from breaking what's valuable during change or de-prioritizing proven features.

Bud — An emerging opportunity or potential with promise but not yet realized. Buds are the raw material for roadmap bets and discovery follow-ups, distinguishing latent possibility from proven value.

Thorn — A challenge, pain point, or risk that is actively causing problems. Naming thorns explicitly creates psychological safety to discuss failures and feeds the problem backlog.

Affinity Clustering — Grouping related sticky notes into themes after generation to reveal patterns. Clustering converts scattered individual observations into actionable categories that map to epics or workstreams.

Divergent Capture — The practice of one idea per sticky note to keep items atomic and re-groupable. This prevents compound statements that conflate multiple issues and resist prioritization.

Action Translation — Converting categorized insights into owned action items, backlog entries, or experiments. Without this step the exercise produces sentiment but no commitment, eroding participant trust.

PM Applications

• Run it as the core activity of a sprint retrospective, mapping thorns to process improvement tickets and buds to discovery spikes for the next iteration.
• Use it in a discovery kickoff to inventory an existing product's strengths and pain points, feeding the 'problem statement' and 'opportunities' sections of a PRD.
• Facilitate a stakeholder briefing where conflicting teams categorize a shared system, surfacing alignment and disagreement before roadmap reviews.
• Apply it during quarterly OKR planning to convert thorns into measurable problem-focused key results and buds into stretch objectives or new bets.
• Conduct it after a major release or beta to triage user feedback into preserve (rose), invest (bud), and fix (thorn) buckets that prioritize the backlog.
• Use it in a backlog grooming session to re-evaluate aging epics, clustering thorns to justify deprecation and buds to justify continued investment.

Benefits

• Easiest tool to explain Participants catch on very quickly Very easy to come up with ideas

Common Pitfalls

• Ending the session with categorized stickies but no assigned owners or backlog entries, so participants conclude their input was ignored and disengage from future workshops.
• Letting dominant voices or HiPPOs anchor the discussion, which suppresses thorns from junior members and produces a falsely positive picture of product health.
• Conflating buds with thorns because facilitators don't define the categories upfront, collapsing the distinction between 'unrealized opportunity' and 'active problem' that drives different responses.
• Writing vague compound notes like 'onboarding is bad' instead of atomic, specific observations, making the items impossible to cluster, prioritize, or convert into stories.
• Treating every thorn as equally urgent without a follow-up prioritization or trimming pass, flooding the backlog with low-impact items and diluting focus on real risks.
• Running it with a homogeneous group of insiders rather than a diverse mix of users, stakeholders, and SMEs, which echoes existing assumptions and misses blind-spot thorns.

Combine With

Trimming to narrow down buds the team wants to take action on

Assets

• PDF: Download
• Markdown Template: template.md

Metadata

Field	Value
ITK Phase	EVALUATE
Difficulty	Beginner
Group Size	4+ people
Time Required	45+ minutes
Source	itk.mitre.org