Why Strategic Solutions Become Implementation Problems
Most large organizations run a long change agenda. CRM, supply chain redesign, ERP, shared services, Six Sigma, Lean, data warehousing — each initiative is strategic, expensive, and promises significant ROI. Many deliver far less than expected.
This is the paradox: instead of producing an integrated suite of business solutions, organizations often end up with a disparate and complex set of implementation problems that consume scarce resources without generating the returns that justified the investment.
The intent is progress and integration. The lived experience is complexity, disruption, and a constant sense of "why is this harder than it should be?"
This is not a strategy problem. The strategy is usually sound. It is an implementation problem — and implementation problems are predictable, diagnosable, and solvable when you know what to look for.
The 8 Predictable Barriers That Derail Major Change
These barriers are not surprises. They show up across nearly every major implementation effort. The organizations that struggle are not failing because of unique, unforeseeable problems. They are failing because of predictable, diagnosable barriers — many of which were visible before launch.
Any 1 of these 8 barriers is enough to slow execution and reduce outcomes. Enterprise-wide change doesn't introduce new barriers — it amplifies all 8 simultaneously, across every silo in the organization.
Cross-Functionality vs the Organizational Silo
Enterprise-wide change has a specific dynamic that single-initiative change does not. There is a tension point at the center of every transformation — the gap between where the organization is and where it needs to go.
| Dimension | Status Quo | Desired State |
|---|---|---|
| Structure | Vertical silos with localized goals | Horizontal organizations with shared outcomes |
| Process ownership | Each silo owns its own processes and metrics | Cross-functional process ownership and shared accountability |
| Culture | Rewards silo performance — individual team metrics | Rewards cross-functional collaboration and enterprise results |
| Leadership | Leaders protect departmental territory and budgets | Leaders sponsor cross-silo change and align reinforcement |
| Implementation approach | Each silo uses disconnected methods | 1 common, structured methodology across the entire portfolio |
Inside each silo are localized goals, political dynamics, sub-cultures, and functional processes. When multiple silos are disrupted at the same time — all running separate implementations with no common approach — you get what IMA's research calls the "Box Effect."
🌀 The Box Effect: A Hurricane of Implementation Chaos
Multiple disconnected initiatives hit multiple silos simultaneously. Each silo manages its own disruption in isolation. There is no shared language, no common methodology, no integrated sponsorship.
Each silo running 2–3 simultaneous initiatives with disconnected approaches = the hurricane rages out of control.
As change strategist John Kotter has noted, when change must cut across silos, it is one of the hardest challenges in management — and most organizations have far less capability to do it than they believe.
The False Simplicity Trap: Fixing One Barrier
When the implementation hurricane hits, leadership usually does 1 of 4 things. Each feels reasonable. Each makes the problem worse — because each treats a systemic failure as a single-point problem.
| The Fix Attempted | Why It Feels Right | Why It Fails |
|---|---|---|
| Stronger communications | "People just don't understand the change." | Communication is 1× weight. Without modeling and reinforcement, messaging generates resistance, not adoption. |
| Greater urgency | "People aren't feeling the pressure to change." | Urgency without readiness increases anxiety. Resistance grows when people feel forced without support. |
| Culture initiative | "Our culture is the problem." | Culture is an output of what gets reinforced — not a lever you can pull directly. Fixing culture without fixing reinforcement changes nothing. |
| Better project management | "We just need tighter execution." | PM tracks technical delivery. It doesn't address the 8 human-side barriers that determine whether people actually adopt. |
IMA's research calls this "false simplicity." Ironically, many organizations pursue cross-functionality in a siloed way — each process owner so focused on their own process that a functional silo is simply replaced by a process silo. The hurricane keeps raging.
What is required instead is an approach that addresses organizational change as a system. Not 1 fix applied to 1 barrier — but a methodology that is scalable, replicable, practical, customizable, and systemic across the entire portfolio.
A Structured, Systemic Approach: IMA's AIM
Decreasing the risk of implementation failure is the goal. IMA's AIM — Accelerating Implementation Methodology — is the structured approach for doing that at enterprise scale. It is tactical, repeatable, practical, and grounded in 40+ years of field research.
AIM is not a framework you apply to 1 initiative at a time. It is a common methodology that gives every silo, every team, and every leader a shared language and a shared process. When 5 silos are each running 3 initiatives, that common foundation is the only thing that prevents the hurricane from spinning out of control.
"A fractured implementation approach results in fractured results. This complexity can only be managed with a common and structured approach."
— IMA White Paper: The Paradox of Enterprise-Wide ChangeAIM includes data-driven diagnostic tools that help organizations do 2 things they cannot do with a point-solution approach:
- Measure the strengths and weaknesses likely to appear when multiple initiatives are deployed across multiple silos at the same time
- Develop targeted strategies to reduce implementation barriers and leverage organizational strengths before they become problems
Each step of the AIM roadmap addresses 1 or more of the 8 predictable barriers. The steps can also be "unbundled" for high-leverage execution — so organizations can prioritize the highest-risk areas first without waiting to run the full process.
AIM research: implementations with actively involved leaders consistently outperform those with uninvolved leaders — across 40+ years and 1,000+ documented implementations.6 Enterprise-Wide Application Points from the AIM Roadmap
The AIM roadmap covers 10 areas of implementation — each with its own diagnostic tools and research-backed practices. In the context of enterprise-wide change, 6 of those areas carry the highest risk when change must cut across silos. The IMA white paper on the paradox of enterprise-wide change identifies these as the critical pressure points to address first.
Define the Change
Who are the key stakeholders? How are they impacted? What critical behaviors must be adopted to support a cross-functional strategy?
Assess the Climate
Is the aggregate implementation activity already exceeding the organization's threshold for change?
Generate Sponsorship
How will you gain and sustain widespread, aligned leadership commitment — both across silos and down each silo's management chain?
Develop Target Readiness
How will you manage the inevitable resistance across all levels of the organization's various silos?
Build a Communication Plan
How will messaging speak to each silo's frame of reference — so employees in each area can answer "What's in it for me?" and "What's going to happen to me?"
Create Cultural Fit
Does your culture reward cross-functional collaboration — or silo competition? What gets reinforced determines what behaviors persist.
These 6 areas don't need to be applied all at once. AIM is designed to be "unbundled" — organizations can prioritize the highest-risk areas first. A climate assessment run before launch can surface capacity problems before they become crises. A sponsorship diagnostic can identify alignment gaps before the hurricane builds. The full 10-area roadmap is available when the scope requires it.
One Company Outcomes — Not Fractured Results
The logic for a "One Company" business model is compelling. The potential ROI is significant. When enterprise-wide change actually works — when it is managed as a system instead of a collection of parallel silos — these 4 outcomes become achievable.
Improved customer satisfaction
Customers experience the organization as 1 coherent entity — not as 5 departments that don't communicate with each other
More effective use of resources
Shared services, common platforms, and integrated processes eliminate duplicate effort across silos
Stronger internal collaboration
Cross-functional teams work toward shared objectives rather than competing for silo-level metrics
Faster response to market changes
A unified organization can shift direction in weeks. A siloed one takes months — while each unit waits for the others
The implementation challenge is real. Enterprise-wide change requires business-side changes — strategy, structure, operations, technology — and people-side changes — expectations, perceptions, behaviors, skills — all happening at the same time, in a context of organizational politics, emotion, and resistance.
This complexity can only be managed with a common and structured approach that purposefully integrates solutions to create One Company results. The alternative is a fractured implementation approach — and fractured results. Organizations spend millions on strategies that stall at implementation because the human side of the change is treated as secondary to the technical side.
IMA's AIM gives organizations the structured approach they need to manage both sides — at portfolio scale, across all silos, with a common methodology that every team can apply.
Managing Multiple Cross-Functional Initiatives?
If execution is getting harder instead of easier, Peacock Hill Consulting can help you reduce implementation risk with a repeatable, data-driven approach that scales across your entire change portfolio.