Everyone supports AI. But what happens when improving the work requires someone to surrender an approval, change a target or let another leader make the decision?

This AI-hosted discussion of Michael D. Kleinbergโ€™s Mesh Insights article examines the operating mandate behind Intelligent Capacity: who can change a workflow, make a customer commitment, challenge an assumption and resolve a material exception. Using a hypothetical services proposal, the hosts explore decision ownership, functional boundaries, escalation and how to test the model before expanding it.

Read the original article: https://insights.meshdigital.io/who-owns-the-decision-when-everyone-supports-ai/

[00:00:00] Imagine handing your enterprise team an artificial intelligence system that can flawlessly analyze scope and price this massive client proposal and it does it in like four seconds. Right, basically instantly. Exactly. But then you watch that exact same mathematically perfect proposal just sit in a departmental inbox for three agonizing weeks. Oh yeah, we see this all the time.

[00:00:26] Why? Because it's waiting for a vice president to come back from vacation, read a summary, and literally just type the word approved. It's incredible, really. It is. The defining paradox of modern enterprise technology. I mean, everyone supports the idea of AI when it means faster answers, right? Less time coordinating routine work. Sure, everybody loves the speed. But the moment someone has to surrender a familiar approval checkpoint to actually let the system move at that speed?

[00:00:55] That unanimous support just hits a brick wall. Right. And that is exactly what we are getting into today. Welcome to this digital deep dive from Mesh Digital. Glad to be here. Because we are looking at a fundamental crisis of organizational behavior today, not a technology failure. Exactly. We are isolating the exact friction point where intelligent systems collide with human authority.

[00:01:20] And our insights today, for you listening, are drawn from a November 8th, 2026 article. Right. Titled, Who Owns the Decision When Everyone Supports AI? Yes. By Michael Kleinberg, the CEO and executive partner of Mesh Digital. And the core thesis for you, and honestly, this is something every executive needs to confront, is that widespread sponsorship of AI is functionally useless without a workable operating mandate. That's the key right there. Right. The operating mandate. Right.

[00:01:49] Because intelligence and system capability never, under any circumstances, grant unrestricted permission to act. Never. You can have the smartest system in the world, but it doesn't give you the authority to pull the trigger. Okay. So let's unpack this. Because moving from the theoretical, you know, boardroom need for a mandate to what this actually looks like on the operational floor, that's where the friction lives. It really is. It's where things break down.

[00:02:13] We have to separate the ability to generate an answer from the right to execute it. So let's ground this in a strictly hypothetical scenario. Good idea. And to be clear to everyone listening, we are using this hypothetical purely to illustrate the mechanics of decision making. This is not a real client result. Right. Strictly hypothetical. Okay. Consider a services business preparing a complex proposal for a customer. You have sales, and they're scoping the work. Yep.

[00:02:40] You have delivery, estimating the resources, and you have finance, reviewing the economics. Right. The classic triangle. And in a legacy operating model, any one of those three functions can alter an underlying assumption that the other two completely rely on. Oh, totally. So, you know, sales wants more scope to win the deal. Which they always do. Naturally. But that forces delivery to alter the resource load, which then forces finance to flag the margin.

[00:03:07] It is the ultimate bottleneck. I always think of this like, well, like a large group of friends trying to pick a restaurant for a Friday night dinner. Oh, that's a perfect way to look at it. Right. Every single person in the group has absolute veto power over the choice. You know, someone does want sushi. Someone says Italian is too expensive. Someone says the commute is too far. But absolutely nobody in the group has the designated authority to pick up the phone and make the reservation. Exactly. So the text thread just circulates endlessly.

[00:03:36] Just going round and round. Right. And in our business scenario, it's the same thing. Sales changes the scope. Delivery shifts the timeline. Finance recalculates and says, oh, the margin is too low. Which forces sales to change the scope again. And the proposal just circles the drain. While the customer is completely in the dark, just waiting for a commitment. And that restaurant analogy, it perfectly illustrates the absence of a mandate. Yeah.

[00:04:01] Because in a modernized AI supported workflow, we have to structurally differentiate the roles to break that endless loop. OK. So how does Michael D. Kleinberg suggest we do that? Well, in this scenario, we have what he calls intelligent capacity. Intelligent capacity. Right. Right. This is the integrated combination of both human and non-human workers. Got it. And that capacity can evaluate all the feasible combinations of scope, timing, and price. It does the heavy analytical lifting simultaneously.

[00:04:31] So it's basically revealing several acceptable options before a commitment is even made to the customer. Exactly. But the technology cannot pick the restaurant. I mean, it can analyze the Yelp reviews. It can check the availability. And it can mathematically prove which restaurant fits the budget. Right. Right. But it cannot make the reservation. No, it can't. The redesign of this workflow fundamentally depends on a management decision regarding who holds the authority to commit. Authority to commit. So a specific person. Yes.

[00:05:01] That authority must belong to a formally designated owner. OK. That designated owner is the single individual who can approve the proposal when the system's evidence shows it meets the agreed upon conditions. Because simply installing an intelligent system does not magically rewrite the rules of who is allowed to make a choice. Exactly. You still need a human authorized to say yes. But wait.

[00:05:23] If we appoint a single designated owner with this authority to commit, we run into the obvious departmental panic, don't we? Oh, absolutely. Because finance and delivery are going to argue that they cannot just be cut out of the loop. They carry massive enterprise risk. Sure they do. Like if sales just hits approve on everything the AI generates, the company could go bankrupt fulfilling terrible contracts. And this is a crucial distinction in the framework.

[00:05:49] We are not advocating for removing all controls here or cutting risk management out of the equation. Finance and delivery must preserve their legitimate obligations. So how do they do that if they aren't the ones hitting approve? The operating mandate designates them as the evidence owners. Evidence owners. I like that. Yeah. So delivery owns the validity of the capacity information. Finance establishes the economic boundaries. OK. So they set the rules of the game. Exactly.

[00:06:17] And if the proposal generated by the intelligent capacity stays within those predefined boundaries, the designated owner can make the commitment immediately. Wow. So no meetings, no endless email chains. None. Just immediate execution. But what if there are material departures from those boundaries? Like say the AI suggests a highly aggressive timeline that really strains delivery's current capacity. Then it requires a decision from someone explicitly authorized to accept those specific consequences.

[00:06:47] OK. The process simply needs to move forward without requiring a fresh, drawn-out negotiation over who owns the decision every single time a proposal goes out. Right. So the mandate states up front, here is who decides, here are the boundaries, and here is who provides the evidence. Exactly. It gives the designated owner a decision they can actually make while giving evidence owners a clear, systemic way to protect the obligations they are responsible for. That makes sense.

[00:07:16] But there's a massive behavioral flaw that companies run into here. Oh, yeah. The incentives. Yes. You can write a beautiful mandate. You can define the evidence owners and the authority to commit perfectly on paper. But if the company's internal targets, the actual performance metrics that determine departmental bonuses and promotions, if those are at war with each other, absolutely nothing changes. So true.

[00:07:42] If we look back at our hypothetical services business, sales is typically rewarded for bookings, right? Right. And delivery is rewarded for utilization, while finance is rewarded for margin. And improving one of those measures naturally makes another one harder to achieve. Exactly. It is an internal zero-sum game. And here's where it gets really interesting for me. The introduction of AI doesn't just fail to solve this tension. No, it makes it worse. It actually weaponizes it.

[00:08:10] Because if you give sales an AI that can generate complex proposals in four seconds, sales can suddenly flood the pipeline with 100 times more proposals to maximize their bookings. Yep. And then delivery and finance, who are still trying to protect utilization and margin, are now facing an insurmountable wave of requests to validate. Right. So you can give an AI all the data in the world, but you cannot code your way out of a management conflict. Exactly. You can.

[00:08:38] And what's fascinating here is that this specific friction point actually redefines the role of the chief executive. Oh, how so? Well, when teams are battling over conflicting metrics, the AI is simply processing the conflict faster. Right. So the CEO must step in and establish the governing outcome for the enterprise. Alongside the acceptable trade-offs the organization is prepared to make to achieve it. Wait. So a governing outcome is different from a departmental metric? Oh, vastly different.

[00:09:09] Okay. Give me an example for this hypothetical business. Sure. For this business, the CEO might define the governing outcome as a feasible customer commitment with acceptable contribution and delivery quality. Okay. That is the enterprise's north star. The functional measures, the bookings, the utilization, the margin, they must subordinate themselves to support that governing result. Got it.

[00:09:31] So if a sales executive improves their local departmental bookings target, but they do it by repeatedly submitting proposals that violate delivery's utilization boundaries, they are hurting the governing outcome. Precisely. And the broader consequences of that behavior have to be addressed by leadership. Right. Rather than just letting the departments fight it out in the approval queue like they usually do. Exactly.

[00:09:53] And if we connect this to the bigger picture, flattening an organization with intelligent capacity forces a radical shift in middle and upper management. How so? Delegation has to move these specific operational choices much closer to the work being done. The frontline people with the actual context and the AI tools are making the calls within the boundaries. Which begs the question, right? What does the remaining management layer actually do all day? That's the big question.

[00:10:21] I mean, if they are no longer just sitting at the toll booth approving routine tickets or rubber stamping proposals, their calendar suddenly looks very empty. It does. But their job evolves from transaction approval to environment architecture. Environment architecture. Right. Management's primary responsibility becomes resolving material tradeoffs when boundaries are breached. Okay. They're developing judgment within their teams and improving the conditions under which those teams act.

[00:10:47] They are calibrating the machine and not pulling the levers manually. Okay. So because management's job is now resolving these material tradeoffs, we really have to look at how we handle disagreements. Yes. Escalation is critical here. Because delivery and finance as evidence owners have to be able to push back if a boundary is crossed. Absolutely. But if we aren't careful with how that pushback happens, we just rebuild the old bottlenecks. And the text thread about the restaurant starts all over again. Exactly.

[00:11:17] Which is why a sound operating mandate preserves independent challenge. Okay. So delivery must be able to question an unsupported resource assumption, for instance. Right. If a proposal assumes a project will take two weeks and delivery's evidence shows it historically takes four, delivery has to raise a flag. And finance must be able to identify terms that fall outside the agreed economics. Exactly.

[00:11:42] But to allow for that pushback without halting the entire enterprise, the escalation cannot just be a vague slack message saying, you know, I don't like these margins. Right. That doesn't help anyone. So the author details the necessity of bounded escalation. Bounded escalation. What does that look like? When the value stream owner needs a route to resolve a concern before a customer promise is made, the escalation must be highly structured. It has to contain four specific elements. Okay. What are they? First, the disputed assumption.

[00:12:12] What exactly is the mathematical or resource disagreement? Right. Second, the available options to resolve it. Third, the consequences of waiting. Meaning, what is the business cost of delaying this specific decision? Okay. And fourth, a named decision owner responsible for breaking the tie. I want to challenge that structure slightly, actually. Sure. Why mandate all four of those elements?

[00:12:38] I mean, in most companies, an escalation is just kicking the problem up the org chart and letting the VP figure out the options. And kicking it up the org chart is exactly why AI fails to accelerate the business. Oh, I see. If you just escalate the problem without the available options or the consequences of waiting, the executive now has to start from scratch. They have to do the research the AI and the frontline team already did. Exactly.

[00:13:04] By requiring the options and the cost of delay, you force the team to use their intelligent capacity to frame the solution. Right. Limiting the executive's job to simply applying business judgment to those options. That makes total sense. It prevents the executive from becoming a researcher again. Right. But wait, what actually happens to the work while we wait for this structured escalation to be resolved? That's a great question.

[00:13:27] Like if finance flags the margin on Tuesday and the named decision owner can't review the options until Thursday, does everything just grind to a halt? No. And a properly designed mandate clarifies this explicitly. While the decision is pending, the team does not freeze. Okay. They continue preparing alternatives, running different scenarios through the AI and refining the scope. The internal work proceeds. Oh, wow. So they keep moving. They do. What must wait, however, is the actual commitment to the customer. Got it.

[00:13:57] The final promise is withheld until the escalation is formally resolved. That brings up two ironclad rules from the text that govern this waiting period. The first rule is about the absence of leadership. Basically, silence or an absent response from a leader cannot quietly become permission. This is so important. Right. You cannot have a culture where a team submits an escalation, waits 48 hours, and says, well, the VP didn't reply to my email, so I assume the margin exception was approved.

[00:14:25] Passive approvals destroy risk management. Exactly. The mandate must explicitly state that no answer means no action. Exactly. And the second ironclad rule focuses on the technology itself. A system's ability to generate an answer does not establish permission to act on it. Right. Human and non-human workers can assemble the evidence, they can draft the proposal, they can show you the mathematically optimal path with stunning speed,

[00:14:51] but the authority to execute that path only comes from the mandate established by management. Going back to our analogy, just because the AI proves a certain restaurant has tables available and fits the budget, it doesn't mean the AI has the authority to put down the corporate credit card to hold the reservation. Exactly. The authority remains stubbornly human, dictated by the organizational design. Okay, so this raises a really important question regarding practical execution. Okay.

[00:15:19] You cannot just draft this mandate, put it in a binder, distribute it to your department heads, and just assume it works, right? Oh, definitely not. So delegation and organizational design have to be actively tested and adjusted. So for you listening, how do leaders actually test if this redesign is functioning in the real world? It's easy for an executive team to say they've empowered their teams, but the reality on the ground is often very different.

