The Rose Bud Thorn retrospective uses a gardening metaphor to create a balanced, optimistic reflection. By framing feedback as roses (successes), buds (potential), and thorns (challenges), teams maintain a growth mindset while still addressing problems.

Teams that run regular retrospectives are 24% more productive (State of Agile Report), and in this guide, you’ll learn how to run an effective Rose Bud Thorn retrospective, when to use it, and how to get the most from this nurturing format.

What Is the Rose Bud Thorn Retrospective?

The Rose Bud Thorn format uses three categories drawn from plant growth:

• 🌹 Rose: Things that are blooming—successes and positives
• 🌱 Bud: Things with potential—emerging opportunities
• 🌵 Thorn: Things that are prickly—challenges and pain points

The gardening metaphor naturally suggests growth, nurturing, and patience—helpful frames for continuous improvement.

Origin of Rose Bud Thorn

This format originated in design thinking and education contexts before being adopted by agile teams. Its strength is the bud category—unlike many retrospective formats, it explicitly captures potential and emerging opportunities, not just what exists today.

The Three Categories

🌹 Rose: What’s Blooming?

Roses represent your successes—things that have flowered and are thriving.

What to capture:

• Wins and accomplishments
• Things working well
• Moments of success
• Positive outcomes
• Effective practices

Example items:

• “Successfully launched the new feature”
• “Team collaboration was excellent”
• “Met all sprint commitments”
• “New automated tests caught several bugs”
• “Customer feedback was very positive”

🌱 Bud: What’s Emerging?

Buds represent potential—things that haven’t fully blossomed but show promise.

What to capture:

• New ideas worth exploring
• Promising practices just starting
• Opportunities on the horizon
• Areas ready for investment
• Seeds of improvement

Example items:

• “Pair programming experiment showing promise”
• “New design system could improve velocity”
• “Growing relationship with Product team”
• “Interest in learning Kubernetes”
• “Customer request that could be a new feature”

💡 The power of buds: This category captures what other formats miss—the emerging, the potential, the “not quite yet but promising.” It’s inherently forward-looking and optimistic.

🌵 Thorn: What’s Prickly?

Thorns represent challenges—things causing pain or difficulty.

What to capture:

• Problems and blockers
• Pain points
• Frustrations
• Things that didn’t work
• Areas needing attention

Example items:

• “Deploy process too slow”
• “Unclear requirements caused rework”
• “Technical debt in payment module”
• “Too many interruptions during focus time”
• “Stakeholder expectations unclear”

When to Use Rose Bud Thorn

Best Use Cases

After Mixed-Outcome Sprints

When results were neither great nor terrible, Rose Bud Thorn’s balanced structure helps teams see the full picture.

For Creative Teams

Design, marketing, and product teams often connect with the growth/gardening metaphor.

When Teams Need Balance

If your team tends toward negativity OR excessive positivity, this format enforces balance.

For Forward-Looking Discussions

The bud category makes this format naturally future-oriented.

When Building Morale

The optimistic framing (two positive categories, one negative) helps struggling teams see potential.

Best For

Attribute	Recommendation
Team size	3-10 people
Experience level	Any
Duration	45-60 minutes
Best timing	Regular sprints, after creative projects

When to Choose a Different Format

• Deep problem analysis needed → 5 Whys
• Emotional processing needed → Mad Sad Glad
• Very quick review → Plus Delta
• Action-focused → DAKI

How to Run a Rose Bud Thorn Retrospective

Before the Meeting

1. Create the board with three columns: Rose, Bud, Thorn
2. Add visual icons (🌹🌱🌵) to make the format memorable
3. Prepare context - Sprint summary, metrics, notable events
4. Schedule 45-60 minutes for full discussion

Step-by-Step Facilitation

Step 1: Set the Stage (5 minutes)

Introduce the metaphor:

“Today we’re using Rose Bud Thorn. Think of our team as a garden. Roses are what’s blooming—our successes. Buds are emerging potential—things that could grow. Thorns are what’s prickly—our challenges. Let’s tend our garden together.”

Share the Prime Directive for psychological safety. Google’s Project Aristotle found psychological safety is the #1 factor in team effectiveness, so setting this tone early matters.

Step 2: Silent Brainstorming (8-10 minutes)

Everyone writes items for all three categories:

• One idea per sticky note
• Encourage items in each category
• Think about the sprint/project period

