Ninety Seconds of Truth: Why Your Next Handover Needs a Screen Recording, Not a Wiki Page

Every UK team has one. A wiki page called something like “Payments Reconciliation — Onboarding (v4 FINAL)”. It was written during an audit, updated once by someone who has since left, and now sits in a folder next to a document called “Read Me First” that nobody has read first. The process it describes has changed twice. The page has not.

Meanwhile, the actual handover happens in ninety seconds at someone’s desk: “You click here, ignore that warning, export this, then paste it into the other thing. If it fails, ask Michelle.” That is not a failure of documentation. It is a failure of format.

The wiki is a write-only memory

Most process wikis are written for the person who already knows the process. They are comprehensive, cautious and structured like a manual for a machine that does not exist. They list every field, every permission and every exception, in alphabetical order. They are, in other words, a novel. And nobody reads a novel when they need to know which button to press before the 10am stand-up.

The problem is not that teams are lazy. It is that a wiki page is a reference document, while a handover is a performance. People do not learn a workflow by reading about it. They learn it by watching someone do it, then doing it themselves while someone watches. The wiki skips both steps.

What a process reel actually is

A process reel is a screen recording, ninety seconds long, with a named narrator. It is not a polished tutorial. There is no intro music, no animated logo, no “welcome back to my channel”. It starts at the trigger and ends at the point where the work leaves your hands.

It covers four beats:

1. The trigger — what kicks the process off. An email, a ticket, a Tuesday.
2. The normal path — the clicks that work 80% of the time.
3. The exceptions — the weird export, the field that must stay blank, the tab that lies.
4. The escalation point — who to ask when it goes wrong, and what “wrong” looks like.

That is it. Ninety seconds forces you to choose. If you cannot fit it into ninety seconds, you either have three processes or one process with a problem.

Why the time limit is the feature

A twelve-minute screen recording is a wiki page with a play button. It will be skipped, bookmarked and forgotten. Ninety seconds is shorter than a tea round. It fits in a Teams message. Someone will actually watch it because the cost of not watching it is higher than the cost of watching it.

The limit also forces the narrator to be honest. You cannot hide a messy workaround behind three paragraphs of context. You have to show the actual path, including the bit where you copy a reference number into a spreadsheet called “DO NOT DELETE”. That is the bit the next person needs.

The named narrator beats the version number

A wiki page says “last updated 2024”. A process reel says “recorded by Priya, 11 November 2026”. One is a date. The other is a person who can be asked a question.

Naming the narrator does two things. It gives the viewer a route to the human behind the process, and it gives the narrator a reason to keep the reel current. When the workflow changes, Priya re-records it or nominates someone else. The reel is not an anonymous artefact; it is a handover with a return address.

This matters more as AI assistants get involved. An AI can summarise a wiki page, but it cannot own the exceptions. A named human can. The reel gives the assistant something to work with — a transcript, a sequence, a real path — while keeping a person accountable for the judgement calls.

The silent run: how to test a reel before you trust it

Do not test a process reel by watching it yourself. You already know the process. Test it by asking someone else to run the workflow using only the reel, without asking you questions.

If they pause, rewind, or say “what’s that tab?”, the reel has failed. Not because they are slow, but because the reel skipped something. The silent run is the only quality check that matters, and it costs less than a coffee. Do it before the person leaves, not after. A reel that has never been run by a second person is just a wiki page with a play button.

Making one without turning it into a production

You do not need a studio. You need a screen recorder and the discipline to stop at ninety seconds.

• Open the workflow tool at the starting point.
• Hit record. Loom, Teams, QuickTime, Snipping Tool — whatever is already on the machine.
• Narrate the four beats. Do not script it. One take is fine.
• Trim the first and last five seconds. That is the whole edit.
• Name the file with the workflow, the date and the narrator: payments-reconciliation_2026-11-11_priya.mp4.

The first one will feel awkward. The second one will take four minutes. By the fifth, someone will ask why you are still writing wiki pages.

Where to store it (not the wiki graveyard)

A reel stored in a folder called “Videos” is a reel that will never be found. Store it next to the work. Link it in the tool’s description, pin it in the team channel, stick a QR code on the physical checklist if you still have one. Keep a lightweight index in SharePoint or Notion with four columns: workflow, narrator, date, link. Add a fifth column for “last silent run” and watch how quickly it becomes the most useful page on the site.

The wiki can stay. It is good for policy, definitions and the stuff an auditor wants. But it is not a handover. A handover is a person showing another person how the work actually gets done.

The objection: “we don’t have time”

You do not have time not to. The average “quick question” about a workflow costs more than ninety seconds. Multiply it by the number of people who ask it, add the delay while the expert is in a meeting, and the wiki page starts to look expensive.

Start with one workflow that is changing hands this month. Record it. Run the silent test. Put it where the work happens. Then ask the next person who joins how long it took them to get up to speed. If the answer is “about ninety seconds”, you have found a better standard than another page nobody reads.