Chapter three · The cause underneath it
Your People Are the Wiring
Where systems do not connect, people become the connection. It appears on no org chart, nobody was hired to do it, and it takes a large share of the working day.

Wilfred Greyling
Systems & Infrastructure

TL;DR
The coordination load from the last chapter has to live somewhere, and it lives in your staff. They become the wiring between systems that do not speak, which is a job nobody was hired for and nobody is measured on. It shows up as decisions made on half a picture, and as juniors who see individual fields for years without ever seeing the pattern that would make them good.
What happens when two systems do not talk to each other?
Somebody makes them talk. That somebody is a person, and the job has no name.
It is worth picturing an ordinary instance rather than the general case. A customer changes a delivery address. The address exists in the ordering system. It does not exist in the dispatch system, or in the invoicing system, or in the note the driver gets. So somebody opens three screens and types the same line three times, and if they are having a bad morning they type it into two of them.
Nobody was hired to do that. It is on no job description and it appears on no org chart. It is also not one task: it is a hundred small ones spread thinly enough through a day that none of them is ever big enough to complain about, which is exactly why it survives.
This is the plainest sentence in the whole series, and the one people repeat back most accurately. Your people are the wiring.
Are your people deciding badly, or deciding on half a picture?
Almost always the second, and the difference matters because the two have completely different fixes.
Attention is finite. If most of somebody’s attention goes on gathering, what is left is what they have available for judging. A quote gets priced on the two facts that were reachable in the time available rather than the five that mattered. A job gets scheduled without the one piece of information that would have changed the order.
Nobody involved is deciding badly. They are deciding on the fragment they had time to assemble, which is a different problem and responds to different treatment. Training does not fix it. Neither does hiring somebody more senior, who will simply assemble a slightly better fragment.
Change the ratio of gathering to judging and the quality of decisions rises without anybody getting smarter. That is not a soft benefit. It shows up as fewer reworks, better quotes and earlier interventions, all of which are margin.
Why do juniors stop getting better?
Because judgement is built by seeing many cases with feedback, and carrying work reduces the number of cases anybody sees.
Watch what a junior person actually does in a day of moving information between screens. They see the field. They do not see the pattern. Six months of that produces somebody who is fast at the screens and no closer to being able to decide anything, because the raw material of judgement never reached them.
The same thing happens at the other end of the seniority scale. A senior person spending the day chasing sees fewer decisions than they would otherwise have made, so the sharpest people in a business get slowly less sharp at exactly the thing they are paid for.
The consequence is not a training problem, it is a supply problem. A business in this shape stops manufacturing capability internally and has to buy it in, which is expensive and slow and puts the business at the mercy of a labour market it does not control.
What is actually left when the carrying goes?
The work that needed a person, and the honest position is that this is the part of the series I can reason about but cannot yet prove.
The reasoning is straightforward enough. Most roles are a mixture of judgement and carrying. Take away the carrying and the proportion of the role that genuinely requires a human being goes up. The job gets harder in the way people actually want jobs to be harder, and roles like that change who applies and who stays.
What I can point at is narrower than that claim. On the Medeq field service work, the decision that has drawn the strongest response from technicians in the rollout is the one that let them do the whole job from a phone on a hospital floor rather than fighting a desktop app designed for somewhere else. That is people preferring a job with less friction in it, which is real and is not the same as the larger claim.
So take this section as reasoning rather than as evidence. The rest of the series stands on work you can go and look at; this part does not yet, and saying so seems better than implying otherwise.
If the people are the wiring, what is the software holding?
Records. That is genuinely what it is for and it does it well.
What it is not holding is the reason anybody buys from this business rather than the one down the road. That sits somewhere else entirely, and where it sits is the next chapter.