Is Rose, Bud, Thorn just a softer Start, Stop, Continue?

It looks similar but works differently. Start, Stop, Continue is action-shaped: every item implies a commitment. Rose, Bud, Thorn is observation-shaped: items are surfaced without an implicit demand to act on each one. That makes it less stressful for the team and better for sprints where most things are going fine.

How is Bud different from Continue?

Continue is for things that are working and should be protected. Bud is for things that aren't yet working but show promise. They're the opposite ends of certainty. A Bud might never become a Rose, and that's fine, naming it is half the value.

Can we use Rose, Bud, Thorn outside of sprint retros?

Yes. It works well for personal one-on-ones, project mid-points, and quarterly check-ins. The Bud category translates naturally to a personal context: what new skill or interest is starting to take shape? Most other retro formats don't translate as cleanly outside of a team setting.

What if every Thorn is the same Thorn?

Surface it directly. If the team converges on one Thorn, that's diagnostic, the format has done its job by giving the room permission to name it. Skip the rest of the discussion and spend the time on what to do about the Thorn instead.

How often should we change format?

Same answer as for any retro: every four to six. Rotate Rose, Bud, Thorn with 4Ls, KALM, and Start, Stop, Continue depending on what each sprint needs. The Bud category in particular is hard to import into other formats, so don't run Rose, Bud, Thorn for too many sprints in a row or the team will lose practice surfacing things into other shapes.

The toolkit · Rose, Bud, Thorn

Rose, Bud, Thorn retrospective

What's blooming, what's just starting to grow, what's prickly. The garden metaphor that says more than it should.

30 prompts · 3 columns · free

🌹

Rose

What bloomed this sprint? What's working beautifully?

10 prompts in this bucket

🌱

Bud

What's emerging that you're excited about?

10 prompts in this bucket

🌵

Thorn

What's prickly? What's actively hurting?

10 prompts in this bucket

Try another framework

Frameworks that pair well with Rose, Bud, Thorn.

4Ls

Liked, Learned, Lacked, Longed for. More texture than 3-column.

Start, Stop, Continue

The classic. Three columns, fast to run, hard to argue with.

KALM

Keep, Add, Less, More. Subtler than Start/Stop/Continue.

Or see all 10 retro frameworks.

About the Rose, Bud, Thorn retrospective

Rose, Bud, Thorn is the retrospective format that sits in the gap between 'too lightweight to surface anything real' and 'too heavy for a sprint where nothing dramatic happened'. The garden metaphor is doing real work. Roses are wins worth celebrating. Buds are emerging things worth nurturing. Thorns are prickly bits worth addressing. The Bud category is the secret weapon that most retro formats lack: a way to talk about the seedling project, the new joiner who's starting to find their footing, the experiment that hasn't proven anything yet but feels promising. Without a Bud category, those things get filed under Thorns (because they aren't yet wins) or ignored entirely. Use Rose, Bud, Thorn when the team is in steady state and you want a rounded view that includes momentum, not just the win-loss column.

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

Thirty-five minutes is the right band for a two-week sprint. Five for context, fifteen for silent writing, fifteen for discussion. The format compresses well because three categories means less to discuss than the 4Ls and more depth than Start, Stop, Continue. For a one-week sprint, run it in twenty-five. For a quarterly, expand to ninety with a full hour spent on Buds.

When Rose, Bud, Thorn beats other formats

When the team is mostly fine, but quietly something is shifting. A new project starting to take shape. A teammate growing into a new role. A practice that's beginning to pay off but isn't proven yet. None of those fit cleanly into Liked, Lacked, Started, or Stopped. The Bud column gives them a home. That's the format's real value: it surfaces things a sharper-edged retro would miss because they don't yet have a category to live in.

Rose, Bud, Thorn versus 4Ls

The 4Ls is heavier and gets into feelings. Rose, Bud, Thorn is lighter and stays focused on the work. Run 4Ls after a hard sprint when feelings are part of what happened. Run Rose, Bud, Thorn for a normal sprint when you want texture without weight. The two formats are good rotation partners, alternating between them keeps the team's frame of reference fresh.

Common mistakes with Rose, Bud, Thorn

First: under-investing in Bud. Buds get less air time than Roses or Thorns because they're harder to articulate, but they're the most actionable category. Second: turning Thorns into a complaints session. Cap the Thorn discussion at one third of the meeting and force a 'what would we do about this?' question at the end. Third: skipping the closing round of Roses spoken aloud. The closing changes the energy of the meeting and is worth the two minutes it costs.

Frequently asked

Is Rose, Bud, Thorn just a softer Start, Stop, Continue?: It looks similar but works differently. Start, Stop, Continue is action-shaped: every item implies a commitment. Rose, Bud, Thorn is observation-shaped: items are surfaced without an implicit demand to act on each one. That makes it less stressful for the team and better for sprints where most things are going fine.
How is Bud different from Continue?: Continue is for things that are working and should be protected. Bud is for things that aren't yet working but show promise. They're the opposite ends of certainty. A Bud might never become a Rose, and that's fine, naming it is half the value.
Can we use Rose, Bud, Thorn outside of sprint retros?: Yes. It works well for personal one-on-ones, project mid-points, and quarterly check-ins. The Bud category translates naturally to a personal context: what new skill or interest is starting to take shape? Most other retro formats don't translate as cleanly outside of a team setting.
What if every Thorn is the same Thorn?: Surface it directly. If the team converges on one Thorn, that's diagnostic, the format has done its job by giving the room permission to name it. Skip the rest of the discussion and spend the time on what to do about the Thorn instead.
How often should we change format?: Same answer as for any retro: every four to six. Rotate Rose, Bud, Thorn with 4Ls, KALM, and Start, Stop, Continue depending on what each sprint needs. The Bud category in particular is hard to import into other formats, so don't run Rose, Bud, Thorn for too many sprints in a row or the team will lose practice surfacing things into other shapes.

When not to use it

Conflict-recovery or post-incident retros where feelings need to come out. Rose, Bud, Thorn is too gentle to surface what people are angry about. After something difficult, run Mad, Sad, Glad first.

How to run a Rose, Bud, Thorn retro

1Block 35 minutes for a two-week sprint. The format sits between Start, Stop, Continue and 4Ls in weight, so size the meeting accordingly.
2Open with a one-line context recap. Don't oversell the metaphor, the team will run with it.
3Show all three prompts. Five minutes of silent writing per category. Rose first sets the tone, Bud second invites optimism, Thorn last to land on what to address.
4Discuss in order. Spend the most time on Bud, the least on Thorn (counterintuitive, but Buds are where the team makes decisions about what to invest in).
5Identify one Bud worth committing time to next sprint. Pick one Thorn to address before the next retro. Owners assigned.
6Close with a round of Roses spoken aloud. Names matter. Send the recap in Slack within an hour.