Modern Organizational Design: The Capability Shift & Agility

Lena: Hey everyone! I was just thinking about those old organizational charts—the ones that lived in dusty three ring binders or static PowerPoint slides. You know the ones, where by the time the ink was dry, the actual team had already changed . It’s kind of wild how much that model has broken down just in the last couple of years.

Miles: It really has. We’re living in a world now where if you aren’t redesigning your organization in real time, you’re basically falling behind. Today is May 7th, 2026, and the data coming out of the latest research is staggering. McKinsey just released their State of Organizations report, and they’re seeing these massive tectonic forces—everything from AI infusion to geopolitical fragmentation—completely rewriting the rules of how we work .

Lena: Tectonic forces—that sounds intense. But it makes sense. I mean, we aren't just talking about a few tweaks to the HR manual here. We're talking about a fundamental shift in what it means to be a "high performing" company. I saw a stat that says 67% of leaders now believe their primary competitive advantage over the next three years will be speed and agility, not just scale .

Miles: Exactly. It used to be that being the biggest player in the room was enough. Now? It’s about being the most nimble. And the bridge between that high level strategy and the actual work being done is something called the capability framework. It’s not just a list of skills—it’s the "secret sauce" for how an organization actually achieves its goals .

Lena: So, if you’re a leader listening to this, or even just someone trying to navigate your own career, this is the blueprint. We’re going to move past the jargon and look at how companies like Levi Strauss or Walmart are actually using these frameworks to outpace everyone else .

Miles: We’re going to break down why your old workforce plans are likely outdated and how AI is actually becoming a "digital worker" sitting right next to us in the org chart .

Lena: I love that. Let’s get into the "why" behind all this chaos—and more importantly, how to actually structure a way through it.

Miles: To really understand why organizational design is suddenly so urgent, we have to look at those tectonic forces McKinsey identified. The first one is the "infusion of technology." We aren't just talking about using a new software; we’re talking about AI, automation, and data analytics reimagining the very end to end processes of a business .

Lena: And it’s not just tech for tech’s sake. It’s forcing companies to rethink traditional structures because AI, automation, and data analytics are leading organizations to reimagine how work gets done, redefine domains and end-to-end processes, and rethink traditional structures.

Miles: Precisely. Then there’s the second force—economic disruption and geopolitical uncertainty. It’s increasing complexity at a rate that makes old, centralized planning impossible. You have to be able to adapt sustainably, not just reactively .

Lena: I think the third force is the one people feel most personally—evolving employee expectations and shifting demographics. People want more than just a job; they want meaningful work. And they expect the organization to transcend those old, rigid structures to provide it .

Miles: That shift is huge. The 2026 research shows that the emphasis has moved from just "surviving" a crisis to "sustained productivity." It’s about long term impact powered by technology at the core .

Lena: It feels like the "performance edge" has changed. It’s no longer about short term gains. If you want to stay relevant, you have to find value amid all this uncertainty .

Miles: That’s a great way to put it. We’re seeing leaders move away from that "locked in" resource model. In fact, more than half of leaders—about 58%—now say they prefer to shape strategy through frequent experimentation at the ground level rather than through some grand, centralized plan .

Lena: So, the strategy is emerging from the work itself? That is a massive shift for anyone who grew up in the era of the five year plan.

Miles: It really is. It’s about moving from "planning" to "orchestration." And that’s where the capability framework comes in as the engine for all that movement.

Lena: Okay, Miles, help me out here. I often hear people use "capability" and "competency" interchangeably. Is there actually a meaningful difference, or is it just corporate wordplay?

Miles: It’s a huge distinction, actually. Think of it this way: a "competency" is about an individual's performance—it’s the specific skills and knowledge someone needs to do their job effectively . It’s very role specific and mostly used for things like performance reviews .

Lena: So, "Lena is good at data analysis" is a competency?

Miles: Exactly. But a "capability" is the organization’s collective potential. It’s the capacity to apply those competencies across different contexts to deliver a strategic outcome . Capabilities are broader and much more stable than individual skills, which can expire pretty quickly these days .

Lena: I like that. So a capability is more like "The organization can reliably launch new products in under six months." It’s the combination of people, tools, processes, and culture .

Miles: Spot on. Capabilities are the building blocks of the business architecture . While a skill might be a "short term, fast expiring" thing, a capability is a long term, stable grouping that enables things like talent mobility and workforce planning at scale .

Lena: That makes sense. If I know my organization has a strong "digital marketing" capability, I can move people around more fluidly than if I just have a bunch of rigid "Social Media Manager" job descriptions.

Miles: That’s the "orchestration advantage." You’re moving away from "who reports to whom" and toward "what can we actually do" .

Lena: And it sounds like the goal of a modern framework is to bridge that gap between human potential and business value . If you can’t tie a capability back to a measurable business outcome, like customer satisfaction or reduced costs, you have to ask why it even exists in your framework .

