There's a meeting that happens in nearly every mid-market services company attempting digital transformation. It's usually framed as a planning session…Everyone arrives with a problem. Everyone leaves with a grievance.

The hidden cost of functional misalignment in digital transformation

There's a meeting that happens in nearly every mid-market services company attempting digital transformation. It's usually framed as a planning session. The CEO or COO has finally gotten the right people in the room — department heads from operations, finance, technology, sales, customer service, HR. The agenda says "strategic priorities." The unspoken agenda is something closer to a budget negotiation.

Everyone arrives with a problem. Everyone leaves with a grievance.

This is the meeting where transformations die before they start.

The Three Cohorts in Every Room

In the dozens of transformation engagements we've run across financial services, transportation, healthcare, and HR support businesses, the leadership layer almost always fractures into the same three groups.

The first group is running the day-to-day. They're meeting requirements, managing their teams, and not looking for additional complexity. A new platform means new things to learn, new things to support, and new ways to fail. They're not obstructionist by nature — they're optimizing for stability in a role that rewards stability.

The second group wants to improve. They're interested in better tools, better customer outcomes, and the kind of results that show up in performance reviews. They have ideas, but they're operating within the constraints of their department. Their lens is their function, not the business as a whole.

The third group sees the whole board. These are the leaders who understand what happens upstream and downstream from their team. They think in systems. They've built informal relationships across the organization because they had to — because solving problems in their area requires understanding problems in adjacent areas. They're the ones who show up to the planning session with a cross-functional proposal and leave frustrated when it gets reduced to a line item.

None of these groups are wrong. But when they're all competing for the same limited budget with no shared destination to organize around, the result isn't strategic planning. It's a negotiation between fiefdoms.

The IT Problem Nobody Talks About

There is a fourth cohort that rarely gets the attention it deserves: the legacy IT team.

In most established services businesses, IT is structured as a support function — built to do for the organization, not to enable it. Their job is to keep things running. Their performance is measured by uptime, response time, and ticket resolution. Every new tool represents a new support burden, new documentation, new training, new failure modes.

This is not a technology problem. It is a structural one.

When visionary department heads push for modern, enabling technologies — tools that put capability directly in the hands of the people doing the work — traditional IT teams can experience it as a threat. The democratization of technology means less centralized control. Less centralized control means a different kind of IT function than the one they were hired to run.

So what happens? Good ideas get queued. Evaluations drag for months. Security reviews become indefinite. The department head who proposed the solution moves on to the next crisis, and the initiative dies quietly in a backlog nobody owns.

Meanwhile, the business has accumulated a new CRM, a new ERP, a new order entry system, a new dynamic pricing platform, and a new financial system — none of which talk to each other, all requiring their own support structure, and none designed as part of a coherent plan. Now someone suggests layering AI on top of this stack, and leadership wonders why nothing is getting better.

The Real Diagnosis: No Shared Destination

When we dig beneath the surface of functional misalignment, the problem is almost never the people. It's the absence of a shared direction that sits above all of them.

There are no top-down outcomes that every department head is accountable to. There is no vision that makes it obvious why the operations team's initiative and the finance team's initiative need to be sequenced together rather than funded independently. There is no framework that shows the IT team why enabling technologies are the path to a more strategic role — not a threat to their current one.

What exists instead is a collection of departmental business cases, each internally logical, each optimized for the team that wrote it, and none aware of the others. The leaders who are skilled at writing business cases win budget. The ones who aren't build resentment. The organization mistakes funding activity for making progress.

This is how companies spend significant capital on digital transformation and have nothing to show for it.

The Skills Gap Nobody Wants to Admit

Here is something that rarely makes it into a transformation planning session, even when it's the most important thing in the room: some companies have been stuck for so long that they no longer know what's possible.

