Why Empowered Teams Still Wait for Permission

Many organisations say they want empowered teams.

Yet those same teams are often expected to seek approval before changing scope, challenging a deadline, protecting technical health, saying no to a request or responding to what they have learned.

In this episode of the Organisational Friction Series, we explore why permission-seeking is often a rational response to the system around the team, rather than a lack of confidence, capability or ownership.

We look at how unclear decision boundaries, governance, funding, measures and leadership behaviour can quietly teach teams where authority really sits. We also explore what meaningful empowerment requires: clear intent, usable authority, trusted boundaries, shared context and leadership support when decisions become uncomfortable.

The episode draws on Matthew Coxall’s upcoming body of work around Harmony, including the Harmony philosophy, The Harmony Operating Model and Harmonised.

A question to take back to your organisation:

What decision does your team repeatedly ask permission to make, even though it already has the context and accountability to make it?

Transcript

Speaker 2 0:00

Why do teams that are described as empowered still feel the need to ask permission before making meaningful decisions?

Speaker 3 0:07

Yeah. I mean, that is uh that is really the defining organizational puzzle of our time, isn't it?

Speaker 2 0:12

It really is.

Speaker 3 0:13

You look around and you have these incredibly capable, you know, highly compensated professionals, and they are essentially stuck. They're in this corporate holding pattern, just waiting for a green light to do the jobs they were hired to do.

Speaker 2 0:26

Right. I want you, the listener, to picture this because, well, you have probably lived it. Imagine you're sitting in a Tuesday afternoon planning meeting.

Speaker 3 0:34

Oh, we've all been there.

Speaker 2 0:35

Exactly. And your official title might be like Agile Squad Lead or Product Owner. And the posters on the wall in your office talk about autonomy, being product led, moving fast.

Speaker 3 0:47

Right, usual buzzwords.

Speaker 2 0:48

Yeah. The internal newsletters are just full of phrases like fail fast and own the outcome. But then to change a minor feature scope or push back a non-critical deadline based on new customer data that you literally just gathered. You can't just do it.

Speaker 3 1:01

No, you have to submit a formal request.

Speaker 2 1:03

Right. You have to wait two weeks for a steering committee to meet, and you just hope a vice president who has like never even met your customers gives you the thumbs up. So you have the label of empowerment, but the daily reality is just this maze of permission slips.

Speaker 3 1:17

It's totally paralyzing.

Speaker 2 1:18

It is. And before we get too deep, I need to mention that the source material for this episode comes from an upcoming body of work around harmony by the author Matthew Coxall, who we will refer to as Matt for the rest of this podcast.

Speaker 3 1:30

And uh our mission for this deep dive really is to use Matt's work to unpack the mechanics of that maze. We are going to explore why this persistent habit of permission seeking, why it isn't a sign of weak or timid or unmotivated teams.

Speaker 2 1:46

Because it's so easy to just blame the people, right?

Speaker 3 1:48

Exactly. We need to stop diagnosing this as a failure of individual courage. Instead, we're going to look at how waiting for permission is actually a perfectly rational, learned response to a contradictory organizational system.

Speaker 2 2:01

A learned response. I like that.

Speaker 3 2:03

Yeah. And we'll explore how we move from what is essentially empowerment theater to genuine usable authority.

Speaker 2 2:09

I want to pull on that thread right away. Empowerment theater. Because it really does feel like a performance a lot of the time.

Speaker 3 2:16

It absolutely is a performance.

Speaker 2 2:17

There is this massive, just undeniable gap between the stated reality, you know, the slides they present at the all-hands meeting, and the lived reality of the people actually writing the code or designing the campaigns or building the products.

Speaker 3 2:32

And that gap exists because organizations, well, they frequently engage in Hass measures. They delegate the accountability for a specific outcome. So let's say they want a team to increase user adoption by 20 percent.

Speaker 2 2:46

Right, a classic target.

Speaker 3 2:47

Or maybe they want to hit a new regional revenue target. They hand down that outcome, but they do not redesign the authority or the funding models or the governance structures around that outcome.

Speaker 2 2:58

So the system stays the exact same.

Speaker 3 2:59

Exactly. They just change the labels on the org chart. So they might rename a traditional IT delivery group into an uh an empowered product squad. Yeah. But the operating reality, the actual mechanisms of how work gets funded and approved, that hasn't shifted an inch.

Speaker 2 3:14

Wow. Okay. So the team gets a shiny new mandate, but the moment they try to act on it, they hit a wall.

Speaker 3 3:22

A massive wall.

