The work that lives only in your hands
A Wednesday push for the job that only your hands know how to do: why every version of it keeps coming back to you, and the twenty-five minutes today that put its steps on a page.
Twice this week, somebody has asked you how one of your jobs gets done. Both times you did it yourself, and both times that was the faster route: twenty minutes of your own hands against an hour of talking somebody through it.
The whole of that task sits in your hands. You learned it by doing it — the order the steps go in, the fiddly part halfway, the shortcut that saves an hour, the one that costs you a day. The page it was supposed to be written on is still empty, so the job travels wherever you go.
The job that waits for you
The requests all point at the same place. A colleague wants the number by eleven, a client wants the wording changed, the file is due Thursday, and every one of them lands on your pair of hands.
Read from the outside, this looks like being needed, and some of it is. It also means the work sits still the moment you step away: a day off, a child home sick, a flight, and the job holds its place exactly as you left it. You come back on Wednesday and the schedule has been waiting for you since Monday.
The handover spends the same hours again. Ask somebody to cover the task while you are away, and they start with the folder and the client's name, and the rest arrives step by step over the phone. The hour a written page would have saved gets spent saying the steps out loud.
Twenty-five minutes with the steps on paper
Take the task you have done most this week. Give it twenty-five minutes at your own desk today, and write the steps the way you would say them out loud to the person taking the job over. The first line says what finished looks like; the lines under it are your moves, in the order you make them.
Use plain words: the folder name, the number to ring, the check you run before the file goes out. Five to twelve lines hold most jobs. Write them in your own phrasing rather than the tidied version, because the steps you can hand over are the steps you can say in a sentence.
Part of the job is judgement, and that part stays with you: what the client actually needs, when the price moves, which detail is worth arguing about. Listing those lines separately is half the value of the exercise, because the steps can travel and the judgement is what you are paid for.
Writing the page can feel like an argument for giving the job away. What usually follows is the reverse: whoever holds the page decides who runs the task, and the week it runs on somebody else's hours is the week your own work gets a morning.
Where the page goes when it is done
Put the page where the work already lives: the project folder, the shared drive, the one place you open first. A copy kept in a private folder helps one person.
Then send it along the next time the question arrives. The first run through the page comes back rough, with two questions and a line that turns out wrong, and that call is the edit. The second run asks less of you.
Some of the job will keep coming to your hands for years: the taste, the read on the client, the call about the price. The page carries the steps, which is the part other hands can hold.
The task I have done most this week: ___ The steps, in the words I would say them out loud: ___ Where the page goes, and who reads it first: ___
Write it this morning, while your hands still know the order. Then the job can spend a day away from your desk and come back to a week that kept moving.
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.