The Bureaucracy Audit: Which of Your Processes Protect the Work, and Which Protect You
Last week we took apart the myths that keep leaders reachable at every hour, and found that most of them don't survive being examined. Beliefs are only half of the picture, though. The other half is what those beliefs build around you once they've been running for long enough: the sign-offs, review steps, standing meetings, and reporting lines that make up your working week. This week we turn from what's in your head to what's in your calendar, and to the parts of the organisation you may have written yourself.
It's Thursday afternoon, and a proposal is waiting for your approval. It's the fourth thing this week to sit in your queue. Your team drafted it, a peer reviewed it, finance checked the numbers, and now it needs your sign-off before it can move. You read it properly, because you always do. You change one word. You approve it. The whole thing took you forty minutes, and the proposal waited two days for those forty minutes. Nobody would call that step a problem. It's simply how things work here. But if someone asked you why the step exists, you might struggle to give an answer that has anything to do with the proposal.
How a Rule Becomes a Process
Every process started as a decision someone made for a reason. Many of the ones that route through you started as decisions you made, usually in a specific moment: a mistake that reached a client, a launch that went wrong, a board meeting where you were caught without an answer. You added a check, and the check worked. Then the moment passed, and the check stayed.
That's how an old rule becomes infrastructure. Earlier in the series we looked at the Origin Code, the set of implicit rules your nervous system wrote about safety, worth, and belonging long before you held a job title. A rule like that doesn't stay in your head once you have authority. It gets compiled into the organisation itself: into approval chains, review cycles, and meetings whose main purpose is that you see everything before anyone else does. At that point the rule no longer needs you to believe it. It runs on its own, every week, whether you're anxious or not.
Bureaucracy has a poor reputation, and much of it is deserved. But the useful question isn't whether your organisation has too much process. It's whose needs each piece of process is actually meeting.
Three Rules That Turn into Process
Three of the rules we've traced over the past few months are especially good at building infrastructure.
The first is the Over-Functioning Mandate, the rule that ties your safety to your visible output. In process form, it's the step that exists so your contribution can be seen - the final review where you add a comment, the status report you insist on compiling yourself, the meeting you chair because chairing it shows you're on top of things. These might be uncomfortable to acknowledge. Each one produces output the Mandate can point to, whether or not the work needed it.
The second is the Blame Node, the rule that routes every organisational failure back through you first. In process form, it's sign-off as advance liability. If everything passes through you, then anything that goes wrong is something you could have caught, so the approval step becomes a way of owning failures before they happen. The irony is that it guarantees they will route through you, because you've built the path for them. It also risks teaching your team that quality is your job rather than theirs, which makes the next failure more likely, not less.
The third is the Risk Premium, the price your nervous system charges for stepping back, set by what similar situations cost you in the past rather than by the one you're in now. In process form, it's scar tissue: the extra check introduced after a single bad incident and kept for years after the conditions that caused it have changed. Ask when that step last caught anything. The answer is often the incident it was built for, and then never again.
What the Bureaucracy Audit Is
The Bureaucracy Audit is a structured review of the approvals, sign-offs, standing meetings, and reporting lines that route through you, testing each one against a single question: does this step protect the work, or does it protect you?
Protecting you isn't automatically a bad thing. Some steps should exist to protect you, such as genuine legal exposure, regulatory accountability, or decisions only you are authorised to make. The audit isn't designed to strip out every safeguard. It's designed to make each safeguard declare its purpose, so you can keep the ones that are doing a job and stop paying for the ones that aren't.
And the payment is real, even when nobody sees the bill. It's the two days the proposal waited. It's the team that has learned to send things up half-finished, because you'll fix them anyway. It's the strategic thinking you didn't do this week, because your attention went to the approval queue. A process that protects you from an old room is paid for, every week, by the people working in this one.
Why Process Carries Extra Weight for Queer Leaders
If you're an LGBTQ+ executive, two things make this audit more delicate, and more valuable.
The first is that process can be genuine protection. Many queer leaders have learned that their judgement gets scrutinised harder than their peers', and that a decision made informally can be questioned later in ways a straight, cisgender colleague's wouldn't be. Documenting everything, getting sign-off in writing, and routing decisions through formal channels can be a hard-won and sensible response to that. The audit doesn't ask you to drop protection the current organisation still makes necessary. It asks you to check whether the organisation you're protecting yourself from is the current one, or an older one.
That distinction matters because the Existential Perfectionism Trap, the belief that your right to space, authority, and safety depends on flawless execution, makes every process that promises flawlessness look essential. And it stacks on the Identity Tax, the extra energy cost of code-switching and hyper-vigilance your peers simply don't pay. Process can look like a way of handing that vigilance over to a system, but a system you built to watch for threats still runs on your attention.
The second is that not all bureaucracy works against you. Informality tends to favour the people who already belong - the decision settled over drinks, the promotion that goes to whoever the senior team already knows, the feedback that only reaches people in the right conversations. Clear, written process is often what protects under-represented staff from exactly that. So as you audit, keep the structures that protect fairness for others, even as you retire the ones that only protect your nerves. A process that protects fairness is doing a different job from one that protects you from being caught out, and it deserves to stay.
Two Ways to Complete the Audit
Like the exercises in other weeks, these are built to collect evidence from the organisation you're in now, rather than from the one your rules were written for.
The Sign-Off Trace
Execution: For two working weeks, list every step in your organisation's processes that requires you: approvals, reviews, documents you're copied into by default, standing meetings you chair or have to attend, and reports you compile yourself.
Action: For each one, note when and why it was introduced, what it actually caught or changed in the last three months, and who would own that outcome if the step disappeared. Then mark it Work (it protects the quality, safety, or fairness of the work) or Me (it mainly protects you from being caught out, blamed, or unseen).
Target: A written map of which parts of your process load are doing a job for the organisation, and which are doing a job for your nervous system.
The Sunset Test
Execution: From your Sign-Off Trace, choose one step marked Me that caught nothing meaningful in the last three months.
Action: Suspend it for four weeks. Tell the people affected that you're doing it, who owns the decision without you, and the date you'll review it together. During those four weeks, keep a factual note of anything that goes wrong and what it actually cost.
Target: Evidence from the current organisation about whether the step was ever load-bearing. If it was, reinstate it with a purpose you can state in one sentence. If it wasn't, retire it, and tell the team why.
Good Process Outlasts Your Anxiety, It Doesn't Encode It
None of this is an argument against process. Good process is one of the most generous things a leader can build. It makes work predictable, protects people who would otherwise be exposed, and lets the organisation function when you aren't in the room. The aim isn't less of it. It's process that does a job you can name. Steps written by an old rule ask your team to keep paying for a room you've already left, and you're allowed to stop charging them.
Next week we look at the Uptime Myth, and what happens when an organisation starts treating its leaders like systems that are never allowed to go offline.
Message me to schedule a confidential consultation to find out how I can help you build an organisation that runs on clear process rather than on your constant oversight.