Speaker 2 3:23

Let's say they're looking at the backlog and they realize, based on, I don't know, a new market trend, that feature A is totally useless and they need to pivot to feature B.

Speaker 3 3:33

which happens all the time.

Speaker 2 3:35

Right. And in a truly empowered state, they just make the call. But in this state of empowerment theater, they can't do that. They have to escalate that pivot to a committee.

Speaker 3 3:45

Yeah, they cannot pivot without permission. They cannot protect their own technical health if it means, you know, slowing down a promised delivery date.

Speaker 2 3:54

Even if the code is a mess. Exactly.

Speaker 3 3:56

They can't say no to a senior stakeholder's ped project, even if that project doesn't align at all with the outcome they were told to own. And perhaps most critically, they cannot act on new learning.

Speaker 2 4:07

Which totally defeats the purpose of being agile.

Speaker 3 4:10

Exactly. This is an anti-pattern that Matt's work refers to as empowerment without authority. The team owns the backlog in name, but they do not own the strategic trade-offs that actually shape that backlog.

Speaker 2 4:22

So they're just managing the tasks, basically.

Speaker 3 4:24

Right. They might be measured on customer satisfaction, but they lack the access to support insights, or they lack the actual authority to pause feature development to fix the underlying technical debt that is causing the dissatisfaction in the first place.

Speaker 2 4:54

Yeah. Like if you have the target, shouldn't you naturally take the reins? If you own the target, it implies you have the reins. Why wouldn't a team just grab those reins and start making the trade-offs?

Speaker 3 5:03

Because accountability without influence is just exposure.

Speaker 2 5:06

Oh, exposure. Wow. Okay. That completely changes the paradigm.

Speaker 3 5:10

It really does.

Speaker 2 5:11

You are saying that without the structural livers to make decisions, a target isn't a goal, it's a liability.

Speaker 3 5:18

It is a profound liability for the people doing the work. If a team can only control their local activity, right? The daily coding, the wireframing, the task execution.

Speaker 1 5:29

The day-to-day stuff.

Speaker 3 5:30

Yeah, the day-to-day. But if they cannot control the major decisions that dictate the product's direction, they're caught between two completely conflicting worlds. They're trapped. Totally. The organization expects them to act like these visionary product owners who can creatively solve complex customer problems. But the system constrains them exactly like a traditional delivery unit whose only job is to execute a pre-written project plan on a fixed timeline.

Speaker 2 5:58

So they have all the pressure, but none of the power.

Speaker 3 6:00

Exactly. They carry the burden of the outcome, but none of the levers to affect it. So of course they freeze. Of course they ask for permission. What else would they do?

Speaker 2 6:09

That makes total sense. So if simply handing out a target and walking away isn't empowerment, then we need to fundamentally redefine what empowerment actually requires.

Speaker 3 6:18

We do. We have to look at the structural prerequisites.

Speaker 2 6:21

Right. Because if we don't know what actual empowerment looks like structurally, we can't begin to fix the friction. So what are the actual requirements for a team to operate with autonomy?

Speaker 3 6:31

Well, the foundation requirement is what we term usable authority. And usable authority is not about just, you know, leaving a team alone in a room and hoping for the best.

Speaker 2 6:40

Right. It's not anarchy.

Speaker 3 6:42

No, not at all. It requires specific active ingredients. So clear strategic intent from leadership, shared context across the team, meaningful outcome ownership, and crucially access to timely expertise.

Speaker 2 6:55

Timely expertise. Okay, I want to challenge this because in my experience, bringing enabling functions like legal or compliance or marketing into the room early, it often feels like the exact opposite of empowerment. No, so well, if I'm trying to ideate and move fast and I have a compliance officer sitting in every single brainstorming session, nothing gets built. They just see risk everywhere. Doesn't early collaboration just lead to early paralysis?

Speaker 3 7:22

That is a very common concern. And it happens when enabling functions operate as auditors rather than co-designers.

Speaker 2 7:28

Oh, auditors, yeah, that's exactly what it feels like.

Speaker 3 7:31

Right. In a traditional setup, legal or compliance arrives at the very end of the line. The team has spent, say, six months building something, and two days before launch, compliance reviews it, finds a regulatory issue, and blocks the release.

Speaker 2 7:45

Which is incredibly frustrating.

Speaker 3 7:47

That is late stage friction. When we talk about timely expertise, we mean shifting those functions to the beginning, but with a completely different mandate.

Speaker 2 7:56

So they're not there to play cop.

Speaker 3 7:58

