Accelerating Implementation Methodology (AIM) Field Research
Most transformation initiatives install a change but never implement it. AIM’s field research identifies the structural causes: delegated sponsorship, missing reinforcement, and activity measured instead of observable behavior. Each is addressable.
A change gets installed but never implemented, because the people meant to work differently never did. The new system is live, the training is complete, and the initiative is formally closed. Ninety days later, the old behaviors are back. This pattern, the gap between installation and implementation, is the central problem AIM was designed to address.
AIM's field research, developed across 40+ years of practice, identifies the structural causes behind this pattern: sponsorship that gets delegated away, no reinforcement system for the new behaviors, and success measured by activity rather than observable behavior change. These are not failures of individual will. They are predictable outcomes of how initiatives are designed and led, and they are addressable.
Field Research Findings
AIM’s field research, developed over 40+ years across hundreds of organizational initiatives, points to three structural causes behind most transformation failures: sponsorship that gets delegated rather than exercised, new behaviors that are communicated but never reinforced, and success measured by activity rather than observable behavior change. These causes reinforce one another, and they are not about individual fault. Each is a predictable result of how the initiative was designed and led.
AIM's field research identifies insufficient and delegated Sponsorship as the most frequently documented structural cause of initiative failure. Sponsorship requires personal, visible action by the leader accountable for the change. When it is handed to a change team, a program office, or a consulting function, the initiative loses the organizational signal that drives adoption. AIM defines a set of Required Sponsorship Activities that cannot be delegated: specific behaviors sponsors must perform personally to keep an initiative moving from installation to implementation.
AIM's Express, Model, Reinforce (EMR) framework shows why this pattern is predictable. Communication (Express) is the lightest lever available to leaders. Reinforcement carries approximately three times the weight of communication in driving sustained behavior change. Initiatives built on announcement cycles and training events, without reinforcement systems that recognize and sustain new behaviors, stall after launch energy fades, reliably and by design.
Measuring go-live dates, training completion rates, and survey-based sentiment produces a false picture of progress. AIM defines a valid implementation measure as one where a manager can observe the behavior directly, on the floor or in operational data, without asking employees how they feel. Activity metrics confirm that things were done. They do not confirm that people changed how they work. AIM's field research documents this conflation as one of the most consistent failure modes across industries.
AIM treats change readiness as a condition that must be actively built before an initiative launches, not assumed from leadership support at the executive level. Readiness encompasses leadership alignment at every level of the sponsor cascade, sponsor capacity relative to the current change load, and whether target transforms behaviors are defined in observable, measurable terms. When readiness is assumed, gaps surface mid-initiative, at the point of highest cost and lowest flexibility to course-correct.
How AIM Addresses These Together
These three causes reinforce one another. Delegated Sponsorship means no one is reinforcing the new behaviors. Without reinforcement, activity metrics are the only signal available, and they confirm deployment rather than adoption. AIM addresses them together: the Required Sponsorship Activities that cannot be delegated, the EMR standard for measuring sponsor commitment, observable behavior measurement, and change readiness assessment work as a system rather than as separate interventions. AIM also identifies Speed Bumps, the common barriers that appear at each Roadmap practice area, as a structural part of planning rather than a surprise.
Consider a CRM rollout: the platform is fully configured, data has been migrated, and every affected employee has completed the required training. The initiative is formally closed. Ninety days later, adoption sits below 30 percent. Sales teams are working around the system, managers are not reviewing pipeline data in the tool, and the behaviors the initiative was designed to produce never materialized. The system was installed. It was not implemented.
A system, process, or structure has been deployed. The technology is live, the policy is published, the training is delivered. Deployment criteria are met and the initiative is declared complete.
Completion is measured by go-live dates and training attendance records, not by observable changes in how people work.
People have sustainably changed how they work. The behaviors the initiative required are observable and consistent. The intended results are being realized and can be measured on the floor or in the data.
Completion is measured by observable behavior change and realized outcomes, not by deployment milestones.
AIM's field research, developed across 40+ years of practice, shows that the gap between installation and implementation is where most of the intended value of an initiative disappears. Organizations invest heavily in design, configuration, and launch, then close the initiative on go-live day. The period that follows, when people are expected to work differently, is left without a reinforcement structure, visible leadership modeling, or a mechanism to detect when adoption is stalling.
The distinction is not semantic. Installation and implementation require different activities, different leadership behaviors, and different success measures. An initiative plan that ends at go-live is, by design, an installation plan. It has no mechanism to drive the sustained behavior change that produces results.
Observable Indicators of the Gap
Signs an initiative stalled between installation and implementation
Trained employees continue using workarounds or legacy processes 60 days post-launch
System adoption metrics are not tracked after go-live; there is no behavioral baseline
Managers do not visibly model the new workflows in team settings
No reinforcement system exists to recognize consistent adoption or address persistent non-use
Initiative ownership transfers to IT or operations at go-live, with no change accountability remaining
AIM builds the installation-to-implementation gap into its framework from the start. AIM's planning process treats the technical deployment and the behavioral adoption as separate workstreams with separate success criteria. Leaders carry Required Sponsorship Activities that cannot be delegated throughout the adoption period, not just at launch. Reinforcement systems are designed before go-live so that consistent new behavior is recognized and inconsistent behavior is addressed promptly.
AIM measures success by observable behavior change: what are people doing differently, and can a manager see it on the floor or confirm it in the data? Go-live dates and training completion records are installation metrics. They are necessary but not sufficient. AIM's field research consistently shows that initiatives that close after installation, without a reinforcement phase, realize only a fraction of their intended value.
AIM's Diagnosis
When AIM's practitioners diagnose a stalled initiative, the root cause is rarely employee resistance or a flawed technology choice. The more common finding is that the leaders sponsoring the change were not personally doing what the change required. Communication was issued, training was delivered, and the system went live. What was missing was specific, visible leadership behavior sustained beyond the launch event.
AIM's field research points to gaps in specific sponsorship behaviors as the primary structural cause of initiative failure. These are not general "executive support" attributes. They are observable activities: sponsoring visibly, communicating the rationale directly, modeling the new behaviors, reinforcing adoption, building a functioning sponsor cascade, and managing resistance rather than ignoring it. AIM calls these the Required Sponsorship Activities that cannot be delegated, because delegating any of them degrades the probability of sustained adoption in a documented and predictable way.
This is a structural observation, not an assignment of individual fault. Initiatives are routinely designed in ways that leave sponsors without clear role definitions, without reinforcement tools, and without accountability tied to behavioral adoption outcomes. The result is a leadership gap at precisely the moment adoption decisions are being made.
A senior leader approves an initiative, attends the kickoff, and hands ownership to a program manager. Employees observe who is visible and who has disengaged. AIM's field research documents this delegation pattern as one of the most reliable predictors of stalled adoption.
A leader announces a new operating model, hosts a town hall, and distributes a summary document. Six months later, the old behaviors persist. The announcement cycle substituted for a reinforcement system. Employees read the absence of follow-through accurately.
Leaders who publicly endorse a new process while continuing to use legacy workarounds in their own work create a visible contradiction. Employees observe behavior, not messaging. When the modeled behavior diverges from the stated expectation, the modeled behavior sets the norm.
A change that has strong executive sponsorship but no functioning sponsor infrastructure in middle management stalls at the layer where adoption decisions are made day to day. AIM's research identifies building and maintaining a sponsor cascade as one of the Required Sponsorship Activities that cannot be delegated. AIM calls the common barriers that appear at each Roadmap practice area Speed Bumps, and an absent cascade is one of the most consistent.
AIM's Structural Response
AIM's structural response to this diagnostic is the concept of the Required Sponsorship Activities that cannot be delegated: a defined set of behaviors that, according to AIM's field research, must be performed by the leader sponsoring the change. They cannot be handed to a change manager, program office, or communications function without degrading the probability of sustained adoption. Delegation of them is itself documented as a failure mode.
The Required Sponsorship Activities give structure to what active sponsorship means in practice. They shift the conversation away from whether a leader is "supportive" (a subjective and often unmeasured attribute) toward whether the leader is performing specific, observable behaviors that employees and the organization can register. When those behaviors are absent, the initiative lacks the reinforcement infrastructure that AIM's research identifies as essential for sustained behavior change.
Assessing sponsor behavior against this task list early in an initiative gives practitioners a diagnostic view of readiness risk before go-live, not after adoption fails to materialize. The section below on Change Readiness explains how AIM uses that assessment.
Sponsorship Commitment and Reinforcement
An organization launches a new compliance procedure with a thorough communications plan: all-hands briefings, an e-learning module, a reference guide on the intranet, and a reminder from the executive sponsor. Ninety days later, roughly half of front-line staff are still following the old procedure. The communication was complete. No reinforcement system was built. The behavior did not change.
AIM addresses this gap through the EMR framework. EMR describes how leaders must engage with a change at three levels. It also identifies where most initiatives fall short: the Express and Model phases receive planning attention, while reinforcement is left to chance or treated as a post-launch activity rather than a design requirement.
AIM Field Principle
AIM uses the EMR framework where reinforcement carries about three times the weight of communication in sustaining behavior change across an initiative.
~25%
of adoption weight
Leaders communicate the rationale, scope, and expected behaviors. Most organizations invest substantially here: town halls, cascade decks, emails from the executive team, and training events.
~25%
of adoption weight
Leaders visibly demonstrate the new behaviors themselves. This means a manager who asks people to use the new system uses it in every team meeting, not as a one-time gesture but as a sustained pattern others can observe.
~50%
of adoption weight
Formal and informal reinforcement systems ensure that changed behaviors are recognized, that non-compliance has consequences, and that people who adopt the change are not penalized for it. AIM's field research indicates reinforcement carries approximately three times the weight of communication in driving sustained behavior change.
The imbalance is not a matter of negligence. Communication is visible and easy to schedule: a town hall has a calendar date, a training session has a completion report, a launch email has a delivery receipt. Reinforcement, by contrast, requires ongoing managerial behavior, consequence systems, and structural changes to how performance is recognized and measured. Those elements take longer to design and are harder to delegate.
When the launch energy of an initiative fades, typically within 30 to 60 days of go-live, the absence of reinforcement becomes consequential. People revert to familiar behaviors not because they misunderstood the communication but because the environment around them has not changed. The old behaviors are still functional, still accepted by managers, and in many cases still more efficient given the existing incentive structures.
AIM's field research across 40+ years and hundreds of initiatives documents this pattern consistently. Organizations that build robust reinforcement systems before go-live, not as a post-launch retrofit, show substantially higher sustained adoption rates at 90 and 180 days. Reinforcement is not a follow-up activity; it is a design requirement.
Observable conditions, drawn from AIM's field research, indicating an initiative is running on communication alone.
Training completion rates are tracked; post-training behavior on the floor is not.
Managers communicate the change in team meetings but have not visibly adopted it in their own routines.
Employees who revert to old behaviors face no consequence, formal or informal.
Employees who adopt the new behaviors early receive no recognition.
The initiative's milestone plan ends at go-live; no reinforcement calendar exists beyond that date.
Leadership declares success based on survey sentiment scores rather than observed behavior data.
Failure Pattern: Measurement
A large-scale HR system deployment reaches its go-live date. Training completion is at 94 percent. Survey scores collected during the rollout show high levels of stated support. The steering committee declares the initiative a success and closes out the workstream. Six months later, roughly a quarter of managers are still running payroll calculations in spreadsheets, and the new self-service portal has an active-user rate below 20 percent.
This pattern is not unusual. AIM's field research documents it consistently across industries and initiative types. The common cause: organizations measured activity and sentiment, not observable behavior. Activity metrics (training sessions attended, communications sent, go-live milestones reached) confirm that things were done. They do not confirm that people changed how they work.
AIM defines a valid implementation measure as one where a manager can observe the behavior directly, on the floor, in a system log, or in operational data, without asking employees how they feel about the change. The test is simple: can someone physically see whether the new behavior is occurring, and can they count it?
Abstract sentiment metrics (buy-in scores, attitude surveys, readiness ratings) reflect perceptions at a point in time. They do not measure what people are doing differently. AIM's approach ties progress indicators to behavior: what is the person doing, how often, and can a supervisor confirm it without a survey?
| Abstract Measure (what most initiatives track) | Observable Measure (what AIM tracks) |
|---|---|
| Training completion rate (percentage of employees who attended a session) | Percentage of managers who use the new process when reviewing team output, visible in weekly reports |
| Survey-based 'buy-in' score collected at go-live | Number of customer-facing staff who follow the updated intake procedure, countable per shift |
| Go-live date achieved on schedule | Adoption rate at 30, 60, and 90 days: what percentage of users are logging interactions in the new CRM versus the legacy spreadsheet |
| Volume of communications sent about the change initiative | Frequency with which senior leaders visibly model the new behavior in staff meetings and documented interactions |
| Number of town halls or roadshows completed | Reduction in workarounds: how often are employees bypassing the new system, and is that rate declining week over week |
Abstract Measure
Training completion rate (percentage of employees who attended a session)
Observable Measure
Percentage of managers who use the new process when reviewing team output, visible in weekly reports
Abstract Measure
Survey-based 'buy-in' score collected at go-live
Observable Measure
Number of customer-facing staff who follow the updated intake procedure, countable per shift
Abstract Measure
Go-live date achieved on schedule
Observable Measure
Adoption rate at 30, 60, and 90 days: what percentage of users are logging interactions in the new CRM versus the legacy spreadsheet
Abstract Measure
Volume of communications sent about the change initiative
Observable Measure
Frequency with which senior leaders visibly model the new behavior in staff meetings and documented interactions
Abstract Measure
Number of town halls or roadshows completed
Observable Measure
Reduction in workarounds: how often are employees bypassing the new system, and is that rate declining week over week
Why This Matters in Practice
Initiatives that track only abstract sentiment metrics frequently report success while behavioral adoption is still near zero. When the steering committee's dashboard shows green across all indicators and the floor reality is still red, the organization loses its ability to course-correct in time. AIM's measurement approach is designed to close that gap by anchoring progress to what managers can see and count, not what employees say in a survey.
Measuring go-live dates and training completion is a natural extension of installation thinking: the system is deployed, the boxes are checked, the initiative is done. AIM's field research shows this conflation is one of the most consistent failure modes across industries. When success criteria are defined at installation rather than at sustained behavioral adoption, the measurement system itself reinforces the gap between deployment and implementation.
Shifting to observable measures requires agreement, before the initiative launches, on what changed behavior will look like, who will observe it, and what threshold constitutes genuine adoption. That agreement is part of AIM's change readiness work, covered in the following section.
AIM Framework
AIM uses the term Speed Bumps to name the barriers that appear at each practice area. Recognizing them early is what separates an initiative that stalls from one that reaches full implementation.
People do not know why the change matters, so they have no reason to move.
Sponsorship is handed to a change team or reduced to periodic announcements, removing the organizational signal that drives adoption.
Sponsorship is missing at a management level, so commitment does not reach the people who must change how they work.
The new behavior is never recognized or reinforced, so people drift back to the familiar way of working.
The initiative tracks completions and sentiment scores rather than observable behavior, producing a misleading picture of progress.
When Change Agents are selected by schedule rather than credibility and skill, their influence with the target transforms population is limited from the start.
Resistance that is not surfaced and addressed does not disappear. It becomes an invisible drag on adoption.
Why Transformation Initiatives Fail
The Change Readiness section explains how AIM assesses and builds the conditions for sustained adoption before an initiative launches.
Next: Change Readiness
Understanding failure patterns is the first step. AIM's Change Readiness framework provides a structured way to assess whether the leadership, reinforcement, and measurement conditions are in place before an initiative moves forward. The section covers specific indicators practitioners can observe and act on.
About this methodology: AIM was created by Don Harrison, founder of Implementation Management Associates (IMA), and refined across 40+ years of field research. AIM is delivered by IMA Worldwide and Peacock Hill Consulting. Peacock Hill Consulting acquired IMA in 2024, and the two deliver AIM together. Learn more about AIM at IMA Worldwide.