AIM identifies six tasks that only the sponsoring leader can perform. Delegating them is the single most common reason change initiatives stall.
This page is a practitioner reference for what leaders must personally do, drawn from AIM's decades of field research. Each task is defined, illustrated with a concrete scenario, and connected to the broader Accelerating Implementation Methodology (AIM) framework.
What "non-delegable" means in AIM: These tasks require the positional authority, visibility, and credibility of the sponsoring leader. A change manager, project team, or communications function cannot substitute for them. When a leader reassigns these tasks, AIM field research consistently finds that the initiative completes installation but not implementation: systems are deployed but behavior does not change.
Part of the Why Transformation Initiatives Fail reference series on theaimmethodology.com. See also: Change Readiness and Why Transformation Initiatives Fail.
AIM identifies six leadership tasks that are non-delegable by definition, not by preference. A change manager, a consultant, or a project team can support these tasks, but cannot perform them on the leader's behalf. What follows is a numbered reference summary. Each task is examined in detail in the sections below.
Communicate personal commitment to the initiative in observable terms. Expression goes beyond a kickoff speech: it requires repeated, specific, visible statements that connect the initiative to business priorities.
Demonstrate the required behaviors visibly, before expecting them of others. Leaders who ask for new behaviors without demonstrating them personally send a contradictory signal that undermines adoption.
Respond consistently to both progress and resistance with targeted consequences. AIM's field research indicates reinforcement carries approximately three times the weight of communication in driving sustained adoption.
Establish and maintain the coalition of sponsors needed across the organization. Most initiatives require a cascade of sponsors, not a single executive. The initiating sponsor must actively recruit and align downstream sponsors.
Identify, diagnose, and address resistance at its source rather than avoiding or dismissing it. AIM distinguishes between resistance as a symptom and resistance as a root cause, and treats each differently.
Connect the initiative to a recognized, felt business need. When recipients cannot see a clear connection between the change and a genuine organizational problem, the initiative reads as arbitrary.
Why non-delegable? Each task requires an act that carries organizational authority: only the sponsoring leader can signal, through their own behavior, that the initiative has genuine priority. Change managers and consultants can coach, diagnose, and advise, but the observable acts of expressing, modeling, reinforcing, building coalitions, addressing resistance, and acknowledging pain must come from the leader in a position of authority over the affected population. The sections below examine each task in depth, with scenarios drawn from AIM's decades of field research. See also the Why Transformation Initiatives Fail reference for how gaps in these tasks map to common failure patterns.
In AIM terms, Express means the sponsoring leader makes repeated, specific, and visible statements that connect the initiative to recognized business priorities. It is the first pillar of the Express, Model, Reinforce (EMR) framework. Expression alone carries the least weight of the three pillars. It is necessary, but insufficient without the actions that follow.
A senior leader sends a well-crafted email on the day a new operating model rolls out. The message is clear, the rationale is sound, and it signals genuine intent. Then silence. The leader attends no working sessions, offers no comment in staff meetings when the initiative comes up, and responds to questions about it with brief reassurances rather than substantive engagement.
Within weeks, the organization reads that silence as signal. People draw their own conclusions: either the leader has moved on to other priorities, or the initiative is lower-stakes than the launch email implied. In AIM's field research, this pattern appears consistently as one of the earliest indicators that an initiative will stall before it reaches full implementation.
A leader who expresses effectively does not rely on the launch communication to carry all the weight. Instead, expression is woven into ongoing interactions: a reference to the initiative in a quarterly review, a direct question at a leadership team meeting about adoption progress, a brief comment in a town hall that ties current results to the initiative's stated goals.
The content matters as much as the frequency. Effective expression is specific, not generic. It names the initiative, connects it to outcomes the audience cares about, and signals that the leader is tracking progress rather than simply having signed off on it.
Express is the leader's ongoing, specific communication of commitment to an initiative. It goes beyond an announcement: it requires the leader to repeatedly and publicly connect the initiative to business priorities in forums where the target transforms population is present or informed. In AIM's EMR framework, expression establishes intent but does not, on its own, produce behavior change.
AIM's EMR framework (Express, Model, Reinforce) is the leadership communication and behavior system at the core of the six non-delegable tasks. The three components are not equal in weight. Reinforcement carries approximately three times the weight of communication. Expression, while the most visible and easiest to execute, is the foundation, not the driver, of sustained adoption.
A leader who expresses clearly but does not yet model the required behaviors, or whose reinforcement patterns still reward the old way of working, will find that expression alone produces initial awareness without durable change. This is why Express is listed as Task 1: it is where visible commitment begins, and it must be sustained, not concluded, at launch.
Repeated, not one-time
Expression must occur across multiple touchpoints over the life of the initiative, not only at launch.
Specific, not generic
Statements name the initiative, name the expected behaviors or outcomes, and make the connection to business priorities explicit.
Visible to the target transforms population
Expression must reach the people who are expected to change. Private statements to a steering committee do not substitute.
Sustained through resistance
When adoption slows or resistance surfaces, the leader's expression must continue and intensify, not taper off.
Model and Reinforce form the behavioral core of AIM's Express, Model, Reinforce (EMR) framework. Together they convert stated intent into observable organizational reality. AIM field research places reinforcement at approximately three times the weight of communication: expression sets direction, but reinforcement determines whether the organization treats that direction as binding.
Task 2 of 6
The leader demonstrates the required behaviors visibly, before expecting them of others.
Scenario
Consider a senior vice president who opens every all-hands meeting by affirming the importance of a new cross-functional collaboration initiative. After the meeting, she routes all decisions through her own direct reports and never consults the adjacent functions the initiative is meant to connect. Within weeks, her team reads the real signal: collaboration is a talking point, not a requirement.
What 'Model' means in AIM terms
Modeling is the visible, repeated demonstration of the behaviors the initiative requires. It is not a symbolic gesture at launch. It is the leader doing, in observable ways, exactly what she is asking the organization to do. If the initiative requires cross-functional input before decisions, the leader provides cross-functional input before decisions, every time, in view of the people she leads.
AIM's field research shows that when leaders describe desired behaviors without enacting them, recipients treat the description as aspirational at best and performative at worst. Modeling removes that ambiguity. It converts the expressed intent of Task 1 into observable evidence. Recipients no longer have to infer whether the leader is serious; they can observe it directly.
Modeling is particularly important early in an initiative, when recipients are still calibrating how much the stated direction will hold. A leader who models consistently in the first 30 to 60 days creates a credible reference point for the rest of the organization. A leader who models inconsistently in that window rarely recovers the trust needed to sustain adoption.
Note
Modeling cannot be delegated. A change manager or communications team can describe the desired behaviors in detail. Only the sponsoring leader can demonstrate them.
Task 3 of 6
The leader responds consistently to both progress and resistance with targeted transforms, observable consequences.
Scenario
A manufacturing company rolls out a new safety reporting system. The plant manager attends the launch event and praises the initiative publicly. Over the following month, supervisors who continue using the old paper-based process face no consequence. Supervisors who adopt the new system receive no recognition. After 90 days, usage of the new system has plateaued at roughly 40 percent. The plant manager is surprised. The organization is not.
What 'Reinforce' means in AIM terms
Reinforcement is the leader's visible, consistent response to behavior: acknowledging and rewarding movement toward the required change, and addressing, not ignoring, continued use of old behaviors. In AIM's framework, reinforcement is an observable consequence, not an encouragement campaign. It operates on both sides: progress is recognized specifically and publicly, and resistance is addressed directly and without delay.
AIM's EMR framework assigns reinforcement approximately three times the weight of communication (Express). Expression sets direction. Reinforcement determines whether the organization believes the direction is real.
The distinction matters in practice. Organizations in AIM field research consistently showed that sustained adoption correlated far more closely with the consistency of reinforcement than with the volume or quality of communications. Detailed change communications sent to a workforce whose leaders continued rewarding old behaviors produced minimal adoption. Sparse communications sent alongside visible, consistent reinforcement produced substantially higher results.
Reinforcement also includes responding to resistance. When a leader observes that a team is not adopting the required behaviors and does not respond, the organization interprets that silence as tolerance. AIM frames this as a reinforcement failure, not a communication failure. The leader is, in effect, reinforcing the old behavior by choosing not to address it.
What reinforcement is not
Reinforcement is not a recognition program administered by HR, a weekly motivational message from the change team, or a progress dashboard shared at quarterly reviews. Those are communications. Reinforcement, in AIM terms, is the leader's direct, targeted transforms response to specific, observed behavior, positive or corrective, delivered in a timeframe that creates a clear connection between the behavior and the consequence.
Note
Because reinforcement requires direct observation of and response to specific behaviors, it cannot be delegated to a project team, a communications function, or an HR partner. It requires the sponsoring leader's active, ongoing involvement.
EMR Framework: Weight of Reinforcement
Reinforcement carries approximately three times the weight of communication in AIM's EMR framework.
This finding, drawn from AIM's decades of field research, reframes the typical change management emphasis on communications planning. A well-executed communications strategy is necessary but not sufficient. The sponsoring leader's consistent reinforcement of required behaviors is the primary driver of sustained adoption. Organizations that invest heavily in communications while reinforcement remains inconsistent routinely see adoption plateau well short of the intended target transforms.
The remaining leadership tasks, building sponsor infrastructure, managing resistance, and acknowledging pain, are covered in the adjacent sections on this page.
Most change initiatives require more than a single sponsoring executive. When an initiative spans multiple business units, regions, or functions, each layer of the organization needs a sponsor who is visibly accountable for adoption in their area. Building sponsor infrastructure is the work of identifying, briefing, and maintaining alignment among those downstream sponsors. It does not happen by default.
The CIO announces a new ERP rollout with visible commitment: town halls, a steering committee, and weekly status reports. Regional managers across six business units receive a rollout timeline and a link to training materials. No briefing takes place. No one explains to them what their role is, what resistance they may face, or what decisions they are authorized to make.
Within two months, regional managers quietly deprioritize adoption. Pressed by their own operational targets, they treat the new system as a compliance burden rather than a business tool. Their teams follow their lead. The CIO's initiative stalls not because of technical failure, but because the sponsor cascade was never built.
In initiatives where sponsor infrastructure is built deliberately, the initiating sponsor identifies each downstream sponsor, meets with them individually or in structured briefings, clarifies their accountability, and maintains regular alignment through the life of the initiative. Resistance encountered at the regional level is surfaced and addressed rather than absorbed silently.
Only the initiating sponsor carries the organizational authority to hold downstream sponsors accountable. A change manager or program coordinator can support the process by preparing briefing materials or scheduling touchpoints, but the act of establishing accountability belongs to the executive who owns the initiative. When the initiating sponsor delegates this task, downstream sponsors receive no signal that their commitment is genuinely required.
AIM's field research identifies absent or misaligned sponsor cascades as one of the most consistent contributors to adoption failure in multi-unit rollouts. The initiating sponsor may be fully committed; the problem is that their commitment does not travel through the organization unless they actively build the infrastructure for it to do so.
Identify the full sponsor cascade
Map every organizational layer where adoption is required. Each layer needs a sponsor who is visibly accountable for results in their unit, not just for completing training.
Brief each sponsor directly
Downstream sponsors need a clear understanding of the business case, their specific role, the behaviors expected of their teams, and how resistance should be handled. A forwarded email does not constitute a briefing.
Establish regular alignment touchpoints
Sponsor alignment degrades over time as operational pressures compete for attention. Structured, recurring touchpoints between the initiating sponsor and downstream sponsors keep the initiative visible and priorities clear.
Define accountability and escalation paths
Each downstream sponsor should know what they are accountable for, what metrics signal progress, and what happens if adoption targets transforms are missed in their unit. Ambiguity at this level is a common source of stall.
Respond to resistance as organizational information
When downstream sponsors surface resistance, the initiating sponsor treats it as useful signal: Where is adoption breaking down? What barriers exist that the sponsor cascade has not addressed? This loop is central to what AIM means by sponsor infrastructure.
The Express, Model, Reinforce (EMR) framework describes how a sponsor communicates commitment. Sponsor infrastructure determines who, across the organization, is performing those EMR behaviors in each unit. A well-built sponsor cascade means that every affected group has a leader who expresses support, models the required behaviors, and reinforces adoption through observable consequences. Without the cascade, EMR may function at the executive level while failing entirely at the point of adoption. AIM field research indicates that reinforcement carries approximately three times the weight of communication. Downstream sponsors are the people closest to where reinforcement happens or fails.
A common confusion is treating sponsor infrastructure as a subset of stakeholder communications. Communication plans address what messages flow to which audiences. Sponsor infrastructure addresses who is accountable for driving adoption in each part of the organization, and whether those people have the information, authority, and alignment to fulfill that accountability.
Downstream sponsors are not message recipients. They are organizational agents of the initiative. The distinction matters because the actions required of them are different: they must conduct briefings with their own teams, address resistance in their units, and provide feedback to the initiating sponsor about where adoption is breaking down. A communication plan alone does not produce those behaviors.
The final two non-delegable tasks address the human dimension of any initiative. Managing resistance requires diagnosis before response. Acknowledging pain connects the initiative to a felt, recognized need. Both tasks demand direct leadership involvement because neither can be delegated to a program office or handled by a communications campaign.
Task 5
In practice
A regional sales team adopts a new CRM system. Six months in, data entry compliance is at 40 percent. The initiative sponsor escalates to IT, who issues reminders and refresher training. Usage holds flat. The real issue: sales managers believe the system benefits head office reporting, not their daily work. No one diagnosed where the resistance lived or why. The reminders addressed activity, not cause.
AIM distinguishes between resistance as a symptom and resistance as a root cause. Most organizations treat resistance as an obstacle to overcome: communicate more, train more, escalate consequences. AIM's field research identifies this as a common accelerant of failure. Resistance is a signal. Leaders who treat it as noise miss the diagnostic information it carries.
In AIM terms, managing resistance requires three distinct actions from the sponsoring leader:
The non-delegable element here is sponsor credibility. A program manager can collect feedback. Only the sponsoring leader can signal that the feedback has been heard and that the response is intentional. When leaders label resistors as obstacles rather than as information sources, they remove their own diagnostic access to the initiative's adoption health.
AIM does not frame resistance as a character issue or a failure of the people experiencing change. It frames resistance as a predictable organizational response that carries useful information about alignment, readiness, and system integrity.
Task 6
In practice
A healthcare network consolidates billing operations across three regional sites into a centralized shared-services function. The business case is clear at the executive level: cost reduction and compliance consistency. At the site level, staff perceive an unexplained reorganization of their work and a reduction in local decision-making. No senior leader publicly names what is being asked of them or why their current way of working is no longer sustainable. Within three months, informal workarounds emerge and the consolidation timeline slips.
AIM requires that the sponsoring leader connect the initiative to a felt, recognized business need. When this step is skipped, recipients experience the change as arbitrary. The instruction to adopt new behaviors arrives without a credible account of why the current state is no longer viable. People fill that gap with their own interpretations, which are often more alarming than the reality.
Acknowledging pain is not an exercise in empathy messaging. In AIM's framework, it is a specific leadership action with two components:
AIM's field research consistently identifies the absence of this task as a contributor to late-stage initiative failure. Organizations complete installation (the system is deployed, the process is documented) but adoption stalls because the rationale for sustained behavior change was never clearly established at the outset.
Task 6 is positioned last in the sequence not because it is least important, but because it is most directly connected to sustained behavior change. Without a recognized reason for change, reinforcement efforts in Task 3 lose their referent. People comply temporarily but revert when oversight recedes.
How Tasks 5 and 6 interact
These two tasks reinforce each other. A leader who has clearly acknowledged pain (Task 6) has already established a foundation for managing resistance (Task 5): people who understand the business rationale for a change are more likely to engage in constructive dialogue about what is difficult, and less likely to interpret all friction as evidence the initiative itself is wrong. Conversely, a leader who manages resistance effectively, by diagnosing it rather than dismissing it, creates the psychological safety that allows people to name what is hard, which is the precondition for Task 6 to land with credibility.
Task 1
Express
Task 2
Model
Task 3
Reinforce
Task 4
Sponsor Infrastructure
Task 5
Manage Resistance
Task 6
Acknowledge Pain
An enterprise HR platform goes live on schedule. Licenses are purchased, the system is configured, training sessions run, and the go-live date passes without incident. Six months later, adoption data shows that fewer than a third of managers are using the system consistently. The rollout succeeded. The implementation did not.
AIM draws a precise line between two outcomes that are often conflated. Installation means deploying a system, introducing a process, or completing the technical rollout of a change. Implementation means sustained behavior change and measurable results. The gap between them is the difference between a change that is present in the organization and one that is embedded in how people actually work.
This distinction is the difference between installation (deploying a system) and implementation (sustained behavior change and results). It is not a semantic point. AIM's field research, accumulated across 40+ years and thousands of initiatives, shows consistently that organizations complete installation at far higher rates than they achieve implementation. The behavior change required to realize the value of a new system or process is the harder and slower part. It requires deliberate, sustained leader action over time.
Leaders who treat rollout as the finish line typically complete installation but not implementation. Once the new system goes live or the new process is announced, they redirect attention to the next initiative. The organization receives a clear signal: the change is not being watched, and compliance is optional.
AIM's six non-delegable leadership tasks are the mechanism by which a leader moves an initiative from installed to implemented. Each task addresses a specific and predictable gap between rollout and sustained adoption. Expressing visible commitment over time (not just at launch), modeling the required behaviors before expecting them of others, reinforcing progress and addressing resistance with observable consequences: these are not supplementary activities. They are the core of implementation as AIM defines it.
Each task on the list requires the sponsoring leader's visible, personal involvement. A project management office can track milestones. A change management consultant can assess readiness and coach teams. A communications team can draft messages. None of them can substitute for the sponsoring leader standing in front of the organization and demonstrating, through repeated behavior, that the initiative matters and that the new ways of working are expected.
The word "non-delegable" in AIM's framing is precise. It does not mean leaders must do all the work. It means that for these six specific tasks, the leader's personal and visible involvement is the task. Assigning them to someone else does not transfer the function. It removes it from the initiative entirely.
Installation
Deploying a system
Implementation
Sustained behavior change and results
The six tasks described in the sections above are organized around this gap. Express, Model, Reinforce, Build Sponsor Infrastructure, Manage Resistance, and Acknowledge Pain are not a generic leadership checklist. Each one targets a specific failure point in the journey from installed to implemented. Understanding why installation and implementation are different is the prerequisite for understanding why each task on the list is necessary and non-delegable.
The six non-delegable tasks are one component of a complete change management system. AIM addresses readiness assessment, failure patterns, and direct comparisons with peer frameworks. The sections below continue that reference.
Examine the patterns that cause initiatives to stall at installation and never reach sustained adoption.
Understand how AIM assesses an organization's readiness before and during a change initiative.
Compare AIM with ADKAR and the 8-Step model across leadership roles, measurement, and reinforcement design.
Why Transformation Initiatives Fail
This reference covers AIM's complete framework: what the methodology is, how its leadership tasks work, where initiatives break down, and how AIM compares with peer change management approaches.
AIM (Accelerating Implementation Methodology) was created by Don Harrison, founder of Implementation Management Associates (IMA Worldwide), and refined across 40+ years of field research. It is delivered by IMA Worldwide and Peacock Hill Consulting. Peacock Hill Consulting acquired IMA in 2024, and the two deliver AIM together.