Rose Bud Thorn Retrospective Template (Free)

What is the Rose Bud Thorn Retrospective?

The Rose Bud Thorn retrospective uses a garden metaphor to help your team look at a stretch of work from three angles. Roses are the things that went well, Buds are early ideas or opportunities that could grow, and Thorns are the problems that caused pain. Because every board has positives, possibilities and problems on it, the conversation stays balanced. Nobody leaves with only a list of complaints, and the Buds point to what you could build on next. The metaphor needs no explanation, so the activity works well for teams new to retrospectives and for cross-functional groups that don't share a vocabulary. You'll see this activity written as both "Rose Bud Thorn" and "Rose Thorn Bud." They're the same exercise listed in a different order, and the meaning of each term never changes: the Rose is a success or highlight, the Thorn is a challenge or pain point, and the Bud is an opportunity showing early promise. Some facilitators prefer the "Rose Thorn Bud" order because it ends the reflection on the forward-looking Bud. Use whichever order your team finds most natural. LUMA Institute lists Rose, Thorn, Bud as one of its human-centered design methods, adapted from a Boy Scouts of America practice, and it travels well beyond software retrospectives. Teachers use Rose Thorn Bud as a daily classroom check-in, managers use it to open one-on-ones, and families use it around the dinner table. After a project sprint, for example, a team member's Rose might be "we shipped the new onboarding flow on time," their Thorn "QA was rushed in the last two days," and their Bud "the new analytics could tell us which step loses users."

Rose Bud Thorn Retrospective Format

Rose What went well, big or small?: Roses represent achievements and positive experiences. Encourage participants to share specific examples of what went well, including both big wins and small victories. This helps build team morale and identifies successful practices to continue.
Bud What's starting to grow that we could build on?: Buds represent potential for growth and improvement. Guide the team to identify promising ideas or partially implemented solutions that could be developed further. Focus on constructive suggestions rather than complaints.
Thorn What's causing us pain right now?: Thorns represent obstacles and challenges. Keep the discussion focused on identifying specific issues that can be addressed, rather than general complaints. Encourage participants to think about potential solutions when raising thorns.

When to use this retrospective

When you want a balanced view of how the team is doing, positives included
At a project milestone, to check progress and spot course corrections
With a team new to retrospectives that needs an easy format to start with
When you need to talk about problems without the meeting turning negative
As a quick check-in activity for a workshop, class or one-on-one

Ideas and tips for your retrospective meeting

Start with Roses so the team warms up on what's working before it gets to the hard parts
Ask for specific examples. "The release went fine" tells you less than "the release checklist caught two bugs"
Give each category similar time so Thorns don't take over
Look for links between Thorns and Buds. A recurring problem often has a fix already sprouting somewhere
Leave with actions: one Bud to grow and one Thorn to remove
Use dot voting to pick which Buds are worth the team's time

Frequently asked questions

What is a rose bud thorn retrospective?

It's a reflection exercise where your team shares Roses (what's working), Buds (what's showing early promise) and Thorns (what's causing pain). Because it asks for positives and opportunities alongside problems, it gives a fuller picture of how the team is doing than a list of complaints.

Is it "rose bud thorn" or "rose thorn bud"?

Both are correct. It's the same exercise listed in a different order, and each term keeps its meaning: the Rose is a highlight, the Thorn is a pain point and the Bud is an early opportunity. Some facilitators prefer "Rose Thorn Bud" because it ends on the forward-looking Bud.

What does the bud represent in rose bud thorn?

The Bud is an opportunity: something that isn't a full success yet but shows early promise. Buds are the ideas, possibilities and small wins that could grow with some attention, and they're what make the exercise look forward as well as back.

What are some examples of rose bud thorn entries?

A Rose might be shipping a feature ahead of schedule, a Bud a new tool the team wants to try, and a Thorn unclear requirements slowing progress. Good entries are specific and tied to the period you're reviewing.

When should a team use rose bud thorn instead of start stop continue?

Use Rose Bud Thorn when you want a low-pressure read on how the team feels and what's emerging. Start Stop Continue is more direct, asking which behaviors to start, stop or keep. Many teams alternate between the two.

How do you run rose bud thorn with a remote team?

Use a shared online board. Give everyone a few minutes to add Roses, Buds and Thorns privately so early answers don't anchor the group, then reveal them, group similar ideas, vote and agree on actions. TeamRetro's free Rose Bud Thorn template runs each of these steps for distributed teams.

What is the Rose Bud Thorn Retrospective?

Rose Bud Thorn Retrospective Format

Rose

Bud

Thorn

When to use this retrospective

Suggested icebreaker questions

Ideas and tips for your retrospective meeting

Frequently asked questions

Related templates