Rose, Bud, Thorn retrospective template

A gentle, visual format that surfaces wins, problems, and untapped opportunities.

Rose, Bud, Thorn is a reflection exercise where each person shares a rose (something that went well), a thorn (something that was difficult), and a bud (an opportunity or something promising that has not bloomed yet). The garden metaphor makes it approachable for groups that find "what went wrong?" too confrontational.

Unlike purely backward-looking formats, the bud column points the conversation at the future — ideas worth exploring, early signals worth investing in. That makes Rose Bud Thorn a strong choice for design teams, classrooms, workshops, and any team that wants optimism in the mix, not just problem-hunting.

Timebox

30–45 minutes

Team size

2–15 people

Cadence

Sprint retros, project milestones, workshops, or weekly check-ins

The Rose, Bud, Thorn board

Rose

What went well? What are you proud of or grateful for?

  • The new onboarding flow shipped ahead of schedule
  • Support tickets dropped 30% after the docs rewrite
  • The team handled the outage calmly and communicated well
  • Pairing sessions made the codebase feel less intimidating
  • Stakeholders finally saw the prototype and loved it

Bud

What is showing promise? What opportunity should we explore?

  • The internal API we built could power two other teams’ features
  • Early user interviews hint at demand for a mobile version
  • The new hire has automation skills we have not tapped yet
  • Customers keep asking about integrations — possible roadmap theme
  • The async retro experiment could work for planning too

Thorn

What was difficult, frustrating, or is still unresolved?

  • Requirements changed three times mid-sprint
  • The staging environment was down for two days
  • One person carried most of the release work — bus factor risk
  • Decisions from the last retro were never followed up
  • Too many meetings fragmented deep work time

How to run a Rose, Bud, Thorn retrospective

  1. 1

    Explain the metaphor (3 min)

    Introduce the three prompts: rose = a win or highlight, thorn = a difficulty or pain point, bud = an opportunity or promising idea that has not bloomed yet. Clarify that everyone shares at least one of each.

  2. 2

    Silent writing (8 min)

    Each participant writes at least one rose, one bud, and one thorn privately. Hidden cards prevent anchoring on the first opinion shared.

  3. 3

    Share and cluster (10 min)

    Reveal cards and let each person briefly present theirs, or read them aloud as facilitator for anonymous input. Group related cards into themes across all three columns.

  4. 4

    Vote on what matters (3 min)

    Vote on the themes worth discussing — include buds, not just thorns, or the conversation collapses into problem-solving only.

  5. 5

    Discuss and decide (10–15 min)

    For top thorns, agree on a fix and an owner. For top buds, decide the smallest next step to explore the opportunity. Roses deserve a moment too: name what made them possible so you can repeat it.

  6. 6

    Capture action items (5 min)

    Write down action items with owners and due dates, and schedule them for review at the next session.

Rose Bud Thorn examples for sprint retrospectives

Rose

  • CI pipeline is 40% faster after the caching fix
  • The bug bash before release caught three critical issues
  • New teammate shipped their first feature end-to-end

Bud

  • The feature-flag setup could enable real A/B testing
  • QA’s test scripts could become automated checks
  • Design system components are almost ready for other squads

Thorn

  • Code review turnaround is still 2+ days
  • Sprint scope grew after planning — again
  • On-call load is uneven across the team

Rose Bud Thorn examples for workshops and classrooms

Teachers, UX researchers, and workshop facilitators use Rose Bud Thorn to debrief lessons, projects, and semesters — it works from primary school to executive offsites.

Rose

  • The group project presentations were the best this term
  • Participants stayed engaged through the whole workshop
  • The icebreaker actually got everyone talking

Bud

  • Students want a follow-up session on the advanced topic
  • The breakout format could work for the bigger conference
  • Two quiet participants opened up in small groups — build on that

Thorn

  • The schedule left no buffer for questions
  • Tech setup ate 15 minutes of session time
  • A few voices dominated the full-group discussions

Rose Bud Thorn examples for personal reflection and 1:1s

Rose

  • Led my first cross-team project and it shipped
  • Got positive feedback on the architecture proposal

Bud

  • The mentoring conversations could grow into a formal role
  • There is budget for a conference talk next quarter

Thorn

  • Context switching between three projects is exhausting
  • I keep skipping learning time when deadlines loom

Best for

  • Teams new to retrospectives — the metaphor lowers the stakes
  • Design thinking workshops and brainstorming sessions
  • Mixed groups (stakeholders + team) where blame games are a risk
  • Check-ins on long-running projects where opportunities get overlooked

Facilitation tips

Do not skip the buds

Teams naturally gravitate to thorns. But buds are where growth ideas live — give them explicit airtime and at least one action item, or the format degrades into a complaints session with extra steps.

One of each, minimum

Asking everyone for at least one rose, one bud, and one thorn keeps the picture balanced and stops any single mood from dominating the board.

Use it when trust is still forming

The metaphor gives people distance from their feedback — saying "a thorn" is easier than saying "this failed." That makes it ideal for new teams or groups with stakeholders in the room.

Anonymize in low-trust rooms

If honest thorns are unlikely with names attached, collect cards anonymously and read them aloud as the facilitator.

Variations

Rose, Thorn, Bud (reordered)

Some facilitators run thorns second so the session opens and closes on a positive note: wins first, problems in the middle, opportunities last.

Daily rose ritual

As a lightweight team or family check-in, each person shares one rose, bud, and thorn from their day — no board, no votes, two minutes per person.

Rose Bud Thorn + voting

For groups over six people, add dot voting after clustering so discussion time goes to the themes with the most energy behind them.

Frequently asked questions

What do rose, bud, and thorn mean?+

The rose is something that went well or that you are proud of. The thorn is something difficult, frustrating, or unresolved. The bud is an opportunity — something promising that has not fully developed yet, like a new idea, skill, or early signal worth exploring.

Is it Rose Bud Thorn or Rose Thorn Bud?+

Both names refer to the same exercise and both orders are used in practice. Many facilitators prefer ending with the bud so the session closes looking forward at opportunities rather than backward at problems.

Where does the Rose Bud Thorn exercise come from?+

The exercise is widely used in design thinking and education — it is often associated with design consultancies and scouting programs — and spread into agile retrospectives because it balances positives, negatives, and opportunities in one simple structure.

How is Rose Bud Thorn different from Start Stop Continue?+

Start Stop Continue asks for behavior changes directly, which makes it more decision-oriented. Rose Bud Thorn is more reflective: it surfaces how the period actually felt and highlights opportunities (buds) that pure process formats miss. Many teams alternate between the two.

Run Rose, Bud, Thorn online in FocusRetro

Start a blank board, name the columns Rose / Bud / Thorn, and invite the team with a link — then run the phases with timers, hidden cards, and blind voting. Free plan available at focusretro.com.

Start a board free

No credit card required

Related guides

Hopes and Concerns retrospective template

Twenty minutes that surface what people want — and what they are quietly worried about.

Open the Box retrospective template

Treat how your team works like a box of tools — then decide what stays, goes, and gets added.

How to run a sprint retrospective (step-by-step guide)

A step-by-step sprint retrospective guide: the 5-phase agenda, exact timings for a 60-minute session, facilitation tactics, remote tips, and common failure modes.

Retrospective timebox calculator

How long Rose, Bud, Thorn should run for your sprint length and team size, split across the five phases.

Icebreaker and check-in questions

Openers for the first two minutes of a Rose, Bud, Thorn session, sorted by situation.