Three attempts at hiring an assistant, what was different about the one who stayed
Two assistants left inside three months. The third has been with me over two years. I did not get better at choosing people; I changed four things about how I set it up, and I am fairly confident it was the setup rather than the person.
What I did the first two times
Wrote a short list of tasks, hired the cheapest competent applicant, gave them logins, and answered questions as they came. Both times the first fortnight looked fine, both times it decayed into me checking everything, and both times they left before I got round to doing anything about it.
What was different the third time
1. I wrote the process down before hiring, not after. Not a job description - the actual steps. Where the files are, what a finished version looks like, what to do when something is ambiguous. This took two full days and it was the single biggest change. The first two hires were being asked to reconstruct my judgement from examples; that is a much harder job than the one I thought I was offering, and it is unrewarding to fail at.
2. I paid above the going rate on purpose. Not enormously. Enough that leaving for a slightly better offer was not automatic. The first two were priced as a cost to minimise, which meant every competitor was a raise.
3. Fixed hours rather than tasks-as-they-arrive. Same block, same days. This mattered more than I expected, because "available when needed" means someone cannot plan their week around you, and the ones who can't will find someone they can.
4. A weekly thirty minutes that is not about tasks. What was annoying, what was unclear, what did I ask for that turned out to be pointless. Most of the process improvements came out of this, and it is also the thing that surfaces someone drifting a month before they hand in notice.
The uncomfortable part
The reason the first two failed was that I had not decided what the work was. I was outsourcing the doing while keeping the deciding, then getting frustrated that the doing needed constant decisions. Writing the process down forced the decisions to happen once, in advance, which is the actual work and I had been avoiding it by hiring.
@wrote_it_down · 3w ago · 3 replies
The first point is the whole post and everyone who has been through this arrives at it eventually.
I would add the version that made it stick for me: write the process by doing the task and narrating it, not by remembering it. I tried to write mine from memory and produced something confident and wrong, because the fiddly parts are exactly the parts you have automated in your head and no longer notice.
Screen recording yourself doing the job once, then writing from the recording, produced a document about three times longer than my remembered version and every extra bit was a real step.
The other benefit nobody mentions: once it is written, the hire is genuinely replaceable, which sounds cold but is the thing that lets you stop worrying about them leaving. The two-year relationship became easier once it was no longer load-bearing.
Reply
Report
@was_the_assistant · 2w ago · 2 replies
From the other side of this, and the thing that made me stay in one job and leave another was neither pay nor hours: it was whether I could tell when I had done a good job.
At the one I left, work arrived, I did it, and it vanished. No feedback either way for weeks. You cannot improve against silence and you cannot feel competent in it, so you start looking.
Your written procedure probably fixed that by accident, because a procedure is also a standard.
Reply
Report
@wrote_it_down · 2w ago
That is a better reason for the procedure than the one I gave. I thought I was saving myself repetition.
Reply
Report