Where ownership breaks down
Customer data crosses marketing, IT, analytics and legal. Without explicit ownership, each group optimises its own tool, definitions drift, and the CDP becomes a shared dependency nobody feels responsible for.
- Marketing owns outcomes and use-case priority.
- Data or architecture owns schemas, identity and quality.
- Engineering owns integration reliability and security.
- Privacy and legal own policy; the platform enforces it.
A lightweight operating model
- Outcome list — five to ten use cases ranked by value and effort.
- Data domain owners — one named person per domain such as identity, consent and events.
- Fortnightly forum — decisions, risks and dependencies, with notes kept short.
- Shared definitions — a glossary for audience, active customer and conversion.
Signals the model is working
- Use cases move from idea to launch with fewer hand-offs.
- Teams quote the same numbers for the same metric.
- Platform changes go through a visible review.
- New joiners can find who decides what.
Frequently asked questions
Who should sponsor a MarTech programme?
Usually a business leader accountable for outcomes, with a technical co-sponsor. Single-function sponsorship often stalls at the first cross-team dependency.
How big should the steering group be?
Small enough to decide: typically one marketing, one data, one engineering and one privacy representative.
Last updated: