The initiative came in on time and under budget. The software worked. The training was delivered. Leadership signed off at go-live. Then, six months later, most people had quietly gone back to the old way of doing things. The system was installed. It was never adopted.
AIM Definition
AIM, the Accelerating Implementation Methodology, is a research-based change management framework that drives sustained adoption by focusing on leadership involvement, reinforcement systems, and observable behavior change.
The Core AIM Distinction
Clarity note
This AIM is a change management methodology, distinct from the innovation-focused AIM Institute and from any marketing use of the initials. When this site refers to AIM, it means the Accelerating Implementation Methodology delivered by Implementation Management Associates (IMA) Worldwide and Peacock Hill Consulting.
AIM was created by Don Harrison, founder of IMA Worldwide. Harrison developed the methodology through applied fieldwork beginning in the early 1980s, refining its concepts across more than 40 years of research with organizations navigating large-scale change.
The methodology's core ideas, including the distinction between installation and implementation, the ten practice area Roadmap, the Required Sponsorship Activities, and the Express, Model, Reinforce approach to measuring commitment, emerged from patterns Harrison and IMA practitioners observed repeatedly across initiatives that succeeded or failed to achieve sustained adoption.
In 2024, Peacock Hill Consulting acquired IMA Worldwide. The two firms now deliver AIM together, including practitioner certification and organizational engagements.
Founded by
Don Harrison
Founder of IMA Worldwide. Developed AIM across 40+ years of field research in organizational change.
Delivering firms (2024 onward)
IMA Worldwide and Peacock Hill Consulting, following Peacock Hill's acquisition of IMA in 2024.
AIM applies a ten practice area Roadmap, informally called the rainbow, that takes an initiative from Define the Change through Prioritize Action. Each practice area is concrete and sequenced: practitioners know which assessments and decisions belong at each point. Practice areas such as Define the Change, Generate Sponsorship, and Develop Reinforcement Strategy illustrate the range, from early framing to sustained adoption work.
Attached to those practice areas is a set of practical AIM Tools (assessments) that help practitioners diagnose conditions and plan sponsor activity at each point in the Roadmap. The Tools translate the Roadmap's practice areas into observable work.
Across the entire Roadmap, sponsorship is the single most important factor in whether an initiative reaches sustained adoption. AIM measures sponsor commitment through three types of behavior: Expressed (what the sponsor communicates), Modeled (what the sponsor visibly does), and Reinforced (what the sponsor allocates and rewards). Reinforced commitment carries roughly three times the weight of Expressed commitment in driving lasting behavior change.
Framework Compatibility
Compatible with Project Management Institute (PMI), Agile, and Lean. AIM operates as a complementary layer, not a replacement methodology. It addresses the human adoption work that technical delivery frameworks do not cover. AIM measures observable behavior, not survey sentiment, so its outputs integrate directly into existing reporting structures.
The difference between deploying a system (installation) and achieving sustained behavior change and results (implementation). Most adoption failures happen in the gap between the two.
AIM's field research consistently identifies sponsorship as the single most important factor in successful implementation. The Required Sponsorship Activities cannot be delegated to a change team without losing their organizational impact.
Reinforcement carries about three times the weight of communication in driving sustained adoption. Most leadership teams over-invest in expressing the change and under-invest in reinforcing it.
AIM defines adoption success by specific, countable actions that can be directly observed in the workflow, not sentiment surveys or self-reported readiness scores.
Foundational Concept
Consider a large organization that spends 18 months deploying a new enterprise CRM system. Every user has a license. The go-live date passes without a technical failure. The help desk answers tickets. Yet six months later, sales managers still run their pipeline reviews in spreadsheets, customer records remain incomplete, and the reports the system was purchased to produce contain unreliable data. The technology is installed. The initiative is not implemented.
This scenario plays out across industries and initiative types. AIM addresses it directly by drawing a precise line between two conditions that are often treated as equivalent.
AIM Definition
Deploying a system, process, or structure. The technology is live, the policy is written, the training is delivered. The organization has completed the technical or administrative work required to stand up the change.
Example: the CRM is provisioned and users can log in.
Sustained behavior change and results. People have adopted new ways of working, the change is embedded in daily practice, and the organization is realizing the outcomes the initiative was designed to deliver.
Example: sales managers run every review in the CRM, and forecast accuracy has improved.
Key Distinction
In AIM's terms: the difference between installation (deploying a system) and implementation (sustained behavior change and results) is the difference between a completed technical activity and a realized organizational outcome.
When initiative teams treat installation as the finish line, they stop planning for the work that drives adoption. Reinforcement systems are not designed. Sponsorship responsibilities are not assigned. Resistance is not anticipated. The result is a technically complete rollout that does not change behavior.
AIM is built around implementation, not installation. Its Roadmap, its sponsorship commitment standard (Expressed, Modeled, and Reinforced), and its observable behavior measurement are all oriented toward the same question: are people working differently, and are those differences producing the intended results?
AIM's field research, spanning decades of applied work across industries and geographies, consistently shows that organizations confuse installation completion with implementation success. This confusion is not a character flaw. It is a structural gap: the methods used to plan and execute technical deployments do not address the human adoption work that follows.
Going live is not a measure of success. The relevant question is whether the people who were supposed to change their behavior have done so, and whether the organization is achieving the outcomes the initiative was designed to deliver.
Installation typically ends at go-live. Implementation requires sustained sponsor presence through the adoption curve. The AIM Roadmap practice areas after go-live exist precisely to structure this sustained work.
Planning only for installation produces initiative plans that end when the system is live. Planning for implementation means including the time, budget, and accountabilities needed to drive and measure behavior change.
The installation-vs-implementation distinction is foundational. It is the premise that gives AIM's other frameworks their purpose:
The AIM Roadmap provides a ten practice area path from Define the Change through Prioritize Action, structuring the work of moving from installation to implementation. Learn more
The AIM Tools are practical assessments attached to Roadmap stages that help practitioners and sponsors diagnose conditions and plan sponsor activity. Learn more
Observable behavior measurement makes implementation progress visible and verifiable, replacing abstract sentiment tracking with specific, countable actions.
For the full treatment of why this gap leads to initiative failure, see Why Transformation Initiatives Fail.
How AIM Works
AIM applies a ten practice area Roadmap, informally called the rainbow, that runs from Define the Change through Prioritize Action. The Roadmap gives practitioners and sponsors a sequenced path: each practice area has a defined purpose, and the transition between practice areas depends on specific conditions being met, not on calendar dates. Attached to the Roadmap is a set of practical AIM Tools (assessments) that attach to specific practice areas, translating the Roadmap's intent into observable work.
The Ten Practice Areas
Each practice area of the Roadmap pairs with one or more AIM Tools: structured assessments that help practitioners and sponsors diagnose conditions, surface resistance, evaluate sponsor commitment, and plan the next practice area of work. The Tools are practical, not theoretical: they produce outputs that feed directly into sponsor decisions.
See the AIM ToolsAcross the entire Roadmap, AIM's field research consistently identifies sponsorship as the single most important factor in whether an initiative reaches sustained adoption. The AIM Roadmap stage Generate Sponsorship appears early because without it, subsequent stages produce activity without organizational weight.
AIM measures sponsor commitment through three types of behavior: Expressed (what the sponsor communicates), Modeled (what the sponsor visibly does), and Reinforced (what the sponsor allocates and rewards). Reinforced commitment carries roughly three times the weight of Expressed commitment in driving lasting behavior change. This weighting has direct implications for how initiatives are designed and resourced.
What the sponsor communicates: statements, town halls, written messages that declare the initiative a priority.
What the sponsor visibly does: using the new process, attending sessions, removing personal workarounds.
What the sponsor allocates and rewards: budget decisions, public recognition of early adopters, accountability conversations with resisters.
AIM measures adoption by observable behavior: specific, countable actions that a third party can verify without relying on self-report. An initiative is considered implemented when those target transforms behaviors are present in the workflow at the expected frequency, not when survey sentiment is favorable. This standard applies equally to sponsor behaviors (the Expressed, Modeled, and Reinforced categories) and to the behaviors of the people affected by the change.
AIM is compatible with PMI, Agile, and Lean. It operates as a complementary layer focused on the human adoption work that technical delivery frameworks do not cover. Its observable behavior outputs integrate into PMI project reporting, Agile sprint reviews, and Lean continuous-improvement cycles without requiring organizations to replace their existing methodology.
Measurement Principle
Consider a large financial services firm that deployed a new case-management system across 1,200 employees. Six months later, leadership reported strong "buy-in" based on pulse surveys. The data showed 78% of respondents felt positive about the change. Yet audit logs revealed that fewer than 40% of staff were consistently using the new system as designed. The survey measured sentiment. The audit measured behavior. Only one of those measures predicted whether the initiative would deliver its intended results.
AIM addresses this gap directly. One of its core measurement principles is measuring observable behavior rather than abstract "buy-in". The reasoning is straightforward: behavior can be seen, counted, and verified. Sentiment cannot. Initiatives succeed or fail based on whether people change what they do, not based on how they feel about the change on a given Tuesday.
AIM Definition
An observable behavior is a specific action that a third party can see, count, or verify without relying on self-report. It describes what a person does, not what they think, feel, or intend.
AIM's field research consistently distinguishes between behaviors that can be measured and tracked versus sentiments that are commonly mistaken for evidence of adoption.
Managers run weekly stand-ups using the new structured format, as scheduled, with documented action items.
Customer-facing staff apply the updated escalation protocol in 90% of recorded support interactions within 60 days.
Employees 'understand the change' or 'are aligned with the new direction' (survey-derived sentiment, not a countable action).
'Buy-in has improved' (abstract, cannot be counted or verified by a third party).
AIM practitioners define specific, role-level behaviors that constitute adoption for a given initiative before that initiative launches. Each target transforms behavior is described in concrete, observable terms: what the person does, in which context, and with what frequency. Measurement then compares actual behavior against those targets transforms at defined intervals.
Common observable indicators tracked in AIM-based initiatives include: use of a new system or process as designed (confirmed by system logs or direct observation), application of a new skill or protocol in real work situations (confirmed by supervisors or coaches), and completion of specific workflows in the new format (confirmed by output review). Each of these can be verified by someone other than the person being measured.
This approach is consistent with how AIM grounds its broader framework in decades of field research and practical application across industries, geographies, and initiative types.
Framework Compatibility
AIM is compatible with PMI, Agile, and Lean.
Observable behavior measurement integrates without conflict into PMI project reporting, Agile sprint reviews (behavioral outcomes alongside velocity metrics), and Lean continuous-improvement cycles (standard work adherence as observable behavior). In each case, AIM's behavioral targets transforms complement, rather than replace, the measurement practices native to those frameworks.
Measuring sentiment has a specific limitation in change initiatives: favorable sentiment does not correlate reliably with changed behavior. AIM's field research documents cases in which high survey scores preceded the rollback of an initiative because the operational behaviors necessary to sustain it were never consistently adopted. Conversely, initiatives with modest sentiment scores but strong behavioral adoption produced durable results.
The distinction between installation (deploying a system) and implementation (sustained behavior change and results) runs directly through this measurement principle. A system can be installed to near-universal satisfaction in surveys and still fail to achieve implementation if the required behaviors do not follow. Observable behavior measurement is one of the mechanisms AIM uses to close that gap.
For a full examination of how AIM applies this principle alongside its other core concepts, including the Roadmap, sponsorship commitment measurement, and the AIM Tools, see the How AIM Works section on this page, or explore the AIM Roadmap and AIM Tools pages.
Frequently Asked Questions
Further Reading
Compare AIM with Prosci, Kotter, and Lewin, or explore the AIM Roadmap and the Required Sponsorship Activities in detail.
A structured comparison of AIM, Prosci (Awareness, Desire, Knowledge, Ability, Reinforcement: ADKAR), Kotter (8-Step), and Lewin (3-stage): scope, emphasis, and practical differences across each framework.
Compare FrameworksAIM's ten-stage Roadmap takes an initiative from Define the Change through Prioritize Action. Each stage is concrete and sequenced, with practical Tools attached to structure the work at every point.
Explore the RoadmapAbout this methodology: AIM was created by Don Harrison, founder of IMA. For practitioner resources, see IMA Worldwide, Peacock Hill Consulting, and imaworldwide.com/what-is-aim. Peacock Hill Consulting acquired IMA in 2024, and the two deliver AIM together.