Exactly. Their job is not to say no to the idea. Their job is to help the team to find the safe boundaries of the experiment. They're there to shape the work safely, identifying those regulatory or brand guardrails so the team can run as fast as they want within those guardrails.

Speaker 2 8:14

Okay, let me see if I can map this to an analogy. It sounds like giving someone the keys to a car and telling them they are an empowered driver, right? You are fully accountable for getting us to our destination.

Speaker 3 8:25

I like this. Keep going.

Speaker 2 8:26

But they are treating the team like they are driving a train on fixed tracks. Management laid down the tracks a year ago, they control the switches, and the team's only real job is to just shovel coal into the engine to keep the speed up.

Speaker 3 8:39

Yes, that is new.

Speaker 2 8:40

But the team was told they were getting an off-road vehicle where they could choose the best route based on the terrain, and they haven't been given a map, the steering wheel is locked, and they have to call headquarters every time they want to change lanes.

Speaker 3 8:52

That captures the friction perfectly. You are told you have an off-road vehicle, but the organization is still actively laying down train tracks in front of you and then, you know, wondering why you aren't adapting to the landscape.

Speaker 2 9:05

Right. It's totally unfair to the team.

Speaker 3 9:06

And that brings us to the vital role of boundaries. Because autonomy is not the absence of constraints. In fact, autonomy is strengthened by clear boundaries.

Speaker 2 9:16

That still sounds a bit contradictory to people who associate autonomy with, you know, total freedom. How do constraints actually strengthen freedom?

Speaker 3 9:25

Well, think about your off-road vehicle. If you were driving across an open desert in the pitch black, and you know there are massive ravines somewhere out there, how fast are you gonna drive?

Speaker 9:36

I mean, I'm crawling. Five miles an hour, maybe less. I don't want to fall in.

Speaker 3 9:41

Right. You are crawling and you are constantly asking the passenger to get out with a flashlight to check the path ahead. You're asking for permission to move forward safely.

Speaker 1 9:51

Oh, I see where this is going.

Speaker 3 9:53

But if you have a GPS and headlights and clear markers showing exactly where the edge of the ravine is, you can confidently drive 60 miles an hour.

Speaker 2 10:02

Because you know where it's safe to go.

Speaker 3 10:04

Exactly. When boundaries, whether they're regulatory rules, architectural standards, or financial limits, when those are explicit and stable, teams know the exact space they can safely explore without needing repeated approval.

Speaker 2 10:16

So it creates like a safe zone.

Speaker 3 10:18

It creates safe freedom rather than hidden control. Leaders establish these boundaries not by micromanaging the exact path the team takes, but by clearly defining the constraints of the terrain.

Speaker 2 10:29

Okay, so we've just established that usable authority and clear guardrails are the logical requirements for a team to move fast. But we know that in reality, many incredibly smart, highly paid teams who seem to have these things, they still default to waiting.

Speaker 3 10:48

They do all the time.

Speaker 2 10:49

If the logic is so clear, what is the system quietly teaching them? Like why do they still wait for permission? Why is waiting the rational choice?

Speaker 3 10:57

Because human behavior in complex systems, it's driven by consequences, not by corporate messaging. Not the posters on the wall.

Speaker 2 11:04

Not the posters. Waiting for permission is a highly rational, learned response to the organization's signals. Teams learn the real rules of the organization based on what happens after they make a decision, not what is written in a glossy strategy dead.

Speaker 3 11:18

It's operating conditioning, basically.

Speaker 2 11:19

Exactly.

Speaker 3 11:20

If you, the listener, step out of line and try to exercise your autonomy and you get burned for it, you are not going to step out of line again. The poster on the wall loses all credibility instantly.

Speaker 2 11:29

It does, completely.

Speaker 3 11:30

So how exactly does the corporate system condition people to be cautious? What are the specific signals? It happens through very specific repetitive signals. And the most damaging signal is when decisions are reversed.

Speaker 2 11:44

Reversed, like overridden.

Speaker 3 11:46

Yes. Let's say a team looks at their customer data, they exercise their supposed autonomy, and they make a local decision to delay a minor feature release to prioritize uh a critical security patch.

Speaker 2 11:59

Which sounds like a responsible product decision.

Speaker 3 12:01

Right. But if a senior leader swoops in, overrides that decision, and demands the feature be released on time anyway, the team learns an immediate lesson. They learn their autonomy is conditional.

Speaker 2 12:13

Conditional autonomy. You are fully empowered right up until the moment we mildly disagree with your choice.

Speaker 3 12:18

