Rose Bud Thorn
Design-thinking friendly: positives, emerging opportunities, and pain points.
Rose
What is working well and felt positive?
Bud
Potential or ideas not yet fully realized—things to nurture.
Thorn
Challenges, blockers, or frustrations to address.
This board is for demo purposes only. Your responses are not saved. Close or refresh the page to clear all cards. Do not add any sensitive information.
What is Rose Bud Thorn?
Rose Bud Thorn is a retrospective and reflection framework that originated in design thinking workshops at organizations like IDEO and the Stanford d.school. The botanical metaphor makes the format intuitive: roses represent things that are blooming and beautiful, buds represent potential that has not yet opened, and thorns represent pain points that prick. The format was adopted by agile teams in the 2010s as design thinking practices merged with software development methodologies.
What distinguishes Rose Bud Thorn from similar three-column formats is the "Bud" category. While most retrospective formats divide the world into positive and negative, buds occupy a unique middle ground—they are neither problems nor successes but rather emerging possibilities. A bud might be a new team member whose potential has not been fully tapped, a tool that was introduced but not yet integrated into workflows, or a practice that showed early promise but needs nurturing.
The organic metaphor resonates particularly well with creative and product-oriented teams. It frames the team experience as a living, growing thing rather than a mechanical process. This subtle shift in language influences how people think and talk about their work, encouraging patience with emerging practices and attentiveness to early signals.
When to use Rose Bud Thorn
Rose Bud Thorn excels when a team is in a growth phase—onboarding new members, adopting new technologies, or expanding into new domains. The "Bud" column is specifically designed for these transitional periods where potential is abundant but unrealized. It is also excellent for product teams that practice design thinking, as the shared vocabulary creates continuity between discovery and delivery processes.
The format works well with teams of four to twelve people and fits into a 45 to 60 minute session. It is particularly effective for cross-functional teams where different roles experience different roses, buds, and thorns. A designer might see a budding opportunity in a new prototyping tool while an engineer sees a thorn in the same tool integration complexity.
Use this format when your team tends to focus only on what is working or what is broken, missing the nuanced middle ground of emerging potential. Avoid it when the team is in crisis and needs to focus exclusively on urgent problems—the contemplative nature of the bud category may feel indulgent when fires need extinguishing.
How to facilitate Rose Bud Thorn
Set the scene with a brief explanation of each category, using real examples from the team context. Roses are clear wins—things that bloomed this sprint. Buds are seeds of potential—things that started small and could become roses with nurturing. Thorns are pain points—things that pricked. Give the team six to eight minutes for silent writing, encouraging at least two items per category.
Process roses first to establish a positive and appreciative tone. Then move to buds—this is the most important and unique part of the format. For each bud, ask: "What would help this grow into a rose? What does it need—time, resources, attention, practice?" This framing turns identification into action planning naturally. Finally, process thorns, grouping related items and discussing root causes.
After processing all three categories, look for connections. Often a thorn and a bud are two sides of the same coin—a painful process (thorn) that has a promising alternative emerging (bud). These connections create naturally compelling action items: invest in the bud to replace the thorn. Close with two to three commitments that balance nurturing buds and removing thorns.
Tips for getting the most out of Rose Bud Thorn
The "Bud" column is what makes this format special, so invest facilitation energy there. Teams new to the format often struggle to distinguish buds from roses or thorns. A good test: if it is working well already, it is a rose. If it is causing pain, it is a thorn. If it has potential but needs investment to realize that potential, it is a bud. Concrete examples during the setup phase prevent miscategorization.
Avoid letting the thorn column dominate. If thorns significantly outnumber roses and buds, the team may be demoralized. In these situations, take a step back and ask: "Are there any buds hiding inside these thorns? What potential exists within these challenges?" Reframing thorns as buds-in-waiting can shift the team from a deficit mindset to a growth mindset.
Track buds across multiple retros. A bud that appears in three consecutive retros without becoming a rose needs attention—either invest in it deliberately or acknowledge that conditions are not right for it to grow. This longitudinal tracking turns one-off retros into a continuous portfolio management practice for team improvement.
Variations and adaptations
For remote teams, use a digital board with visual elements—actual rose, bud, and thorn emojis or images make the metaphor more vivid on screen. Consider having participants submit cards asynchronously with brief voice notes explaining their thinking, then use the synchronous session for discussion and prioritization. The voice notes add emotional texture that text alone misses in remote settings.
For asynchronous teams, run a "garden journal" variation where the board stays open for an entire sprint. Team members add roses, buds, and thorns as they experience them throughout the iteration, not just at the retro. The synchronous session at the end reviews the accumulated garden and identifies patterns. This real-time capture produces richer, more specific feedback than end-of-sprint recall.
A powerful adaptation for product teams adds a fourth category: "Soil"—the underlying conditions that enable growth or hinder it. Soil items might include team culture, organizational support, technical infrastructure, or process maturity. This addition shifts attention from symptoms to root conditions and works especially well for quarterly reviews. Another variation used in education and workshop contexts replaces the sprint focus with a learning focus: roses are insights gained, buds are questions that emerged, and thorns are concepts that remain confusing.
Run Retrospectives in CodeKudu
CodeKudu includes dozens of retrospective board templates, anonymous feedback, AI summaries, and action items that sync to GitHub Issues, Jira, and Linear.
