Ruin
I have been involved in multiple transformation engagements, including situations where programs had to be stabilized after months of “progress” with little real value delivered. Over time, a clear pattern emerges: most problems are not caused by the technology itself. They are caused by leadership misalignment, unclear decision rights, weak governance, vendor incentives that do not match business outcomes, and insufficient readiness for the people and process change.
This post summarizes the observations that repeat across industries and program types. It is written for executives because the root causes are usually executive-level issues, and the most effective fixes also sit at that level.
Technology is rarely the hardest part
When a transformation struggles, the delivery team often asks for more time, more budget, or a better partner. In recoveries, the real breakthroughs usually come from a different move: making the leadership and governance system work.
If you remember one thing, let it be this: A transformation is a decision program, not a software program.
Strategic alignment and leadership: where programs really slow down
What I repeatedly see:
A unified vision exists only on slides. Executives say they agree, but each department optimizes for its own priorities.
The program is treated as a “big IT project.” Leadership expects a go-live event to produce value automatically.
Steering committees exist, but do not steer. Meetings become status updates, not forums for resolving disagreements.
Why it matters
When priorities conflict, the delivery team cannot design stable processes. Every workshop becomes a negotiation. Every decision is revisited. The program continues to “move” but does not converge.
Executive actions that change outcomes:
Write down the value definition in business terms (for example: shorten order-to-cash by X days, reduce manual rework by Y percent, reduce operational risk in Z area). Keep it short and measurable.
Assign a single accountable business owner per end-to-end process, not per department and not per system module.
Create explicit decision rights: who decides process, data standards, risk acceptance, and scope tradeoffs. If decision rights are unclear, decisions will default to politics.
Partner and vendor management: outsource delivery, not accountability
What I repeatedly see
Partners optimize for speed and billable scope. That is rational behavior given how most contracts work.
Brand selection replaces fit selection. A strong logo is treated as proof of capability in your specific context.
Technical jargon becomes a shield. Complex terminology is used to deflect from product limitations, unclear requirements, or missing design work.
Governance drifts to the partner. External teams end up setting the agenda, the pace, and sometimes even the definition of success.
Why it matters
If the vendor drives the agenda, you risk delivering a technically “implemented” solution that is not operationally adopted. The organization then pays twice: first to implement, second to fix.
Executive actions that change outcomes
Keep governance client-owned. Vendors can prepare materials, but you control decision-making, priorities, and acceptance criteria.
Measure vendors on outcomes, not only milestones. Require evidence of adoption readiness, operational stability, and business impact, not only “configuration complete.”
Demand plain language. If an issue cannot be explained simply, it usually is not understood properly or it is being avoided.
Protect your long-term leverage. Ensure contracts and delivery plans include clear ownership of data, integrations, documentation, and transition support.
Organizational readiness and change: generic training does not create adoption
What I repeatedly see
Change management is treated as communication plus training. Often this is a few emails, a short training schedule, and a launch event.
Training focuses on tool features, not on workflows. Employees learn where to click, not how their work will change.
The operating model is not updated. Roles, approvals, controls, and escalation paths remain as they were before the transformation.
Post go-live is underfunded. Support drops immediately after go-live, exactly when the organization needs it most.
Why it matters
Business value depends on people using the new way of working consistently. If daily routines do not change, the system becomes an expensive overlay on old processes.
Executive actions that change outcomes
Require role-based enablement tied to real work. “Day in the life” scenarios are more valuable than generic training.
Fund reinforcement after go-live. Coaching, floor support, local champions, and performance tracking are what prevent reversion to old habits.
Update incentives and accountability. If people are measured on old metrics, they will keep old behaviors.
Define who owns adoption. Adoption is not owned by IT. It is owned by business leaders, supported by IT and the program.
Resource and risk management: the hidden cost is internal capacity
What I repeatedly see
Key internal experts are overloaded. They are expected to run business-as-usual and deliver transformation at the same time.
“Green” status persists for too long. Reports stay optimistic until late-stage issues become undeniable.
Aggressive dates override operational reality. Teams are pushed to hit go-live even when readiness indicators are weak.
Risk ownership is misunderstood. When things go wrong, organizations discover that vendors do not carry the real operational risk.
Why it matters
Most large failures are not sudden. They are slow accumulations of ignored warnings: weak readiness, unresolved design decisions, untested operational scenarios, and exhausted internal teams.
Executive actions that change outcomes
Treat capacity as a strategic constraint. Decide what will stop so your best people can focus.
Replace comfort metrics with leading indicators. For example: process sign-off completion, data quality thresholds, training completion for critical roles, pilot performance, support ticket trends.
Make “no-go” a real option. If readiness is not met, delaying go-live is cheaper than recovering from disruption.
Keep operational continuity as a primary success criterion. Hitting a date is not a victory if the business suffers for months afterward.
Red flags you should treat as early warning signals
If you see these patterns, the program is at risk even if reports look positive:
Steering meetings are mostly status updates and few decisions are made.
Multiple versions of the truth exist about scope, success metrics, or process design.
“We will fix it after go-live” becomes a default response.
The partner is leading stakeholder management instead of internal leadership.
Training is generic and late, and operational support is not clearly funded.
All dashboards are green, but frontline teams express confusion, fatigue, or resistance.
Critical business process decisions are repeatedly deferred.
A simple playbook for stabilizing a transformation
If you are starting fresh or recovering a struggling program, these are the highest leverage moves:
Step 1: Re-anchor the program (2 weeks)
Define measurable business outcomes.
Confirm a single accountable owner per end-to-end process.
Lock decision rights and escalation rules.
Step 2: Rebuild governance (2 to 4 weeks)
Convert steering to a decision forum with a clear decision log.
Require forward-looking risk indicators and interdependency tracking.
Make tradeoffs explicit: scope, timeline, cost, risk, and operational disruption.
Step 3: Reset vendor control (2 to 6 weeks)
Align vendor plan and reporting to outcomes and readiness, not only delivery.
Simplify communication: plain language explanations and clear options.
Ensure you can operate the solution without the vendor permanently embedded.
Step 4: Fund adoption properly (continuous)
Role-based enablement tied to workflows.
Reinforcement and support post go-live.
Ownership for adoption and operational performance, not only project delivery.
Closing
Digital transformation succeeds when leadership treats it as a strategic shift in operating model, not as a technical rollout. In the engagements I have seen, the strongest predictors of success are consistent: unified executive alignment, active sponsorship that resolves real conflicts, governance that enforces decisions and transparency, vendor management that protects outcomes, and change enablement that reshapes daily work.