Yes. And the second time that situation arises, they won't even bother analyzing the data. They will just ask the leader what to do.

Speaker 2 12:25

Why do the work if it's just going to be thrown out? Exactly.

Speaker 3 12:29

Another powerful signal is shifting boundaries. We just talked about how stable boundaries create safe freedom. But what happens when the rules of the game change depending on the context?

Speaker 2 12:39

Or the political climate in the office.

Speaker 3 12:41

Or just the mood of a stakeholder on a given Tuesday.

Speaker 2 12:43

Right. The boundaries become invisible fences. You don't know where the shock is going to come from.

Speaker 3 12:49

And if you don't know where the boundary is today, the most rational, self-preserving action is to ask for permission. You wait for reassurance rather than risk stepping out of line.

Speaker 2 12:59

That makes total sense. You're just trying not to get electrocuted by the invisible funds.

Speaker 3 13:03

Exactly. A third signal involves how organizations treat roadmaps. In a healthy environment, a roadmap is a series of hypotheses to be tested.

Speaker 2 13:13

Yeses, essentially. Educated guesses.

Speaker 3 13:15

Right. But often roadmaps become fixed commitments.

Speaker 2 13:19

Oh, I see this constantly. A team does three months of deep discovery work, they talk to users, and they realize the feature they promised the board six months ago is actually not going to solve the customer's problem at all.

Speaker 3 13:31

And what happened?

Speaker 2 13:31

The roadmap is treated like a blood oath. They have to build it anyway.

Speaker 3 13:35

Exactly. When roadmaps are treated as fixed promises rather than hypotheses, the system is actively teaching the team that adapting to new evidence is punishable. They learn that delivering the flawed plan on time is organizationally safer and more valued than delivering actual value.

Speaker 2 13:52

That is so backward, but so common. What's the fourth signal?

Speaker 3 13:56

The fourth signal is when consultation is confused with approval.

Speaker 2 14:00

Okay, unpack that.

Speaker 3 14:01

Well, a team might approach, say, an enterprise architect or a security lead simply to ask for advice on shaping a solution. They just want some informal guidance.

Speaker 2 14:12

Just a quick sanity check.

Speaker 3 14:13

Right. But if that informal advice-seeking conversation suddenly morphs into a mandatory multi-week sign-off gate.

Speaker 14:20

Oh man.

Speaker 3 14:21

The team learns to hide their work. They will wait until the product is entirely finished before showing it to anyone, or they just stop seeking early advice altogether.

Speaker 2 14:29

Because asking for help just slows them down. Every time they try to operate like the off-road vehicle they were told they are, they hit a newly laid piece of train track.

Speaker 3 14:37

They do?

Speaker 2 14:37

And eventually they just accept that they are a train. They stop trying to steer and they start escalating.

Speaker 3 14:43

And we have to look closely at the psychology of that escalation. Permission seeking becomes a mechanism to distribute organizational risk.

Speaker 2 14:51

To spread the blame, basically.

Speaker 3 14:53

Yes. If a team knows they will carry the downside of a decision, if they know they will be blamed if an experiment fails or a metric drops, but they do not have the structural protection or authority to defend their rationale, they will logically seek approval.

Speaker 2 15:07

They want a senior leader's fingerprints on the decision.

Speaker 3 15:10

Exactly. Approval simply becomes a quest for cover. If the VP signed off on it, the VP shares the blame.

Speaker 2 15:18

They are looking for an umbrella because the system has taught them it is going to rain. That makes complete sense.

Speaker 3 15:23

It really does.

Speaker 2 15:24

But I want to take this out of the abstract. Let's ground this. Let's look at a concrete pattern. I want you to walk us through a scenario where this learned helplessness actually plays out. Sure. Not because people are malicious or incompetent, but because well-intentioned professionals are just trying to navigate these conflicting mandates.

Speaker 3 15:42

Let's examine a very recognizable pattern Matt calls the decision latency scenario.

Speaker 2 15:47

Okay, set the scene for us.

Speaker 3 15:48

Imagine a large product organization, and they're responsible for a major digital commerce platform. You have two critical functions involved in this scenario: marketing and engineering.

Speaker 1 15:59

Oh boy. Already a classic pairing. I can feel the friction brewing.

Speaker 3 16:04

Right. So marketing has analyzed the market, and they've identified a major promotional campaign that is absolutely vital for hitting a critical quarterly revenue target.

Speaker 2 16:14

Okay. Big stakes.

Speaker 3 16:15

