Part I — Discovering Organizational Flow · Chapter 5 · 4 min read · First Public Draft
The model
The Picture I Keep Coming Back To
One tree, standing in a forest of others. Every chapter after this is the same drawing from a different distance.
Jump to a chapter
Narrated with Microsoft's neural voice, not me — a recording.
Here is the picture this paper uses, and it is the only one it uses.
I have tried others. Machines, pipelines, engines, orchestras, the human body. Every one of them was useful for about a chapter and then started lying — a pipeline has no roots, an orchestra has a conductor, and a body cannot be reorganized in April. The tree kept working, and it kept working in the awkward places, which is the only real test a metaphor has to pass.
Light is purpose — the one part of this that isn’t inside the tree at all, and the part most easily misread. A tree is not trying to reach the sun. It is trying to keep living: to grow, to adapt, to survive a bad season and come back larger. Light is one of the conditions that makes that possible, alongside water, soil, and room for roots — and what it does is orient the growing rather than serve as its destination. Purpose works the same way for an organization. Not a value stated on a wall, and not a finish line either, but the thing that decides which direction the growing goes in, whether anyone has named it or not. An organization without one does not stop. It grows in every direction at once, which is the expensive way of standing still.
Roots are capabilities — what the organization can always do. Invisible from above, doing the unglamorous work of holding everything else up.
Soil is culture — the medium every root grows through. Nobody sees it directly, and it determines almost everything about what’s able to grow at all.
The trunk is structure — the load-bearing shape that channels what the roots gather upward. Thick enough not to bend in normal weather, and still, underneath the bark, alive and changing.
Branches are collaboration — the visible reaching-out between one part of the organization and the rest of it. Some load-bearing, some purely for light.
The canopy is value — the part the outside world actually sees. It looks like the whole tree from a distance. It’s really just the most recent season’s growth sitting on top of everything underneath.
And flow is the circulation — water and nutrients moving from roots through trunk to canopy, and back again as fallen leaves return to soil. The same way information, decisions and execution move through an organization, and the outcomes of that execution return as learning.
None of these layers work alone, and none of them work by being managed into place.
A machine responds to instruction. A living thing responds to conditions.
You cannot instruct a root system to grow faster; you can only improve the soil and wait. You cannot instruct a canopy to be more valuable; you can only strengthen what’s underneath it and let the canopy be the honest result. This is the hardest habit to unlearn for anyone trained the other way — the impulse to intervene on the outcome rather than on the conditions that produce it.
A tree that stops circulating dies standing up, long before it looks dead from the outside. An organization where information doesn’t reach decisions, where decisions don’t reach execution, where execution’s outcomes never make it back to inform the next decision, is doing exactly the same thing — just slower, and with better PR in the meantime.
Foresters had a name for this before organizations needed one. Girdling — a ring cut through the bark, all the way round the trunk, that stops the sap without felling the tree. The canopy stays green for weeks. A girdled tree doesn’t announce that it’s dying. It arrives as still being green.
That image is the reason I kept the metaphor. I have walked into organizations that were, in the strict sense, already girdled — still profitable, still shipping, still green from the road — and the only visible symptom was that nothing anyone decided seemed to reach anything.
Every chapter from here on is this drawing, looked at from a different distance. Not because the tree explains everything — no metaphor does — but because switching metaphors every chapter would be like redesigning the tree every season.
The value of a model isn’t that it’s perfect. It’s that everyone can keep using the same one long enough for it to actually mean something.
One last thing about the drawing, because it decides how everything after it should be read.
The tree is an organization. Yours. Not organizations in general.
Around it stands a forest of others — competitors, partners, suppliers, the places your people worked before they came to you. Each is a tree in its own right, grown in its own soil, reaching for light that falls at a different angle, shaped by weather yours never had. Two organizations in the same industry, on the same street, are no more interchangeable than two trees on the same hillside.
Which is worth holding onto, because it is the quiet reason so much borrowed advice disappoints — including, quite possibly, some of mine.
Editor's Notes
That organizations behave more like living systems than machines is not a new observation — Ludwig von Bertalanffy's general systems theory made the general case, and Donella Meadows' *Thinking in Systems* remains the most readable starting point. What this chapter does with it is more specific: it fixes one metaphor, assigns each layer of it to a named part of an organization, and then holds that mapping steady for the rest of the paper, so the metaphor can carry an argument instead of decorating one.