Rose, Thorn, Bud retrospective

A rose is something that went well, a thorn is something that hurt, and a bud is something promising that has not bloomed yet. Three words anyone understands, which makes this the retro to run when the room is not only your developers.

Rose

What bloomed—highlights and strengths

Thorn

What pricked—obstacles or annoyances

Bud

Emerging ideas or chances to nurture next

Use this template — it's free

What a Rose, Thorn, Bud retrospective is

Everyone looks back over the same stretch of work and writes three kinds of cards. Roses are the highlights and strengths. Thorns are the obstacles and annoyances. Buds are ideas and opportunities that have only just started and could grow into something if someone looks after them. The team groups the cards, votes, and spends most of the meeting on the thorns and buds that matter most.

The exercise is a staple of design thinking workshops, and many people know a version of it from home: "what was your rose today, and what was your thorn?" is a familiar dinner-table question. In a retrospective it does the same job with more structure.

What it does better than most formats:

• The bud is a third category. Most retros sort the world into good and bad. A bud is neither yet: the half-finished experiment, the customer request that keeps coming back, the new hire who has quietly started fixing the docs. These are easy to miss and are often where the next good idea is hiding.
• No jargon, so anyone can take part. A sales lead, a client or a support agent does not need to know what a retrospective is. And "thorn" is a gentle word: people from outside the team can criticize the work without feeling they are attacking the people who built it.
• It keeps the board balanced. Asking everyone for at least one card of each kind stops the session from turning into a list of complaints, or into polite praise that changes nothing.
• Thorns point at buds. A complaint often has an opportunity next to it. "The release checklist takes half a day" is a thorn; "Priya's script already automates part of the checklist" is the bud that answers it. Seen side by side, the complaint becomes a starting point.

When to use it, and when not to

Rose, Thorn, Bud is at its best when the people in the room do not share the same vocabulary:

• with a mixed group — product, design, engineering, support, a client or a partner team;
• at the end of a workshop, an offsite, a hackathon or a training, to review the event itself;
• after a pilot, a beta or a round of prototype tests, to sort what users liked, what tripped them up and what they hinted at;
• for a team's very first retrospective, when nobody knows the routine yet;
• when the team has spent months hunting problems and has stopped noticing what is going right.

Pick something else when:

• You need to fix a specific process. Rose, Thorn, Bud is good at surfacing topics and weaker at pushing them to a concrete change. The KPT retrospective asks directly what the team will try next.
• Emotions are running high. "Thorn" is too mild for a sprint that made people angry. Give the feeling its real name with Mad Sad Glad.
• You are reviewing a single piece of work. To give structured feedback on a demo, a design or a document, the Ladder of Feedback keeps critique more precise.

The three columns

The ProstoRetro board opens with Rose, Thorn and Bud side by side. Here is what goes into each, and how to tell them apart when a card could fit in two places.

Rose: what bloomed

Highlights and strengths: things that went well and that you would like to happen again. The test is simple: it already happened, and it worked. Push for detail. "Good teamwork" is wallpaper; "Ana and Tom paired on the migration and finished two days early" is a rose the team can learn from.

• The new onboarding flow went live without a single rollback
• Support and design rewrote the help articles together, and the tickets about invites dropped
• Thursday customer calls: we finally hear users directly, not through three people
• Code review now happens the same day, since we set up a review rota

Thorn: what pricked

Obstacles and annoyances: whatever slowed the work down or made it worse during this period. Small thorns count — a daily irritation that costs everyone ten minutes deserves a card. Describe the situation rather than the person: "specs changed after the sprint started", not "Sam changed the specs".

• Staging was down for most of Tuesday and nobody knew who owned it
• The scope of the settings page changed twice after the sprint started
• The analytics dashboard is so slow that we stopped opening it
• Twelve people in the Monday sync, and most of us only listen

Bud: what could grow next

Emerging ideas and chances to nurture: something that has started, or could start, and is small for now. The test against a rose: has it already delivered? Then it is a rose. The test against a thorn: is it something you would like more of? Then it is a bud, even if it was born from a problem. A bud does not need a plan yet — it needs attention.

• Two customers asked for a public status page; a one-day prototype could tell us if it is worth it
• Mia's flaky-test detector caught three bad tests in its first week
• The design system now covers enough to build simple pages without a design review
• Support wants to join sprint demos — could cut the repeat questions after releases

Use this template — it's free

A 45-minute Rose, Thorn, Bud agenda

This plan fits a group of five to twelve people, including guests who have never been to a retro.