The board is expecting this revenue, and marketing needs to launch the campaign in two weeks. At the exact same time, engineering has been monitoring platform health, and they know they must complete a critical payment gateway upgrade.

Speaker 2 16:28

And let me guess, the timing conflicts.

Speaker 3 16:31

This upgrade has to happen before the upcoming holiday trading period, or the platform risks crashing under heavy traffic. And here's the structural catch. Both of these initiatives require the exact same limited pool of specialist back-end engineers.

Speaker 2 16:45

Okay, this is fascinating because this isn't a case of one side being wrong.

Speaker 3 16:50

Not at all.

Speaker 2 16:50

It's not just stubborn personalities clashing in a meeting room because someone didn't get enough sleep. We have a collision of completely legitimate outcomes.

Speaker 3 16:58

Absolutely legitimate.

Speaker 2 16:59

Marketing is absolutely right to push for the campaign. They are accountable for revenue. Engineering is absolutely right to push for the upgrade. They are accountable for operational stability.

Speaker 3 17:10

And neither side can safely concede. They're both fiercely protecting the outcomes the organization has explicitly asked them to deliver.

Speaker 2 17:18

They're just doing their jobs.

Speaker 3 17:20

Exactly. Marketing looks at the delay and sees missed revenue and failed targets. Engineering looks at the delay and sees a catastrophic platform outage during the most important time of the year.

Speaker 2 17:32

And this is the exact moment in the stares at each other, the energy completely drains from the room, and someone finally throws their hands up and says, We can't solve this here. We need to escalate this to the VP or the executive board.

Speaker 3 17:44

That is exactly what happens.

Speaker 2 17:46

Yeah.

Speaker 3 17:46

And when it lands on the executive board's desk, what do you think the executives usually think?

Speaker 2 17:52

They probably think, why are these teams so difficult?

Speaker 3 17:55

Yes. They look down and think, why are our teams so slow? Why can't these highly paid professionals just collaborate and figure this out locally? Why do they constantly need us to break ties?

Speaker 2 18:06

But the executives are missing their own role in the bottleneck.

Speaker 3 18:09

Entirely. The root cause of this latency isn't a failure of team collaboration. The root cause is an unclear strategic boundary.

Speaker 2 18:17

The boundary wasn't set at the top.

Speaker 3 18:19

Exactly. The organization as a whole, at the executive level, has not made it clear how short-term revenue growth should be balanced against long-term platform stability in this specific operating context.

Speaker 2 18:31

Because the executives haven't made that overarching strategic trade-off, they have essentially exported the conflict down to the teams.

Speaker 3 18:38

That's a great way to put it.

Speaker 2 18:39

They've handed down two competing priority one mandates and just expected the teams to magically resolve the physics of limited resources.

Speaker 3 18:47

Yes. Because the strategic trade-off hasn't been made visible at the top, the team is forced to escalate to force the issue. The escalation is essentially the team saying, We don't have the authority to decide if the company values revenue or stability more today. You have to tell us.

Speaker 2 19:04

Right. They need the business rule.

Speaker 3 19:05

And once the executive is forced to define the boundary, let's say they confirm that avoiding a holiday crash is the absolute priority. The overarching risk is absorbed by leadership.

Speaker 1 19:16

Because they made the call.

Speaker 3 19:18

Right. And from there, a safer compromise can emerge locally.

Speaker 1 19:21

Oh, I see.

Speaker 3 19:22

Maybe marketing realizes they could do a slightly smaller static promotion that doesn't require those back-end engineers, allowing the gateway upgrade to proceed. But they could not invent that compromise safely until the boundary and the risks were made visible.

Speaker 2 19:36

So the friction, the delay, the endless waiting in that room, none of that came from the team members lacking the skills or the desire to move fast. It came from the system around them failing to provide coherent trade-offs.

Speaker 3 19:48

The strategy was vague, so the execution stalled.

Speaker 2 19:50

Which means we can't fix this by sending the team to another agile training seminar. We have to look beyond the team to the wider operating system of the company itself.

Speaker 3 19:59

This is where we introduced the lens of the harmony operating model.

Speaker 2 20:02

The harmony operating model.

Speaker 3 20:04

Okay, yes. Or Tom. We will use this to understand how individually reasonable mechanisms within an organization, things that seem perfectly logical on their own, how they combine to create a contradictory system that acts like a vacuum just pulling all decisions upward.

Speaker 2 20:21

Let's spend some real time here because this feels like the core of the issue. I want to break down these systemic mechanisms. How do these individual pieces, strategy, funding, governance, actually connect to create this friction?

Speaker 3 20:34