Miles: That’s a powerful filter. It forces the design to stay grounded in impact rather than just theory.

Lena: You mentioned "orchestration" earlier. It sounds very musical, but what does it actually look like for a business?

Miles: Deloitte uses a great analogy for this. They say "allocation" is assigning a musician to play a specific part. But "orchestration" is the conductor’s role—adjusting everything in real time to deliver the outcome .

Lena: So it’s less about a fixed structure and more about fluidly reconfiguring your people and tech as conditions change?

Miles: Exactly. And AI is the "exponential multiplier" here. We used to think of a "speed, quality, and cost" triangle where you could only pick two. But AI is creating a new frontier where you can improve all three at the same time .

Lena: Wait, all three? That’s usually impossible in business strategy.

Miles: I know! But look at how some companies are doing it. Scaling no longer automatically requires more people or more spending. You’re seeing "AI companies" that are essentially small human teams doing high leverage work, simulating the operations of a massive firm .

Lena: It’s like the difference between "humans plus machines" and "humans times machines" .

Miles: That’s exactly how they phrase it. Take Levi Strauss as an example. They used AI to sense "weak signals" that baggy jeans were becoming a trend. They rapidly brought together designers, merchants, and marketing teams—essentially orchestrating their capabilities—and increased sales in that category by 15% in just three months .

Lena: That is fast. But it sounds like most companies are still struggling to actually do this.

Miles: They are. There’s a massive gap. In a 2026 survey, 88% of leaders said dynamic orchestration is extremely important, but only 7% feel they’re making great progress . That’s an 81 point difference—the largest gap in the entire study .

Lena: Wow. So everyone knows they need to be a conductor, but most are still just handing out sheet music to individual players.

Miles: And that’s why we need to talk about how to actually build these frameworks so they support that kind of movement.

Lena: So, if I’m ready to build a capability framework that doesn't just sit in a binder, where do I start? What’s the "anatomy" of a good one?

Miles: Think of it as a layered system. At the top, you have "Capability Sets"—broad, functional groupings like Finance, HR, or even something strategic like "AI Fluency" .

Lena: Okay, so those are the big buckets. And then you drill down?

Miles: Right. Under those sets, you have the actual "Capabilities"—the specific skills, behaviors, and knowledge required. Usually, you want about 12 to 25 of these per set to keep it manageable . The key rule here is that they must be unique. You don't want to duplicate them across different sets, because that just leads to "assessment chaos" and "reporting distortion" .

Lena: I can see that. If I'm being rated on "communication" in three different places, I'm going to get "framework fatigue" pretty fast .

Miles: Exactly. Then, the third layer is "Proficiency Levels." This is where you define what "good" looks like. Most experts suggest four to six levels—five is usually the "sweet spot" .

Lena: And you want those levels to show a clear progression, right? Like moving from "Foundational" to "Expert."

Miles: Yes, and that progression is usually measured by three things: how much independent judgment you use, the complexity of the tasks, and the scope of your influence . A "Foundational" person might just share their own knowledge, while an "Expert" is leading organization wide reform .

Lena: I’ve noticed some organizations use different labels for these.

Miles: They do. Some use the "Dreyfus" model, which goes from Novice to Expert based on situational awareness . Others use a simpler linear scale. The important thing is that the "Proficiency Level Descriptors"—the actual sentences describing the behavior—are clear and observable .

Lena: It’s basically about making the abstract concrete. If I can see the behavior, I can measure it.

Miles: And if you can measure it, you can move talent to where it’s needed most. That’s how you get that "plug and play modularity" where you can assemble mission driven teams on the fly .

Lena: We've talked about building the framework, but how do we actually fill those capability gaps once we find them? I remember the old "Build, Borrow, or Buy" model, but it feels like that might be too simple now.

Miles: It definitely is. We’ve actually added a fourth "B" to that list: "Bot" .

Lena: "Bot"? As in AI agents?

Miles: Exactly. 56% of leaders now say they organize and evaluate AI agents as digital workers . So when you have a gap, you’re not just asking "Do we train someone (Build), hire a contractor (Borrow), or hire a full timer (Buy)?" You’re also asking, "Can an AI agent do this (Bot)?" .

Lena: That changes the whole math of workforce planning. But I imagine it’s not always a choice between a human and a bot.

Miles: Right, there’s also the "Blend" strategy. This is where AI acts as that exponential multiplier for human workers. Think of doctors using AI to detect diseases earlier and more accurately than either could alone .

Lena: I love that "humans times machines" concept. But what about the people already in the building?

Miles: That’s where "Bridging" comes in. This is about unlocking talent across organizational boundaries—moving people into temporary assignments or agile, mission driven squads . Cisco’s VP of People, Megan Bazan, actually said that "the static team is becoming a thing of the past" because of this rapid mobilization .

Lena: And then there’s "Break," right? Redesigning the work itself?

