Each person names a rose (something going well), a bud (something with potential) and a thorn (something difficult). Thirty seconds each. Run weekly at the top of a team meeting it does more for a team's awareness of itself than any quarterly survey.
What it is good for
- CommunicationPractising clear hand-offs, active listening and saying the hard thing early.
- Trust & safetyLowering the cost of admitting a mistake or asking for help.
- WellbeingGiving the team a genuine break rather than another meeting with a theme.
- InclusionDesigning participation so the loudest voice does not set the pace.
What you need
- Nothing
The run sheet
Define the three, once (1 min)
Rose: something that went well. Bud: something early that could become good. Thorn: something that is difficult or stuck. Work or life, their choice, and say that explicitly.
Go first, and include a real thorn (1 min)
If the facilitator's thorn is 'too many meetings', every thorn will be 'too many meetings'. Name something that actually bothers you.
Round the group, thirty seconds each (8 min)
No cross-talk, no problem-solving, no 'have you tried'. The discipline of not fixing things is what makes people willing to name a real thorn.
Pick up at most one thorn afterwards (5 min)
After the round, you may choose one thorn to actually discuss — or none. Say which, and move on.
Facilitator notes
- The no-fixing rule in the round is the whole technique. Break it once and the next week everyone brings a solved thorn.
- Weekly is the right cadence. Monthly loses the thread; daily turns into a recital.
- Watch the pattern over time rather than the individual items. Three people with the same thorn in the same month is a signal you would not otherwise have had.
Debrief questions
Ask these immediately afterwards, not next week. Fifteen minutes of these is what turns the activity into something the team refers back to — see the debrief guide.
- Did more than one person name the same thorn?
- Is there one thorn this team could actually remove this week?
Variations
Written edition
Posted in a channel rather than spoken in a meeting. Lower quality, asynchronous, and far better than not doing it at all for a team across many time zones.
Project edition
Run it about one project rather than the person. Makes it safe for teams who do not want to share personal context at work.
Access and inclusion
Nobody should have to produce a thorn on demand — 'pass' is a complete answer and should be used by the facilitator occasionally so it stays normal.
Running it remotely
Works perfectly on a call. Go in a published order so the silence between speakers does not become a game of chicken.