Designing with the end in mind: why functional delivery matters more than project delivery.
When enterprises evaluate the success of a major technology deployment, executive scorecards typically rely on three conventional governance criteria: was the system delivered on time, within budget, and according to scope?
By Greg Jarvis, Global Customer Success Director at Connect
While these parameters are essential for IT risk management, when an enterprise evaluates success purely through these technical benchmarks, a disconnect frequently emerges between the delivered technology platform and the operational realities of the frontline workforce.
When projects fail to deliver.
It is not uncommon for contact centre operators to invest in new software deployments without realising a significant operational transformation or meaningful return on investment (ROI).
While a migration can meet every defined architectural and integration metric, it can also burden frontline agents with fragmented workflows, clunky interfaces, and heightened cognitive load. A compromised user experience (UX) ultimately degrades key performance indicators across the board.
In this scenario, project delivery success is usually defined by building exactly what was specified. In contrast, functional delivery asks a far more critical question: did we improve how people work?
Aiming for operational utility.
This mismatch between technical deployment and operational value is rarely the result of incompetent project management or deficient technology. It is more commonly a structural issue.
As enterprise transformation budgets sit primarily within the IT domain, technology leaders naturally retain ownership of system architecture, security protocols, vendor selection, and platform governance. These are legitimate and necessary responsibilities.
Yet, because IT serves as the primary procurement authority, initial conversations naturally focus on technical outcomes, such as, infrastructure constraints rather than operational outcomes, such as workflows.
Conversations regularly begin with a technical mandate, such as replacing a legacy on-premise PBX platform, rather than an operational strategy to elevate customer experience delivery (CX) or reduce Cost to Serve.
When the supervisors, workforce managers, and frontline agents who work in the contact centre daily are consulted too late in the design process, technology solutions are engineered to mimic legacy systems rather than eliminate operational friction.
The outcome is often a like-for-like replacement that satisfies technical compliance requirements without fundamentally changing the UX or operational performance.
The trap of a minimum viable product.
To manage implementation risk and keep ballooning software expenditures in check, organisations routinely default to a minimum viable product (MVP) strategy. This model is designed to move existing operations onto modern cloud architecture with as little disruption as possible.
While the technical migration often succeeds, because the deployment was restricted to matching legacy guardrails, the contact centre often fails to unlock any meaningful operational uptick in agent productivity, First Contact Resolution (FCR), or self-service containment rates from the investment.
This illustrates a common industry misconception: leadership teams expect transformational commercial outcomes from what is, in practice, merely an infrastructure relocation exercise. Where a technical migration transfers capability, functional delivery unlocks business value.
Defining operational requirements before technical specs.
Before a contact centre solution or vendor is selected, true functional delivery requires a different engagement model that begins with an operational discovery phase.
Instead of entering an enterprise environment with a pre-packaged technology stack, a vendor-agnostic, service-led transformation partner will first develop a granular understanding of how the customer operation functions.
This engagement must include the frontline users who determine operational success, such as agents, team leaders, quality management (QM) assessors, and workforce management analysts.
This process requires moving beyond standard technical requirements to gather insights that deliver a deeper operational assessment. This analysis should focus on operational aspects, such as task execution, process efficiency, quality metrics, and employee friction.
Important questions to ask include:
- How many disjointed applications must an agent navigate to resolve a single customer enquiry?
- Where do manual processes, duplicate data entry, and swivel-chair handoffs degrade Average Handling Time (AHT)?
- How is traditional quality assurance (QA) currently executed, and does it provide actionable coaching data?
- Which operational bottlenecks create agent frustration and drive voluntary turnover?
Only once these operational realities are fully mapped can solution providers engineer technology architecture with greater precision.
Make your technology work for people with Connect.
Extract measurable operational value from your transformation.
Co-designing with end-users.
Conducting a deep operational discovery phase upfront can alter the trajectory of a transformation programme.
By identifying operational edge cases and workflow gaps before finalising technical scopes, organisations can mitigate implementation risk and insulate budgets against expensive downstream change requests.
When this process precedes implementation, technical decisions are no longer made in a vacuum, and system architecture is directly informed by real-world usage patterns.
Furthermore, when frontline employees actively participate in shaping their daily working tools, user adoption rates tend to surge after deployment.
When this happens, contact centre transformation shifts from a potentially disruptive, single-event project to an incremental, value-driven process that delivers compounding operational returns and better business outcomes over time.
Mitigating implementation risk.
The commercial necessity of functional delivery is demonstrated by our work with a leading discount retailer across seven contact centre departments.
While initial project planning had already been completed under a standard IT framework, prior to implementation, Connect requested direct access to evaluate frontline operations.
Through structured user interviews and workflow analysis across every department, our Data-Driven Insights (DDI) team uncovered major operational risks that had gone undetected during initial technical scoping:
- Manual processes and system fragmentation were severely inflating AHT across every department
- Real-time visibility into supervisor dashboards and queue management was missing
- Traditional QA processes were sampling less than 3% of total voice interactions, leaving vast blind spots in compliance and agent performance.
Critically, the assessment also uncovered a severe platform limitation. The business required approximately 50 outbound Calling Line Identifications (CLIs) for distinct regional operations, yet the target platform supported only 10 natively.
Had this operational dependency remained hidden until the implementation phase, it would have resulted in severe project delays, scope creep, and unexpected custom development costs.
Because the issue was identified early on during the operational discovery phase, a custom orchestration layer was engineered before scope finalisation, protecting the budget, mitigating risk, and ensuring a smoother delivery roadmap.
Adoption is the ultimate success metric.
Beyond the cost savings and production go-live timeframes, the ultimate test of any technology platform is whether human users embrace it.
When frontline employees perceive a new system as an administrative burden that complicates their daily routine, adoption stalls, platform functionality remains underutilised, and the expected ROI fails to materialise.
Frontline teams rarely resist technology that makes their lives easier – they tend to resist tools designed without an understanding of their operational reality.
Functional delivery ensures that Agent Experience (AX) is treated as a primary success metric, designing Agent Assist interfaces, automated summaries for after-call work (ACW), and smart handoffs that directly alleviate operational strain.
Delivering rapid operational wins.
With these outcomes in mind, where traditional project delivery terminates at go-live regardless of whether operational benefits are realised, functional delivery treats go-live as the starting point.
By establishing an operational baseline during initial discovery, organisations construct a logical, phased transformation roadmap linked directly to commercial value.
Immediate pain points are resolved in phase 1, creating rapid operational wins that build organisational momentum.
Subsequent expansion or optimisation phases that incorporate advanced automation, workflow refinements, and intelligent routing are no longer viewed as speculative technology expenditures, but as justifiable investments backed by measurable operational outcomes.
Within this functional delivery paradigm, DDI functions as targeted accelerators of business value.
However, relying solely on artificial intelligence (AI) without deep operational context can result in inflated context costs and missed expectations, as an AI model is only as effective as the underlying operational logic that guides it.
The ideal approach leverages frontline business analysts upfront, who first identify the operational questions, key metrics, and interaction trends required by the business.
Once that process is complete, configured AI systems can then process unstructured voice and text data to deliver actionable intelligence. In this DDI-led model, the fundamental principle remains constant: technology must serve the operation, not the other way around.
By designing solutions around people, processes, and measurable business outcomes, organisations move beyond traditional tick-box project delivery to a functional approach that delivers long-term operational excellence.
Frequently asked questions.
What is the difference between project delivery and functional delivery?
Project delivery focuses on whether a technology solution is implemented on time, within budget, and according to scope. Functional delivery goes further by asking whether the solution improves how people work, removes operational friction, supports better adoption, and delivers measurable business value.
Why should operational discovery happen before technical implementation?
Operational discovery helps organisations understand frontline workflows, user pain points, process gaps, and performance bottlenecks before a solution is designed. This ensures the technology is shaped around real operational needs, reduces implementation risk, avoids costly change requests, and increases the likelihood of user adoption.
About'Connect.
Connect is a global AI-enabled CX specialist and digital transformation partner. Founded in 1990, we help organisations modernise customer journeys and optimise service operations across every touchpoint, applying AI where it delivers measurable operational value.
Our differentiation lies in the experience we’ve gained from operating CX in the real world. We deliver end to end; from the network that carries customer contact, through interactions in the contact centre, to the integrated back-end systems that support them. This end-to-end accountability creates a unified view of the customer and operations, enabling consistent, reliable outcomes at scale.
Connect with us Connect United Kingdom, Connect South Africa, Connect India, Connect USA.
Find out how we can help your business communicate better.
To discuss your communications challenges and requirements, get in touch with us today.
Connect with us now.
New web: Contact Us
"*" indicates required fields