Step 3: Share Roses (10 minutes)

Start with positives:

• Each person shares their rose items
• Group similar items
• Celebrate successes
• Discuss what enabled these wins

Facilitator prompt: “What conditions helped these roses bloom?”

Step 4: Share Buds (10 minutes)

Explore potential:

• Share bud items
• Discuss what’s emerging
• Identify what could help buds grow
• Consider which buds to invest in

Facilitator prompt: “What would help this bud blossom?”

Step 5: Share Thorns (12 minutes)

Address challenges:

• Share thorn items
• Group by theme
• Discuss impact and root causes
• Consider how roses and buds might address thorns

Facilitator prompt: “Is there a rose or bud that might help with this thorn?”

Step 6: Action Items (8-10 minutes)

Create specific actions:

• Tend roses: How do we maintain successes?
• Nurture buds: Which buds do we invest in?
• Prune thorns: Which thorns do we address?

Assign owners and timelines.

Rose Bud Thorn Template

Use this visual template:

┌─────────────────────────────────────────────────────────────────┐
│                    🌸 OUR TEAM GARDEN 🌸                        │
├─────────────────────┬─────────────────────┬─────────────────────┤
│     🌹 ROSE         │     🌱 BUD          │     🌵 THORN        │
│   What's blooming?  │   What's emerging?  │   What's prickly?   │
├─────────────────────┼─────────────────────┼─────────────────────┤
│                     │                     │                     │
│ • Feature launch    │ • New design system │ • Slow deploys      │
│   was smooth        │   looks promising   │                     │
│                     │                     │ • Unclear specs     │
│ • Great team        │ • Pair programming  │   causing rework    │
│   collaboration     │   experiment        │                     │
│                     │                     │ • Tech debt in      │
│ • All sprint goals  │ • Customer interest │   payments module   │
│   achieved          │   in analytics      │                     │
│                     │                     │ • Too many          │
│ • Positive customer │ • Growing trust     │   interruptions     │
│   feedback          │   with Product team │                     │
│                     │                     │                     │
└─────────────────────┴─────────────────────┴─────────────────────┘

Sample Questions for Rose Bud Thorn

🌹 Rose Questions

• What are we proud of from this sprint?
• What went really well?
• What should we celebrate?
• What processes worked smoothly?
• What made you happy about your work?
• What wins did we achieve?

🌱 Bud Questions

• What shows potential for the future?
• What new practice seems promising?
• What opportunity is emerging?
• What are you curious to explore?
• What could grow into something great?
• What seeds have we planted?

🌵 Thorn Questions

• What caused frustration?
• What got in our way?
• What needs attention?
• What should we address before it gets worse?
• What was harder than it should be?
• What’s a pain point we keep encountering?

For discussion prompts that pair well with this format, see our retrospective questions guide.

Tips for Facilitating Rose Bud Thorn

1. Emphasize the Bud Category

Teams often neglect buds. Actively prompt:

“Before we move on, does anyone have more buds? Think about what’s just starting, what shows promise but isn’t proven yet.”

2. Connect the Categories

The magic happens when you link roses, buds, and thorns:

• “Could this rose help address that thorn?”
• “Would nurturing this bud prevent that thorn?”
• “What turned last sprint’s bud into this sprint’s rose?“

3. Use the Gardening Language

Lean into the metaphor for engagement:

• “Let’s water these buds”
• “What fertilizer does this rose need?”
• “How do we prune this thorn?“

4. Balance Quantity

If one category dominates, prompt for others:

“We’ve many thorns but few roses. Let’s make sure we capture what went well too.”

5. Create Growth-Oriented Actions

Frame actions using garden language:

• “We’ll nurture X by…”
• “We’ll prune Y by…”
• “We’ll protect this rose by…”

Common Mistakes to Avoid

Skipping or Minimizing Buds

The bud category is what makes this format unique. Don’t treat it as optional. Companies practicing continuous improvement see 37% lower employee turnover (State of Agile Report), and buds are where that forward-looking improvement mindset lives.

Treating Roses as Just “Positives”

Roses should be specific blooming successes, not vague positivity. “Good communication” is too vague; “Daily syncs caught three blockers early” is a rose.

Letting Thorns Dominate

The two-positive-one-negative structure is intentional. If discussion skews to thorns, redirect:

“We’ve spent a lot of time on thorns. Let’s make sure we give equal attention to our roses and buds.”

