Follow the Value: Turning Released Capacity into Enterprise Value | Deep Dive

[00:00:00] You know that feeling when you sit down for a quarterly review and every single department head has this beautifully polished slide deck proving just how much faster they become? Oh yeah. Everyone's got a chart going up and to the right. Exactly. I mean sales is moving faster, legal is suddenly processing contracts in record time, operations says they've improved utilization. Right, and finances somehow magically slashed all their administrative efforts. Right. Everyone at that table is absolutely crushing their internal KPIs.

[00:00:28] But then, you know, you look at the actual business metrics and the customer is still waiting just as long for delivery. Yeah, nothing's changed on the outside. Literally nothing. Critical decisions are still trapped in committee. And the underlying economics of the enterprise, they've barely moved a single inch. It is, I mean honestly it is the defining frustration for any operating leader right now. Yeah. You have this massive glaring disconnect where there is this absolute abundance of localized productivity, right?

[00:00:55] But zero change in the end-to-end outcome. You're basically running faster just to stay in the exact same place. Which is incredibly demoralizing. Everyone is crushing their KPIs, but the customer is still waiting. So today we're doing a deep dive into exactly why that happens. And how to fix it. Exactly. We're being guided by a really fascinating framework from Michael D. Kleinberg in his article, Follow the Value, where intelligent capacity creates real enterprise returns. It's a great piece.

[00:01:25] It really is. And the core thesis we're dissecting today, specifically for the operators listening, you know, the CEOs, COOs, and CFOs, is that making individual tasks faster does not automatically improve your end-to-end business outcomes. No, it absolutely doesn't. Right. That time and effort you just save by introducing AI or automation, which, by the way, we're going to refer to today as released capacity, that save time is essentially meaningless unless leadership deliberately gives it a destination. Meaningless.

[00:01:55] Which, you know, requires a pretty fundamental shift in how we actually view the organization. How so? Well, we've spent decades optimizing individual activities within vertical silos, right? We manage performance vertically through functional departments, through divisional budgets. Rigid reporting structures, yeah. Exactly. But value doesn't move vertically up and down an org chart. Value moves horizontally across the enterprise to actually deliver an outcome to the customer.

[00:02:21] So it sounds a lot like optimizing a single intersection in a busy city. Oh, I like that. Yeah. Like, you might tweak the timing of the traffic lights and get cars through that one specific intersection twice as fast. But if the very next light, just a block down, is still red... You haven't fixed the commute at all. Right. You haven't gotten anyone home faster. You've literally just taken the traffic jam and moved it 50 yards down the road. That is the perfect analogy.

[00:02:47] And the order-to-cash lifecycle is the perfect corporate representation of that traffic jam. Walk me through that. So a customer relationship starts in sales. Right. But then it has to move through contracting, fulfillment, invoicing, and finally collection. Each department owns its specific vertical slice. Right. So let's say the sales team implements a new generative AI tool, and they start churning out proposals twice as fast. Which they will absolutely brag about at the quarterly review. Oh, 100%.

[00:03:17] But if the legal department's contractual approval process remains the exact same bottleneck it was yesterday, those fast proposals just sit in a queue waiting. They just hit that red light you were talking about. Exactly. Or, you know, if you automate your invoicing process to make it lightning fast, it honestly doesn't matter if the physical orders are constantly getting delayed upstream in fulfillment. The customer still waits, and your cash flow remains exactly the same. Wow.

[00:03:42] So to create real enterprise returns, leaders have to follow the value stream horizontally from end to end. Yes. You have to trace the work from the initial trigger all the way to the final outcome. You have to identify exactly where the work waits, where it gets repeated. Where it crosses those organizational boundaries. Right. And where it consumes incredibly expensive human attention just to, you know, shuttle information from one silo to another. Okay. I want to push back on abandoning the vertical structure, though.

[00:04:11] Because, I mean, the vertical org chart is there for a very real operational reason. Sure. It creates clear accountability, you know, exactly who is responsible for the budget, who owns the risk, who handles compliance. If we just blur those lines and tell everyone to operate horizontally across the whole enterprise, doesn't operations risk turning into, like, the Wild West? That's a super valid concern. Because when everyone owns the process, no one owns the outcome. Right. And accountability is absolutely necessary.

