What is a common issue in full CX transformation programs?

• A. Multiple vendors leading to fragmented data and competing internal stakeholders.
• B. A single vendor with fully integrated data.
• C. Excessively centralized governance.
• D. No data management requirements.

Answer: (A)

The main idea being tested is how vendor ecosystems impact data and decision-making in an enterprise CX transformation. When a CX program runs with multiple vendors across platforms—CRM, marketing, analytics, contact centers, data platforms—the data often lives in separate systems with different definitions, formats, and update cycles. That creates fragmentation and makes it hard to assemble a single, trustworthy view of the customer. Stakeholders from different parts of the business may push their own metrics or roadmaps, leading to competing priorities and governance friction. All of this slows progress, increases integration risk, and undermines a cohesive customer experience.

In many large CX initiatives, the aim is a unified, seamless customer journey. A single vendor with fully integrated data, while desirable, is less common because of legacy investments, specialized tools, and organizational silos. Excessively centralized governance can also become a bottleneck, hindering agility. And saying there are no data management requirements isn't realistic in any full CX program, since data quality, integration, and governance are essential to delivering a consistent customer experience. The reality is that multi-vendor setups are a frequent source of the challenges described above, which is why they’re identified as a common issue.