After more than twenty years working on contact centre and CCaaS transformation programmes, across organisations of different sizes and in different sectors, the failure modes are familiar. Integration complexity that was underestimated. Governance structures that reported status without driving decisions. Commercial models that looked different in practice from what was proposed. Programme plans that did not survive contact with the complexity of the actual environment. All of these are real failure modes, and all of them are worth addressing. But if I had to name the single most consistent factor in the contact centre transformation programmes that underdelivered, the one that I have seen recur most frequently and with the most significant consequences, it is this: the technology was selected before the strategy was clear.
The pressure to begin with platform evaluation is understandable. Technology suppliers are active in the market and skilled at creating momentum. The CCaaS market is visible and well-covered, and organisations that have been on legacy platforms for years are aware that modernisation is overdue. Board-level mandates to “move to the cloud” or “digitise the contact centre” create a sense of urgency that translates into early engagement with suppliers, market briefings, and in some cases formal procurement processes, before the strategic questions that should shape those activities have been properly answered. There is also a genuine belief, in many organisations, that the technology evaluation process itself will surface the strategic answers. That engaging with suppliers, seeing demonstrations, and reviewing proposals will clarify what the organisation needs and what is possible. In my experience, this belief is incorrect. What the technology evaluation process surfaces is a set of platform capabilities. What it does not do is tell you which of those capabilities are relevant to your specific strategic goals, or whether the goals themselves are the right ones.
The questions that matter most in contact centre transformation are not technology questions. They are strategic ones, and they need to be answered, or at least seriously considered, before an RFP is issued or a supplier is invited to demonstrate. What outcomes is the contact centre trying to achieve, and how will success be measured? This is not a question about technology features. It is a question about what the contact centre is for and what it needs to do differently. The answer shapes everything that follows: the requirements that go into the RFP, the evaluation criteria that are used to assess proposals, the business case that justifies the investment, and the metrics that will be used to judge whether the programme has delivered. What does the contact centre need to look like in three to five years, and what does that imply for technology decisions today? A contact centre that needs to significantly expand its digital channel capability has different platform requirements from one that needs to improve operational efficiency in a voice-led model. A contact centre that is considering AI-driven self-service has different integration and analytics requirements from one that is focused on quality management and coaching. These are not generic CCaaS questions: they are specific to the strategic direction of the organisation. What does the current environment actually look like, and what constraints will shape what is possible? Legacy system dependencies, integration complexity, data architecture, and organisational readiness all influence what is achievable and over what timeframe. A strategy that does not reflect these constraints produces a programme plan that does not survive contact with reality.
When technology is selected before the strategy is clear, the consequences follow a consistent pattern. The evaluation produces a platform that the organisation has assessed against capability criteria that do not map cleanly to what actually needs to be achieved. The implementation begins with requirements that are still being defined, which creates change control disputes, scope uncertainty, and programme delays. The business case is built around the features of the chosen platform rather than the outcomes the organisation needs to achieve, which makes benefit realisation difficult to demonstrate when the programme concludes. More fundamentally, the organisation enters a long-term technology relationship without a shared understanding of what it is trying to achieve. The supplier is implementing a platform. The organisation is trying to transform a contact centre operation. Without a clear strategic framework connecting those two activities, the gap between them becomes visible during delivery and is costly to close.
The organisations I have worked with that get contact centre transformation right share a common characteristic: they invest time in strategic clarity before they engage with the market. They are clear about what they are trying to achieve, honest about the constraints of their current environment, and deliberate about the technology decisions that follow from their strategic direction. That clarity translates into better procurement processes, more realistic programme plans, and a stronger basis for the supplier relationship throughout delivery. The platform matters. The right CCaaS platform, well implemented in the right environment, is genuinely transformative. But the clarity of thinking that precedes the platform decision matters more, and it is the investment that organisations are most likely to underestimate or defer.