[00:04:39] But we have to look at why those specific rigid boundaries were built in the first place. Okay. Many of these constraints and departmental handoffs, they exist because our processes were designed around workforce limitations that were established, like, 50 years ago. Oh, interesting. Yeah. We had to break work into these narrow departmental chunks because a human workforce can only process so much information at once. You needed a billing department and a shipping department because no single human could hold all that context simultaneously. That makes total sense.

[00:05:09] But we are no longer just dealing with a human workforce constraint. We're looking at intelligent capacity, meaning humans and AI working side by side, which means the old limits on how much data we can process at once have pretty much vanished. Oh, wow. So the constraints have fundamentally changed. We aren't limited by human cognitive bandwidth in the same way, meaning we don't actually need to chunk the work into those tiny vertical silos anymore just to make it manageable. That is the paradigm shift right there.

[00:05:39] Intelligent capacity gives operators the mandate to reconsider how work should function from beginning to end without being anchored by those historical constraints. Right. It doesn't eliminate accountability. It allows you to redesign the work so that accountability isn't constantly bottlenecked by fragmented information and legacy handoffs. Okay.

[00:05:57] So if we accept that these old boundaries are obsolete, I feel like the immediate temptation for a lot of executive teams is just, you know, buy a shiny new AI software license and overlay it right on top of the existing org chart. Which is a disaster. Right. They want to plug the new tech into the old machine. But if you inject AI into a broken supply chain or a fragmented value stream, you don't fix the chain. You just fail faster. You just fail much faster. Exactly. The work absolutely has to be redesigned first.

[00:06:26] So how do we do that? Well, Michael Kleinberg offers a really specific three-step framework for this operational redesign. And it's eliminate, flatten, and reinvent. Okay. Let's break those down. Starting with eliminate. Yeah. So starting with eliminate, we have to recognize that for generations, businesses have introduced all these approvals, reconciliations, and manual handoffs solely to compensate for fragmented systems. Like when two software platforms literally don't talk to each other? Exactly. So what do you do?

[00:06:56] You hire a person to download a CSV from one system, format it in Excel, and then upload it to the other. And then you inevitably hire a manager to double check that the first person didn't make a copy-paste error. Yes. And that is exactly what we have to stop doing. When you look at your value stream today, the first question shouldn't be, how do we use AI to make this reconciliation faster? Right. The question must be, why are we still reconciling this at all?

[00:07:21] If we fix the underlying data flow using intelligent capacity, the reconciliation task shouldn't be optimized. It should disappear entirely. So it's addition by subtraction. Stop redundant reporting. Eliminate the activities that only exist to serve the bureaucracy. Precisely. Which takes us to the second step. Flatten. Now, the classic corporate reflex when we hear the word flatten is to just, you know, fire a layer of middle management and call the organization agile. But I'm guessing this isn't just about the org chart, is it?

[00:07:51] Not at all. I mean, you can remove an entire layer of middle management tomorrow, but if the underlying operational processes still require the exact same approvals, the exact same escalations, and the same coordination between departments? You haven't actually solved anything. Right. The organization chart looks flatter on paper, sure, but the actual daily work remains just as complex, and now your remaining employees are just way more stressed out. Yeah, they're drowning. Exactly. What you actually need to flatten are the decisions.

[00:08:22] Flattening the decisions. Okay, let's unpack the mechanics of how that actually works in practice. Because historically, say, a sales rep wants to offer a custom discount. Okay. They have to email a manager. The manager takes, what, three days to pull the customer's lifetime value data, cross-reference the current margin requirements, and finally approve it. A classic bottleneck.

[00:08:42] But under this framework, an AI agent can instantly cross-reference that lifetime value data against the company's dynamic margin rules the literal millisecond the rep proposes the discount. Wow. The decision is flattened because the system does the reconciling instantly. You remove the manager from the routine loop entirely, not by firing them, but by designing the work so that routine progress happens continuously based on established logic. Which bridges us perfectly into the third part of the framework.