Let's start with strategy and prioritization.

Speaker 2 20:36

Okay, let's do it.

Speaker 3 20:37

When we look at strategy, the friction usually occurs in one of two extremes. On one end, strategy functions as a detailed, step-by-step instruction manual rather than a directional constraint.

Speaker 2 20:48

Like over prescribing the solution.

Speaker 3 20:50

Exactly. Leaders try to define exactly how a problem should be solved rather than defining what the problem is and letting the team find the best path. This paralyzes teams because the moment they encounter a reality that doesn't match the instruction manual, they have to stop.

Speaker 2 21:05

And ask for a new manual.

Speaker 3 21:07

Right. They have to ask for permission to deviate from the instructions.

Speaker 2 21:10

And the other extreme, what's the opposite of the instruction manual?

Speaker 3 21:13

The other extreme is the illusion of prioritization.

Speaker 2 21:16

Oh, I like that phrase.

Speaker 3 21:18

This is where leadership avoids making difficult trade-offs by labeling everything on the roadmap as priority one.

Speaker 2 21:24

If everything is priority one, nothing is.

Speaker 3 21:26

Exactly. If you have 10 initiatives and they are all P1, you have no strategy. You have a wish list. Yeah. And teams have no framework to resolve resource conflicts locally. So they escalate, just like the marketing and engineering scenario.

Speaker 2 21:41

It's the executive avoidance of discomfort trickling down to become a team level crisis.

Speaker 3 21:46

That's very well said.

Speaker 2 21:47

Okay, what about funding? I have to imagine how the money flows dictate almost everything about how a team behaves.

Speaker 3 21:54

Funding is the loudest signal in any organization.

Speaker 1 21:58

The loudest signal.

Speaker 3 22:00

CEO stand on a stage at an all-hands meeting and passionately demand agile product adaptation and rapid learning and customer obsession.

Speaker 2 22:08

Everyone cheers.

Speaker 3 22:10

Right. But if that same organization funds its teams through rigid stop-start project cycles with fixed scopes and rigid deadlines tied to annual budgets, the teams will optimize for the funding model, not the learning.

Speaker 2 22:23

Because the funding model is what determines if they still have jobs next quarter.

Speaker 3 22:27

Exactly.

Speaker 2 22:28

Can you explain the mechanics of that? Like how does that stop-start funding actually force permission seeking?

Speaker 3 22:32

Imagine a team learns through early testing that their initial product idea is flawed.

Speaker 2 22:38

Okay. So they need to pivot.

Speaker 3 22:39

Right. To adapt, they need to change the scope. Right. But if change the scope means they have to halt work, write a new business case, go back to an investment board, and beg for their budget to be reapproved in a process that takes two months. What do you think they will do?

Speaker 2 22:55

They are going to ignore the learning. They will just build the flawed product because it's already funded.

Speaker 3 23:00

Exactly. They will deliver the flawed plan because the funding model penalizes adaptation. To survive, they seek permission at every gate, ensuring they are perfectly aligned with the original funded scope, regardless of whether it still makes sense.

Speaker 2 23:15

Which flows right into governance, right? We talked about consultation morphing into approval earlier.

Speaker 3 23:19

Yeah.

Speaker 2 23:20

How does governance typically misbehave in this contradictory system?

Speaker 3 23:24

Well, governance is absolutely critical for a healthy organization. The issue is how it behaves and when it occurs.

Speaker 2 23:31

The timing.

Speaker 3 23:32

Yes. When governance forms act as late-stage approval gates demanding absolute certainty, detailed ROI calculations, and exhaustive risk mitigation plans before any actual discovery or building has even happened, they create what Matt refers to as reassurance theater.

Speaker 2 23:48

Reassurance theater, that is a brilliant term. If you've ever spent a Friday afternoon polishing a spreadsheet so that all the status indicators are green, just to get a steering committee off your back, you have performed in reassurance theater.

Speaker 3 23:59

We all have. Teams spend their time and cognitive energy polishing slides to look confident and certain for executives, rather than doing the messy, uncertain work of learning and exposing actual risk.

Speaker 2 24:11

It's all about making the executives feel comfortable.

Speaker 3 24:14

Right. Reassurance theater delays learning entirely because the goal of the meeting isn't to uncover truth, it's to present an illusion of control. And measurement ties directly into this as well.

Speaker 2 24:25

Right, the metrics. What happens when the tools we use to measure success actually strip teams of their authority?

Speaker 3 24:32

