The disconnection that costs growing businesses more than they realise

If you run a growing business, you probably spend more time than you'd like thinking about things that should be working but aren't.

Not in the dramatic sense. The business isn't failing. You're not in crisis. But there's a persistent, low-level experience of friction that keeps surfacing in different parts of the business, and the friction never quite gets resolved, because every time you look at a specific instance of it, the instance seems small.

This article is about why that friction exists, why it's usually invisible when you look at any single part of the business in isolation, and why it's almost always more costly than leaders realise.

The short version: the friction is a symptom of disconnection. The three most consequential parts of your business, how you grow through your customers, how your people spend their days, and how your technology supports both, are almost certainly not working as a connected system. They're working as three parallel projects that share a building.

Let us work through a typical pattern.

The commercial team is running a growth campaign. They've identified a new segment they want to move into. The campaign is well-designed, the messaging is sharp, and the pipeline builds. But when customers start converting, the onboarding process breaks in small, specific ways. The operations team wasn't fully briefed on what the commercial team had promised, because the briefing happened in a meeting where no one from operations was present. The CRM and the operational systems don't quite agree on what a customer looks like, so the handoff between sales and delivery creates data gaps that someone has to fix manually. The new customers notice, say nothing, and quietly become slightly worse customers than they would have been otherwise. Some of them churn earlier than expected. The commercial team runs the next campaign with slightly less confidence that growth will translate cleanly into revenue. Nobody connects the dots.

Or another pattern.

The technology team, under pressure from the board about AI, runs a pilot programme. They pick a use case, build a proof of concept, and demonstrate it to leadership. It works. Everyone is pleased. Six months later, when the system is supposed to be in production, adoption is low. The commercial team isn't using it because the workflow doesn't fit how they actually work. The operations team isn't using it because the data quality issues that the pilot glossed over are real blockers at scale. The AI investment, which was meant to be transformative, becomes a sunk cost that nobody quite wants to write off, and the next AI conversation at the board happens with everyone slightly more tired than they were before.

Or a third pattern.

Senior leaders are concerned that the business isn't scaling well. Cost per customer is rising. The team is stretched. So they commission a process redesign. The operations team spends weeks documenting current state and designing future state. The future state is good. But when it's implemented, it doesn't produce the efficiency gains expected, because the underlying commercial assumptions are wrong. The business was serving three customer types with one process. The new process assumes all three are similar. They aren't. Efficiency improves for one segment, degrades for another, and stays flat for the third. Net effect: minimal. Everyone assumes the redesign was flawed, rather than recognising that the commercial inputs to the redesign were incomplete.

These are not unusual failures. These are the normal, expected failures of growing businesses where the commercial, operational, and technology sides are working on related problems in different rooms.

The cost of this disconnection is usually invisible, because no single instance of it is big enough to stand out. The commercial team doesn't see the churn attributable to the onboarding breakdown, they see a slight underperformance of the campaign. The technology team doesn't see the real cost of the failed AI adoption, they see a project that 'didn't quite land.' The operations team doesn't see the commercial misdiagnosis, they see a redesign that 'needed more iteration.' Each team is looking at the friction from inside their own work, and from inside, the problem always looks smaller than it is.

But the sum of these invisible costs, across a year or two, is substantial. Growth costs more than it should. Technology investment produces less than expected. Operating costs creep up. The business appears to be succeeding, but the economics underneath the success are getting worse quarter by quarter, and nobody can quite point to where.

The temptation, when this pattern is named, is to go looking for a better project management tool, a better executive cadence, or a set of values posters about 'collaboration' and 'alignment.' These don't fix the underlying problem, because the underlying problem isn't that people aren't talking to each other. They are. The problem is that the three parts of the business are being optimised against their own local metrics, and the connections between them are treated as coordination overhead rather than as where the actual value sits.

The fix isn't more coordination. The fix is to design the work itself so the connections matter. Commercial decisions made with operational and technology realities considered. Technology investments chosen because they solve specific commercial or operational problems, not because they look modern. Operations redesigned around how customers actually arrive and what the business is actually trying to sell to them.

This is harder than it sounds, because it requires someone in the room who can see across all three at once. In most businesses, nobody is in that role. The CEO is closest, but the CEO is also pulled into every specific crisis and rarely has the space to see the pattern. The CFO sees the financial outcomes but is usually one step removed from the operating decisions that produced them. Function heads see their own function.

The practical question is: who, in your business, is looking at how the commercial, operational, and technology sides connect to each other, week by week? If the honest answer is nobody, or only partly, then the friction you've been noticing isn't a series of small unrelated problems. It's a single systemic problem showing up in many different places.

Naming it that way is the first move. Fixing it is the work.