The OD Fit Problem: Why More Capability Won’t Fix What’s Broken
Photo by thinkstock_images on FreeImages
The majority of organizational development (OD) leaders tend to share a similar set of priorities, mostly focusing on stronger diagnostics, better change frameworks, and earlier seats at the table to raise crucial questions.
And while those priorities are sound, what’s harder to see from inside the function is the second variable running alongside capability, which is how the work gets activated in the first place.
The two diagnostic tools we’ve built give practitioners a way to look at both at once.
What the Field Keeps Telling Us
Before we created the tools to help address an organization's OD needs, we anchored it to the three patterns we've observed that often came up in these conversations:
A mismatch of size and scope.
A small OD team, sometimes fewer than ten people, is responsible for org design, culture, change enablement, diagnostics, and leadership development across an organization of fifty or a hundred thousand employees. And org design tends to be the heaviest piece of that load.
The timing of when OD gets brought in.
By the time a senior leader reaches out, the decision about what to do has already been made. The team is asked to execute, communicate, or clean up after a choice they had no hand in shaping, and the people doing that work want the exact opposite, which is to be in the room when the question is still open.
How the function's priorities get set.
The work that lands on OD's plate tends to come from whichever senior leader pushed for it hardest in the most recent meeting, not from any reading of where the organization is struggling. The engagement survey results and the diagnostic data that could tell the most accurate results sit in a dashboard nobody opens.
Outside our conversations, broader research points in the same direction.
The World Economic Forum’s Future of Jobs Report 2025 found 63% of employers now name skills gaps as their primary barrier to business transformation, ahead of regulation, infrastructure, and capital. By 2030, 39% of core workforce skills are expected to change. A 2024 review in the Journal of Management, looking across two decades of organization design research, frames a related point, discussing how the field is not converging on one best way to organize. Designs are competitive choices made under contingencies that keep moving, which means the work of getting the design right is never finished.
Skills disruption and structural misfit are OD's territory, and the demand on that territory has outgrown how most OD functions get activated.
Start with the Disconnect, Not the Capability
When attempting to design OD programs, most teams skip the first question. They go straight to "what should we build?" before they ask, "what are we being asked to address?" In fact, the order matters because the answer to the second question changes what the first one means.
Capability without a clear disconnect produces deliverables that nobody can tie to a business outcome.
Step one of the OD Capability and Alignment Tool defines four disconnects we see often inside large organizations. Each describes a specific way an organization's strategy fails to land, and the practitioner's first job is to identify which one the work in front of them is about.
The most structural of the four is Strategy-to-System.
It sounds like a leader saying, "We know where we're going, but the way we're organized works against it." Strategy and structure are out of sync, which puts the work in operating-model territory: org design, role clarity, governance, decision rights.
When the strategy is sound, and the structure is sound, but something still feels off, the disconnect is Diagnosis-to-Action.
A leader knows the system isn't performing, but they cannot put a finger on why. The work here is investigative before it is anything else, requiring data interpretation, sensemaking, and facilitation that helps the leadership team converge on what they are looking at.
A third disconnect shows up further downstream, after the diagnosis is in hand.
Siloed Solutions is the pattern where the right initiatives exist, but they were built in isolation, by different teams, on different methods, and they collide instead of compounding. A leader's version of this sounds like "we have the pieces, but they aren't working together." The work shifts to integration: shared methods, common standards, and a shared view of what the change is trying to do.
The fourth disconnect is the one most OD leaders feel before they can name.
Scale-and-Capacity is what happens when the demand on OD outruns what a small team can carry, and the question stops being "what should we build?" and starts being "how do we extend the work without losing its quality?" The answer involves leader-enabled tools, clear governance, and a small set of priorities the team will defend.
Naming the disconnect first changes what comes next. The team stops asking which capability to build and starts asking whether the work they have been handed matches the posture they bring.
Test the Fit
Once the disconnect has been identified, it's time to test the fit using two reference postures, with a hybrid in between.
A team operating in a Localized and Responsive posture adapts to what the people closest to the work need, moves quickly, and treats each engagement as its own contract with that part of the business. A team in an Integrated and Systemic posture works at the level of the operating model. They sit with senior leaders on questions that cross boundaries, and they look across the system for patterns that keep repeating. Neither posture is more advanced than the other. Those two are the different operating modes for different kinds of disconnects.
What’s more costly for the organization is when the match is wrong.
A team built for systemic work gets pulled into bounded firefighting, and its senior practitioners start to disengage from work that feels small relative to what they can do. The strategic questions they were brought in to address keep getting handed to other parts of the business.
The reverse mismatch happens just as often. A responsive team picks up a cross-enterprise mandate it has neither the relationships nor the standing to land, and the work it does well becomes harder for leaders to point to. In both cases, the team has the capability to do good work. The missing piece is somewhere between posture and brief. That is why step two has to come before any conversation about what to build. When posture and disconnect do not match, the lever to pull is renegotiating what OD takes on, or how it takes it on, before deeper investment in capability changes the picture.
Map the Gap, Choose the Move
Once posture and disconnect are aligned, the work moves to capability. The tool walks a practitioner through twelve areas an OD function might own, partner on, or support:
Org design
Role clarity
Diagnostics
Change enablement
Team effectiveness
Leadership alignment
Culture work
Facilitation
Survey insights
Impact storytelling
Shared methods
Leader capability building
For each area, the practitioner rates current strength against needed strength, then picks one of those three roles.
The first time a team works through this map, the temptation is to chase whichever area scored lowest. We have learned to push back on that instinct. The capability that matters is the one this disconnect requires, and the ratings get most useful when a team reads them through the disconnect they identified in step one. A team whose disconnect is Strategy-to-System needs strong org design and decision-rights work, even when their facilitation rating sits higher on the page. Context sets the priority. The map gives the team something concrete to bring into the conversation with the leaders who set that context.
From there, the tool offers six moves a team can make in response to what the map shows:
Clarify scope: Name what OD leads versus what the team partners on or does not own at all.
Build capability: Strengthen a specific area that the disconnect requires.
Create governance: Set intake, prioritization, and shared standards.
Move upstream: Use contracting questions to shape the brief before the work begins.
Tell the impact story: Shift the metrics OD reports against from activity to alignment, decision quality, and behavior change.
Scale through others: Equip leaders with the tools and methods to do parts of the work themselves.
Four of those six address fit before they address capability, and the ratio is deliberate.
The Canvas as a Mirror
The Capability Mapping Canvas is the companion piece to the Alignment Tool. Where the Alignment Tool runs the diagnostic on a single piece of work, the Canvas plots the OD function against the three field-level patterns we named earlier, plus a fourth quadrant that holds a measurement gap running underneath all of them.
The score itself is not where the value sits. We have watched OD leaders fill the Canvas out in fifteen minutes and then spend the next hour in a different conversation with their CHRO about what OD should own, what it should partner on, and what the function should stop carrying alone. That hour is what moves the function forward. The Canvas exists to start it.
There is also a field-level signal worth pairing with this. The OECD’s 2024 Survey of Public Servants, conducted across central government workforces in ten countries with nearly 57,000 respondents, found that learning and development is the most impactful driver of employee engagement and well-being, alongside leadership quality. The setting is public-sector, but the signal travels. For an OD function trying to make a case for the work it does, this kind of evidence is useful: capability building, when employees experience it firsthand, registers as a serious investment in the workforce. The Canvas opens the conversation; data like the OECD’s gives the conversation somewhere to go.
Final Reflection for Practitioners
The line we keep returning to from the tool is the one we want to leave you with: “Effective OD is not about having more capabilities. It is about matching capability to context.”
To understand whether your OD function is positioned for the work in front of it, do not start with the capability map, but with the disconnect.
Sit with these questions before reaching for a build:
What is the disconnect we are being asked to address right now? Strategy-to-System, Diagnosis-to-Action, Siloed Solutions, or Scale-and-Capacity?
Does the posture our team brings, localized or integrated, fit that disconnect, or are we being misused?
Where is the system around us pulling us toward work we are not built for, and where could we make the case to be brought in earlier?
Of the six next moves on the table, which one would do more for our usefulness than another round of capability building?
Key Takeaways:
Capability is rarely the missing piece. Most OD functions carry the skills they need; the misalignment is between posture and the work on the table.
Fit is the diagnostic question to lead with, not maturity. Localized and integrated postures are different choices, not different stages.
The Canvas opens conversations, not scorecards. The hour leaders spend on the conversation it triggers is what moves the function forward.
