an illustrated analogy
Capability Brown.
Platform architecture as landscape - terrain, beds, paths and seasons. The estate, tended over years.
Monowai · Engineering Advisory
lancelot brown, 1716 - 1783
He didn't plant flowerbeds
He read the terrain
Rivers, hills, woodland - the whole estate, walked before anything was drawn. He told owners their land had 'capabilities'. The name stuck.
He designed for flow
Sweeping lawns, sightlines, paths that led you round the estate without a single sign telling you where to go.
Natural, but engineered
The lake at Blenheim looks like it was always there. He made it by damming the Glyme.
He planted for decades
His landscapes took a generation to reach the view he drew. Much of it arrived after he died.
He shaped the ground - the gardeners made it grow.
the estate
Every part of the estate has a platform twin
Terrain
= enterprise context - business units, legacy, regulation
Soil
= infrastructure - clusters, cloud, networking
Beds
= domains - clear ownership, agreed edges
Paths
= the paved road - pipelines, templates, tools
Irrigation
= automation - tests, scans, deploys on every change
The ha-ha
= guardrails - governance built into the ground
Gardeners
= delivery teams - tend, prune, share the shed
Harvest
= user outcomes - the reason for the estate
The architect is Brown. The teams are the gardeners. Both are needed.
the corporate default
The garden most organisations run
No beds
Services planted wherever there was space. Roots tangle, and no one can say whose patch is whose.
No paths
Every team tramples its own route to production. The lawn is mud by the end of the quarter.
Buckets, not irrigation
Deploys carried by hand. The beds go dry whenever the one person who waters them is on leave.
Weeding is a campaign
Debt left for a clean-up quarter that never quite arrives. By then it has set seed.
From the house, it still looks green - so does every status dashboard.
terrain - enterprise context
Read the land before you plant
Survey first
Legacy systems, regulation, org charts - that is the land you have. Draw the plan on it, not on a blank page.
Water follows the contours
Delivery follows team structure. Change the team boundaries and the architecture follows, whether you planned it or not.
Name the capability
The architect's first deliverable is an honest read of what the estate can become - and what it will cost to get there.
Brown didn't flatten the estate to fit the drawing - he drew to fit the estate.
beds - domains & boundaries
Beds give shape, so roots don't tangle
One bed, one gardener
Every domain has an owner. Shared ownership of a bed means it gets weeded by whoever notices first, which is no one.
Edges are contracts
What crosses the edge of a bed is agreed before it crosses - an interface, versioned, not a root pushing under the border.
Sized for the mature plant
Draw the boundary for the service at scale, not as planted. Moving a grown tree is a migration project.
Without beds, the strongest plant wins - that's competition, not architecture.
paths - the paved road
Lay the path where people already walk
Read the desire paths
The worn track across the lawn is the requirement. Teams' workarounds show you which road to pave next.
Easiest is right
Brown's paths felt natural because they were engineered to. The golden path wins by being the least effort, not by mandate.
Off-path, but uphill
Teams can leave the road. They carry their own water when they do - and they can see the cost before they choose.
A road no one walks is a monument - pave the desire paths.
the ha-ha - guardrails
The best fence is one you never see
A sunken wall and ditch. Livestock stay off the lawn, and from the house the view runs unbroken to the horizon.
The boundary is in the ground
Policy lives in the pipeline, not in a review board meeting every second Tuesday.
The view stays open
Within the estate, teams see everything and deploy freely. Nothing to ask permission for.
The sheep still can't cross
An unsigned image, a broken contract, missing evidence - stopped at the wall, every time, without a gatekeeper.
Compliance by default - governance built into the land, not bolted on.
irrigation - automation
Stop carrying buckets
Buckets
- Whoever's on shift waters - from memory
- Some beds drown, some go dry
- No record of what got water, or when
Irrigation
- Tests, scans and deploys run on every change
- The same water reaches every bed
- Evidence of what ran, stamped per release
A gardener carrying buckets has no time left - to garden.
weeds & pests - debt & security
Weeding is a schedule, not a campaign
Small and often
Dependency updates every week, merged by the pipeline when green. A weed pulled at a week old has no roots.
Variants self-seed
Every unrecorded local choice seeds the next one. Four ways to deploy started as one reasonable exception.
Pests at the gate
Scanning and a patch cadence at the boundary. A pest caught at the gate costs less than one found in the orchard.
The clean-up quarter is where tech debt goes to set seed.
seasons - change & evolution
No garden stays planted
Prune on purpose
Retire components deliberately - a deprecation with a date, not a service left to die back on its own.
The strangler fig
Replace legacy by growing around it until the old trunk can go. A big-bang rewrite is clear-felling - and nothing grows for years.
Plant for the canopy
Contracts, the versioned system, the paved road - the oaks. Slow to establish, and they shape everything planted under them.
Good platform decisions pay out after the architect has moved on.
gardeners - delivery teams
Gardeners, not factory hands
Tending
- Notice what needs water, pruning or support
- Share the shed - tools, templates, what they learned
- Work inside the beds they agreed to
Neglect
- Weeds and pests left for later
- A fence round their plot, the good tools inside it
- Planting wherever there's a gap
The output isn't more plants - it's a healthier garden.
the fragile garden
Platforms are fragile to neglect.
Not technically brittle. Golden paths get overgrown, and shared tooling rots when its gardeners disperse.
A platform is an agreement to work in a prescribed way - held by contracts and automation, and kept alive by the gardeners who choose to respect the beds.
harvest - from garden to kitchen
The point of the estate is the yield
Lawns impress visitors. The kitchen garden feeds the house. A platform exists so fruit reaches the business faster and fresher.
you are here · the harvest goes to the kitchen
closing thought
Brown didn't plant the flowerbeds.
He shaped ground where gardeners could thrive - paths that felt natural, boundaries you never saw, and a view that kept improving long after he'd gone.
That's the platform architect.