
The week before I moved from a platform team to a product team, my manager asked a simple question: “If you were hit by a bus, who could deploy your service?” I laughed. Then I realised the honest answer was nobody. I had run that service for two years, and everything about it lived in my head and my shell history. What follows is the step-by-step way I handed it over, told as I did it. If you are about to change roles, finish a contract or simply take a long holiday, this is a plain method for passing on a service so that the next person can pick it up on their first morning.
Step 1: Pick the date and the person
I started by fixing two things: the day my responsibility would officially end, and the name of the person taking over. A handover with no date drifts, and one with no named recipient lands on a team alias where everyone assumes somebody else will read it. My manager and I agreed on a date three weeks away and a colleague who had only worked on the edges of the service. That distance turned out to be useful, because she asked the naive questions I had long stopped asking myself.
Step 2: Write down what is finished
With an empty document in front of me, I began by listing what genuinely worked: the deployment pipeline, the staging environment, the health checks, the nightly clean-up job. Beside each item I put one line explaining how to see it working. For the pipeline, it was a link to the last green run; for the health checks, the page where they show up. This section took twenty minutes and felt almost too easy, which is why I did it first.
Step 3: Write down what is not finished
This was the uncomfortable one. I had a half-migrated configuration, a monitoring rule I had meant to tighten, and a pull request open for six weeks. I wrote each down with its state and the next step. Two items turned out to be things I could finish that week, so I did. The rest went into the note under a heading that said, plainly, “unfinished, in this order of importance”. Naming them out loud took the shame out of them.
Step 4: Map where everything is kept
Next came the locations: code repositories, the cloud accounts, the secrets vault, the scheduler, the shared drive with old design notes. I did not copy any passwords into the document, only where they live and when they next expire. While doing this I found a certificate that would lapse in five weeks. If I had not been writing a handover, it would have lapsed on my replacement’s second week, in the middle of the night.
Step 5: Collect the oddities
Every service has habits, and I had learned most of mine the hard way. The restart that needs a ten-minute pause between nodes. The report that arrives thin when a new month starts. The alert that fires on Sundays and means nothing. I put them all under one heading and kept the tone chatty, because a friendly note gets read. Newer engineers sometimes doubt that such details count, yet the stories in our account of the path from a first DevOps job to a senior one show how often seniority is simply the accumulated memory of oddities like these.
Step 6: Name the people
I listed who knew what: who owned the database, who understood the billing export, who approved production changes, who to call about the vendor. Next to each I wrote what they were good for. I also wrote my own line: I would answer questions for a month, through chat, within a working day. Setting that limit was kind to both of us.
Step 7: Sit down and read it together
I booked an hour with my colleague and watched her read the whole note. She stopped at four places. I had not said which cloud account held staging. I had used a nickname for the database. I had assumed she knew how to get into the vault. And I had never explained why the clean-up job ran at that odd hour. I fixed each on the spot. Those four fixes were worth more than all the writing before them, because they came from the reader rather than from my guesses.
Step 8: Let her do the risky things while I watch
Reading is not doing. On day two we sat together and she deployed a small change, rolled it back and rotated a credential. I kept my hands off the keyboard. She got stuck on the rollback because a permission was missing, which we sorted out that afternoon rather than during an incident. It is a lot easier to discover a missing permission when someone is sitting next to you with coffee than at three in the morning on your own.
Step 9: Tidy the access, both ways
On my final day we went through accounts together. She received everything she needed, and my own elevated rights were reduced, with a date in the note. I also removed a few personal tokens I had been using for convenience. It felt a little like clearing out a desk, and it left nothing hanging.
Step 10: Say goodbye properly and keep the door ajar
I sent a short message to the wider team saying who now owned the service, where the note lived and how long I would answer questions. Nothing more. In the weeks afterwards she asked me three things, I answered each in minutes, and by the fourth week the questions stopped.
Looking back, the process took about two working days spread over three weeks, which is a small price compared with the hours of rediscovery that would otherwise have landed on someone else. If you want a sense of how far this habit can carry a person, our roadmap of the skills and projects that move a DevOps engineer forward lists many technical milestones, but the quiet ones, like leaving a service in good order, tend to make the biggest difference to how colleagues see you.
A thought for people who work on short engagements
Some of us never change teams at all; we simply move from client to client. For those who work that way, step ten arrives every few weeks. A directory such as DevOps FreeLancers, which presents DevOps freelancers country by country, serves people looking for exactly that kind of short, defined engagement, and it is a good reminder that the person who leaves cleanly is the person who gets called back.
A tiny version if you only have an hour
Not every handover gets three weeks. If you have one hour, do steps two to four in note form, name two people to ask, and arrange a ten-minute call so the reader can ask whatever the page leaves out. It is not perfect, but it is miles better than a folder and a wave goodbye. The next time you move on, you will wish you had started sooner, so begin the note today, even if the date is far away.