[00:09:12] Reinvent. Because this is the trap we've been falling into for 20 years, isn't it? Oh, big time. We've just been trying to digitize paper processes step for step. We take a form that used to sit in a physical manila folder on a desk, and we turn it into a PDF that sits in a digital email inbox. Yep. Same process, different medium. We just carry yesterday's complexity into tomorrow's enterprise. We shouldn't be asking where we can add AI. We should be asking what prevents the value stream from delivering its outcome instantly.

[00:09:42] Spot on. Imagine if order-to-cash-operated is one continuously coordinated process instead of a series of batch-processed handoffs. Human and non-human workers share information and context throughout the entire life cycle. Validations occur instantly as soon as the information becomes available rather than waiting for some end-of-week reconciliation report. So inconsistencies surface early. Exactly.

[00:10:13] That's what we're seeing. The entire process isn't running wild. The routine work flows on its own. But the consequential exceptions, the high-risk anomalies, the massive enterprise deals, critical supply chain disruptions, those are routed directly to the accountable human leaders. Yes. And when those exceptions actually reach the human leaders, they arrive with all the synthesized evidence and context needed to make a quick decision. You aren't asking the executive to hunt for the data. Exactly. You are presenting them with a fully prepared decision point.

[00:10:44] AI is really just a lever you pull when its specific capabilities can materially improve the redesigned operation. Sometimes, you know, just establishing clear ownership across the horizontal stream or simply rewriting an outdated company policy is more than enough to fix the constraint without touching a single line of code. That's such a good point. So let's follow this through to the ultimate operational reality. Let's do it. A leadership team actually pulls this off. They look horizontally. They eliminate the junk.

[00:11:14] They flatten the decisions. They reinvent the process with intelligent capacity. The enterprise successfully frees up a massive amount of time and effort. And the pilot is a runaway success. Sounds great. It does. But saving time is not the same thing as realizing financial value, is it? Time is just time until you allocate it. It is. And there is a really harsh economic reality to released capacity that leadership often overlooks during the hype of a technology rollout.

[00:11:41] The core rule here is that released capacity is simply an opportunity. An opportunity. Right. Realized value depends entirely on what the business deliberately chooses to do with it. Reducing administrative effort doesn't automatically reduce operating costs. Right. Because if you save a salaried employee 10 hours a week by automating their reporting, their salary doesn't suddenly drop by 10 hours. Nope. The payroll cost remains exactly the same unless you change how those 10 hours are utilized. Precisely.

[00:12:10] Let's map out the mechanics of this decision using an explicitly hypothetical example. And I really want to stress here, this is entirely hypothetical, purely to illustrate the strategic choices. We're not promising any specific real-world client result, endorsement, or guarantee of ROI here. Of course. Purely a thought experiment. Exactly. So imagine a hypothetical customer service team. They map their value stream. They redesign their workflow. They introduce intelligent capacity.

[00:12:39] And they successfully free up 20% of their team's capacity. Okay. So they are now finishing the exact same amount of work in 20% less time. Right. The question the executive team must answer is, what do they do with that newly released 20%? And they have distinct structural choices here. Three paths, specifically. Path one.

[00:13:03] Do they use that 20% to handle more incoming ticket demand without having to hire proportional headcount as the company grows? That's the efficiency play. Right. Path two. Do they use it purely to improve service speed, meaning they maintain the same volume, but ensure the customer gets an answer in five minutes instead of two hours? The quality play. Exactly. Or path three.

[00:13:27] Do they use that released time to create room for highly complex, higher-value advisory work that requires deep human judgment, empathy, and relationship building? The value play. And let's talk about why standard vendor ROI slides are so dangerous in this exact moment. Because usually when someone pitches a new automation tool, they just throw all three of those benefits onto the exact same slide. Oh, all the time.

[00:13:52] They tell the executive team, you're going to handle more volume and give lightning-fast service and transition your team to higher-value work. It's pitched as this magical byproduct of just buying the software. Which is a huge mistake. Those are not automatic benefits that occur simultaneously. They are mutually exclusive choices. Right. If our hypothetical service team deliberately chooses to spend their newly released time diving deep into complex, high-value advisory cases rather than just absorbing more daily ticket volume, that is a specific allocation choice.

