Rose Bud Thorn

A gentle, well-balanced format that gives equal weight to the good, the painful and the promising. The rose marks what went well, the thorn what hurt or got in the way, and the bud what shows potential and is worth nurturing. Including the bud keeps the conversation forward-looking instead of dwelling only on the past.

Rose

What is clearly working right now

Roman

The new deploy pipeline cut releases to minutes

Maria

Support and engineering now triage together on Mondays

Bud

Early signs worth investing in before they fade

Anna

The prototype for self-serve onboarding looks promising

Daria

Two juniors are close to owning review on their own

Thorn

What hurts and keeps hurting until someone fixes it

Maria

Flaky tests still block builds several times a week

Kirill

One person holds all the billing knowledge

Try Template

What is the Rose, Bud, Thorn retrospective?

The Rose, Bud, Thorn retrospective is a balanced reflection format borrowed from gardening metaphors. It invites the team to look at what went well, what shows promise, and what hurts — in a single, easy-to-grasp structure. Because every entry maps to a flower, the format feels approachable even for people new to retrospectives, while still producing actionable insight. It works for sprint reviews, project milestones, and personal check-ins alike. The format uses three columns:

Rose — clear wins and things that are going well.
Bud — ideas and opportunities with potential to grow.
Thorn — problems, blockers, and pain points.

Rose

The Rose column captures the highlights: successes, positive moments, and practices worth keeping. Recording roses reinforces good habits and reminds the team of progress that is easy to forget in the rush of delivery. Be specific — "the new code review checklist cut review time in half" is more useful than "reviews were good."

Bud

The Bud column is about potential. These are early ideas, emerging opportunities, or things that are not fully formed yet but could blossom with attention. Buds turn a backward-looking retro into a forward-looking one, giving the team a place to plant seeds for the next iteration.

Thorn

The Thorn column names what is painful or blocking progress: recurring bugs, unclear ownership, friction in the process. Treating thorns honestly — without blame — lets the team prune what slows it down and decide which issues deserve immediate action.

Benefits of the Rose, Bud, Thorn retrospective

Balances celebration, opportunity, and problem-solving in one view.
Uses an intuitive metaphor that lowers the barrier to participation.
Surfaces growth ideas, not just complaints.
Works for teams, projects, and individuals.
Quick to set up and easy to facilitate.
Produces a clear mix of things to keep, grow, and fix.

How to run a Rose, Bud, Thorn retrospective

Create a board in QRetro from the Rose, Bud, Thorn template and invite your team.
Explain the metaphor and the time period the retro covers.
Give everyone 5–7 minutes to add cards silently to all three columns.
Group related cards and read each column aloud, starting with Rose.
Discuss the most important buds and thorns, then vote on what to act on.
Assign owners to the top action items and save the board for follow-up.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.

Hopes and Fears

A forward-looking format best used at the start of a project, quarter or initiative. The team shares its hopes for what could go right alongside its fears about what might go wrong. Naming both early builds shared understanding and surfaces risks while there's still time to act on them.

Good Bad Better Best

A four-column format that turns reflection into a ladder of improvement. The team names what was good and what was bad, then pushes further to what could be better and recognizes the very best results, performances and people. Ending on the high note of best keeps the energy positive and celebrates standout contributions.

Likes / Wishes / Wonders

A concise, exploratory format that blends feedback with curiosity. Participants share what they liked, what they wish were different and what they wonder about going forward. The wonders column invites open questions and fresh ideas, making it a great fit for teams exploring new ways of working.

OKR Template

A goal-focused format that ties reflection to objectives and key results. The team reviews its objectives, examines the key results that measure progress and aligns on the initiatives that will drive them forward. It's a strong choice for connecting day-to-day retrospectives with the bigger goals the team is accountable for.

Retrospective Template: WWW

A nuanced take on the classic what-went-well format that adds a middle ground. Instead of a strict worked-or-didn't split, the team also captures what kinda worked — the partial successes and half-measures. That extra shade often holds the most useful insights, where small adjustments can turn a near-miss into a win.

Safety Check for Retrospective

A short anonymous poll that measures how safe people feel to speak openly before the real retrospective begins. Everyone rates their comfort from 1 to 5, and the aggregated result tells the facilitator whether the team is ready for candid conversation. It's a valuable warm-up for new teams or after tense periods, where psychological safety can't be taken for granted.

Try Template