When metrics are used primarily as a form of judgment, for instance, comparing one team's velocity against another, or demanding that a team's status reports always show upward, linear progress, it drives defensive reporting.

Speaker 2 24:44

So people start gaming the metrics.

Speaker 3 24:45

They hide their struggles. They will artificially lower their targets so they could easily hit them.

Speaker 24:49

Right, playing it safe.

Speaker 3 24:51

Metrics in a healthy system should be used as feedback to guide learning and adjustment. When they are used as a surveillance tool to punish variants, teams will stop taking risks and start asking for permission for every move they make.

Speaker 2 25:03

I understand how all these pieces of the operating system strategy, funding, governance, measurement, how they all combine to create this creeping bureaucratic slowness. But I have to push back a little on the reality of corporate life here. Sure.

Speaker 3 25:19

Go ahead.

Speaker 2 25:20

All of this theoretical system design sounds logical when things are calm, but what happens when the pressure spikes? All of this gets ten times worse when there's a crisis or a tight deadline, right? Doesn't the need for speed override all this systemic bureaucracy?

Speaker 3 25:33

It's quite the opposite, actually, and it brings us to a crucial behavioral pattern in leaders known as the urgency reflex.

Speaker 2 25:39

The urgency reflex.

Speaker 3 25:41

Yes. Yeah. We have to look at how leaders react under immense pressure. When a crisis hits, maybe a competitor launches a rival product, or there is a macroeconomic shift, the urgency reflex kicks in, and leaders instinctively pull decisions upward.

Speaker 2 25:54

So they centralize control.

Speaker 3 25:56

They bypass the teams, they demand daily status updates, and they override local decisions in the name of speed and executive action.

Speaker 2 26:03

Which, honestly, in the heat of the moment, that feels like strong leadership. It feels like they are taking charge and steering the ship through the storm.

Speaker 3 26:11

It feels like taking charge to the leader, yes. But what it signals to the organization is devastating.

Speaker 2 26:16

What does it signal?

Speaker 3 26:18

It teaches the team that autonomy is a luxury. It teaches them that empowerment is a fair weather concept, only permitted during calm times when the stakes are low.

Speaker 2 26:28

Wow. So the moment things get difficult, the mask slips, and the team realizes they never really had the keys to the car in the first place.

Speaker 3 26:36

Exactly. And the long-term damage of that is profound. Once the crisis passes and things return to normal, that habit of waiting for permission has been cemented in the team's psychology.

Speaker 2 26:47

Because they remember what happened last time.

Speaker 3 26:49

Right. They have learned that their authority is easily revoked, so they preemptively wait for instructions the next time things get even slightly complex. The urgency reflex trains the organization to be passive.

Speaker 2 27:00

That is heavy. So if the current operating system, with its rigid stop-start funding, its reassurance theater, its invisible boundaries, and this executive urgency reflex, if all of that is currently tuned to pull decisions upward, what does the inverse look like?

Speaker 3 27:17

The healthy state.

Speaker 2 27:18

Yeah. What does it actually look like when an organization tunes its system to push decisions down to where the work is happening?

Speaker 3 27:25

That is the transition from empowerment theater to healthy empowerment. And healthy empowerment is defined fundamentally as usable authority operating inside clear, trusted, and visible boundaries.

Speaker 2 27:37

So redefining the target state.

Speaker 3 27:39

Exactly. It means that decisions are made as close to the work as possible by the people who hold the deepest and most current context about the customer and the technology.

Speaker 2 27:48

So in this state, you actually have the off-road vehicle, you have the map, the headlights work, and management has clearly marked where the ravines are.

Speaker 1 27:56

Exactly.

Speaker 2 27:56

But how does that play out day to day? Because we established earlier that healthy autonomy doesn't mean a team just goes into a cave and builds whatever they want in isolation.

Speaker 3 28:04

Correct. Healthy autonomy requires intense, continuous collaboration, particularly with those enabling functions we discussed earlier: legal, finance, compliance, marketing.

Speaker 2 28:16

But the timing changes, right?

Speaker 3 28:17

The timing and the intent change completely. These functions are brought in early as co-creators to shape the value safely. They help build the guardrails so the team can move fast without breaking enterprise rules.

Speaker 2 28:29

So legal is a partner in designing the architecture of the feature rather than a roadblock the date before the launch date.

Speaker 3 28:36

Yes. And healthy empowerment inherently embraces learning loops. It means that the system is designed to allow assumptions to be tested quickly.

Speaker 2 28:44

Which reduces risk.

Speaker 3 28:46