[00:14:22] And it comes with trade-offs. Huge trade-offs. It means they will not get the hard headcount savings, but they might achieve a significant bump in customer retention and lifetime value. The right choice depends entirely on the specific constraint and strategic priority of the business at that given moment. And it requires an owner. Someone actually has to actively change how the work is allocated. Because if you just leave the saved time unmanaged, we all know exactly what happens. Parkinson's law. Exactly.

[00:14:50] Work expands to fill the time allotted. That 20% capacity will simply evaporate into longer coffee breaks, slower work paces, or employees just inventing new busy work to look productive. Yep. Allocating this capacity is a choice that heavily affects both the daily operations and the underlying economics of the firm. So it sits squarely on the desks of the COO and the CFO. They have to share an explicit agenda here. They do. It's essentially like having a joint checking account between operations and finance.

[00:15:19] You can't just have operations running around claiming they saved a million dollars by making a workflow faster, while finance is looking at the P&L and seeing expenses completely flat. Exactly. The operations team can't write checks on efficiency that finance refuses to cash. Both sides need to look at the ledger and agree exactly where those operational savings were deposited, whether that's into work and capital, into better contribution margins, or strictly into customer experience improvements.

[00:15:46] That alignment is totally non-negotiable before a single piece of software is deployed. The COO and the CFO need a rock-solid, common understanding of the operating baseline. And they need to know the full true cost of the redesign process, including the shadow costs. Shadow costs are the silent killers of these transformations. Oh, they really are. You celebrate automating a complex compliance form, but you ignore the fact that the IT department now has to spend 30 hours a week maintaining the bot, updating the API, and fixing breaks.

[00:16:16] Right. You didn't actually eliminate the work. No. You just hid the cost in the IT budget instead of the compliance budget. Exactly. A faster process isn't a better process if it suddenly creates unacceptable downstream errors that cost a fortune to remediate, or, you know, if it compromises internal controls. Quality and security must remain intact. So how does the CEO fit into this dynamic? This is where the CEO's role becomes the linchpin of the entire strategy.

[00:16:45] The recommendation here is not to try and boil the ocean or launch some massive company-wide AI transformation all at once. The CEO's role is to begin with one consequential value stream. Start small but meaningful. You define the specific business outcome of that single stream, and then you empower an accountable executive to redesign the work, giving them the explicit authority to knock down those functional departmental boundaries that are in the way. Exactly.

[00:17:13] You establish the baseline, you test the redesigned operation, and then you rigorously measure the performance before committing to any further expansion. Right. You review what actually happened with the freed capacity. Did it go where we planned? Did it improve throughput or margin or customer experience? And that review has to leave room for an honest operational answer because the evidence might completely support expanding the tool to other value streams. Sure.

[00:17:38] But the data might also reveal that the workflow needs further structural changes or that the capacity allocation decision was just wrong and needs to be adjusted. And realizing that an adjustment is needed doesn't mean the project failed. Right. It means the business case is functioning as a testable, actionable operating plan rather than just some ambitious pitch deck that gets forgotten the moment the vendor contract is signed. It connects the proposed technological benefit to a structural decision that a specific executive actually owns. Exactly.

[00:18:07] Resulting in an economic outcome that finance can actually verify. So to pull this all together, time saved is really just the starting line. Getting a task done faster is great, but a better end-to-end business outcome requires an owner. It requires a deliberate, horizontal plan for exactly where that released capacity should go, and it needs to be backed by hard evidence that demonstrates real improvement. Right. The ultimate measure of intelligent capacity isn't how many tasks you can automate.

[00:18:36] It is what the enterprise can accomplish differently and the tangible economic value it can prove. I want to leave you with a final provocative thought to mull over, taken directly from Michael D. Kleinberg. It's a question every operator should ask themselves the next time they look at their org chart. He asks, if you were designing your most important business processes today with intelligent capacity available from the outset, how many would resemble those you're running right now? It is the fundamental question. It is.

[00:19:05] And it's the one that separates the enterprises that will merely run a little faster from the enterprises that will fundamentally change their operating economics. Absolutely. If you want to dig deeper into these concepts and start mapping your own horizontal streams, you can read Michael Kleinberg's full article, Follow the Value, by clicking the link right there in the episode description. Take a hard look at your value streams, find those red lights, and make sure your released capacity actually has a destination.