Writing It Down Once

On a global payroll desk, every resolved case is a small piece of hard-won expertise — and most of it lives in one person's head. Which means the answer to the same question changes depending on who happens to pick up the ticket. In payroll, that isn't a quirk. It's a risk to someone's pay.

Tribal knowledge doesn't scale and doesn't survive. The most careful person on the team quietly becomes a single point of failure, and "just ask them" stops working the moment the queue grows or they're on leave. Meanwhile the same hard cases keep getting re-solved from scratch, a little differently each time.

I turned the recurring resolutions into written infrastructure: step-by-step SOPs for the cases that kept coming back, response macros for the explanations we gave over and over, and a searchable knowledge base that carried the diagnosis, the edge cases, and the exact fix. The bar I held it to was specific — could the newest person on the team resolve a case the way the most careful person would?

They could. The same question started getting the same correct answer no matter who caught it, and time-to-right-fix stopped depending on who was online. Writing it down did something quieter, too: it exposed the places where our "expertise" was really just habit, and forced us to decide what the right answer actually was. Heroics don't scale. Written-down judgment does.