Eight implementation path origins, two main ingredients
In “Why are customer data platforms frustrating to buyers, strategists, and consultants?”, I posited that there may be some eight or so implementation path origins for customer data platforms.
These paths arise because there are various states of readiness and various priorities that create the perceived need for software in the first place.
The paths result in different speeds to market. Decentralized side projects are generally the quickest to implement, and are not always a bad idea. It depends on the situation. That said, these projects are certainly nowhere near the perfect CDP implementation. No ma’am. For that, you need two main ingredients to start:
1. The ever important data strategy (read: centralization)
At a simple level, this means that organizational time has been spent understanding, architecting, and activating data. Plans for progress exist. The customer data platform is part of these plans, or is becoming part of these plans.
2. Internal implementation support team
For a customer data platform implementation to be wildly successful, designate a cross-functional team to support the implementation. Not just strategists and star technologists. Include stakeholders who will ultimately be sharing in the benefits of the CDP, who understand their own data points and data needs. The level of involvement day-to-day will vary across the team, but all will be needed for phase-by-phase planning, reviews and sanity checks.