I’ve been building rules lately. Not the kind you enforce on a team, but the kind you enforce on yourself. Thresholds for when something needs a meeting before it ships. Guidelines for which decisions get consulted vs. unilateral. Approval matrices for things that used to move on instinct.
Most of them make sense. You build process when you’re hiring, when you’re scaling, when you’re trying to make sure decisions don’t slip through the cracks. Process is good. It’s also how you can accidentally build a permission structure that only gives you permission to do things that don’t matter.
The rule that feels safe
The thing about creating a rule is that it feels like you’re being responsible. You’re adding rigor. You’re preventing chaos. You’re making sure things don’t go sideways because someone decided to do something without checking.
So you make a rule: any decision that affects more than three people needs async feedback. Good rule. Prevents surprises. Makes sure you’re not being a jerk who decides things in a vacuum.
Then you have something you need to decide that affects five people, and suddenly this rule means you’re waiting for three people to respond to a Slack message instead of just… making the decision and telling them about it.
The rule was created to prevent bad decisions. But it’s actually preventing decisions, period.
This is where I am right now. I’ve built enough structure around decision-making that I can now point to the structure and say “well, I can’t decide that until the structure says I can.” Which sounds responsible. Which is actually me using process as permission to not choose.
What the structure hides
Here’s the thing nobody tells you about creating permission structures: they feel like they give you freedom, but they actually redistribute control.
You’re not getting more autonomous. You’re getting more justified in not moving. The rule says “wait for feedback,” so now when you want to move fast, you can point to the rule and say “I have to wait.” The rule is doing the hesitation for you.
And because the rule is doing the hesitation, you never have to articulate what you actually believe. You never have to say “I think this is right and I’m going to do it.” You can just say “well, the process requires…”
The structure is comfortable. It is also a cage.
I noticed this last week when I caught myself saying to someone: “I know the right call, but we have to follow the process.” Which is a polite way of saying: “I have permission from the process, but not from myself, so we’re doing this the long way.”
The process exists because I wanted to be careful. But being careful isn’t the same as being right. And careful can become an excuse for not exercising judgment at all.
The permission you actually need
This is where it gets tricky. Process is useful. You need some rules. The question is: what are they actually for?
If they’re for preventing bad decisions, they’re protecting against the wrong thing. Bad decisions aren’t usually stopped by process — they’re stopped by people who care about outcomes and think things through. Process stops impulsive decisions, but impulsive decisions are usually fine. The bad ones were bad because someone didn’t think, not because they didn’t follow the right approval chain.
If the rules are really for protecting your authority — making sure nobody goes rogue, making sure you stay in control — then call that what it is. That’s a different conversation. That’s about trust.
What I’m realizing is that the real permission structure isn’t the one you write down. It’s the one you carry in how much you trust yourself to choose.
The rules I’ve built are mostly me not trusting that I’ll think things through if there’s no external structure forcing me to. So I’ve built the structure. But the structure can become a way of avoiding the actual work, which is: developing judgment good enough that I don’t need the structure to tell me when to slow down.
The cost of too much permission
There’s a paradox in creating permission structures: at first, they clarify. You know exactly when you need to consult. You know the gates. Then, they start to control you.
The team has noticed. We have standing meetings where we’re supposed to make decisions, but the meeting is just async feedback waiting for consensus instead of an actual decision. We have escalation processes that mean simple calls now take a week. We have so much permission structure that nothing moves unless it fits the shape.
And the worst part? It’s not making decisions better. It’s making them slower and less owned. Because now when something goes wrong, it’s not “I decided badly,” it’s “the process let us down.” The permission structure has also become a diffusion structure. Everyone was consulted, so nobody is responsible.
That’s the real trap. You build the structure thinking it will prevent chaos. Sometimes it prevents better decisions, which are the only thing that actually prevent chaos.
The permission I’m reclaiming
So I’m taking apart some of it. Not all of it — I’m not going back to total chaos. But I’m asking: which of these rules exist because they prevent something real, and which exist because I was nervous?
Most of them exist because I was nervous.
The nervous ones are coming down. They’re being replaced with something simpler: think clearly, explain your thinking, move. If it’s wrong, we adjust. The structure that was supposed to give us safety was actually just me dressed up as process.
What I’m learning is that the real permission structure is knowing the difference between a decision that needs consultation and a decision that needs clarity. A decision that needs buy-in and a decision that needs to exist.
Some decisions benefit from input. Some decisions benefit from being made quickly and adjusted visibly. I was treating them all like they needed input, because input felt safe.
It did feel safe. It just also felt slow.
I’m reclaiming the permission to decide. Not to decide alone — collaboration is real. But to decide clearly, quickly, and own the outcome instead of letting the structure own it for me.
That’s harder than following a rule. But it’s how you actually build something.
The permission structure I’m building now isn’t a series of gates. It’s a practice of judgment. It’s asking before I move: “Do I know what I think? Can I explain why?” If yes, I move. If no, I think. But I don’t use the absence of clarity as permission to wait for the structure to decide for me.
That’s the permission structure that actually matters.