Digital

The digital transformation playbook nobody wants to run

June 18, 2026 · 7 min read

Most digital transformation programs start with the same slide: a maturity curve, a competitor comparison, and a bold claim about becoming "digital-first." Leadership nods, budget gets approved, and eighteen months later the organization has a new app, a new CMS, and roughly the same operating model it had before. The technology changed. The way decisions get made didn't.

The slide that gets skipped is the one nobody wants to present: which existing process are we willing to kill, and which team is going to lose ownership of it. Transformation isn't additive. You can't layer a modern digital experience on top of an analog decision-making structure and expect the two to reconcile themselves. Somewhere, a manual approval step, a legacy reporting line, or a team's entire reason for existing has to change shape — and that's the conversation every deck avoids by staying at the level of "capabilities" and "platforms."

In the transformation I ran across a multi-brand retail portfolio, the technology rollout was the easy 30%. The other 70% was renegotiating who owned the customer relationship once it moved online, and rebuilding incentive structures so regional teams weren't quietly sabotaging a channel that competed with their own numbers. No amount of good UX fixes a team that's financially motivated for the new platform to fail quietly.

If your transformation roadmap doesn't name a team, a role, or a process that's going away, it isn't a transformation — it's an IT upgrade with better branding. The organizations that actually change are the ones willing to have that uncomfortable slide in the deck, present it early, and let people react to it before the budget is spent.