Objects and Models: Why Work Never Matches the Diagram

Editor’s Note: This essay sits within Cultivated’s library on representation, systems, and organisational reality. It explores the persistent gap between how work is modelled and how work is lived, and why leadership requires attention not just to plans and diagrams, but to the behaviours, relationships, and informal practices that actually produce value.

Objects and Models: Why Work Never Matches the Diagram

Plans, roadmaps, operating models, org charts
— these are necessary objects.

They help us coordinate.
They allow a complex system to be discussed at all.
But the object is not the work.

There’s a simple, uncomfortable truth at the heart of modern work: our observation is always partial.

Sometimes we’re not even seeing the thing itself
— only a representation of it.
A diagram.
A plan.
A model.
A neat abstraction that lets us point, explain, and feel a small sense of control.

But if our observation is limited, so is our interpretation.

What we think we’re looking at is shaped by what we already know, what we expect to see, and what the organisation has trained itself to notice.

At some point, observation alone runs out.
We reach the limit of what the object can explain.

That’s where many organisations quietly stall:
not for lack of talent,
not for lack of effort,
but because the object becomes the truth.

I once worked with a leader who had built a truly beautiful model of his part of the organisation.

It covered an entire wall
— five metres wide, three metres tall
— a careful landscape of boxes, lines, colours and arrows.

He needed a step ladder to reach the top. It was meticulous. Thoughtful. The result of real attention.

He ran the business from that model.
He made decisions based on it.
He used it to explain how work flowed, where accountability sat, how value moved through the system.

The problem was not that he was careless.

The problem was simpler, and more human: the model was treated as reality.

All models are wrong — he knew that, intellectually. What he didn’t know was how wrong, or in which places.

He drove the business into decline from behind his desk, steering by an artefact that could no longer tell him what was actually happening.

In another organisation, I watched a group of coaches celebrated for shaving six months off a delivery plan.

Six months. Twenty million saved — on paper.
High fives all round.

But the work hadn’t started.

The plan had not yet met people, dependencies, uncertainty, or the slow surprises that appear the moment a diagram turns into a week of real meetings and real constraints.

The “saving” was, at best, provisional.
At worst, it was the early celebration of a fiction.

Later, the cost returned — with interest.

This is the seduction of object-centred work:
the plan becomes the achievement.
The diagram becomes the proof.
The model becomes the comfort.

Meanwhile the only thing that ultimately matters
— what the organisation can do, deliver, learn, and sustain
— remains untested.

To make sense of this, it helps to name three distinct realities that sit on top of one another.

At the surface are the objects we use to describe work: plans, roadmaps, operating models, org charts, frameworks.
They are necessary.
Without them, coordination collapses.
They allow an organisation to orient itself, to speak in shared language, to attempt coherence.

But objects are incomplete by design.
They smooth away detail.
They hide uncertainty.
They compress lived complexity into something that fits on a wall or a slide.

Underneath the objects is what people actually do.

How the roadmap is interpreted, bent, ignored, or quietly rerouted.
How decisions are really made.
How work truly flows.
Who influences whom.
Where negotiation happens.
Where improvisation keeps the system alive.

Org charts don’t show power.
Job descriptions don’t show contribution.
Process maps don’t show workarounds, care, creativity, or the informal agreements that make the formal system function.

This is why generic frameworks disappoint so often:
they are objects designed for broad utility,
not the specific texture of lived reality.

They can coordinate language, but they can also obscure the very nuance that determines whether work succeeds.

And then there’s a third reality
— the one most people forget to revisit.

What was the object meant to represent in the first place?

That diagram on the wall wasn’t really about boxes and arrows.
It was trying to represent how value moves.
How work gets done.
How customers are served.
How accountability holds.

The tragedy is not that we create objects.
The tragedy is that we stop at the object
— and stop checking whether it still represents the system we are actually living inside.

Objects and models are essential.
But work does not happen in them.

Work happens in the space between design and use
— between intention and interpretation,
between what we draw and what people actually do when they come together to get something real across the line.

Good leadership lives in that gap.

Not defending the model.
Not worshipping the plan.
Not mistaking tidiness for truth.

Just staying close to reality.

Staying curious where reality refuses to conform.
Learning from what people actually do
— especially when the diagram says they shouldn’t have to.

That’s where improvement starts.

Not with a better diagram, but with noticing.