All Books
Cover of What the Masters Forget
The System Parables · Book 3 of 3

What the Masters Forget

Thirty-six parables on handing work on

by Baisil Geevarghese

Somebody on your team knows how a thing works and cannot explain it. When that person leaves, what they knew leaves with them, and writing it down beforehand almost never works. This book is about why.

This is a book about software teams, and what happens to the knowledge that only one person has.

Somebody on your team knows how a thing works and cannot explain it. A rule is followed that nobody can justify. A system has one name attached to it, and that person is on holiday. A new starter asks the question everybody stopped asking years ago. When that person leaves, what they knew leaves with them, and writing it down beforehand almost never works.

It is taught as a story. A village, a well, an old master who built most of it, and the people who come to him with problems. There is no code in it, no mathematics beyond arithmetic a baker does in her head, and no tool, company or product is named anywhere. The things that change are not the things worth teaching.

WHAT IT COVERS

Tacit knowledge and why expertise cannot explain itself. Decisions with no surviving reason, and how to read the marks older hands left. Removing what you do not understand. Single points of knowledge, the week the expert was ill, and handover done in an afternoon. Documentation, why it rots, why nobody opens it, and writing for somebody who is not you. Onboarding, the curse of knowledge, and the month a new person is worth nothing. Apprenticeship, the mistake you must let somebody make, pacing, and being corrected by your own pupil. Delegation, supervision without taking over, the standard you cannot describe, and two ways that both work. Legacy systems, fear as a design constraint, systems nobody owns, and rebuild against repair. Ownership, collective memory, and teaching people to teach.

WHAT IS IN EVERY CHAPTER

First the story. People get it wrong before they get it right, and the wrong answer is usually the one you would have given.

Then the name for what just happened.

Then it is explained plainly: what it is, why the trouble is built into the shape of it rather than caused by anyone being careless, what it costs, why the obvious fixes fail, and when you should not do any of it.

Then one real incident, followed from the first symptom to the fix, including the wrong turns and how long they took. Nobody in those accounts behaves stupidly. That is the point of including them.

Then a table of what each answer actually costs, because a strategy offered without its price is not advice.

Then a short list of things to go and look at in your own system this week. Every item is something you can come back from with an answer.

WHO IT IS FOR

If you are the only person who knows how something works, or you work next to somebody who is, this is the part nobody explained. It is for engineers, team leads and anyone who has inherited a system and a silence.

Nobody in it is at fault. The master is not withholding. He genuinely cannot see the step he skipped, because to him it is not a step. That is what mastery does, and it is the whole problem.

Seventy-two diagrams. They are drawings of mechanisms, not decoration.

You do not need to have read the first two books.

Also in The System Parables

About The System Parables