Digital Transformation · 8 min read · Sekhar Palanisamy

Digital Transformation Leadership: The CEO and COO Playbook

After leading digital transformation programs at Dell and inside mid-market businesses, the pattern is consistent: technology is rarely the problem. Leadership is almost always the problem. Here's how to fix that.

The mid-market digital transformation conversation has changed dramatically. Five years ago, it was about ERP modernization and moving to the cloud. Today it's about AI integration, data infrastructure, and building the operational systems that let a $50M–$300M business compete with companies ten times its size. The technology options are better than ever. The leadership challenges are the same as they've always been.

The CEO's role: set the mandate, protect the investment

The CEO's job in a digital transformation is not to understand the technology. It is to establish an unambiguous mandate — this is happening, it is resourced, and we are not going back — and then protect the program from the organizational immune system that will try to reject it. Every transformation encounters resistance. The CEO's visible, consistent commitment is the single most important variable in whether that resistance wins or loses.

What CEO commitment looks like in practice: attending the monthly transformation review, not delegating it. Calling out backsliding publicly, not letting it slide. Allocating real budget, not a pilot budget. And making the first hard call — the manager who won't change, the process that needs to be retired, the vendor who needs to be replaced — visibly and early.

The COO's role: translate strategy into governed execution

The COO owns the execution layer of the transformation. That means governing the program cadence — weekly reviews, milestone accountability, resource allocation decisions. It means owning the change management layer — ensuring that training, communication, and behavioral reinforcement are happening at the pace the program requires. And it means being the person who identifies what's slowing the program down before the CEO has to ask.

The best COOs I've seen in transformation situations have one habit in common: they spend as much time on the human side of the change as on the technical side. The ERP goes live in six months. The behavior change takes eighteen. The COO who only governs the technical timeline will consistently underdeliver.

The technology never fails as dramatically as the governance does. Fund the change management program at the same level as the technology implementation — or accept that the technology will not deliver its intended value.

The governance structure that works

Successful mid-market digital transformations share a common governance pattern: a steering committee that meets monthly (CEO, COO, CFO, and functional heads), a program management office that meets weekly (COO and workstream leads), and a clear escalation path for decisions that cross functional lines. The PMO is not optional. Without it, the transformation is a collection of parallel workstreams with no coordinating mechanism — and no one to make the calls that fall between functions.

Where mid-market transformations specifically break down

Mid-market companies face a specific challenge that large enterprises don't: the people running the business today are the same people who need to transform it. There is no transformation team separate from the operations team. Your VP of Ops is running operations and leading the ERP implementation simultaneously. Your IT director is supporting current systems and building the new infrastructure at the same time. Capacity is the constraint — and the companies that manage it well are the ones that either bring in dedicated transformation resources (a fractional COO, a program lead, external implementation support) or are ruthlessly disciplined about what not to do during the transformation period.

The 90-day launch sequence that works

The first 90 days of a digital transformation set the trajectory for everything that follows. The sequence that consistently works: 30 days of structured diagnosis (current state assessment, constraint identification, stakeholder alignment); 30 days of program design (roadmap, governance model, resource plan, quick win identification); 30 days of launch (first initiative underway, first win delivered, governance cadence running). By day 90, the organization should believe the transformation is real. If they don't, the rest of the program will be fought uphill.

Leading a transformation that needs operational momentum?

Book a 30-minute strategy call. I'll assess where you are and tell you exactly what I would focus on first.

More from the blog