Rose, thorn, bud is a simple tool for reflection for yourself or your team. The basic idea is to look back at a recent project or how things are going and consider each aspect of a rose:

Rose: what are the successes? What's gone well?

Thorn: what are the challenges? What could we do better?

Bud: what are opportunities with potential? What could we explore or try?

If running as a team retro activity or retrospective, you might spend a few minutes individually adding thoughts for each prompt, then talk through each of the thoughts in Rose, Thorn and Bud.

A separate but no less important step is often to capture actions from the reflection—what you'll do as a result. If you're conducting retros regularly, consider revisiting actions from previous sessions.

I like "rose, thorn, bud" as it's beautiful to consider that a rose contains such different facets, like so many things.

I've come across many retro and reflection activities that are variations of these three prompts: "What went well?", "What didn't go well?" and "What else?" A few to mention:

The sailboat retro: Goal/vision, Rocks, Wind, Anchor — a nice feature for a team is that this activity places you all in the same boat

Strengths, Weaknesses, Opportunities, Threats (SWOT)

A reader suggested a fourth aspect of the rose analogy to reflect on as its leaves or roots: what are the unnoticed or behind-the-scenes things that contribute to the rose's success?

I've come to consider that it doesn't matter too much what activity you choose to get a discussion going. What matters most is regular reflection, hearing all the voices in a team, and making progress together. One teammate ran an excellent retro by us all finishing early and heading to the pub.

I didn't intend it, but some of the products and prints for rose, thorn, bud out to be some of the nicest I have.

Also see: Information radiator, MoSCoW prioritisation, RACI, How to peel a Post-it so it doesn't fall down, the upward spiral

Rose, Thorn, Bud

The frog boil metaphor illustrates how it's easy to miss small changes that build up over time until it's too late. The scenario, as told, is that of a poor frog who would leap away from hot water but, if put into cooler water that is gradually warmed, won't respond in time to getting boiled.

As a metaphor, it describes a powerful and pernicious shortcoming in how we perceive the world. A student kitchen that gets messy mug-by-mug, a business with gradually slowing sales, software that builds up with tech debt, a river that is slowly polluted, a road that gets busier each day, a bay that sees fewer fish each year, content that drifts, cancer that slowly spreads, a story or behaviour that becomes normal, a website that gets slower feature-by-feature, or a climate that slowly warms are all cases where we may not be happy where we end up, but we didn't notice how we got there.

It's hard to respond to gradual change, especially when it spans generations. Jared Diamond called it out as a potential fate of the Easter Islanders and how they could have cut down the last tree. One barnacle is nothing, but many barnacles can cause significant headaches for big ships.

Fortunately, there's a flip side. Many, many things are getting better without us realising. Small positive changes, such as in attitudes, education, or healthcare, add up over time—the Destiny Instinct can mislead us. Fast and slow layers make a system, like a forest, more robust. Getting one percent better each day leads to a 37x improvement in a year. And enough molehills can make a mountain.

What a frog does, in this case, is not, apparently, true—don't try it—it's much better as a metaphor, not an experiment.

The frog boil metaphor

Perhaps, like me, you’re used to thinking about bringing customers onboard as a funnel. It’s a very natural metaphor for thinking about customer acquisition. For example, you market to 10,000 people, 500 people visit your website, 50 of them put something in the basket and 10 of them buy. If you draw it out it looks like a funnel. And the next time you market you start fresh with a new 10,000. But the real world isn’t like that. Delivering a good service to your customers helps the next customers come in. Hence the flywheel model.

A flywheel is typically a big heavy wheel that stores and releases energy from an engine or vehicle. The flywheel metaphor is about happy customers driving your growth. And when you think about your business this way it can cause you to make different decisions. Having more customers is like a bigger, heavier flywheel containing more energy. Happy customers speed you up, unhappy customers slow you down. Making it easier for customers to try your product reduces friction, as does making it easier for for customers to talk about and share your product. Get your flywheel big, heavy and spinning like crazy and your business is doing well.

The flywheel model is from Brian Halligan at Hubspot. I’ve thought about customer funnels for literally years and I wish I’d known about the flywheel long ago. Check out Hubspot’s flywheel intro for more.

The business flywheel

More value will likely be found through analogy than the shipping situation. Watch out for barnacles on your project. One by itself is nothing, but enough of them can cost you.

Watch out for barnacles

Maslow’s is interesting, but not terribly helpful if you want to use it for something. This one however, I still find a very useful framework when designing (read about it in the DMI paper System Logics). Your sweet spots for the exciting innovations are the context and activity level needs. 

Patnaik’s Hierarchy of Needs

Half the time when you pick up a whiteboard pen that doesn’t work, it’s because it’s been stored nib-upwards. It usually just needs a little re-charging.

Store whiteboard pens with the nib down

I love the idea that the computer just disappears backwards into the plug. Neal Moore first mentioned this to me. In the Theory of Inventive Problem Solving there’s an idea that all functions will eventually be subsumed by the system above it. Assuming that we will always need some sort of power it makes sense that the computer will disappear into there at some point. The iMac was essentially a jump where the computer disappeared into the screen. For this reason I’ve often thought that floors, walls and ceilings should be given more thought than they are. When everything else has changed, I reckon they will still be around. I wouldn’t mind if our dinner table disappeared into the floor once we were done with it for example.

Plug computing

Underlining was a by-product of typewriters. It generally doesn’t improve things. Now, I’m still waiting for someone to make a pen with a button on it to write in bold. And to write a straight line without a separate ruler. Anyone want to team up?

Urge to underline? Use bold or italic instead

The realisation originally came to me when I saw, pinned outside a Professor’s door, an entire sheet of plain letter paper with a single line quote at the top. The standards are driving the system. About time we got more flexible.

If we plumbed in printers

Do not hesitate to ditch that which doesn’t stack and replace with ones that do. Life is too short.

Non-stacking Tupperware should be destroyed

I think I would buy one of these if it existed as cool as it does in my mind.

Get my new weekly sketch in your inbox

Category: product