Some good ideas are still too young to count as wins. Rose Bud Thorn makes room for them. Rose holds what worked, Bud captures a promising signal that needs more evidence, and Thorn names the friction or risk the team needs to face.
Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.
What worked well, helped the team, or deserves protection?
What is starting to show promise, which evidence points in that direction, and what deserves a closer look during the next cycle?
What caused pain, added friction, created risk, or blocked progress in a way the team could observe during this sprint or project?
A complete path from framing the room to assigning one concrete follow-up.
Name the sprint, project, or experience under review, including the point where it began and the point where this reflection ends. Define Rose, Bud, and Thorn before anyone begins writing.
Give everyone seven quiet minutes to add specific observations. Keep one idea on each card, and invite contributions to every section.
Read the cards one section at a time and let authors add brief context. Clarify the evidence, then save solution talk for the discussion.
Group related cards, including any pattern that connects 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 strongest learning potential. Give each person the same number of votes before discussion begins.
Choose one Rose to protect, decide if a Bud deserves a small experiment, and give someone ownership of reducing the leading Thorn.
Review customer evidence, product outcomes, emerging opportunities, and usability or delivery pain from one release.
Before a project begins, name the strengths to carry forward, possibilities worth testing, and risks that need an early response.
Collect cards before the meeting and reveal them together. Save the live session for grouping, prioritization, and ownership.
Before the retro
Rose Bud Thorn sorts observations into strengths, emerging opportunities, and difficulties or risks. Teams can use the same three labels to review an experience, idea, project, or period of work whenever they need a balanced view.
Rose captures what worked or deserves protection, including the condition, behavior, or decision the team wants to carry into the next stretch of work. Bud holds something promising that needs more evidence or exploration. Thorn records pain, friction, risk, or a constraint the team should address, with enough detail for everyone to understand what happened.
A Bud is an emerging possibility that still needs evidence. Once the team chooses to explore it, the Bud becomes a small experiment with an owner and a review point.
Plan 30–40 minutes for a team of three to twelve. Collecting cards asynchronously can shorten the live session and preserve enough time for the team to discuss the patterns, choose a response, and give that response an owner.
Protect one condition behind a strong Rose, test one promising Bud, 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 the evidence, choose the strongest pattern, and give the next step a clear owner.
