Part I — Discovering Flow

Gardening Organizations

A garden is not a machine. You cannot specify a tomato plant into existence, hand it a deadline, and expect fruit by Friday. You can only create the conditions — soil, light, water, space — and then do the patient, unglamorous work of tending while the plant does what plants do. Teams are the same. You cannot manage a team into greatness. You can only tend the conditions that make greatness possible, and get out of the way often enough to let it happen.

That distinction — between managing and tending — is most of what this chapter is about.

A well-tended garden bed doesn’t hold one kind of plant. Companion planting works because different roots reach different depths, pull different nutrients, and support each other in ways a monoculture never could. A team works the same way — architects, designers, developers, testers, product owners, each reaching into a different part of the problem, all sharing the same plot. The best moments happen when that variety moves in sync: covering for each other, playing to each other’s strengths, growing toward the same light.

Nothing about tending is passive, though. A gardener still has a plan — deciding what goes where, which beds get sun, which plants need staking before they fall over. Teams need the equivalent: guiding principles that connect every day’s work to something bigger, so a sprint isn’t just busy, it’s aimed. Without that plan, you don’t get a wild, thriving garden. You get weeds.

Underneath all of it is soil, and nothing grows in soil that’s been compacted by fear. Trust improves the same way soil does: slowly, through repeated seasons of people knowing what to expect from each other. Clarity about vision, goals, and responsibility is what keeps the soil loose enough for roots to spread. A culture of open communication and tolerated risk isn’t a nice-to-have on top of trust — it is how trust gets built, one honest conversation at a time.

Three conditions show up again and again in the research on what makes people thrive at work — autonomy, mastery, and purpose — and they map onto gardening almost too neatly. Autonomy is room to grow in your own direction within the bed you’ve been given. Mastery is the slow thickening of a root system that only comes from staying in one place long enough to actually take hold. Purpose is what the whole garden is for — not just the reason to grow, but the reason anyone’s tending it in the first place.

No gardener plants without deciding where one bed ends and the next begins — not to keep beds apart out of suspicion, but because clear edges are what let each bed be tended on its own terms, without one plot’s weeds choking the plot next to it. Organizing teams around business domains is the same instinct: clear boundaries that let each team act independently and decide quickly, without every root system tangling into every other one. How you draw those boundaries matters more than most teams realize — the shape of your teams becomes the shape of your systems, whether you plan for it or not. Rigid, centralized communication produces rigid, centralized software. Loosely coupled teams tend to produce loosely coupled systems. The garden’s layout and the garden’s yield are never really two separate things.

The best gardens, in the end, aren’t the biggest ones — they’re the ones sized so one person can actually reach every plant without trampling three others to get there. Teams work the same way: small enough that everyone can still see the whole bed, organized around a domain they actually own, given autonomy, mastery, and purpose, and tended with clarity and trust rather than instruction.

Great teams are gardens. They need space, light, and time to grow — and someone patient enough to keep tending them after the planting is done.