Framework · Facilitation techniques · 2 min read
Rose, Thorn, Bud
What's working (rose), what's painful (thorn), what's promising (bud). Ideal for a new lead's first-30-days listening.
RRose
What is working well today and should be kept.
e.g. "Critiques are useful"TThorn
What is painful, slow or frustrating. Cluster these first.
e.g. "Specs change after handoff"BBud
What is promising: an idea or early change worth growing.
e.g. "Two teams share a library"Use it when
- You are a new UX lead in your first 30 days and want to listen before you change anything.
- You assess the current state of a practice: tools, process, collaboration with product managers and developers, growth.
- You run a retro and want a format that includes what is promising, not only what is wrong.
How to use it
- Pick the areas. Choose three or four areas to reflect on, for example tools, process, collaboration with product managers and developers, and growth. Output: the areas, written as rows or sections on the board.
- Assign one colour per type. For example pink for roses, blue for thorns, green for buds. Output: a colour key everyone can see.
- Write in silence. Everyone writes roses, thorns and buds, one per sticky, for each area. No talking. Output: many colour-coded stickies. About 10 minutes.
- Share and place. Each person reads their stickies briefly and places them on the board. Output: the current state, visible in one place. About 15 minutes.
- Cluster the thorns, then dot-vote. Group similar thorns with Affinity mapping and vote for the top problems. Check whether a bud already points to a solution. Output: the top two or three problems. 20–30 minutes for the core exercise.
Worked example
A new UX lead runs the 90-minute listening workshop in their first month with 7 designers who work in different product teams of an internal operations platform. Rose, Thorn, Bud takes 25 minutes.
| Area | Rose | Thorn | Bud |
|---|---|---|---|
| Tools | "Our component libraries are tidy." | "Each team has its own icon set." | "Two teams already share one icon set." |
| Process | "Critiques are useful." | "Specs change after handoff." | "One team tried a handoff checklist." |
| Collaboration | "Developers join some reviews." | "Product managers ask for screens, not problems." | "A product manager asked for a discovery sprint." |
| Growth | "We learn from each other." | "No clear career path." | "People want to run critiques." |
After affinity mapping, the team votes "specs change after handoff" as the top thorn, and the bud from process becomes the first experiment.
Watch out for
- Talking before writing. The first person to speak shapes everyone's stickies. Keep the silent part.
- Only collecting thorns. Roses tell you what not to break. Buds give you a place to start.
- Defending as the lead. In listening sessions, thorns may be about decisions you inherited. Thank people and ask for more detail, don't explain.
- No follow-up. Share the summary and the top problems within 24 hours, and say what happens next.
Template
Draw this grid on the board, one row per area.
ROSE, THORN, BUD Colours: Rose = ____ Thorn = ____ Bud = ____
Area | Rose (working) | Thorn (painful) | Bud (promising)
---------------|-----------------|-----------------|-----------------
Tools | | |
Process | | |
Collaboration | | |
Growth | | |
Top thorns after dot vote: 1. 2. 3.
Bud we can grow first:
Saved only on this device.