Organizational Development Consulting: Why Most Change Fails
Updated: Oct 3
(And What Actually Works)
Dr. Yinnon Dryzin-Amit is the founder of PublicWise, former Senior Division Head for Systemic Organizational Development at the Israel Courts Authority, and a lecturer in the MA program in the Department of Sociology at the University of Haifa. His research has been published in PLOS ONE, Journal of General Management, and The Journal of Applied Behavioral Science.
The conference room had floor-to-ceiling windows overlooking Tel Aviv. Twenty-three people sat around the table as the new executive director presented a slide titled “Our Path Forward.” People nodded. But the room did not feel aligned. It felt exhausted.
As the organizational development consultant working with the organization, I had begun to notice a familiar gap: the formal conversation suggested agreement, while the conversations outside the room told a different story. Within weeks, mounting turnover and the departure of key leaders forced a question that the organization had been avoiding: What is actually holding us back?
That question changed the direction of the work. The organization did not lack a strategy. It did not lack intelligent people or committed leaders. And another training program, restructuring exercise, or communication initiative would not necessarily have addressed what was happening. Before choosing an intervention, we needed to understand the system producing the symptoms.
*This case is drawn from my organizational development practice. Names and identifying details have been changed to protect confidentiality.
The Visible Problem May Not Be the Real Constraint
This is one of the central challenges in organizational development consulting: organizations usually seek help because they can see a problem, but the problem they can see is not necessarily the constraint they need to address. Low engagement may reflect a leadership problem — or conflicting priorities, poorly designed roles, weak coordination, or a loss of trust. Slow decision-making may be caused by bureaucracy — or by unclear authority, competing accountabilities, or leaders who have learned that taking initiative carries more risk than waiting. A strategy may fail in execution not because employees resist change, but because the organizational conditions required to enact it were never built.
This is why effective organizational development begins with inquiry rather than a predetermined solution. Contemporary OD includes both diagnostic traditions that examine organizational conditions and dialogic approaches that change how organizational members collectively make sense of their reality [2]. More recent evidence from 317 OD and change-management projects similarly found that higher-impact practitioners were more likely to diagnose what was distinctive about the client system, attend to behavior patterns linked to performance, adjust the scope and pace of change to organizational capacity, and tailor interventions to the circumstances rather than rely on standardized programs [6].
Diagnose before you prescribe.
That principle sounds simple. In practice, it changes the consulting question from:
Which intervention should we implement?
to:
What is happening in this system — and what kind of change does the evidence actually call for?
That is where organizational development consulting begins.
What This Guide Will Help You Understand
This guide examines organizational development consulting from both research and practice. It addresses five questions that matter when an organization knows something needs to change but is not yet certain what:
What is organizational development consulting — and what makes it different from a predefined change program?
Why do apparently well-designed organizational changes still stall?
How can diagnosis distinguish visible symptoms from underlying system constraints?
When does an organization need OD consulting — and when would another intervention be more appropriate?
How can OD build the organization’s own capacity to learn, adapt, and sustain change after the consultant leaves?
The aim is not to offer another universal change model. It is to show how organizational development can help leaders understand the system they are trying to change before deciding how to change it.
What Is Organizational Development Consulting?
Organizational development (OD) is sometimes mistaken for a collection of activities: leadership workshops, team-building sessions, employee surveys, culture initiatives, or executive coaching. Any of these can be part of OD. None of them, by itself, defines it. At its core, organizational development is a systematic effort to improve organizational effectiveness by working with the relationships, processes, structures, capabilities, and patterns of behavior through which an organization functions and changes [1]. That distinction matters.
If a team lacks a specific skill, training may be the right intervention. If a process is inefficient, process redesign may solve the problem. If a new system needs to be implemented, change management may help people adopt it. But organizational problems are often less contained. A leadership problem may also be a role-design problem. A coordination problem may reflect competing incentives. Low engagement may be connected to workload, decision rights, trust, or a gap between what the organization says it values and what employees experience in practice. In these situations, intervening in the most visible symptom can leave the conditions producing it largely unchanged.
OD Consulting Starts With the System
Organizational development consulting therefore begins by asking not only:
What needs to change?
but also:
What in the organization is producing the current pattern?
This requires looking across levels rather than treating people, teams, structures, and strategy as independent problems. The consultant may examine leadership behavior, decision processes, organizational structure, formal and informal roles, relationships across boundaries, patterns of communication, organizational culture, and the way employees interpret what the organization expects and values. The purpose is not to diagnose everything. It is to identify the conditions that matter most for the organizational outcome the client is trying to change.
This systemic orientation has deep roots in OD. Classic definitions emphasize planned change grounded in behavioral science [1], while later scholarship distinguishes between diagnostic OD, which seeks to understand how organizational conditions contribute to current outcomes, and dialogic OD, which focuses on how conversations, narratives, and collective meaning-making can generate new possibilities for action [2]. These traditions need not be treated as competing alternatives. In complex organizational work, diagnosis can help identify consequential patterns in the system, while dialogue can help organizational members interpret those patterns, challenge assumptions, and construct different ways of working together.
The Consultant's Role Is Not to Arrive With the Answer
This is also why OD consulting differs from consulting approaches built around implementing a predetermined solution. The consultant brings expertise in diagnosis, organizational behavior, change processes, facilitation, and intervention design. But expertise does not mean assuming in advance what the organization needs.
The work is iterative: gather evidence, make sense of it with the people who know the system from the inside, design interventions that fit the diagnosis, observe what happens, and adapt.
My longitudinal research on OD consulting illustrates how this can develop over time. Across a six-year organizational transformation, the analysis identified three interconnected mechanisms through which OD consulting supported change: adaptive spaces, where difficult issues could be surfaced and examined; emergent capabilities, developed through cycles of action and reflection; and systemic integration, through which new practices and learning became connected across organizational levels [3]. The important point is not that every organization should reproduce these particular interventions. It is that sustainable organizational change requires more than selecting the right workshop, structure, or methodology. The intervention needs to fit the system — and the organization needs to develop greater capacity to understand, adapt, and act on that system itself. That is the difference between delivering an intervention and building organizational capability.
Why Organizational Change Fails —
Even When the Strategy Makes Sense
Organizational change does not fail for one reason. Sometimes the strategy is flawed. Sometimes leadership is inconsistent. Sometimes structures, incentives, capabilities, or resources do not support what the organization is asking people to do. And sometimes employees interpret the proposed change very differently from those leading it.
That last point matters. Research on organizational change increasingly treats employee responses not as a simple choice between “support” and “resistance,” but as multidimensional and shaped by the change itself, its context, leadership, individual differences, time, and the way people make sense of what is happening [7]. This makes one of the most common explanations for failed change — people resist change — insufficient. Resistance may be part of the picture. But treating it as the diagnosis can obscure the organizational conditions producing it.
When an Implementation Problem Is Really a System Problem
Consider a strategy that requires greater collaboration across departments. Leadership communicates the strategy clearly. New cross-functional meetings are introduced. Managers are told to collaborate. Progress is monitored. And yet the silos remain. The immediate conclusion may be that managers are territorial or resistant. But diagnosis might reveal something different: performance targets still reward departmental results; decision rights remain concentrated within functions; information does not move easily across boundaries; leaders are held accountable for outcomes they cannot control; or previous attempts at collaboration have taught people that cooperation creates personal risk without corresponding authority. In that situation, more communication about collaboration is unlikely to resolve the constraint. The organization is asking for one behavior while parts of the system continue to reinforce another.
This is why organizational change cannot be understood only as the implementation of a plan. Employee responses to change emerge from an interaction between people and context, and can include support, resistance, ambivalence, or combinations of reactions that develop over time [7].
The Cost of Diagnosing Too Quickly
Organizations under pressure understandably want solutions. A leadership team sees low engagement and commissions leadership training. Slow decisions trigger a restructuring. Conflict between units produces a team-building intervention. A culture problem leads to a new set of values.
Each intervention may be useful. But only if it addresses conditions that are materially contributing to the problem. Otherwise, organizations can become very active without becoming more effective. The risk is not simply choosing the “wrong” intervention. It is creating repeated cycles in which initiatives are launched, initial energy fades, underlying patterns reappear, and the organization concludes that employees — or the latest change program — are the problem.
Evidence from OD and change practice reinforces the value of a more contingent approach. A recent study examining 317 organizational development and change-management projects found that practitioners associated with stronger evidence of positive impact were more likely to diagnose what was distinctive about the client system, connect behavioral patterns to performance, and adapt the scope, pace, and intervention to organizational circumstances [6]. The implication is not that diagnosis can eliminate uncertainty. It cannot. The implication is that intervention should follow a sufficiently credible understanding of the system rather than substitute for one.
From “How Do We Implement This?” to “What Is Constraining It?”
This distinction becomes particularly important when the desired change is clear but repeated attempts to produce it do not hold. At that point, the useful question may no longer be:
How do we get people to adopt the change?
It may be:
What conditions in this organization make the desired behavior difficult to enact or sustain?
That question opens a wider diagnostic field.
It may lead to leadership.
It may lead to structure.
It may lead to capabilities, incentives, workload, decision rights, psychological safety, relationships across organizational boundaries, or the meanings people attach to the change.
Often, it leads to interactions among several of them.
This is where organizational diagnosis becomes more than a preliminary consulting step. It becomes a way of distinguishing the intervention the organization initially requests from the change the system may actually require.
When Do You Actually Need
Organizational Development Consulting?
Not every organizational problem requires organizational development consulting. If the problem is a clearly defined technical failure, fix it. If employees lack a specific skill, training may be sufficient. If a project has clear objectives but weak execution discipline, stronger project management may be the answer. And when the destination is already defined and the primary challenge is implementation and adoption, change management may be particularly useful.
OD consulting becomes more relevant when the problem is systemic: when several parts of the organization interact to produce an outcome, when the source of the problem is unclear, or when repeated attempts to change something do not produce lasting results.
Here are six situations in which organizational diagnosis is particularly valuable before deciding what to do.
1. Growth Has Outpaced the Organization
A company grows rapidly. Decisions that once required a hallway conversation now require several meetings. Founders or senior leaders become bottlenecks. Roles overlap. Coordination becomes slower. Employees say that the organization has “lost what made it special.” It is tempting to call this a structure problem and redraw the organizational chart. Sometimes that is exactly what is needed.
But growth can simultaneously affect decision rights, managerial capability, communication, identity, coordination, and informal relationships. The diagnostic task is to determine which of these conditions is actually constraining the next stage of development — and how they interact.
2. The Strategy Is Clear, but Execution Keeps Stalling
The strategy has been discussed, approved, communicated, and resourced. Yet months later, priorities compete, decisions drift, and different parts of the organization interpret the strategy differently. The immediate response is often another round of communication or tighter performance monitoring. But persistent execution gaps may indicate something else: unclear priorities, competing accountabilities, weak coordination across units, insufficient capability, or a strategy that has never become meaningful enough to guide everyday decisions. The question is no longer simply whether people understand the strategy. It is whether the organizational system enables them to enact it.
3. Silos Are Undermining Performance
Marketing blames Sales. Headquarters blames the field. Professional groups optimize their own work while the organization as a whole struggles to coordinate. Silos are often described as an attitude problem. But telling people to collaborate rarely changes the conditions under which collaboration occurs.
Boundaries can be reinforced by structures, incentives, professional identities, information flows, competing goals, and histories of mistrust. Effective intervention therefore requires understanding what makes working across those boundaries difficult — and what would make coordinated action possible.
4. A Major Transformation Changes More Than the Process
A merger, restructuring, digital transformation, new operating model, or significant strategic shift may look like an implementation challenge. But major transformations can also alter roles, status, professional identity, relationships, routines, and expectations about the future.
Research shows that employee responses to organizational change are shaped by both the characteristics of the change and the context in which people experience it, and that responses may include support, resistance, and ambivalence rather than a single uniform reaction [7]. This is where OD can complement implementation-focused change management: not by replacing it, but by addressing organizational and relational conditions that determine how the change is understood and enacted.
5. The Organization Keeps Trying to Change — and Keeps Returning to the Same Patterns
A new structure is introduced, but decisions gradually return to the same people. A leadership program generates enthusiasm, but managerial behavior changes little. New organizational values are launched, but employees continue to experience the old norms. When different interventions repeatedly produce temporary movement followed by familiar patterns, the problem may not be insufficient effort. It may be that the interventions are not reaching the conditions that reproduce those patterns. Repeated change without sustained change is a strong reason to step back and diagnose the system.
6. You Want to Build Capacity Before the Next Crisis
OD is not only for organizations in trouble. Organizations can also invest in the ability to learn, coordinate, adapt, and make decisions under changing conditions before disruption exposes their weaknesses. Research on organizational resilience increasingly emphasizes that resilience is not simply an individual trait or a response activated after adversity occurs. It can emerge from interacting resources and capabilities across organizational levels [8]. For leaders, this changes the question from:
How will we respond when the next disruption arrives?
to:
What capabilities should we be building now so that the organization can respond when conditions change?
That is a different kind of organizational development — one focused not on repairing failure, but on strengthening the system before its limits are tested.
A Simple Diagnostic Test
If you are uncertain whether the problem requires OD consulting, ask three questions:
Do we know what is causing the problem — or only what the problem looks like?
Have we already tried plausible solutions, only to see the same pattern return?
Does solving the problem require coordinated change across leadership, teams, structures, relationships, or organizational practices?
If the answer to one or more is yes, diagnosis may be more valuable than immediately selecting another intervention. The purpose of the first conversation with an OD consultant should therefore not be to sell you a program. It should be to determine whether there is a problem worth diagnosing — and whether OD is the appropriate way to address it.
Schedule a 30-minute discovery conversation and let's talk.
What Makes Organizational Development Work?
Organizational development is not simply a sequence of consulting activities. Its effectiveness depends on how the work is conducted — and on what the organization itself is willing and able to contribute. Drawing on research and practice, five conditions are particularly important.
1. Start With Inquiry, Not a Predetermined Solution
Organizations often approach consultants with both a problem and a proposed answer:
We need leadership training.
We need to restructure.
We need to fix the culture.
We need a team-building process.
Sometimes they are right. But treating the requested intervention as the diagnosis creates an obvious risk: the organization can invest considerable effort in solving the wrong problem.
OD begins by testing assumptions.
What evidence supports the current explanation?
Who experiences the problem differently?
Where does the pattern occur — and where does it not?
What organizational conditions might be sustaining it?
Recent evidence from OD and change-management practice reinforces this principle: practitioners associated with stronger evidence of positive impact were more likely to diagnose the distinctive client context and adapt their interventions accordingly [6]. Diagnosis does not mean endless analysis. It means developing enough understanding to make an intervention defensible.
2. Involve the People Who Live in the System
Organizational charts show formal structures. Policies describe intended processes. Senior leaders can explain strategy. None provides a complete picture of how the organization actually works.
People at different levels experience different parts of the system. They encounter informal workarounds, conflicting expectations, coordination failures, local successes, and consequences that may remain invisible from the top. Their participation therefore serves two purposes. It improves the quality of the diagnosis. And it creates opportunities for people to interpret evidence together rather than simply receive someone else's conclusions.
This is consistent with both diagnostic and dialogic traditions in OD: organizational inquiry can generate information about the system while dialogue can alter how organizational members understand that system and the possibilities for changing it [2]. Participation, however, should not be confused with consensus. Good OD does not require everyone to agree. It requires enough candor to surface consequential differences.
3. Create Conditions Where Difficult Information Can Surface
That candor cannot be assumed. People make judgments about whether raising a concern, questioning a senior leader, acknowledging failure, or challenging an established practice is safe.
Research on psychological safety shows that interpersonal conditions influence whether team members engage in learning behaviors such as seeking feedback, discussing errors, and asking for help [9]. For OD, this has a practical implication: if people believe that telling the truth about the organization carries unacceptable interpersonal or professional risk, the diagnosis itself can become distorted. Leaders therefore influence OD not only through sponsorship or resources. They influence what the organization is capable of saying about itself.
This does not mean that psychological safety requires comfort or agreement. Difficult organizational work often produces tension. The relevant question is whether disagreement, uncertainty, and bad news can enter the conversation without automatically becoming personal threats.
4. Treat Change as an Iterative Learning Process
Complex organizational problems rarely yield to a single intervention followed by implementation exactly as planned. Interventions generate information. A new decision process reveals an unexpected bottleneck. A leadership forum surfaces a conflict that was previously hidden. A pilot works in one unit but fails in another. A structural change exposes a capability gap that was not visible beforehand. The organization therefore needs to learn while changing.
Research on organizational change has emphasized the importance of temporality — including sequence, timing, pacing, and rhythm — rather than treating change as a uniform linear progression [10]. In practice, this means working through cycles:
Diagnose → Act → Observe → Learn → Adapt
The aim is not to abandon direction whenever difficulties arise. It is to use what happens during implementation as additional evidence about the system.
5. Build Capability, Not Dependence on the Consultant
The consultant should not become the organization's permanent mechanism for solving organizational problems. A stronger outcome is that leaders and teams become better able to identify patterns, conduct difficult conversations, coordinate across boundaries, learn from interventions, and adapt their own practices.
This distinction emerged clearly in my longitudinal research on OD consulting. Change developed through adaptive spaces, emergent capabilities, and systemic integration rather than through a single discrete intervention [3]. The implication is important:
A successful OD engagement should leave the organization more capable than it was before the consultant arrived. That does not mean the organization will never need external expertise again. It means that the value of OD should not be measured only by what the consultant delivered, but also by what the organization became better able to do for itself.
How Organizational Development Consulting Works
There is no single sequence that fits every organizational development engagement. The scope, methods, participants, and pace should depend on the problem and the organizational context. But effective OD requires movement from understanding the system to changing it — and from consultant-led intervention toward greater organizational capability. In my consulting practice, I organize that work around five connected stages:
1. Diagnosis — Understand the System Before Choosing the Intervention
The first task is not to confirm the client's initial explanation. It is to understand what is happening. Diagnosis may combine interviews, focus groups, observations, organizational data, surveys, document analysis, and examination of workflows, decision processes, relationships, structures, and stakeholder perspectives.
The specific methods matter less than the question they are designed to answer:
What conditions are producing or sustaining the outcome we are trying to change?
Organizational diagnostic models can help structure this inquiry. Models such as Weisbord's Six-Box Model, the Nadler-Tushman Congruence Model, and other diagnostic frameworks direct attention toward different parts of the organizational system. But the model is a lens — not the diagnosis itself. The purpose is not to fit the organization into a framework. It is to use evidence to develop a sufficiently credible explanation of what is constraining performance and where intervention may have the greatest value.
2. Strategic Design — Decide What Needs to Change
Diagnosis should change the intervention. Once consequential patterns become clearer, the next step is to determine where change is required and how different interventions may interact. The answer may involve leadership behavior, roles, structures, decision processes, cross-boundary coordination, team dynamics, capability development, or several of these at once. This is where OD differs from simply selecting an intervention from a catalogue. The design should follow the diagnosis. It should also account for the organization's capacity to absorb change.
Evidence from OD and change-management practice suggests that higher-impact practitioners pay attention not only to what should change, but also to the scope and pace the client system can realistically support [6].
3. Embedded Implementation — Change the Organization Through the Work
Organizational development should not exist only in workshops or off-site meetings. Where possible, change needs to enter the places where organizational life actually happens: leadership meetings, decision processes, cross-functional work, managerial routines, strategic discussions, feedback processes, and everyday interactions. This is what I mean by embedded implementation. Rather than separating “the change program” from operational work, interventions become opportunities to test different ways of working inside the system itself.
This also creates feedback. What happens during implementation provides new information about the diagnosis. Some assumptions are confirmed. Others prove incomplete. New constraints become visible. The work therefore remains iterative:
Act → Observe → Learn → Adapt
4. Capability Development — Make the Organization Better Able to Change Itself
An intervention can solve an immediate problem without increasing the organization's capacity to deal with the next one. OD should aim for more. Leaders and teams can develop capabilities to diagnose emerging problems, work across boundaries, surface difficult information, make sense of uncertainty, learn from action, and adapt their practices as circumstances change.
My longitudinal research illustrates this process through the development of emergent capabilities: capabilities that were not simply transferred through formal training, but developed through repeated cycles of experience, reflection, experimentation, and application in organizational work [3]. This is why leadership development can be part of OD — but is not automatically the answer to an organizational problem. The relevant question is not:
Do our managers need another program?
It is:
What capabilities does this system need in order to perform and adapt more effectively?
5. Longitudinal Impact — Look Beyond the Intervention
The final question is not whether the workshop went well. It is whether something consequential changed. Depending on the engagement, that may involve changes in decision-making, coordination, leadership practices, relationships, organizational processes, employee experience, operational indicators, or other outcomes connected to the original diagnosis. Evaluation therefore needs to return to the problem that initiated the work.
What changed?
What did not?
What appears to be holding?
What requires further adaptation?
And what can the organization now do that it could not do before?
My longitudinal OD research found that sustainable change involved not only local interventions but systemic integration — connecting learning, practices, and capabilities across organizational levels over time [3]. This is why organizational development should not end with implementation. It should ask whether change has become sufficiently embedded in how the organization actually operates.
From Diagnosis to Change:
An Anonymized OD Case
The organization from the beginning of this article did not need another statement of intent. It needed a way to understand what people were experiencing but were not yet able to discuss collectively. I began with individual conversations. One question proved particularly revealing: What is the conversation this organization needs to have but isn't having?
The answers were cautious at first. Then a recurring pattern became visible. People described exhaustion after an extended period of crisis. They worried about the organization's direction and about whether difficult concerns could be raised openly. Several were carrying similar concerns without knowing that colleagues were experiencing them too. That changed the diagnostic question. The issue was no longer simply how to implement the new leadership's agenda. We needed to create conditions in which the organization could examine what was preventing it from moving forward.
Creating a Space for What Was Not Being Said
A facilitated group conversation brought 23 people together around one question:
What are we not saying?
The beginning was uncomfortable. Then one participant raised a concern about whether the organization still knew what it stood for. Others began voicing concerns about relevance, exhaustion, unresolved frustration, and the gap between the organization's formal conversations and what people were actually experiencing. Nothing had been “fixed.” But information that had previously existed in fragmented private conversations had become available to the organization as a whole.
In my longitudinal research on OD consulting, I describe settings of this kind as adaptive spaces: environments in which organizational members can surface assumptions, tensions, and competing interpretations and engage them through structured dialogue [3]. Psychological safety matters here because speaking candidly in a group involves interpersonal risk. Research shows that psychological safety is associated with team learning behaviors such as discussing errors, seeking feedback, and asking for help [9]. But the purpose of the session was not psychological safety for its own sake. It was to make organizational learning possible.
Turning Conversation Into Organizational Practice
The work did not stop with the facilitated conversation. We created a cross-organizational transition team composed of eight people from different parts of the organization. Its role was to help surface and work with issues that crossed formal organizational boundaries.
Leadership meetings also changed. Instead of beginning only with reports and updates, meetings created room for a different question:
What are you noticing that concerns you?
Initially, the conversations were awkward. Over time, issues that had remained outside the formal leadership conversation began to enter it. We also introduced structured reflection around major projects and decisions. The aim was not only to ask:
What went wrong?
but also:
What might this tell us about the assumptions behind how we work?
This distinction has a long foundation in organizational learning research. Argyris described single-loop learning as correcting action while leaving underlying governing values largely unchanged, whereas double-loop learning involves questioning and potentially altering those governing assumptions [11]. In practice, the important shift was from treating reflection as something that happened after failure to making it part of how the organization worked.
From Intervention to Capability
Over time, the purpose was increasingly less about facilitating individual conversations and more about strengthening the organization's own ability to notice, discuss, and respond to consequential patterns. This corresponds with the second mechanism identified in my longitudinal research: emergent capabilities — capabilities that develop through recurring cycles of action, reflection, learning, and adaptation rather than through one-time knowledge transfer [3]. One executive described the process this way: “It's not just about trying new things — it's about having a systematic way to learn from what we try.” [3] That distinction matters. The aim was not to make the organization dependent on better facilitation. It was to make it better at learning from its own experience.
When Change Begins to Travel Through the System
A further shift became visible when practices and ways of thinking began appearing beyond the settings in which they had originally been introduced. Teams adapted decision processes. Managers began using questions and reflection practices from the OD work in their own settings. Learning was no longer confined to a facilitated intervention.
My research describes this third mechanism as systemic integration: the process through which new practices, capabilities, and learning become connected across levels and increasingly embedded in organizational work [3]. This matters because a successful local intervention is not necessarily organizational change. The larger test is whether what has been learned begins to influence how the system operates when the consultant is not in the room. That is where OD moves from an intervention to organizational capability.
Organizational Development vs. Change Management: What Is the Difference?
Organizational development and change management overlap considerably. Both are concerned with helping organizations change. Both can involve diagnosis, stakeholder engagement, communication, leadership, implementation, feedback, and adaptation. And in complex transformations, organizations may need both. The useful question is therefore not:
Which one is better?
It is:
What kind of change problem are we trying to solve?
When Change Management Is Particularly Useful
Change management is especially valuable when an organization has made a substantive decision about a change and now needs to implement it effectively.
A new technology is being introduced.
A new operating model has been approved.
A merger requires new processes and roles.
A restructuring needs to move from design to implementation.
In situations like these, important questions include:
Who will be affected?
What do people need to understand or do differently?
What barriers could undermine adoption?
How should implementation, communication, feedback, and reinforcement be managed?
Contemporary evidence-based approaches to change management go well beyond simply communicating a predetermined plan. They can incorporate diagnosis, stakeholder evidence, practitioner expertise, feedback, and redesign throughout the change process [12].
When Organizational Development Is Particularly Useful
OD becomes especially valuable when the organization cannot yet adequately explain the problem, when several parts of the system interact to produce it, or when developing the organization's capacity to adapt is itself part of the objective. The questions are different:
What is producing the current pattern?
How do structures, leadership, relationships, capabilities, incentives, and meaning interact?
Whose perspective is missing from our understanding of the problem?
What needs to change in the system — not only in individual behavior?
What capabilities should remain after the intervention ends?
OD therefore often places greater emphasis on inquiry into the system, participation in sense-making, behavioral-science knowledge, and the development of organizational capability [1][2]. But this should not be turned into a rigid boundary. OD itself contains different approaches to change, from more diagnostic strategies to dialogic and generative ones [2][13]. Likewise, change management ranges from relatively programmatic implementation approaches to more evidence-based and adaptive practices [12].
Sometimes the Organization Needs Both
Consider the implementation of a new enterprise-wide digital system. Change management may be essential for stakeholder analysis, communication, training, adoption, implementation sequencing, feedback, and reinforcement. But suppose the implementation also reveals longstanding conflict between functions, unclear decision rights, low trust between headquarters and operating units, or leadership practices that prevent problems from being surfaced. Those are no longer only adoption issues. OD can help diagnose and work with the organizational conditions surrounding the implementation. The two approaches can therefore be complementary:
Change management helps an organization implement a defined change. Organizational development helps an organization understand and change the system in which change must occur — and build greater capacity to adapt over time.
The distinction is one of emphasis, not an impermeable professional boundary. Research on OD and change-management practice supports this more contingent view. In a study of 317 OD and change-management projects, higher-impact work was associated with diagnosing what was distinctive about the client system, linking behavior patterns to performance, adjusting scope and pace to client capacity, and selecting interventions that fit the circumstances [6]. The practical implication is straightforward:
Do not begin by deciding whether you need “OD” or “change management.” Begin by understanding the change problem well enough to know what kind of support it requires.
Why People Make Sense of Change Differently
Organizational change is designed at one level and experienced at another. A restructuring may be described by senior leaders as a way to improve coordination. Employees may experience the same change as a loss of autonomy, expertise, status, or trusted relationships. A new strategy may appear clear in a presentation but create very different questions across the organization:
What does this mean for my work?
What will I be expected to do differently?
What are we giving up?
Can I trust the people leading this change?
Does this fit with what I believe this organization stands for?
These interpretations matter because people do not respond only to the formal content of a change. Research on organizational change shows that employee responses are shaped by characteristics of the change, the organizational context, leadership, individual differences, and the ways people interpret what is happening [7].
Change Is Also a Process of Sensemaking
When established routines and expectations are disrupted, people try to understand what is happening and what it means. Sensemaking research describes this as a process through which organizational members construct meaning in situations that are uncertain, ambiguous, or changing [14]. That process is not merely an obstacle to implementation. It can reveal information about the organization.
Questions, disagreement, hesitation, or ambivalence may point toward conflicting expectations, previous experiences of change, identity concerns, operational constraints, or consequences that were not visible to those designing the intervention. This is one reason OD creates opportunities for dialogue rather than relying only on communication. Communication can explain the intended change. Dialogue can reveal how the change is actually being understood.
Meaning Does Not Replace Organizational Conditions
There is an important limit to this argument. Not every problem can be solved through better conversations or more compelling narratives. If people lack resources, decision authority, time, capability, or workable structures, asking them to “embrace the change” does not remove those constraints. Likewise, strong identification with an organization's purpose cannot indefinitely compensate for structural conditions that make effective performance difficult. OD therefore needs to work with both:
how people interpret organizational reality — and the organizational conditions producing that reality.
Sustainable change becomes more plausible when meaning, behavior, structures, relationships, and capabilities begin to reinforce rather than contradict one another.
Before You Hire an OD Consultant:
Three Questions to Ask
Hiring an organizational development consultant does not automatically make an organization ready for organizational development. Before starting, three questions are worth asking.
1. Are We Willing to Discover That Our Initial Diagnosis Is Wrong?
Organizations rarely approach a consultant without an explanation.
The managers are the problem.
People resist change.
We have a communication problem.
The structure no longer works.
These explanations may be correct. They may also describe only the visible part of the problem. A meaningful diagnostic process requires leaders to treat their initial explanation as a hypothesis rather than a conclusion. That means being willing to discover that a problem attributed to employees may also involve leadership practices, that a perceived capability gap may reflect structural constraints, or that a communication problem may actually be a disagreement about priorities.
If the diagnosis is predetermined, the consulting process can easily become an exercise in validating a decision that has already been made. The first readiness question is therefore simple:
Are we genuinely prepared to learn something that could change what we think the problem is?
2. Is Leadership Willing to Be Part of the System Being Examined?
Leaders often sponsor organizational change. OD may require something more: recognizing that leadership behavior, relationships, decision processes, and assumptions can themselves be part of what needs to be understood. That does not mean assuming that leadership is the problem. It means not placing leadership outside the diagnosis.
If an organization asks employees to speak candidly, question established assumptions, learn from mistakes, or work differently across boundaries, leaders influence whether those behaviors are actually possible. The second question is therefore:
Are leaders willing not only to sponsor the process, but also to examine how their own practices may be influencing the outcomes they want to change?
3. Are We Prepared to Stay With the Work Beyond the Initial Intervention?
Diagnosis can surface issues that are difficult to address. A workshop can reveal conflict without resolving it. A survey can expose distrust without rebuilding it. A new structure can clarify responsibilities while creating new coordination problems. This is why OD should not be treated as a sequence of disconnected events.
The organization needs sufficient leadership attention, time, and capacity to learn from what emerges and adjust the work as it develops. That does not require an endless consulting engagement. It requires enough commitment to move from insight to action — and from action to learning. The third question is:
If the process reveals something consequential, are we prepared to act on it?
If the answer to these three questions is broadly yes, the organization may be ready for more than another intervention. It may be ready to examine the system that keeps producing the outcomes it wants to change.
What Changed — and What the Case Can Tell Us
Six years after that first facilitated conversation, the organization was not free of conflict, uncertainty, or failure. That was never the objective. What had changed was its capacity to work with them.
During the engagement period, staff turnover declined from approximately 40% to 8%. The organization's employee survey also recorded a 60-point increase on items concerning people's ability to raise concerns and their belief that leadership listened. Other changes were visible in how the organization worked. Cross-departmental initiatives became possible in ways that had previously been difficult, and practices developed through the OD process began appearing beyond the settings in which they had originally been introduced.
Perhaps most revealing was what happened when the organization encountered another major disruption. When an important source of funding was unexpectedly withdrawn, leaders and staff were able to convene, acknowledge the situation, make difficult decisions, and move forward. The organization had not eliminated uncertainty. It had become better able to work through it.
What This Case Does — and Does Not — Show
These outcomes should be interpreted carefully. This is a longitudinal practice case, not an experiment. The decline in turnover, changes in survey responses, and later organizational behavior occurred during a period of sustained OD work, but they should not be interpreted as proof that consulting alone caused those outcomes.
Organizations are open systems. Leadership changes, external conditions, resources, workforce dynamics, and other factors can all influence what happens over time. The value of the case lies elsewhere. It shows what organizational development can look like when diagnosis, dialogue, experimentation, capability development, and learning are connected over time rather than delivered as isolated interventions.
That pattern is consistent with my longitudinal research, which identified adaptive spaces, emergent capabilities, and systemic integration as interconnected mechanisms through which OD consulting supported bounded organizational transformation [3].
The Question to Take Back to Your Organization
At the beginning of the process, I asked:
What is the conversation this organization needs to have but isn't having?
It remains a useful question. But it is not the only one. Your organization's constraint may be a conversation that is not happening. It may also be a decision nobody has authority to make. A structure that reinforces the wrong behavior. A capability the organization has never developed. Competing priorities that make coordination almost impossible. A gap between what the organization says matters and what its systems actually reward. Or several of these interacting at once.
That is why the starting point should not be another program, workshop, restructuring, or change methodology. It should be a better question:
What is actually constraining this organization from performing, coordinating, and adapting as it needs to?
That is where organizational diagnosis begins. And when the constraint becomes clearer, the organization can make a much better decision about what — if anything — needs to change.
Not Sure What Needs to Change?
You do not need to arrive with the diagnosis. The first conversation is designed to understand what is happening, what you have already tried, and whether a deeper organizational diagnosis would be useful.
Schedule a 30-minute discovery conversation and let's talk.
References
[1] Cummings, T. G., & Worley, C. G. (2019). Organization development and change (11th ed.). Cengage Learning.
[2] Bushe, G. R., & Marshak, R. J. (2009). Revisioning organization development: Diagnostic and dialogic premises and patterns of practice. The Journal of Applied Behavioral Science, 45(3), 348–368. https://doi.org/10.1177/0021886309335070
[3] Dryzin-Amit, Y. (2026). OD consulting as a catalyst for change. The Journal of Applied Behavioral Science, 62(3). https://doi.org/10.1177/00218863251376151
[4] Edmondson, A. C. (2019). The fearless organization: Creating psychological safety in the workplace for learning, innovation, and growth. Wiley.
[5] Schein, E. H. (2010). Organizational culture and leadership (4th ed.). Jossey-Bass.
[6] Cohen, H. (2026). Why some organization development and change management practitioners achieve higher impact. Journal of Organizational Change Management, 39(1), 178–194. https://doi.org/10.1108/JOCM-08-2025-0746
[7] Oreg, S., & Sverdlik, N. (2026). Responses to organizational change: Evolution of the concept, established findings, and future directions. Annual Review of Organizational Psychology and Organizational Behavior, 13, 387–413. https://doi.org/10.1146/annurev-orgpsych-020924-064623
[8] Duchek, S. (2020). Organizational resilience: A capability-based conceptualization. Business Research, 13, 215–246. https://doi.org/10.1007/s40685-019-0085-7
[9] Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999
[10] Bartunek, J. M., & Woodman, R. W. (2015). Beyond Lewin: Toward a temporal approximation of organization development and change. Annual Review of Organizational Psychology and Organizational Behavior, 2, 157–182. https://doi.org/10.1146/annurev-orgpsych-032414-111353
[11] Argyris, C. (1977). Double loop learning in organizations. Harvard Business Review, 55(5), 115–125.
[12] Rousseau, D. M., & ten Have, S. (2022). Evidence-based change management. Organizational Dynamics, 51(3), 100899. https://doi.org/10.1016/j.orgdyn.2022.100899
[13] Bushe, G. R. (2023). Three change strategies in organization development: Data-based, high engagement and generative. Leadership & Organization Development Journal, 44(2), 173–188. https://doi.org/10.1108/LODJ-05-2022-0229
[14] Maitlis, S., & Christianson, M. (2014). Sensemaking in organizations: Taking stock and moving forward. The Academy of Management Annals, 8(1), 57–125. https://doi.org/10.1080/19416520.2014.873177
Comments