1. Warm-up, 4 minutes. One easy question that strangers can answer too — pick it from our list of icebreaker questions. In a mixed group, ask people to start with their name and role.
2. Frame the period, 2 minutes. Say exactly what you are looking back at: the last sprint, the beta, the two-day workshop. Without this, a client reviews the project and an engineer reviews last week.
3. Silent writing, 8 minutes. At least one card per column, one idea per card. Cards are hidden until the writing ends, so the first person to post does not set the tone for everyone.
4. Grouping, 6 minutes. Merge duplicates and move each bud next to the thorn it answers, if there is one. ProstoRetro can propose groups of similar cards, which you keep or undo.
5. Voting, 4 minutes. Ask people to spend their votes on thorns and buds. Roses are there to be celebrated, not ranked.
6. Roses out loud, 3 minutes. Read the roses before the discussion and thank the people behind them. It sets a constructive tone for the thorns that follow.
7. Discussion, 13 minutes. Take the top two or three topics. For a thorn, ask "what would make this stop happening?" For a bud, ask "what would it need to grow — time, a person, a decision?"
8. Action items, 4 minutes. One owner and one due date per action. Bud actions are usually small: a two-hour prototype, a call with a customer, a slot in the next planning.
9. Close, 1 minute. One word from each person about the session.

Set the meeting length to 45 minutes when you create the board: ProstoRetro then budgets time for each phase and each topic, and starts every timer itself.

Running it remotely, with guests

• Let outsiders in with just a name. Clients and colleagues from other departments rarely have an account. When the room is open to anyone with the link, they type a name and join. If you want to see who is coming in first, turn on the waiting room.
• Anonymous thorns, signed roses. Cards are anonymous by default, and each person can choose per card. A client may prefer an anonymous thorn; a rose with a name on it doubles as a thank-you.
• Show it instead of describing it. Cards can hold images and GIFs, so paste the chart that went up, the customer message that made your day or the error screen everyone hated.
• Let the group choose which bud to back. When two buds compete for the same time, run a quick anonymous poll: "Which one should get a day next sprint?" It settles the question in a minute.
• Collect cards during a multi-day event. For a workshop or an offsite, open a permanent board — an infinite room — and let people add roses and thorns as they happen. The cards stay hidden until the review starts.

Variations

The quick round

For a weekly team meeting, skip the board phases: each person names one rose, one thorn and one bud out loud, and the facilitator notes any bud that deserves follow-up. With eight people it takes about ten minutes, and it is a gentle habit for teams that do not hold formal retros yet.

Sorting user research

In design work, the three categories are often used to sort observations from interviews or usability tests. Put one observation per card: what users liked is a rose, where they struggled is a thorn, and what they hinted at or asked for is a bud. Grouping then shows the patterns across sessions, and voting picks what goes into the next round of design.

Rose, Thorn, Bud, Next

If your group tends to leave buds hanging, add a fourth column for the first step toward each one. In ProstoRetro you can build this as a custom template with your own column names, descriptions and colors — up to five columns.

Common mistakes

• Polite roses. "Great team" and "nice work everyone" feel good and teach nothing. Ask what exactly went well and why.
• Thorns with names on them. Rewrite them as situations before the discussion, or the person named will spend the meeting defending themselves.
• Buds with no roots. "We should use AI for everything" is a wish. A bud grows from something that already exists: a script, a request, a small success.
• Voting on roses. It turns appreciation into a popularity contest. Celebrate roses, vote on the rest.
• Turning every bud into an action. Back one or two. The others can stay on the board and come back next time — some buds need a few weeks before they are ready.

FAQ

What do rose, thorn and bud mean in a retrospective?

A rose is a highlight or strength, a thorn is an obstacle or annoyance, and a bud is an emerging idea or opportunity that could grow with some attention.

Is Rose, Bud, Thorn the same exercise?

Yes. Some teams put the bud in the middle; the meaning of each part does not change. The ProstoRetro board goes Rose, Thorn, Bud, so the session ends on what could come next.

How long does a Rose, Thorn, Bud retrospective take?

About 45 minutes for up to a dozen people, as in the agenda above. The spoken round without a board takes ten to fifteen minutes.

How is it different from What Went Well?

What Went Well has two columns, good and bad. Rose, Thorn, Bud adds the bud, which catches opportunities that are not yet a success and not a problem either.

Can I run a Rose, Thorn, Bud retrospective online for free?

Yes. The template is built into ProstoRetro, which costs nothing, and a client or a colleague from another department can join with just a name when the room is open to anyone. See how to run a great retro for a walkthrough of the app, or browse all retrospective templates.