Massively. If the evidence shows a direction is wrong, the team can change direction without that pivot being framed organizationally as a failure. Risk awareness is actually much higher in a healthy system because risk is managed continuously through small, rapid experiments rather than being hidden behind false certainty and green status reports until it explodes at launch.

Speaker 2 29:07

So in this ideal healthy state, does a team never escalate anything? Does the executive board just sit around drinking coffee because all the decisions are happening at the team level?

Speaker 3 29:17

Not at all. Escalation still happens. And it is a vital part of a healthy system. But it transforms from being habitual to being intentional.

Speaker 2 29:27

Intentional escalation.

Speaker 3 29:28

Right. In empowerment theater, teams escalate because they are afraid or because boundaries are hidden. In a healthy system, teams escalate when a decision genuinely requires cross-portfolio alignment.

Speaker 2 29:40

Like the marketing and engineering conflict.

Speaker 3 29:42

Yes. Or when a decision crosses a known strategic boundary, or when it involves a level of enterprise risk that the team cannot and really should not absorb locally.

Speaker 2 29:52

They aren't escalating because they are paralyzed. They're escalating because it's genuinely above their pay grade to make a structural trade-off for the entire enterprise.

Speaker 3 30:00

Precisely. And in this state, governance transforms as well. It moves from being a control mechanism focused on audits and approvals into an enabler.

Speaker 2 30:08

An enabler. What does enabling governance look like?

Speaker 3 30:10

Governance forums exist to clarify decision rights, to make difficult strategic trade-offs visible, and to connect ongoing investment to actual validated outcomes rather than just tracking project milestones.

Speaker 2 30:23

And what about the leaders? We talked about the damage of the urgency reflex. How do leaders behave in a state of healthy empowerment, especially when things go wrong? Because in any complex environment, outcomes are imperfect. Experiments will fail.

Speaker 3 30:37

Healthy empowerment requires a fundamental shift in leadership behavior. Leaders must respond to uncertainty and failure with curiosity, not control.

Speaker 2 30:46

Curiosity, not control. That's a great mantra.

Speaker 3 30:49

It is. When a decision yields an imperfect outcome or a well-designed experiment fails, leaders in a harmonized organization focus on what the system learned, not who is to blame. They actively protect psychological safety.

Speaker 2 31:01

So they don't revert to the urgency reflex.

Speaker 3 31:10

Or what did this outcome teach us about our assumptions, rather than who authorized this?

Speaker 2 31:16

Okay, taking a step back, this is a massive paradigm shift. But getting to this state isn't about rolling out a massive new agile framework, hiring a fleet of consultants, or buying a new project management software tool.

Speaker 3 31:29

No, it's not about adding more tools.

Speaker 2 31:32

It's about looking at the signals right in front of us and seeking coherence in the system.

Speaker 3 31:37

If we connect all this back to the core philosophy of Matt's work, we see that harmony is not a rigid framework you install like an operating system update.

Speaker 1 31:46

Right.

Speaker 3 31:46

Harmony is a state of coherence. It is what happens when strategic intent, authority, boundaries, risk, funding models, governance structures, measurement, and leadership behavior all reinforce one another instead of pulling the organization in competing directions.

Speaker 2 32:02

It's about making sure that the steering wheel, the gas pedal, and the map are all actually designed for the same vehicle and that the road you are on matches the vehicle you were given.

Speaker 3 32:11

That's the perfect way to visualize it.

Speaker 2 32:13

Which brings us directly to you listening to this right now. We want to move this from abstract theory into your day-to-day practice. Rather than feeling overwhelmed and trying to fix your entire corporate operating system tomorrow morning, you can start by looking for the small signals of friction.

Speaker 3 32:30

You can observe the habits that have formed in your immediate environment.

Speaker 2 32:33

Exactly. It starts by interrogating the friction. The next time you feel that latency, that pause where everyone is waiting for someone else to make a call, recognize it not as a personal failing of the people in the room, but as a diagnostic signal from the system itself.

Speaker 3 32:49

Think about the invisible train tracks that are forcing your off-road vehicle to a halt.

Speaker 2 32:54

What if the very tools you use to measure your team's success, the status reports, the utilization metrics, the strict roadmap milestones are the exact mechanisms stripping them of their authority? What decision does your team repeatedly ask permission to make, even though it already has the context and accountability to make it? What has the system taught them might happen if they decide without asking?

Speaker 3 33:16

If this tension feels familiar, it is one of the signals Harmony is designed to surface.

Speaker 2 33:21

And remember to visit agileproducthub.com for more information, articles, podcasts, tools, and books from Matt.