The handover is the product
A site is only finished when the people who run it can change it without calling us.
Digital
·
·
4 min read

Malik Darrow
Digital
Malik builds what the studio designs, and stays until the client’s own team can change it without him.
Most of our digital work ends in a meeting nobody photographs: the afternoon we hand the site over. There’s no launch party and no big reveal. Just a table, a laptop, the two or three people who will look after the site from now on, and a list of things they want to be able to do on their own.
It’s the part clients remember longest. A homepage gets admired for a week. The handover decides whether the next two years feel easy or expensive, so we design it as carefully as anything the public will see.
Built to be edited
Every page we build is made from parts, and every part has a job. A hero, a project card, a quote with a face, a row of numbers. Each one can be moved, repeated or removed without anything else on the page falling over. That sounds obvious, and it’s still the most common thing we fix when a client comes to us with a site somebody else made.
The test we use is simple: could someone who has never opened the tool change this in an afternoon? If the answer is “only if they’re careful”, the part isn’t finished. We would rather spend another day on a component than leave a client one wrong click away from a broken page.
So text lives in text fields, not inside pictures. Colours come from a palette with names, not from hex codes typed into forty places. A section that only works with exactly three items is redesigned until it works with two or five, because sooner or later there will be two or five.
Before the handover we fill every part with the worst content we can find. The longest product name in the catalogue. A team member with a double-barrelled surname. A photo shot on a phone in a dark warehouse. If the layout holds with those, it will hold with anything the client throws at it on a busy Monday.
Names a marketing team would use
Developers tend to name things after how they’re built. Card, wrapper, container, variant two. That’s fine until the person editing the site is a marketing manager on a Friday afternoon, looking for the box with the quote in it.
We name every part after what it’s for. “Project card”, “Team quote”, “Opening times”. If a part needs a manual, we redesign the part instead of writing the manual. It takes longer on our side and saves hours on theirs, every week, for as long as the site is live.
If a part needs a manual, we redesign the part instead of writing the manual.

The afternoon itself
We book half a day, in person if we can. The client brings the people who will actually do the editing, not just the people who signed off the budget. Those are rarely the same people, and the ones doing the work are the ones we need in the room.
Then we stop talking. Someone from the client’s team changes a headline, swaps a photo, adds a new project and publishes it, while we watch with our hands in our pockets. Every time they hesitate, we write it down. Every hesitation is a small design flaw, and we fix it that week rather than explaining it away.
The first time we ran a handover like this, it was uncomfortable for everyone. Now it’s the meeting clients look forward to, because they leave it knowing the site is theirs. They’ve already changed it, published it and seen nothing break.
A month later we come back for an hour. By then the team has used the site for real, under deadline, without us. We ask them to show us the thing that annoyed them most, and we fix it. It is almost always something we couldn’t have predicted from our side of the table, and it is almost always small.
What we leave behind
A handover pack is short on purpose. Nobody reads a forty-page guide, and a guide that long is usually a sign the site is too complicated. Ours fits on a single screen:
A two-minute film for each part of the site, recorded with real content, showing the three things people most often change.
One page that lists what not to touch, and why, in plain words.
The fonts, images and licences, in one folder, with the dates the licences renew.
A phone number, and a promise that we’ll answer it.
The number rarely rings. When it does, it’s usually good news: a new product, a new page, a team that has grown into the site and wants it to do more. That’s the call we want, not the one about a menu that disappeared.
The best compliment we get after a launch is silence. It means the people who run the site are busy running it, and they don’t need us to do it for them.
Next note
Why we draw a logo by hand before it goes near a screen, and what tracing paper still does better than any vector tool.

