The handoff

Hi, it's Nora.

Saturday I made the case for putting ninety minutes of rest on the calendar. A few of you wrote back with a version of the same objection, which is that it's not the time that's the problem. It's that things stop when you stop.

That's a real constraint and it deserves a real answer, so that's today. Last issue of September, and it's the one that unlocks most of the others.

Here's the situation. There are somewhere between three and eight things in your life that only you know how to do. The report that pulls from four places in a specific order. The client who only talks to you. The way the school portal actually works. Where the insurance documents live and when the renewal hits.

Being the only one who knows feels like security. For a long time I thought it was. It reads as importance, and there's a genuine satisfaction in being the person things route through.

But look at what it actually gets you. You can't be off. You can't be ill without a cost being paid somewhere. You can't take the better project, because you're holding this one. And here's the part that took me too long to understand: you cannot be given anything larger while you're the load bearing wall for something smaller. Indispensable at one level is a ceiling, not a floor.

So this is about dismantling that on purpose, and it takes about two hours spread over a month.

Twenty minutes. Go through the last month, work and home, and write down everything that happened that only you could have done.

Be strict about "only." Not things you're best at, not things you prefer to do, not things it's faster for you to handle. Things that would genuinely not have happened, or would have gone badly wrong, in your absence.

The list is usually shorter than people fear and more alarming than they expect. Most people land on five or six, and at least two of them are things they'd never thought about, usually at home, usually involving a login.

Then rank them by one question: if this broke while I was away for two weeks, how bad is it? Start at the top.

Every item gets one, same principle as the calendar audit a few weeks back.

Document it. For things that happen rarely and don't need skill, just knowledge. The annual renewal. The quarterly report. Nobody needs to be trained, somebody needs a page to follow.

Train someone. For things that happen often and do need judgment. Costs real time up front and it's the only verdict that genuinely transfers the load.

Automate it. For anything that is genuinely the same steps every time. Recurring payments, scheduled reports, renewals on autopay with a calendar reminder. If a task has no judgment in it, it should not require a human to remember it.

Stop doing it. Always ask this one before the other three, because the cheapest thing to hand over is a thing nobody actually needs. There is usually one item on the list that exists only because it always has, and documenting it would be a waste of a good afternoon.

Here's the format. One page, six headings, and the fifth is the one that matters.

What this is for. One sentence on why it exists. People do a task badly when they don't know its purpose, because they can't tell which parts are essential and which are habit.

When it happens. The trigger. A date, or an event, or a signal. "First Monday of the month." "When the client sends the file." "When the balance drops below a thousand."

The steps. Numbered, plain, in order. Assume no context. Write it for a competent person who has never seen it, because that's exactly who will be reading it.

Where things live. Files, logins, the shared folder, the person who has the password. This is the section that turns a document from interesting to usable.

The traps. Everything you only know from having done it wrong. The system times out after fifteen minutes and loses your work. The form says Friday but the office needs it Thursday. This number always looks wrong in month one and it's fine.

This section is the entire value of the document. Anyone can reconstruct steps. Nobody can reconstruct three years of small painful surprises, and the traps are what make a handover succeed instead of technically succeed while going quietly wrong for two months.

Who to call. When it breaks and the page doesn't cover it. A name, not a department.

One page. If it's running to four, the task is too big and should be split.

The reason most people have no documentation isn't laziness, it's that documenting is treated as a separate project, and a separate project needs a free afternoon, and there are no free afternoons.

So don't do it as a project. The next time the thing comes around, do it with a blank document open beside you and write the steps as you take them. It adds maybe fifteen percent to a task you were doing anyway, and it produces something accurate, because you're describing what actually happens rather than what you remember happening.

Documentation written from memory is always wrong in the same way. It skips the three small steps you do automatically, which are invariably the three steps the next person gets stuck on.

One task per month, written while doing it. In a year you've handled twelve, which is more than the list.

For the ones that need a person rather than a page, there's a sequence, and skipping stages is why handovers fail.

They watch you do it. Once. Narrate what you're doing and why, especially the judgment calls.

You do it together. They drive, you're next to them. They'll be slow. Let them be slow.

They do it, you watch. This is the stage everyone skips and it's the one that matters. You're present, you're not touching anything, and you only speak if something is about to genuinely break. Sitting on your hands here is uncomfortable and it's the whole exercise.

They do it alone and tell you it's done. Then, after two or three clean rounds, they stop telling you.

Four rounds. Roughly three or four times the time it would have taken you to just do it, and then never again.

That ratio is exactly why nobody does it. In any given week, doing it yourself is faster, and that's true every single week, which is how people spend four years being the only one who knows.

You take it back.

Something goes wrong in week three, and it's easier to just fix it, and then easier to just handle the next one, and inside a month it's yours again and now you've also taught the other person that they can't do it. That's worse than never handing it over, because you've spent the training time and bought nothing.

Two protections. Agree in advance what actually justifies you stepping back in, and make it a high bar, something like a real financial consequence or an external deadline missed. Everything below that bar is theirs to handle imperfectly.

And accept that they'll do it differently. If you hand over the task but keep the standard, you haven't handed over anything, you've appointed yourself as quality control. Same as the domains at home a couple of weeks ago. Name the floor, then leave the rest alone.

This is the one I'd actually prioritize, and almost nobody has it.

One document, one place, that another adult in your house could open and use if you were unreachable for two weeks. Not morbid, just practical, and the two week version is the realistic one.

What goes in it: where the important accounts are and how to get into them, ideally through a shared password manager rather than a list. What bills go out and when and from where. The insurance policies and their renewal dates. School logins and who the contacts are. The mortgage or landlord details. Anything with an annual renewal that would quietly lapse.

An hour. One evening. Tell one other person where it is, which is the step that makes the whole thing worth anything.

And if you're the person in your house who doesn't know any of this, this is the ask to make this week. Not "show me everything." Just: "walk me through the four things I'd need if you were away for a fortnight."

There's a fear underneath all of this that's worth saying out loud, because pretending it isn't there doesn't help anyone.

If everyone can do what I do, what am I for.

Here's the answer as best I can put it. Your value was never the fact that nobody else knew. That's not a skill, that's an accident of information. Your value is that you can do the thing well and, more to the point, that you can build something that keeps running without you standing next to it. The people who get given more are consistently the ones who hand things off cleanly, because handing off cleanly is the visible evidence that you could hold something bigger.

The version where you hoard it is a job you can never leave and never grow out of. It looks like security right up until the moment you want to do anything else.

Twenty minutes to list the things only you can do. Pick the top one. Next time it comes around, write the page while you do it.

And if you do only one thing from this whole issue, do the home document. It's the one with the highest cost of not existing and the lowest cost of existing.

That's September. October opens on Saturday and I'll see you then.

Better, not busier.

Nora Bishop

P.S. Handing things off is what makes the last stretch of the year survivable. If you haven't picked up The Last 90 Days yet, it's free and it's built for exactly the nine weeks in front of you. The underlying systems are all in Better, Not Busier, and if you'd rather start with something you can do tonight, the default setting is where I'd send you.