Rose Bud Thorn is a simple reflection method for separating what is positive, what shows potential, and what creates difficulty. In a retrospective, those three lenses help a team protect a strength, explore a promising signal, and reduce a specific source of friction.
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
What worked well, created value, or deserves to be protected?
What is beginning to show promise or deserves a closer look next?
What caused pain, friction, risk, or blocked useful progress?
A complete path from framing the room to assigning one concrete follow-up.
Name the sprint, project, or experience being reviewed and define Rose, Bud, and Thorn before anyone starts writing.
Give everyone quiet time to add specific observations. Ask for one idea per card and encourage contributions to every section.
Read cards section by section and let authors add brief context. Clarify evidence without debating solutions yet.
Cluster related cards, including patterns that connect a Rose worth protecting with a Bud or Thorn that could affect it.
Vote across the whole board, then discuss the themes with the greatest effect on team outcomes or the most useful learning potential.
Name one Rose to protect, choose whether a Bud deserves a small experiment, and assign an owner to reduce the highest-priority Thorn.
Review customer evidence, product outcomes, emerging opportunities, and usability or delivery pain around one release.
Before a project begins, identify strengths to carry forward, possibilities worth testing, and risks that need an early response.
Collect cards before the meeting, reveal them together, and reserve live time for grouping, prioritization, and ownership.
Before the retro
Rose Bud Thorn is a reflection method that sorts observations into positives or strengths, emerging opportunities, and difficulties or risks. It can be used to review an experience, idea, project, or period of work.
Rose captures what worked or deserves protection. Bud captures something promising that needs more evidence or exploration. Thorn captures pain, friction, risk, or a constraint the team should address.
A Bud is an emerging possibility, not a commitment. The team should first decide what evidence it needs, then turn a promising Bud into a small experiment with an owner and review point.
Plan 30–40 minutes for a team of three to twelve. Collecting cards asynchronously can shorten the live session while preserving time for discussion and ownership.
Protect one condition behind a valuable Rose, test one high-potential Bud when useful, and assign an owner and check-in date for the Thorn the team most needs to reduce.
Open Rose, Bud, and Thorn on one shared board, collect evidence, prioritize the strongest patterns, and give the next step a clear owner.
