Marguerite had run the orders desk of a small online homeware shop for four years, and on a Thursday in early spring she told the owner she was moving cities. The team’s first reaction was congratulations. Their second, a few minutes later, was a quiet look around the table. Everyone realised that most of what kept the shop running was stored inside one person’s head. This story, with invented names and a made-up shop, follows what the team did in her last two weeks, and what a clean handover at work can look like when nobody has a spare afternoon.
The week the cracks showed
The owner, Tobias, asked a simple question: “If Marguerite were unreachable tomorrow, what would break first?” Nobody answered quickly, and that was the answer. The courier account was in her name. The supplier who shipped the ceramic lines only replied to her. The refund rules existed as habits, not as paragraphs. A spreadsheet called “orders_FINAL_v3” fed the monthly accounts, and only she knew why one column was always blank on the first of the month.
Dev, the newest hire, was due to take over the desk. He was keen and slightly terrified. Tobias made a decision that turned out to be the best of the year: the handover would not be a farewell lunch with a shared folder. It would be a small project with an end date, an owner and a definition of done.
Day one: agree what “done” means
Marguerite and Dev sat down for twenty minutes and wrote a single sentence on a whiteboard: “By Friday week, Dev can run a normal day and a bad day without calling Marguerite.” Everything else hung off that line. It kept the work honest, because a task either helped Dev handle a bad day or it did not make the list.
They then split the job into the four things a successor wants to know, a framing Marguerite borrowed from a friend who worked in operations:
- What is finished and can be left alone.
- What is half-done and needs a decision.
- Where everything is kept, including the awkward bits.
- What to watch for in the coming weeks.
Days two to four: writing down what felt obvious
Marguerite’s first draft was five lines long, and she was proud of how brief it was. Dev read it and asked nine questions. That exchange became the real document. Whenever he asked something, she answered it in writing, in the note, rather than out loud. By Wednesday the note had grown into something useful without ever becoming a monster.
Under finished she listed the autumn returns clean-up, the new packaging supplier and the shipping-rate review, each with a one-line outcome and the location of the supporting file.
Under half-done she was candid. The loyalty-card idea had been trialled and stalled because the till software could not support it. A complaint from a customer about a cracked bowl was still open, with the last email attached and a note that the customer had been polite and was waiting for a reply. A price change was drafted but not approved. She wrote what she would do next in each case, and flagged which choices belonged to Tobias.
Under where things are kept she drew a rough map: the shared drive layout, which inbox received supplier notices, where the courier labels were generated and who actually held the login. That last item turned out to be an awkward discovery. The courier account sat under her personal email, and moving it took three days of waiting for a verification step. Better to find that out in week one than on her last evening.
Under watch for she wrote the quirks: the supplier who goes quiet around their own holiday season, the postcode that always trips the shipping calculator, and the customer who orders twice because the confirmation email lands in spam.
The walk-through that changed the note
On Thursday, Dev ran the desk for a morning while Marguerite sat beside him with her hands in her lap. She was forbidden to touch the keyboard. Within an hour he had hit three problems that nobody had foreseen: a refund that needed a manager’s code, a label printer that sulked, and a customer message whose tone made him freeze. After each, they stopped and added a line to the note.
This was the moment the team realised the document was not the point. The document was a by-product of a conversation that happened because there was a deadline. A note written alone, however neat, would have missed all three.
Borrowing ideas from the rest of the business
Tobias used the same fortnight to tidy other loose ends. He had been reading about how a small business can plan its digital growth in a sensible order, and an article on planning digital growth step by step reminded him that the shop’s website, inbox and payment tools were all part of one picture, which was exactly what the note needed to describe. Another read, about joining web, cloud and smart tools into one setup, nudged him to write down which online services the shop actually depended on and who owned each account.
The money side got attention too. A piece on spotting small spending leaks and protecting digital payments prompted Dev to ask which subscriptions renewed in the coming months and who received the receipts. Marguerite had never listed them; now they sat in a table at the end of the note.
When the helper is a freelancer, not a colleague
A few months later the shop needed help with a technical project: moving its website to a new host and tidying up how updates were deployed. Tobias hired an outside engineer for a few weeks. This time he asked for the handover plan up front. If you are in a similar position and wondering where to look for short-term technical help, DevOps FreeLancers sorts its listed DevOps freelancers by country, which suits brief engagements where a tidy exit counts for a lot. Whatever route you take, write the handover into the agreement in the first week, not the last.
What the team kept
After Marguerite left, the shop ran for six weeks without a single phone call to her, which was the original measure of success. Two things did go wrong. A seasonal supplier changed their ordering form, which nobody could have predicted, and Dev spent an evening working it out. But because the note named the supplier’s usual contact and the previous year’s order, he rebuilt the process in an hour instead of a day.
Tobias turned the note into a template. Every role in the shop now has a living one-pager with the same four headings, updated when something changes rather than when someone leaves. The first update was dull: a changed courier phone menu. The second saved a Saturday.
Five lessons from the story
- Define done before you start. A sentence on a whiteboard focused two people for two weeks.
- Let the receiver ask the questions. The best content came from Dev’s nine questions, not Marguerite’s confident five lines.
- Be honest about the half-finished. Dead ends are gifts. They cost the next person nothing to avoid.
- Check who really owns each account. Personal logins hide in every small business.
- Practise on a real morning. Watching beats reading every time.
Handover is rarely glamorous, and nobody ever celebrated a thorough one at a team party. Yet the shop’s smoothest spring in years came from a few pages of plain writing and a morning spent sitting on one’s hands. If someone you work with is about to move on, or you are, start the note today. It will never be easier to write than it is right now, while the details are still fresh and the person who knows them is still in the room.