[00:15:45] Well, the author suggests a highly specific stress test for your next operating review. Okay, what does that look like? You identify one customer commitment that has repeatedly stalled in the past, maybe a specific type of complex service proposal. Yep. You bring the responsible leaders together in the review, and you force them to walk through the mechanics of two specific scenarios under the new mandate. Two scenarios. Right. One routine case and one difficult exception. So we are looking at the physical reality of the work here. Exactly.

[00:16:15] During that operating review test, we aren't looking at theoretical flow charts. We are measuring actual friction. Right. And you examine four primary measures. Okay. First, you look at elapsed time. Did the routine case actually move from conception to customer commitment faster? Got it. Second, you look at rework. Did we have to iterate the proposal five times because evidence owners were brought in too late, or was it handled concurrently? Okay. That's huge. Third, you look for avoidable escalations.

[00:16:44] Did minor variances get kicked up to the executive level that the mandate should have empowered the front line to handle? Right. And finally, you look for dependable commitments. Did we make a promise to the customer that our delivery teams can actually fulfill without heroic, unsustainable effort? So what does this all mean for the listener? Because I think it's vital to push back on these metrics for a second. Sure. We need to ensure we understand these are purely measures to test the mandate's health, right?

[00:17:12] These are not guaranteed returns just because you bought an enterprise AI license and wrote a new policy. That's exactly right. But a clearer mandate should make the operating result observable. Okay. If you have cleanly defined who has the authority to commit and who the evidence owners are, you should empirically see fewer avoidable escalations and a massive reduction in elapsed time. And if those improvements fail to materialize during the operating review test. Then that is a glaring signal.

[00:17:39] It means leaders need to investigate the structural design of the mandate itself. Right. So if the test fails, we can't just look at your department heads and tell them to collaborate harder. No. Or tell the team to be more innovative. Demanding a better attitude doesn't fix a broken system. Exactly. If there are repeated exceptions stalling the work, it usually indicates that the economic or capacity boundaries you drew were unrealistic to begin with.

[00:18:04] Or perhaps the baseline information your teams are feeding into the AI is unreliable, which is causing finance to just constantly reject the outputs. Right. Or quite often you find that an approval currently sitting with a director could safely be moved down to a frontline manager who actually understands the context of the work. So you fix the organizational design. Exactly. It is engineering the organization's behavior to match the speed of its technology.

[00:18:30] Because if your intelligence systems are working perfectly, but your process is still bogged down in week-long review cycles, the bottleneck is your mandate. Precisely. Intelligent systems bring unparalleled analysis and execution capacity, but they do not manage themselves. No, they don't. The chief executive must definitively establish who is empowered to use that capacity, who owns the evidence, and who answers for the consequences.

[00:18:57] That is the only way theoretical executive support for AI actually translates into a functional high-speed operating mandate. Absolutely. Absolutely. And for you listening, preparing for your next operating review, you really must bring this framework to the table. Yep. If you are trying to accelerate any process with AI, you have to answer five practical questions to ensure your mandate is real. Okay. Let's hit those five questions. Question number one. Question number one. Who decides?

[00:19:24] Meaning, who actually holds the authority to commit? Right. Question number two. What evidence must be present for them to make that decision? Question number three. Who has the legitimate right to challenge the decision, acting as an evidence owner? Question number four. Where does an unresolved disagreement go, and is the escalation bounded by options and consequences? And finally, question number five. Do the outcomes actually improve when we test it in the real world?

[00:19:52] Because if your organization cannot answer those five questions with absolute clarity, your investment in intelligent systems will simply result in generating the wrong proposals faster. Only to have them sit in the exact same approval cues. Exactly. If you want to dig deeper into the mechanics of making AI actually work within your operational structure, I highly recommend reading Michael Kleinberg's full insights. It's a great read. You can find this article, Who Owns the Decision When Everyone Supports AI?

[00:20:20] along with his broader frameworks for digital operations, at insights.meshdigital.io. It is an essential reality check for anyone attempting to bridge the gap between technological capability and business execution. It really is. Now, to wrap this up, I want to leave you with a final thought to mull over. Okay. We started this deep dive talking about the friction of giving up control. You know, we all love the idea of speed until it means we don't get to review the document first. So true. So consider this.

[00:20:49] If your new intelligent systems can generate complex, viable, mathematically sound solutions in a matter of seconds. Which they can. But your organizational hierarchy still requires three weeks to debate who is allowed to click approve. Yeah. Is your biggest bottleneck actually your legacy technology stack? Or is your biggest bottleneck a lack of executive courage to delegate authority? Until next time.

Digital transformation broadcast network

Follow Us on LinkedIn

Follow us on LinkedIn and be part of the conversation!

Powered by