AIM's pre-rollout assessment approach: what to verify before deployment, and why most initiatives skip it.
A large financial-services firm launches a new core-banking platform. Training is complete, go-live is on schedule, and the steering committee declares success on day one. By month four, branch staff are using workarounds, exception processing is up, and the compliance team is flagging deviations. The system was installed. The change was not implemented. The gap was visible before rollout began. No one assessed it.
AIM addresses this gap through a structured pre-rollout readiness assessment. Rather than measuring sentiment or awareness, it evaluates the observable conditions that determine whether an organization can sustain behavior change after deployment ends. Those conditions can be verified before a single license is activated.
This reference covers
Definition
Readiness, in AIM's framework, is not a state of mind. It is a set of observable conditions that either exist in an organization or do not. Those conditions determine whether behavior change survives after the deployment team leaves and the go-live energy fades.
AIM's working definition
An organization is ready for change when its sponsors are actively performing the leadership behaviors the initiative requires, when reinforcement systems are aligned to the new expected behaviors, and when feedback loops are in place to catch and address resistance before it compounds. Readiness is measured by what people are doing, not by what they say they intend to do.
The central distinction in AIM is installation versus implementation. Installation is a technical milestone: a system is deployed, licenses are activated, and the go-live checklist is completed. Implementation is something different. It is sustained behavior change, with people operating under the new rules weeks and months after deployment ends.
Most organizations measure success against installation criteria. AIM's readiness framework asks a different question: are the conditions in place that make implementation, not just installation, the likely outcome?
Risk and Assessment
The question AIM asks before any major initiative begins is not whether the technical deployment plan is solid. It is whether the human system can sustain the behavior change the initiative requires. Those are different questions, and organizations consistently underinvest in the second one.
AIM places this work at the Assess the Climate practice area of the AIM Roadmap, early in the sequence, before deployment commitments are locked in. Once a rollout is underway and momentum is established, surfacing and correcting readiness gaps becomes substantially more costly. The same assessment framework also feeds the Implementation Risk Forecast, which AIM practitioners use to monitor a change in progress and flag conditions that predict adoption difficulty before they fully materialize.
AIM's field research, accumulated across more than four decades of implementation work, shows that organizations consistently confuse the technical act of deploying a system with the organizational act of changing behavior. The two are not the same. When readiness conditions are absent at launch, adoption follows a predictable decline: high in week one, then steadily lower as old habits reassert themselves.
When an initiative surfaces readiness problems in month three, the remediation effort competes with the perception that the change is already done. Sponsors have moved on. Budgets have closed. The implementation team has been reassigned. AIM's pre-rollout assessment identifies those same gaps at a point where they can be addressed without reversing deployment decisions.
The most common pattern AIM's research identifies is not outright resistance, but passive sponsorship. A senior leader endorses the initiative, delegates execution, and assumes involvement from that point is unnecessary. Frontline staff read leadership behavior accurately. When the sponsor is absent, the change is treated as optional. That signal spreads faster than any formal communication.
Organizations that rely on deployment milestones, training completion rates, or post-launch surveys to measure change health frequently encounter surprises. Workarounds are already established by the time survey data surfaces them. Usage figures mask the difference between compliance and adoption. AIM's readiness assessment substitutes direct behavioral observation for lagging indicators.
AIM treats readiness assessment as a risk management discipline, not a communication exercise. The goal is to identify where the conditions for sustained adoption are weak before the initiative launches, and to strengthen them at the point where doing so is still straightforward.
Assessment Scope
AIM's readiness assessment applies specific Tools from the AIM Tools set, aligned to the Assess the Climate practice area of the AIM Roadmap. Each area is evaluated against observable criteria, not self-reported intentions. The three Tools below are those most directly associated with readiness and risk assessment before a rollout begins.
Organizational Change Stress Test and Implementation History Assessment
These two AIM Tools assess the Climate for Change. The Organizational Change Stress Test evaluates how much change the organization is currently absorbing and whether adding this initiative creates overload conditions that will deplete sponsor attention and workforce resilience. The Implementation History Assessment looks at how similar changes have fared in this organization in the past, because past adoption patterns are strong predictors of current risk.
Individual Readiness Assessment
The Individual Readiness Assessment identifies where the people affected by the change sit on the readiness spectrum and what is driving their position. AIM treats resistance as information, not as an attitude problem. Understanding whether resistance comes from lack of awareness, disagreement with the approach, workload concerns, or perceived loss allows practitioners and sponsors to address the actual source rather than applying a generic communications response.
Sponsor Assessment
The Sponsor Assessment evaluates the strength and type of sponsor commitment using AIM's three-category standard: Expressed (what the sponsor communicates), Modeled (what the sponsor visibly does), and Reinforced (what the sponsor allocates and rewards). AIM weights these differently: Reinforced commitment carries roughly three times the adoption impact of Expressed commitment. A sponsor who announces the change but does not visibly model it or realign reinforcement systems provides less than a third of the commitment the initiative needs.
Improving Readiness
Readiness is not a fixed state that an organization either has or lacks. It is produced by specific actions taken by specific people before and during a rollout. These are the five areas where AIM practitioners focus improvement effort when a readiness assessment reveals gaps.
Before any assessment is useful, the initiative must specify the new behaviors in concrete, observable terms. If a manager cannot look at two employees and say which one is performing the new behavior and which one is not, the target transforms is not yet defined precisely enough to measure readiness against it.
Readiness improvement starts with the sponsor. Use the Sponsor Assessment to identify whether the sponsor's commitment is Expressed, Modeled, and Reinforced, and which of those categories has gaps. Review the Required Sponsorship Activities that cannot be delegated and build a specific plan for closing the gaps before rollout begins.
If reinforcement mechanisms are not in place at launch, plan for them to be. This means updating performance expectations, establishing recognition for early adopters, and ensuring supervisors know how to address non-adoption. These mechanisms take time to build and cannot be improvised after deployment.
Each layer of management that must change behavior needs a visible local sponsor performing the Required Sponsorship Activities for that group. Identifying and preparing those sponsors before the rollout reaches their teams is the most direct way to raise readiness across a large organization.
Readiness assessment requires two-way information flow. Post-launch surveys reveal problems after behavior has already reverted. Active channels, in which managers report resistance signals to sponsors in real time, allow for course correction while adoption is still in progress.
Improving Readiness
When the readiness assessment surfaces gaps, the response depends on which condition is weak. Each scenario below is drawn from the pattern types AIM's field research has documented across initiatives in multiple industries. The actions described are structural, not motivational.
From the field
A large healthcare system's ERP rollout stalled at month three. The executive sponsor had endorsed the initiative at kick-off, then assigned day-to-day oversight to a program manager in IT. By the time the implementation team surfaced resistance patterns among clinical staff, the sponsor had moved on to a capital project and had not spoken about the initiative in six weeks.
What AIM recommends
Return to the sponsor and re-establish the specific behaviors the initiative requires. In AIM's framework, this is not a coaching conversation about engagement. It is a structural clarification: the Required Sponsorship Activities cannot be performed by proxy. Use the Sponsor Assessment to identify which of the Expressed, Modeled, and Reinforced commitment categories are weak, and build a specific plan to address them before the initiative falls further behind.
From the field
A retail organization retrained store managers on a new inventory process. The training was well-designed and well-attended. At the ninety-day mark, store-level compliance with the new process was below forty percent. Investigation found that existing productivity metrics still rewarded the old approach. Managers who followed the new process saw their numbers decline. Those who reverted saw them recover.
What AIM recommends
Audit the formal reinforcement systems, specifically performance metrics, recognition criteria, and management feedback practices, for direct conflicts with the target transforms behaviors. Where conflicts exist, they must be resolved before expecting sustained adoption. The reinforcement audit is not a communications exercise. It requires decision authority over metrics and evaluation systems, which means sponsor involvement is non-negotiable.
From the field
An initiative described its goal as 'improved cross-functional collaboration.' When field practitioners asked what that meant specifically, no two stakeholders gave the same answer. Without a shared behavioral definition, training had no clear target transforms, managers could not reinforce anything specific, and the initiative had no way to measure whether the change had occurred.
What AIM recommends
Define the target transforms behaviors in observable terms before proceeding. An observable behavior is something that a third party could see and verify: a specific action performed by a named role in a named context. 'Collaborate more effectively' is not observable. 'Supply chain lead confirms with regional sales director before finalizing procurement orders above threshold X' is observable. Starting from that level of specificity, the initiative can be assessed, trained, reinforced, and measured.
From the field
Senior leadership of a financial services firm was fully committed to a new compliance initiative. The front-office behavior changes required were significant. Six months post-launch, adoption rates were low. Post-implementation interviews revealed that middle managers had not been briefed on their sponsor role. They saw themselves as change recipients, not sponsors, and had not modified their own behavior or reinforced the new practices with their teams.
What AIM recommends
Build the sponsor cascade explicitly. Identify the management layers at which behavior change is required and assign sponsor responsibilities to leaders at each level. Each layer of the cascade requires its own Expressed, Modeled, and Reinforced commitment. Waiting for behavior change to flow down from senior leadership through passive middle management is a pattern AIM's research consistently identifies as a primary reason initiatives stall before reaching frontline staff.
From the field
A government agency implementing a new case-management platform found usage rates declining at month two. Informal interviews with frontline workers surfaced consistent themes: the new system added processing time per case, caseload targets transforms had not been adjusted, and supervisors were not using the system themselves. Resistance was not hostility. It was a rational response to conditions that made adoption costly.
What AIM recommends
Treat resistance as information, not as an attitude problem. AIM's approach requires surfacing resistance through direct feedback channels, then classifying the concerns: are they process issues that can be fixed, workload issues that require sponsor decisions, or modeling gaps that require leadership behavior changes? Resistance that is acknowledged and addressed at source dissipates. Resistance that is dismissed or driven underground compounds. The distinction is whether the sponsor is involved in the response.
A note on measurement
Measuring readiness in observable terms is what makes it possible to act on. A vague sense of buy-in cannot be tested, tracked, or corrected. Observable conditions can be verified, assigned accountability, and monitored over time.
When a readiness indicator is phrased as "employees understand the rationale for the change," it cannot be confirmed or denied through observation. When it is phrased as "sponsors have communicated the business case in team meetings at least twice in the past four weeks," it is verifiable. The sponsor either has or has not. That specificity is what allows a readiness gap to become a workable problem with a person responsible for closing it.
This is the core discipline that distinguishes AIM's approach from readiness models based on attitude surveys or training completion rates. Attitudes are difficult to observe and difficult to change deliberately. Behaviors can be modeled, reinforced, measured, and held accountable. AIM treats readiness as a behavioral question, not a perceptual one.
For practitioners, the practical implication is straightforward: before conducting a readiness assessment, define the target transforms behaviors precisely enough that two independent observers would agree on whether each is occurring. If that definition does not yet exist, building it is the first task of the assessment process, not a byproduct of it. See the AIM framework overview for the distinction between installation and implementation that underpins this approach.
Readiness connects to the Required Sponsorship Activities that cannot be delegated, the AIM Tools that structure the assessment, and the foundational distinction between installation and implementation.
About this methodology
The Accelerating Implementation Methodology (AIM) was created by Don Harrison, founder of Implementation Management Associates. The methodology is delivered and developed by IMA Worldwide and Peacock Hill Consulting, which acquired IMA in 2024 and continues to deliver AIM training and implementation support. For the primary source on AIM's methodology, see imaworldwide.com/what-is-aim.