Home → Insights → Partial Adoption Is Not a Minor Issue. …

Partial Adoption Is Not a Minor Issue. It Is Value Destruction.

By Alexandra Salamis M.A., M.S.W., ICF, EMCC, CEC, CCMP Article C2.2

Partial adoption is often treated as an inconvenience. Some teams are slower than others. Some roles use the new process more consistently. Some exceptions are tolerated while people “get used to it.” In the short term, this can feel pragmatic. In the long term, it is one of the most reliable ways organisations destroy the value they invested in change.1 Partial adoption is not a transition state. It is a structural condition, and once it sets in, it is surprisingly difficult to reverse.2

What partial adoption actually looks like

Partial adoption rarely shows up as outright refusal. It looks like this instead:

  • some teams follow the new process end to end
  • others follow it selectively
  • key steps are skipped under pressure
  • legacy tools are kept “just in case”
  • informal fixes become accepted practice

From a governance perspective, this can look tolerable. The system is live. The process exists. Results are not catastrophic. From a value perspective, the operating model has already fractured.

Why partial adoption feels reasonable at the time

Partial adoption persists because it often makes sense locally. Managers are balancing delivery targets, staffing constraints, and service expectations. Individuals are reconciling new requirements with existing performance measures. Leaders are reluctant to disrupt operations for what appear to be marginal gains. Each decision, taken on its own, is defensible. The problem is cumulative. When these local accommodations are left unaddressed, they become the default way the organisation operates. What began as flexibility hardens into inconsistency.

How partial adoption erodes value

Most business cases assume consistency. They assume that processes are followed, data is comparable, and decisions are made using the same information across the organisation. Partial adoption breaks all three assumptions. Over time, this leads to:

  • duplicated work as teams re-check or re-enter information
  • declining data quality that undermines reporting and insight
  • increased error rates as handoffs become unpredictable
  • uneven service or customer experience
  • growing reliance on expert intervention to “fix” exceptions

These effects are rarely dramatic. They are persistent. They show up as friction, inefficiency, and fatigue — the kinds of problems that are easy to normalise and hard to attribute.

Why enforcement alone doesn’t fix it

When partial adoption becomes visible, the instinctive response is often enforcement.

Leaders restate expectations. Compliance is monitored more closely. Exceptions are discouraged. Sometimes this helps. Often, it doesn’t. Enforcement addresses surface behaviour, not underlying conditions. It does not resolve conflicting incentives, capacity constraints, or design assumptions that made partial adoption attractive in the first place.3 Under pressure, people comply where they are watched and adapt where they are not. The organisation gains the appearance of control while losing insight into how work is actually getting done.

Partial adoption as a warning sign, not a nuisance

Partial adoption is one of the earliest indicators that an operating model is under strain.4 It signals that:

  • the new way of working is harder than anticipated
  • trade-offs are being made implicitly rather than explicitly
  • local optimisation is winning over enterprise consistency
  • value assumptions are no longer holding

Treating partial adoption as a minor issue misses its diagnostic value. It is not noise. It is feedback.

The long-term cost organisations underestimate

The most damaging effect of partial adoption is not immediate inefficiency. It is erosion of organisational coherence. Over time:

  • standards lose meaning
  • comparability disappears
  • accountability blurs
  • confidence in shared systems declines

Eventually, the organisation reaches a point where no one fully trusts the data, the process, or the model. At that stage, change fatigue sets in not because there has been too much change, but because previous change never fully took hold. Future initiatives inherit the drag of unresolved partial adoption.

Protecting value means addressing consistency, not perfection

None of this implies that organisations should pursue rigid, exception-free compliance. The issue is not perfection. It is unmanaged inconsistency. Value is protected when organisations are explicit about:

  • which behaviours are non-negotiable
  • where flexibility is acceptable
  • how exceptions are surfaced and addressed
  • who owns consistency once the project ends

When these questions remain unanswered, partial adoption fills the vacuum.

A more honest way to view adoption

Adoption is not binary. But neither is it neutral. Partial adoption is not a temporary inconvenience to be tolerated. It is a structural condition that steadily undermines the logic of the change. Recognising it early, and treating it as a value risk rather than a behavioural irritation, gives organisations a chance to intervene while the cost of doing so is still manageable. This is one way of thinking about why change succeeds or fails. Other pieces go deeper into how value erodes in practice, and how leaders can respond before value is lost.

  1. Rumelt, R. P. (1974). Strategy, Structure, and Economic Performance. Harvard Business School Press. Rumelt’s empirical study demonstrates that strategically coherent firms consistently outperform strategically incoherent ones — and that incoherence between stated strategy and actual execution patterns is one of the most reliable predictors of underperformance. Partial adoption creates precisely this incoherence: the organisation’s intended operating model and its actual operating model diverge, and the business case built on the intended model does not materialise. ↩︎

  2. Tushman, M. L., & Romanelli, E. (1985). “Organizational Evolution: A Metamorphosis Model of Convergence and Reorientation.” Research in Organizational Behavior, 7, 171–222. Tushman and Romanelli show that organisations can only realign their structures through discontinuous, frame-breaking change — incremental attempts to correct embedded patterns consistently fail because the patterns are reinforced by the very routines being adjusted. Partial adoption that has hardened into standard practice requires the same discontinuous intervention; gradual correction simply accommodates the existing deviation. ↩︎

  3. Hackman, J. R., & Oldham, G. R. (1976). “Motivation Through the Design of Work: Test of a Theory.” Organizational Behavior and Human Performance, 16(2), 250–279. https://doi.org/10.1016/0030-5073(76)90016-7. Hackman and Oldham demonstrate that job characteristics — the structure of the work itself — predict behaviour more reliably than motivational effort or enforcement. Partial adoption that persists under enforcement pressure signals that the structural conditions of the work (incentives, task design, capacity) have not changed; enforcement addresses symptoms while the structural cause remains intact. ↩︎

  4. Weick, K. E. (1968). “Adapting to Intergroup Conflict.” Administrative Science Quarterly, 13(4), 656–673. https://doi.org/10.2307/2391019. Weick shows that organisations that attend to actual behaviour — rather than to stated intentions or formal compliance — adapt more effectively to emerging conflict and strain. Partial adoption is behavioural data: it tells practitioners where the operating model is generating resistance, where local conditions override enterprise design, and where the new way of working is not yet structurally supported. ↩︎

Additional Related Articles