At Mallard, we started four new engagements this month.
That means four consultants, four founder-led businesses and four people who had days rather than weeks to work out how each business actually runs.
One of those four clients made it easy.
That client has a comprehensive handbook (or wiki, knowledge repo or intranet – I don’t really mind what you call it). It’s open to all staff and covers far more than employment policy stuff.
It sets out how work actually gets done. It tells people what’s expected from each role. It shows the workflows people follow, the checklists they use and the tools they’re supposed to be in. Our consultant read it and knew where to start.
The other three didn’t have anything like it.
Our consultants working with those clients had to build the picture the hard way, through interviews, shadowing and a lot of diving into “who actually owns this.”
It’s worth remembering that a slow start for a consultant is a slow start for every new hire. Except new hires don’t do this for a living so aren’t used to discovering how things work at pace.
That contrast isn’t really about consulting or the Mallard team. It’s about what happens every time someone new joins one of those businesses – which is pretty frequent in scaling businesses.
This is what usually happens. A new hire walks into the same gap our consultants did. Nobody hands them a document that explains how the business actually operates day to day. They ask around. They guess. They shadow whoever seems to know and they hope what they picked up is accurate.
If they’re lucky they get a pretty good idea from that about what they should do in their work. But even that version loses fidelity every time the message gets passed on. Or if they’re unlucky they’ll become overwhelmed with the uncertainty of what they need to do, often leading to an early resignation.
Founders often treat this as a normal cost of onboarding, but for us at Mallard it’s a sign that the knowledge of how the business runs lives in people’s heads rather than in the business itself. That’s fine while those people stay. It’s a real problem the moment they don’t.
Capturing it on the way out is already too late
Most businesses that do try to fix this get the timing wrong. They wait until someone resigns, then scramble for a handover document in their final two weeks.
That document only ever captures what’s still in that person’s head at the point they’re already leaving – when they’re distracted and mentally somewhere else. Half of what made them good at the job never makes it onto the page, because they’ve stopped thinking about how they do things and started thinking about what comes next.
Institutional memory built this way is always incomplete because it’s being captured at the worst possible moment.
The businesses that get this right treat documentation as a live practice, not an offboarding task.
People write down how they work while they’re still doing the work, not as they’re walking out the door. We like to call this “working out loud”.
That documentation gets checked, used and updated as part of the normal rhythm of the business. It’s not filed away and forgotten until the next departure forces someone to open it again.
Build the habit, not the wiki
The instinct, once a founder sees this gap, is to commission a big documentation project.
A wiki gets built, a weekend gets spent writing everything down and six months later half of it is wrong because no-one thought how to keep it current.
The fix is a cadence, not a project.
Documentation needs to be part of how work actually gets done, reviewed at the same rhythm as the work itself, owned by whoever does the job rather than handed to someone else to write up after the fact.
For us at Mallard that’s a practices question as much as a tools question. The handbook we saw this month works because updating it is baked into how that business operates, not because someone found the right software.
Ask yourself how long it would take someone new, a hire or a consultant, to work out how your business actually runs without asking you a single question.
If the honest answer is weeks, the knowledge that keeps your business running isn’t in the business, it’s in your head, and in the heads of a handful of people who happen to still be there. That’s a business scaling risk you need to fix.
First published in Below the Waterline on LinkedIn (opens in a new tab).
Contact us