Observation 006
Part Of The Architecture
A rod hangs inside most hot water tanks, there to corrode, and even that rod needs to be specified, inspected and replaced on a schedule. The load one person carries for an organisation gets none of the three, and the praise for that person is an inspection finding nobody wrote up.
This piece discusses pressure, burnout and recovery. If any of it lands close to home, Resources lists support lines that answer at any hour.
Inside most hot water tanks hangs a rod the owner has never heard of. It is there to corrode. Water and steel together rust a tank from the inside, so the maker hangs a rod of a metal that corrodes first, at the join between the water and the steel, and the water works on the rod instead of the wall. Boat builders bolt the same block to the hull and the shaft, and the sea eats the block instead of the boat.
Nobody expects the rod to last. So even a part designed to be eaten needs three things. Someone specified it, the metal and the size, for the water it would sit in. Someone checks it at the service, before the tank needs it. Someone has the replacement planned before the old one is fitted.
Every organisation has a name for the person who holds it together. The rock. The glue. The one you can always count on. The praise is accurate. Read it the way a plumber reads a tank.
Two systems are documented as agreeing. They agree because one engineer pulls the exports every month and fixes by hand the records the two describe differently, and nobody has written down that she does. It works through her. She takes two weeks’ leave and the numbers stop matching, and nobody can say why. The join was never drawn.
The senior leader comes off the all-hands and calls their team. What they say is what happened upstairs, edited three ways: for what the team needs, for what they were told they can say, and for what they believe. The three do not agree. The leader holds the difference so that neither floor has to. Above and below each believe they are in contact with the other. Each is in contact with the join.
One parent sits between the school and the child, or between two homes, turning timetables, instructions and moods from one side into something the other can carry. The school believes the child is organised. The child believes the arrangement is reasonable. Both believe it simply works.
Nobody specified any of them for that load.
Nobody inspects the join.
Nobody has planned the handover.
Whatever a system cannot run without is part of its architecture, drawn or not.
When nobody fits the next rod, the corrosion does not stop. It moves to the shaft, the fittings, the tank wall. A new job, a promotion, two weeks’ leave, and the two parts that never fit meet directly: the numbers stop matching, the layers touch with nothing between them, the timetable arrives untranslated. Nothing about the person failed. The system had been running on a part it never drew.
Write the load down where the design lives, with the person who carries it in the room to describe it. Then change what keeps producing it. Fix the mapping that makes the engineer reconcile the exports. Resolve the conflicting instructions the leader keeps translating. Give both homes a timetable they can actually use. Some of the work will remain. Give it time, cover and a handover someone else has practised.
“We could not do it without him” is not a compliment. It is an inspection finding nobody wrote up.
The question is: what in your system runs on a person nobody drew, and when was that join last inspected?
What this earned
Design the system, not the hero.
Test the claim
The claim is that whatever a system cannot run without is part of its architecture, drawn or not. The operator recovery guide is for the week after an incident, when the people who held the line are about to be called heroes and handed the next one.
Read next
Come back
One line when something new is added. No schedule, no newsletter, no marketing.
Or take the RSS feed instead: no address, no record of you.