
The Myth of Stable Implementation
Implementation does not remain stable over time. It is either strengthening through reinforcement or gradually weakening through drift. One of the most persistent assumptions in...
Implementation does not remain stable over time. It is either strengthening through reinforcement or gradually weakening through drift.
One of the most persistent assumptions in human services is that implementation is something organizations eventually complete. A leadership team selects a practice model. Staff receive training. Supervisors attend workshops. Policies are revised, forms are updated, and expectations are communicated. For a period of time, there is visible momentum. People are using the same language, approaching families differently, and working toward a shared vision of practice.
Eventually someone says, “We’ve implemented the model.” It is a perfectly reasonable statement. It is also one of the most misleading.
Implementation is not an event that organizations finish. It is an organizational capability that must be continually maintained. The moment reinforcement stops, implementation does not simply remain where it was. It begins responding to the realities of everyday work.
That is not a failure of leadership or commitment. It is simply how human performance works.
No practitioner comes to work intending to gradually move away from good practice. Most are doing exactly the opposite. They are trying to serve families well while balancing competing priorities, documentation requirements, productivity expectations, staff shortages, crises, and the countless unexpected situations that emerge throughout the day.
Imagine a newly trained facilitator six months after completing an excellent implementation process.
Their caseload has grown. Two experienced coworkers have left the organization. Their supervisor now has twice as many direct reports as before. Documentation requirements have expanded. Families continue experiencing crises that rarely fit neatly within scheduled meetings.
Nothing about the model has changed. Everything about the environment has.
No one tells this practitioner to stop practicing with fidelity. Instead, they begin making small adaptations that help them survive the demands of the work. Conversations become slightly shorter. Reflection becomes a little more directive. Team preparation becomes less thorough. Follow-up becomes less intentional. None of these adjustments feel significant. In isolation, they rarely are.
But implementation almost never changes through dramatic departures from a model. It changes through hundreds of small adaptations that each seem reasonable at the time.
The practitioner has not rejected the model. They have adapted to the system surrounding it.
This is where implementation becomes much more interesting. We often talk about practitioners drifting, but practitioners are not the only ones adapting.
New staff learn from experienced staff who have already adjusted their practice. Supervisors begin coaching toward the version of the model they now see every day. Leaders gradually normalize patterns that would have looked noticeably different a few years earlier.
Drift rarely announces itself. Instead, it quietly becomes the new normal.
One organization may describe itself as faithfully implementing the same model it adopted five years ago. Another organization may say exactly the same thing. Both leadership teams believe they are practicing the model.
If you observed the work, however, you might conclude they are implementing two very different versions of it.
This is one of the more challenging realities of organizational change. Organizations do not simply implement practice models. Over time, they implement whatever their systems consistently reinforce.
It is tempting to explain drift as a problem of commitment. Perhaps staff stopped caring. Perhaps supervisors became less engaged. Perhaps people simply need more accountability. Those explanations are appealing because they suggest relatively straightforward solutions. Unfortunately, they rarely describe what is actually happening.
Most practitioners care deeply about their work long after implementation begins. Most supervisors continue wanting high-quality practice. Most leaders remain committed to better outcomes. What changes is the environment.
None of these changes require anyone to consciously abandon the model. The environment simply begins teaching something different than the training did.
Many organizations recognize drift only after they begin measuring it. A fidelity review identifies inconsistent practice. An observation reveals important elements of the model are no longer occurring consistently. Outcomes begin varying more widely across practitioners.
These assessments are valuable. But they are often expected to accomplish something they were never designed to do. Measurement tells us where practice is today. It does not strengthen practice tomorrow.
Imagine stepping onto a scale every morning. The scale provides useful information. It tells you whether something has changed. It does not create the habits that influence what happens next.
Fidelity functions much the same way. Assessments help organizations recognize drift. They do not replace the coaching, observation, leadership development, feedback, reflection, and organizational learning required to continually pull practice back toward the model.
By the time an audit identifies significant erosion, practitioners have often been working in those patterns for months. Supervisors have adjusted their coaching accordingly. New employees have learned those patterns as normal practice.
Over time, every organization implements two models: the one it trained people to use, and the one its systems reward every day. Eventually, the second one wins.
Perhaps the most important implication is that practice drift should not surprise us. It should be expected. Not because organizations are poorly led. Not because practitioners lack commitment. Because every complex practice is continually being shaped by the environment in which it exists.
This shifts the leadership question entirely. Instead of asking, “Have we successfully implemented the model?” leaders begin asking, “What is our organization reinforcing today?”
Those are fundamentally different questions. The first assumes implementation is complete. The second recognizes that implementation is always happening.
Every organizational priority is either strengthening the practice model or gradually replacing it with something else.
This understanding sits at the center of how MiiWrap approaches implementation.
Training is intentionally treated as the beginning of implementation rather than its conclusion. Certification, coaching, communities of practice, recertification, leadership development, and internal capacity building are not additional services layered onto the model after implementation is complete. They are part of the implementation process itself.
The underlying assumption is simple. Complex practices naturally drift unless organizations intentionally create systems that reinforce them over time.
The goal, therefore, is not to eliminate drift entirely. No organization can. The goal is to build learning systems capable of recognizing predictable pressures, responding to them early, and continually strengthening practice before drift quietly becomes the new normal.
Because implementation is never standing still. The only question is which direction it is moving.

Implementation does not remain stable over time. It is either strengthening through reinforcement or gradually weakening through drift. One of the most persistent assumptions in...

The more responsibility the system carries for change, the less space remains for the person to develop ownership of it. Most practitioners do not wake...

“The written plan and the lived plan often begin separating long before anyone formally recognizes it.” One of the challenges in human services is that...

A person can be surrounded by services and still remain dependent on the system to sustain progress. At first glance, that statement seems contradictory. If...

There is a moment in nearly every team based care model when the team leaves the meeting feeling hopeful. The family has shared their vision....

A person can attend every meeting, agree with every recommendation, and still stop working the plan when the work comes into conflict with their daily...

Team-based care models are built on a powerful idea: meaningful change is more likely when support is organized around a person’s actual life rather than...

If you lead an organization that provides intensive services, there is a pattern you have likely lived through more than once. You select a...

There is a moment in almost every case where the team starts to feel cautiously optimistic that the worse is behind them. A caregiver says...