The Meeting Where It Shows
Every leadership meeting has its version of the scene. The CFO asks why paid media spend rose 30% while cost per acquisition barely moved. The Head of Sales complains that leads arrive with no record of where they came from or what they care about. The Customer Success Director points out that the newest campaign is offering discounts to customers who paid full price last week.
Three departments. Three accurate reports. One customer, and not one person in the room, can describe her whole journey.
The fault is rarely any individual team. Each one optimises the part of the journey it owns, using the tools it chose and measured by the numbers it was given. The fault lies in a way of working that treats marketing as a series of disconnected campaigns and transactions rather than an ongoing relationship. The customer becomes a baton passed between runners who cheer only for their own lap.
Four Faces of One Person
Behind the scenes, the fragmentation runs deeper than departmental rivalry. The same person may be known by an email address in the email platform, a device token in the analytics suite, a customer ID in the CRM, and an advertising identifier in the paid media stack. Consent preferences differ between systems. Attribute names differ. Even the definition of an active customer differs.
No team is wrong within its own system. Together, they describe a customer who does not exist.
This is not a minor inconvenience. It is a daily source of expense and embarrassment. A customer who complained to support yesterday receives a we miss you win-back email today. A loyal buyer is treated like a cold prospect on the website. A high-value account is offered an entry-level bundle because the commerce system never learned what sales already sold. Each failure feels personal to the customer. Each one costs the business money in ways no single dashboard captures, because the waste happens in the gaps between systems, and every team’s own report looks healthy.
The Reflex That Fails
When leadership finally sees this pattern, the reflex is to buy something. A customer data platform. An identity resolution tool. Another integration project to connect the systems already in place.
The reasoning sounds sound. The problem is fragmented data, so the answer must be a technology that unifies it. But technology is necessary and not sufficient. I have seen enterprises buy leading platforms and move the needle barely at all, because the tools were never the constraint. Elegant architecture without the right people becomes a system nobody can operate. Strong measurement without governance produces insights nobody is allowed to act upon. The stack works technically and fails organisationally.
A single view of the customer does not mean one system for everyone. No such system exists. It means the data is unified enough that the next interaction can be based on the whole relationship rather than the last touch. When a loyal customer visits the website, she should not see a prospect offer. When a frustrated customer contacts support, the next email should not ask for a referral.
Ownership Is a Design Decision
The remedy has four parts, and none of them is software.
Shared definitions, so that active customer means the same thing in every system. Shared metrics, so that no team is rewarded for winning a lap while the race is lost. Shared incentives, so that the hand-off is an accountability and not a hope. And shared governance, so that someone answers the practical questions. Who decides which tools to buy? Who owns the data model? Who designs the journeys? Who measures return? Who fixes things when they break?
When those questions go unanswered, every decision becomes slow and political. When they are answered, the technology finally has something worth connecting to.
The unit of success must change with it. The campaign is the wrong unit, because it ends. The relationship is the right one, because it does not. A team that asks only whether this message converted will keep passing the customer along. A team that also asks whether this interaction earned the next one has started to own the customer. That shift in the question is where unification actually begins, and no vendor can make it on the organisation’s behalf.
A Simple Test
You do not need an audit to know where you stand. Take the next campaign brief on your desk and ask one question. When this customer clicks, who owns what happens next?
If a name comes to mind, you have an operating model. If a committee comes to mind, you have a baton race with better paperwork. If nothing comes to mind at all, the fragmentation is further along than anyone has admitted.
Nobody sets out to build it this way. The silos were assembled one reasonable decision at a time, each team picking the tools that served its own targets and the metrics that rewarded them. That is exactly why the pattern persists. Undoing it is not an integration project. It is an agreement about who owns the customer, made explicit before the next purchase order is signed.
Want to Know More?
If you want to know more, check out Customer Lifecycle and MarTech: A Practitioner’s Guide to Maturity, Governance, and ROI. Chapter 1 sets out the customer-first imperative in full, and the operating model chapters answer the ownership question with five disciplines that turn intent into daily practice.
Leave a Reply