What happens the day Mary resigns?

What happens the day Mary resigns?

Codegenix East Africa1 min read

Every business has a Mary.

She’s the one who knows which supplier to call, what the real price is for that awkward job, why that client gets a discount, and where the spreadsheet lives that ties it all together. Ask anyone a hard question and the answer is “ask Mary.”

Mary is brilliant. Mary is also a single point of failure.

The knowledge that isn’t written down

The dangerous thing isn’t that Mary is busy. It’s that a huge amount of how your business runs exists only in her head:

  • The steps a job goes through that aren’t written anywhere.
  • The prices and terms that live in her memory, not a system.
  • The client history that’s in her WhatsApp, not your business.

None of that is a problem — until the day she’s off sick, goes on leave, or resigns. Then it stops being a staffing question and becomes an existential one. That’s not a gap in your rota. That’s your business walking out of the door.

Systems don’t replace Mary — they protect her work

This isn’t about making Mary redundant. The best Marys become even more valuable when their knowledge is captured, because they stop being a bottleneck and start being a leader.

A good system writes down what only she knew:

  • The workflow becomes explicit — the stages, the approvals, the rules.
  • The prices and terms live in the software, not a memory.
  • Every client’s history is in one place the whole team can see.

The test

Here’s the question we ask every business owner: if your Mary didn’t come in tomorrow, could the rest of you keep the business running?

If the honest answer is no, the fix isn’t to hope she never leaves. It’s to get what she knows out of her head and into a system — so the business knows what only she used to know. That’s a lot of what we build for clients, and it’s usually the first thing worth doing.

Tags:#systems#risk#sops

Want to learn more?

A software studio, forged in production.

Contact us →