CTO Bottleneck: Five Decisions Route Through You

You told your VPE they could decide it. They brought it back anyway. That isn't a confidence problem on their side, it's a risk calculation: if the call goes wrong and you weren't consulted, it's on them, and if they check with you first it's shared. Everyone below you is running that arithmetic, and verbal delegation loses to it every single time.

What changes the arithmetic is naming the decision class in writing, with the failure pre-forgiven out loud. Which calls your VPE owns outright, including the ones they'll occasionally get wrong. Which you sanity-check asynchronously, with a stated turnaround so that async doesn't quietly come to mean stalled. And which genuinely need a live conversation, a list that should be short and mostly about people and money.

Then the criteria pointing the other way, so the org knows when interrupting you is the correct move rather than guessing and defaulting to always. That's the half people skip, and it's the half that gives you your Fridays back.

By week 6 roughly 30% of what used to route through you no longer does, your VPE has a defined scope rather than an implied one, and the calls that still reach you are the ones that should.