The Value Creation Protocol

Part III — The Core Framework Traps

Chapter 16

The Authority Trap → Value-First Leadership


"We've literally built these businesses with silos, with hierarchies, with structures that have created bottlenecks. Because now, all of a sudden, there's just too much going on. You absolutely can't cope because there's just too many inputs, too much information."

Tony Dowling said that in June 2025, in our conversation on this trap.

I hear the "you" in his last sentence as the person at the top. That is my reading, not something Tony said. This trap usually gets told as a story about frustrated teams, and it is one. But read his words that way, and the one who can't cope is whoever every decision has to pass through.

You know the other side of it too. Your team has an idea that would solve a real problem for a customer. Everyone agrees it makes sense. Then it goes into the approval chain. Six months later it is dead, or so watered down that it barely resembles what it was, and the customer still has the problem. That isn't bad leadership, and it isn't lazy teams. It is a structure doing what it was built to do.

What this is

Centralizing control in ways that prevent the distributed intelligence organizations need.

That is the Authority Trap. The methodology's longer description opens with a harder sentence: "When control replaces enablement, organizations become their own worst enemy."

Central control made sense when judgment was scarce and expensive, and an approval chain was a way to ration it. Now the people who talk to customers and do the work hold much of what is known. The authority to act on it is still in the middle. So every decision travels from where the knowledge is to where the permission is and back again, and it loses something in each direction.

The methodology names the belief a trap breaks for five of the twelve, and this trap is not one of them; the belief to keep beside you here is Empowerment over Learned Helplessness: "Organizations thrive when people are empowered to create and share value naturally rather than waiting for permission or instruction." The methodology also calls the Managed Services Trap of Chapter 12 the inverse of this one: that trap starves people's capability, and this one jams the flow of decisions, so the capability people already have goes unused.

The alternative is Value-First Leadership:

Enable rather than control. Push decisions to where information lives. Trust teams with context and autonomy. Leadership's role is to create conditions for others to succeed, not to make every decision.

How to tell where you are

If you lead, the evidence is in your own last week.

  • Look at the decisions that reached you. For which of them did the person who brought it already know the answer?
  • Find one decision that waited. What was it waiting for, information or permission?
  • When did bad news last reach you early, from the person closest to it?
  • Is there something only you can approve, and does it stop when you are on a plane?

If you don't lead, it is in yours.

  • You know the answer, and you are writing a justification for someone who knows less about it than you do.
  • A customer asked for something plainly reasonable, and you had to say you would check.
  • You have stopped suggesting things.

Either way, try one question on someone close to your customers: what would you fix today if it were yours to decide? If the answer comes back immediately, the knowledge was there the whole time and the permission wasn't.

What to do

These are written for the person who holds the authority, because that is who has to move first.

  1. List the decisions that came to you recently. Beside each, write who had the most information about it.
  2. Pick the ones where that wasn't you. Start with the ones that are cheap to undo.
  3. Hand each one over with its context. What we are trying to do. What it may cost. Who else is affected. What you would want to hear about afterward. A decision handed over without context isn't trust. It is a setup. The context travels when what the work is for is written down where the work is recorded, and the person closest to the work can write that too. Value Accounting, Chapter 2 shows how.
  4. Say it where others can hear. Tell the room whose decision it is now. Then leave it decided. The first time you overrule a decision you handed over, everyone learns it was never handed over.
  5. Change what comes back to you. Not a request beforehand. A short account afterward: what they decided, and what happened.
  6. When one goes badly, fix the context and leave the permission where it is. Ask what they didn't know, and make sure the next person knows it. Taking the decision back is the quickest way into this trap again.
  7. Open the road in the other direction. Ask the people closest to your customers what they are seeing, regularly, and show them what changed because they told you.
  8. Spend the time you get back on the conditions. A clear purpose, shared context, barriers removed. In this model that is the leader's work.

How you know it worked

Two groups receive the value here: the people who can now act, and the customers they act for.

  • The person closest to the work makes the call and tells you afterward, and you learn something from how they made it.
  • A customer gets an answer from the first person they speak to.
  • Bad news reaches you early, from the person nearest to it, and they aren't nervous telling you.
  • You are away, and nothing is waiting in a queue for you when you get back.
  • Somebody describes a decision to you, and the word "allowed" isn't in the sentence.

Approval times falling is a count, and a risky one to trust. Approvals also get faster when nobody reads what they are approving.

Where it goes wrong

Abdication. You hand over the decision and none of the context, then step away. When it fails, the lesson everyone takes is that authority should have stayed at the top.

The rubber stamp. The approval step stays, the approver can't keep up, and they start waving things through. The AI-Native Shift names what is left: "the appearance of oversight without its substance." With AI producing work at machine speed, this is where a nervous organization lands first.

Moving the decision without the information. If the authority goes to the front line and the context stays in someone else's system, people are now free to decide blind. Chapter 19, on the Four Unified Views, has the answer to that one. The Unified Strategy View is defined as "Strategic intelligence embedded where decisions happen."

The trap beside this one is the Conformity Trap (Chapter 15). You hand people the decision, and only one answer is acceptable. They will work out which one, and you will have a slower version of deciding it yourself.

Its mirror is the Managed Services Trap (Chapter 12). You can give your people every decision and find they can't act on any of them, because the capability sits with an outside provider. Check both.

Read further

Stop 1 of 6: What this is

Back to contents