// chapter 02 of 13

Somebody designed the hospital

Matt Roberts
By Matt Roberts, co-founder, ZOKRI
From Trading to Scaling, the free book

In a well-designed hospital, it is about ninety seconds from the ambulance bay to the resuscitation room.

That is not luck. Somebody sat with a drawing and decided it. They knew what happens in those ninety seconds, they knew the trolley needs to turn a corner without stopping, and they put the doors where they went for that reason.

Figure 1 · Every distance was set by somebody, or by nobody
Designed
Ambulance bay
90 seconds
Resuscitation
Accidental
A problem appears
?
Somebody can act
The corridors in your company are made of meetings, routes and permissions rather than walls. They still have a length, and somebody set it.

Nobody who works in that building thinks about it. The porters do not know they are inside somebody's decision. They just find that the right thing is the easy thing to do, all day, without effort.

That is what a design does. It is not a set of rules. It is an environment that makes good work the path of least resistance.

Nobody designed yours

Your company also has corridors. They are just not made of walls.

They are the meetings where a decision gets made, or does not. The moment somebody finds out a project is in trouble, or it’s hidden until too late. The half hour where a good idea either gets heard or gets forgotten. The route a piece of bad news takes to reach you, and how much it changes on the way.

Every one of those is a distance, and every distance was set by accident.

Which means your people are walking a route nobody chose, and when they take longer than you would like, or arrive with the wrong thing, they are doing exactly what your designs tell them.

This is the job, and it is probably not in your diary

You are the architect of how your company works. Not because you applied for that job. Because nobody else in the building can do it.

A functional head can improve its own function. A good manager can protect their own team. Only you can decide what the environment teaches everybody, because only you own more than one part of it. That is not a claim about your talent; it is a fact about your position.

And I would put it higher than most of what is currently in your calendar. Strategy decides what to aim at. Hiring decides who aims. The design decides what all of them actually to do when nobody is watching, and it does that every day, for everyone.

So why does nobody do it?

Three reasons, and none of them are about intelligence.

It does not look like work. There is no deliverable.

There is no job title for it. Nobody owns how the company decides, so it belongs to whoever last had an opinion about it, although the COO or Chief of Staff tends to have it in their Job Description.

And nothing breaks the week you skip it. The one that does the real damage. A design problem never presents as urgent. It presents as everybody being slightly slower than they should be, for years.

Which is also why it is available. Almost nobody is doing this, including your competitors, so the return on it is unusually high for something that costs so little.

What it looks like when the load is accidental

Two examples, and I choose them because most companies have both.

The monthly meeting where each part of the business gives an update. Too long, half of it slides that could have been an email, and nobody can name a decision that came out of the last one.

Look at what it is carrying. It is the only hour of the month when someone has to stand before their peers and explain why a project they started nine months ago is still ongoing. Nobody designed it for that. It is doing the most important job in the room by accident, which is why shortening it feels sensible and costs so much.

And the away day. Two days, expensive, half of it theatre, and the last one produced a list nobody looked at again.

What is it carrying? The only time in the year the leadership team is out of the business, together, with nothing scheduled and permission to ask whether the plan still makes sense. The permission was the point, and it was never designed either. It came free with the venue.

An architect would not accept either of those. Not because removing them is dangerous, but because valuable functions in that company are currently being performed as side effects. Somebody should decide where they live, deliberately, and then they will keep happening.

What an architect actually does

Not an audit. Two habits, and they are quick.

Decide what each thing in the week is for, and say it out loud. Not what it is called. What it produces, and what it teaches. A meeting with a stated purpose survives a busy month. One with an inherited purpose does not.

And when you move something, name what picks up the load. Every time. This is the whole of good practice, and it takes one sentence.

That second habit is why Part Two is shaped the way it is.

Each of the six parts either enhances or replaces something you already have, and each names what it is picking up.

The weekly rhythm replaces your status meeting and picks up the accountability, twelve times as often, with a name against each decision. The one page replaces the annual plan and picks up the argument. The monthly look at the measures picks up the away day's best hour and asks its question without needing a venue.

If I told you to cancel your status meeting and nothing picked up what it was quietly carrying, I would have made you faster at running the wrong things and called it progress.

And the reason to enjoy this

Everything above sounds like maintenance. It is not. It is the most interesting problem in the building.

You get to decide how far it is from a problem appearing to somebody being able to act on it.

You get to decide whether the honest answer or the comfortable one is easier to say.

You get to design a company where doing good work is the path of least resistance, which is a real thing you can build and which most people never get to work in.