Not Connecting Categories

Missing the insight that comes from seeing how roses, buds, and thorns relate:

• A rose in one area might address a thorn in another
• A thorn might be blocking a bud from growing
• A bud, if nurtured, might become a rose

Rose Bud Thorn Variations

Rose Bud Thorn with Gardener

Add a fourth element:

• Gardener: What/who helps our garden grow?

Captures external support, tools, and resources.

Rose Bud Thorn with Soil

Add context:

• Soil: What environment/conditions enable growth?

Useful for discussing team culture and working conditions.

Rose Bud Thorn with Seasons

Frame by time:

• Spring (Starting): What’s just beginning?
• Summer (Growing): What’s developing?
• Fall (Harvesting): What are we reaping?
• Winter (Resting): What needs to pause?

Good for longer project retrospectives.

Personal Rose Bud Thorn

Individual reflection variation:

• Each person shares one rose, bud, and thorn about their own work
• Creates personal accountability and connection

Rose Bud Thorn vs Similar Formats

Rose Bud Thorn vs What Went Well

Aspect	Rose Bud Thorn	What Went Well
Categories	3	2
Future focus	High (buds)	Medium
Metaphor	Gardening	None
Positivity balance	2:1 positive	1:1

Rose Bud Thorn is more optimistic and future-focused.

Rose Bud Thorn vs Mad Sad Glad

Aspect	Rose Bud Thorn	Mad Sad Glad
Focus	Growth/potential	Emotions
Tone	Optimistic	Processing
Future orientation	High	Low
Best for	Forward planning	After difficult sprints

Mad Sad Glad processes emotions; Rose Bud Thorn focuses on growth.

Rose Bud Thorn vs 4Ls

Aspect	Rose Bud Thorn	4Ls
Categories	3	4
Learning focus	Low	High
Unique element	Buds (potential)	Learned
Tone	Growth	Reflective

4Ls emphasizes learning; Rose Bud Thorn emphasizes potential.

Related Retrospective Formats

If you like Rose Bud Thorn, try these:

• 4Ls Retrospective - Four-dimensional reflection
• Sailboat Retrospective - Navigation metaphor
• Starfish Retrospective - Five action categories
• What Went Well - Simple two-column format

See our complete sprint retrospective formats guide for 30+ options.

Try This Format in RetroFlow

RetroFlow has a built-in Rose Bud Thorn template. Here’s why teams pick it:

• ✅ Anonymous input for honest feedback
• ✅ Built-in voting to prioritize what matters
• ✅ Completely free — no signup required

Start Free Retrospective →

Frequently Asked Questions

What is the Rose Bud Thorn retrospective format?

The Rose Bud Thorn retrospective is a growth-focused reflection framework that uses a gardening metaphor. Roses represent successes that are blooming, buds capture emerging opportunities and potential, and thorns identify challenges and pain points. The format originated in design thinking and education before being adopted by agile teams.

How long should a Rose Bud Thorn retrospective take?

A Rose Bud Thorn retrospective typically takes 45 to 60 minutes for a full session. This includes 5 minutes to set the stage, 8-10 minutes for silent brainstorming, about 10 minutes each for roses and buds, 12 minutes for thorns, and 8-10 minutes for action items. Tools like RetroFlow make setup faster with a built-in template.

What makes the “bud” category different from other retrospective formats?

The bud category is what makes this format uniquely forward-looking. Unlike most retrospective formats that only capture what happened (good or bad), buds explicitly surface emerging opportunities, promising experiments, and potential that hasn’t fully materialized yet. This encourages teams to invest in growth rather than only react to problems.

When should I use Rose Bud Thorn instead of other retrospective formats?

Rose Bud Thorn works best after mixed-outcome sprints, for creative or design teams, and when you want a balanced discussion that leans optimistic. Its two-positive-to-one-negative structure (roses and buds vs. thorns) helps struggling teams see potential. Choose a different format if you need deep problem analysis (try 5 Whys) or emotional processing (try Mad Sad Glad).

How do I keep the bud category from being ignored?

Teams often neglect buds because they default to discussing clear wins or obvious problems. Actively prompt the team by asking “What’s just starting that shows promise?” and “What could grow into something great?” during the session. Spending dedicated time on buds and connecting them to thorns (asking whether nurturing a bud could address a thorn) helps reinforce their importance.