Rose / Bud / Thorn
It's the format you run when 'Mad' is too sharp for the room. Engineering teams should pick something else.
Three prompts — Rose (what's good), Thorn (what's painful), Bud (what's emerging). Originated in American Boy Scouts as a daily reflection; now used in design thinking, classrooms, and leadership offsites. Gentle by design, which is its purpose and its limit.
When to use
Design teams, marketing teams, education, leadership offsites, mixed-discipline rooms, and any retrospective where the audience isn't a software engineering team. If you're an engineering team and you've ended up here, you probably want SSC instead — Rose/Bud/Thorn's gentle framing makes it slow for the work software teams need a retro to do.
How it runs
Three columns
Rose, Bud, Thorn. The metaphor is gardening — Rose is in bloom, Thorn is what cuts, Bud is what's about to flower. Keep the metaphor light; don't draw the bush.
Silent write, eight minutes
Standard silent write. The reflective register of Rose/Bud/Thorn rewards more time than SSC — people surface emerging things on minute six that they wouldn't have on minute three.
Read each column out loud
Rose first to set the tone, Thorn next to surface friction, Bud last because Bud is the column that matters and you want the team's attention there.
Spend the time on Bud
Bud is the column nobody runs out of cards on, and the column most pages skim. Twenty minutes here. 'What's emerging' is the only one of the three prompts that points forward.
Pick one Bud to nurture
One Bud becomes a thing the team commits to growing in the next cycle. A Bud without a commitment is decorative.
Why it works
The gardening metaphor lowers the temperature. 'Thorn' is a softer prompt than 'Mad' and produces more measured cards — useful for a room where directness would shut people down. The Bud column is the format's actual contribution: most retros are about what is, not what's emerging. Bud asks the question competitor formats don't.
Variations
- Run it as a leadership offsite check-in: each leader brings one Rose, Bud, and Thorn from their team, and the discussion is about patterns across teams.
- Drop Rose if the room is in self-congratulation mode and you need the friction surfaced. Two columns: Bud and Thorn.
- Use it in 1:1s — Rose/Bud/Thorn for what's going on with the person, not the team. Different exercise; same prompt.
Facilitator notes
If you're running this for an engineering team, ask yourself why. The most common answer is 'because Mad/Sad/Glad seemed too aggressive' — and the honest fix is to run SSC, which is direct without being emotional. Rose/Bud/Thorn for engineers is usually a comfort choice for the facilitator, not the team.
Pitfalls
- Letting the gardening metaphor become the meeting. Five minutes max on metaphor talk.
- Skimming Bud. It's the column that matters; protect at least a third of the meeting for it.
- Running it as a sprint default for a software team. The polite framing makes the meeting slow without making it kinder.
- Treating Bud as a wishlist. Buds need a name attached or they're decorative.
Remote tips
The vertical flower metaphor doesn't add anything you can't get from three columns — don't waste effort on a beautiful bush diagram remotely. Three labelled columns on a shared board is the same exercise; pre-open it 24 hours before for async writing.
Example outputs
- Rose: the cross-team workshop last Thursday. People we don't usually work with showed up.
- Thorn: the brief revision cycle on the brand refresh — three rounds and we still haven't aligned on tone.
- Bud: the new pattern of pairing copywriters with designers earlier. We've done it twice; it's working.
- Bud: a quarterly retrospective format, not just sprint-based. Owner: Maya. Trial next quarter.
FAQ
- Rose/Bud/Thorn or Mad/Sad/Glad?
- Same shape, different register. Mad/Sad/Glad for software teams that can handle a sharp prompt. Rose/Bud/Thorn for design, marketing, education, and mixed-discipline rooms where 'Mad' would land wrong. The choice is about your audience, not the work.
- Can engineering teams use this?
- You can. You probably shouldn't. Engineering teams are usually well served by SSC or Sailboat — formats that don't soften their prompts. Rose/Bud/Thorn for an engineering team is most often a sign the facilitator is uncomfortable with the team's directness, not that the team needs gentler framing.