Miles: Exactly. Look at the Cleveland Clinic. They had a healthcare talent shortage, so they "broke" the role of a medical assistant down into 40 tasks. They realized 37 of those could be done by non clinical staff or automated. It created the capacity equivalent of 430 full time employees and saved over $2 million .

Lena: That’s incredible. It’s not just about finding more people; it’s about freeing up the people you have to do the work that actually matters.

Miles: And that’s the heart of modern organizational design. It’s a move away from "managing headcount" to "orchestrating capacity" .

Lena: Okay, so we have the framework, and we have our strategies for filling gaps. But how do we keep this from becoming another "dusty binder" situation?

Miles: The secret is "Always On" planning. We have to retire the spreadsheets . In 2026, the model where HR and Finance build a plan in a vacuum once a year is completely broken. AI and real time data are changing "who plans" and "how they plan" .

Lena: So, instead of a static chart, we’re looking at something more dynamic?

Miles: Exactly. Companies are starting to use "Digital Twins"—live, AI powered models of their entire workforce . It lets them simulate scenarios. Like, "What happens to our talent needs if we shift our location strategy to Brazil instead of India?" or "What if we increase our AI investment?" .

Lena: That sounds like a flight simulator for business leaders.

Miles: It really is. And it’s not just for the C suite. Companies like Mastercard and Standard Chartered are using orchestration platforms where every worker can see tasks, skills, and AI "performers" . If a project needs a specific skill, the system identifies the right person and the right AI agent to get it done in real time .

Lena: That’s amazing. It democratizes the design process.

Miles: It does. And it builds accountability. It’s hard to feel responsible for a plan you had no part in making. But when managers at every level have the tools to make these decisions, the plan actually lives in the "rhythm of the business" .

Lena: It’s moving from "PowerPoint planning" to "Dynamic Visual Planning." You can instantly see how moving a box on the screen affects costs, spans of control, and even turnover risk .

Miles: And that’s why 61% of organizations now say they align and deploy workers based on tasks, skills, and outcomes . We’re finally seeing the "org chart" evolve into a "mission driven network" .

Lena: We’ve covered a lot of ground. For anyone listening who’s feeling a bit overwhelmed, let’s boil this down. What are the concrete steps to actually start building this "future ready" organization?

Miles: Step one: define the mission. Start with the business outcomes you want to achieve, not your current reporting lines . If your goal is "faster innovation," your capability framework needs to be built around the skills and processes that drive that, across every department .

Lena: Step two: map your capabilities. Use that layered approach we discussed. Capability sets, specific capabilities, and then five levels of proficiency . And remember, keep them unique—no duplicates!

Miles: Step three: assess your maturity. Be honest about where you are versus where you need to be. Are you "lagging," "performing," or "leading" in each critical capability? . This is where you involve your managers—they know the systems and the people better than anyone .

Lena: Step four: activate the "Four Bs." Once you see the gaps, decide if you’re going to Build, Borrow, Buy, or use a Bot . And don't forget the "Blend"—how can AI make your existing team more powerful?

Miles: Step five: move toward "Always On" planning. Look for tools that connect your workforce data to your source of truth in real time . You want to be able to run scenarios and see the financial impact of your design choices instantly .

Lena: And a quick pitfall to avoid: don’t make it too complex. A 5 level framework with detailed descriptors is great for precision, but if it’s too "heavy" for a manager to use during a busy week, it’s going to fail . Adoption is more important than perfect complexity.

Miles: That’s a great point. The goal is to create a shared language, not a PhD thesis. If everyone in the company understands what "Advanced" looks like for a specific capability, you’ve already won half the battle .

Lena: So, as we wrap things up, I’m struck by that one quote from Jon Pitts—the CEO who used the Formula 1 analogy. He said, "All functions, data streams, sensors, and analytics are unified around a single mission: making the car go fast and stay fast" .

Miles: "Egos are set aside as everyone collaborates in real time." That really captures the spirit of what we’re talking about, doesn't it? . It’s not about who has the biggest office; it’s about how all the parts of the machine work together to hit the goal.

Lena: It’s a big shift—moving from being a "planner" to being an "orchestrator." But given that 2026 is already proving to be a year of massive disruption, it feels like the only way to stay in the race .

Miles: We’ve seen that the organizations winning right now are the ones that can turn unpredictability into momentum . They aren't just reacting to change; they’re built for change.

Lena: To everyone listening, I hope this gives you a clear path forward. Maybe your first step is just looking at one key team and asking, "If we had to double our output without hiring, what work would we have to 'break' or 'bot'?"

Miles: Or even just starting the conversation between HR, Finance, and IT to get onto a single "source of truth" for your people data .

Lena: Thank you so much for joining us for this deep dive. It’s a fascinating time to be thinking about how we organize human and digital potential.

Miles: Take some time to reflect on your own organization’s "car." Is it built for the track you’re on today, or are you still working from that three ring binder?

Lena: We’ll leave you with that. Thanks for listening.