Below the Waterline · Issue 2

Just enough process to make the wheels turn.

Process is organisational memory, not bureaucracy. Why Mallard never maps every process – and the short list founders should write down instead.

By Simon Wakeman, Principal Consultant & Fractional COO
· 4 minute read

Almost every founder-led business the Mallard team walks into during a Find diagnostic has the same gap. No one can tell us how the work actually gets done. They can only show us who does it.

In business operating system terms, that’s an organisational memory problem. It’s the reason founders end up firefighting long after they thought they’d hired people to find their way out of it.

Process is organisational memory not bureaucracy

Process gets a bad name because most people think it means red tape. It doesn’t. Process is what’s left after someone in the business has already made the mistake, felt the pain and worked out a better way.

In the early days that knowledge lives in the founder’s head and in the heads of whoever was working there when things went wrong. Every founder-led business runs on this for a while. It works because the team is small enough that intuition travels by osmosis, from sitting next to someone and watching a call or overhearing a decision get made.

That works right up until the point when it doesn’t.

New people join and have no access to any of that prior knowledge. They either shadow someone for weeks, guess or quietly reconstruct how things are supposed to work by trial and error. That usually means repeating the exact mistakes the business already paid to learn from.

In the worst cases that’s then misdiagnosed as a bad hire. In fact we usually see it as an institutional memory problem. It caps how fast you can bring people in and get them contributing at full strength.

The trap of mapping every process

The usual instinct, once a founder spots this gap, is to fix it properly. Get everything down. Map every workflow, every handoff, every decision point, so nothing is ever again only in someone’s head.

At Mallard we understand the instinct. But we don’t think it’s the right one.

Full process mapping is a huge amount of effort for the return you’ll get. You’ll usually end up with a load of lists or flowcharts that sit on a shared drive nobody opens.

It’s so long winded that the business has usually changed shape by the time the mapping is finished. And it quietly kills the thing that made the business work in the first place, which is people using their judgement to solve problems that don’t fit a template.

Don’t think you can map everything and you have built an operating system. All you’ve done is built an organisational straightjacket that will stifle the entrepreneurialism out of your business.

Why Mallard never maps every process on an engagement

Here’s the bit that tends to surprise founders when we say it out loud. We have never done full process mapping on any client engagement. Not once, not for any client, regardless of size.

What we do instead is work out which handful of things that if they broke tomorrow would actually cost the business money, time or a customer relationship. Usually there are four or five things that happen that really make a difference – things like onboarding a new client, handling an operational escalation, approving spend above a certain threshold or how decisions get made.

These are the real moments where inconsistency is genuinely expensive.

Those are the only places that get a written process and even then it’s built around a principle rather than a script. Not “step one, step two, step three, no deviation,” but “here’s what good looks like, here’s the two or three things that must always happen, use your judgement for the rest.” That’s the difference between organisational scaffolding and an organisational straightjacket.

Everything outside that short list stays exactly as flexible and judgement led as it was on day one. That gives the business the space to move fast, pivot and flex when the need arises.

The practical shift

If you’re the founder still getting pulled into decisions you thought you’d delegated, please don’t reach for a process mapping exercise. Reach for a much shorter list first.

Write down the four or five moments in your business where getting it wrong genuinely costs you something real. Not “how we do things” – just focus on the handful of points where inconsistency has an actual cost. For each one write down the two or three things that must always happen in plain language, in under half a page. Leave everything else alone.

You’ll find most of what you thought needed documenting doesn’t. You’ll see it needs people with good judgement and clarity on your expectations about how things are done.

Ask yourself what’s currently sitting only in your head or in one other person’s head that would genuinely hurt the business if that person took two weeks off with no contact.

That’s your list. Nothing else needs writing down yet.

First published in Below the Waterline on LinkedIn (opens in a new tab).

Stop being a bottleneck in your own business

Book your free 30 minute
founder review call