The longer people stay inside an organization, the more internal bias they accumulate. The assumptions about what the business can do, what customers will tolerate, what technology can realistically deliver — these calcify over time. A 25-year-old company with a 25-year-old leadership team isn't just competing against modern businesses. In many ways, it's competing against its own institutional memory.

The result is transformation plans that are technically ambitious by internal standards but still leave the business years behind where the market is heading. The ideas in the room are the same ideas that have been circulating for years — repackaged, re-prioritized, and re-presented as a bold new direction. Nothing actually changes because the thinking hasn't changed.

This is where fresh eyes become not just helpful but essential. Not to replace the internal vision — the ideas and the direction must come from within the organization, from the people who understand the business, its customers, and its culture. But those people need someone in the room whose job is to push back against what everyone has quietly agreed to stop questioning.

A real strategic advisor challenges the assumptions that have calcified into facts. They ask what's possible before asking what's practical. They introduce what the market has already solved elsewhere — in adjacent industries, in companies that started from scratch without the weight of legacy infrastructure — and they hold that up against the plan on the table and ask: is this truly transformative, or are we just tidying up the same ideas we've always had?

A company more than 20 years old needs to think like a startup in one specific way: it needs to be willing to question the beliefs that made it successful in the past but may be limiting it now.

What Alignment Actually Looks Like

We've seen the moment it shifts, and it's recognizable every time.

It happens when every functional leader can see a plan that represents their team's reality — not a plan handed down to them, but one built with them. A plan that shows where their work fits in the sequence, why it fits there, and what it connects to on either side. A plan that makes the dependencies visible, so the operations leader understands why their initiative needs to come before the technology initiative, and the IT team understands why the new platform reduces their long-term support burden rather than increasing it.

When people can see their role in the whole — not just their piece — something changes. The negotiation stops. The defensiveness softens. The systems thinkers who have been quietly frustrated for years finally have a structure that matches how they already think.

That's alignment. Not agreement for its own sake, but a shared map that makes individual decisions easier because the destination is no longer in dispute.

The Consultant Trap

There is one more mistake worth naming directly, because it is expensive and common: hiring consultants to build the plan for you.

The consulting firm comes in, conducts interviews, runs workshops, and produces a document. Leadership reviews it. Some people recognize themselves in it. Others don't. It gets presented to the board, approved in principle, and then handed back to the same organization that was already struggling to agree on priorities — now with the added complexity of executing a plan they didn't build.

This almost always fails. Not because the plan is wrong on paper, but because ownership of a transformation cannot be outsourced. The ideas and the vision have to come from inside. The role of the right strategic partner is not to generate the plan — it is to challenge the thinking that produces it. To push the room beyond the comfort zone of familiar ideas, to introduce what's genuinely possible, and to pressure-test whether the plan being built is truly transformative or just a more organized version of the status quo.

The difference between talk therapy and real transformation advisory is the willingness to make the room uncomfortable in service of a better outcome.

Why We Build It This Way

The Plan phase of our methodology exists precisely because this problem is structural, not interpersonal. You cannot solve functional misalignment by running better meetings or hiring a better facilitator. You solve it by giving every leader in the room something concrete to align to — three specific, measurable future-states for the business, a roadmap that shows how each department connects to those outcomes, and a sequence that makes prioritization feel inevitable rather than arbitrary.

You also cannot solve it by staying inside the organization's existing frame of reference. Part of what the Plan phase does is introduce an outside view — not to replace internal knowledge, but to hold it up against what the market has already proven is possible and ask whether the ambition in the room is truly proportionate to the opportunity.

When the destination is defined at the organizational level before any department writes a business case, the negotiation changes. Leaders stop asking "why should my initiative come before yours" and start asking "how do we make sure both of our pieces are ready when the plan needs them."

That's the difference between a transformation that moves and one that stalls. Not better technology. Not better people. A better — and braver — starting point.

This is part of a series of six articles exploring the most common challenges facing digital transformation leaders — and how a connected, cross-functional approach changes the outcome. Read the full series here.