How the score is calculated
Each area holds pairs of statements: one from the cx perspective and one from the it perspective, each answered on a scale from 1 (strongly disagree) to 5 (strongly agree). A pair scores the gap between its two answers. An area scores the average gap of its pairs, and the overall score is the weighted average of the areas; the weights are shown below and total 5. Lower is closer agreement. A band is assigned only when every statement is answered, and an answer outside the scale counts as unanswered.
Two kinds of pair reach your checklist. A pair whose answers are 2 or more points apart is misaligned, and adds the alignment action. A pair answered at 2 or below on both sides is a shared weakness, and adds the build action: both sides agree the capability is missing, which a gap of zero would otherwise hide. The checklist runs from the area with the largest gap. The next diagnostic is the one named below for that area.
Bands
| Average gap | Band | What it means |
|---|---|---|
| 0 to below 0.8 | Aligned | CX and IT answer these statements alike. Keep the joint planning that got you here, and check the shared weaknesses: agreement can also mean both sides see the same gap. |
| 0.8 to below 1.5 | Minor Gaps | CX and IT see the same capabilities slightly differently. Work through the differences in a regular joint planning session. |
| 1.5 to below 2.5 | Significant Gaps | CX and IT see the same capabilities in materially different ways. Differences this size tend to show up as friction, rework or delay in joint projects. |
| 2.5 and above | Critical Misalignment | CX and IT see these capabilities very differently. Agree on a shared view of where things stand today before you plan joint technology work. |
Areas, paired statements and actions
Strategy Alignment
Weight 1 of 5. If largest gap, next diagnostic: Governance Model| CX perspective | IT perspective | If 2+ points apart | If both at 2 or below |
|---|---|---|---|
| CX has a documented strategy with measurable outcomes. | IT has a technology roadmap that maps to the CX strategy. | Put the CX strategy and the IT roadmap side by side and mark each CX outcome with the roadmap item that delivers it. Resolve every outcome that has no item. | Write the CX strategy's measurable outcomes first, then build the technology roadmap items against them together. |
| CX priorities are clearly communicated to IT leadership. | IT understands which CX initiatives require technology investment. | Hold a joint review where CX states its top five priorities and IT states the technology each needs; record where the two lists differ. | Set a standing CX and IT priorities review, monthly or quarterly, with one shared list as its output. |
| CX leadership participates in technology selection decisions. | IT involves CX stakeholders in architecture and vendor decisions. | Agree in writing which technology decisions require CX sign-off and which require IT sign-off. | Add a CX seat to the architecture and vendor selection process, with a named person and decision rights. |
Data & Integration
Weight 1 of 5. If largest gap, next diagnostic: Platform Decision| CX perspective | IT perspective | If 2+ points apart | If both at 2 or below |
|---|---|---|---|
| CX teams have access to the customer data they need for decisions. | IT provides reliable, governed data pipelines to CX systems. | List the decisions CX says it cannot make for lack of data and have IT confirm, for each, whether the data exists and where it stops. | Pick the three CX decisions with the least data behind them and scope one governed pipeline for each. |
| Customer journey data is connected across channels and touchpoints. | The integration architecture lets data flow between systems. | Trace one customer journey across every channel together and mark where CX sees a break and where IT sees one. | Map the systems one high-volume journey touches and fund the integration for the first break in it. |
| CX can measure outcomes such as CSAT (customer satisfaction), FCR (first contact resolution) and customer effort with data it trusts. | IT maintains data quality standards and monitoring for CX systems. | Agree the definition, source system and owner for each CX outcome metric, then have IT confirm its data quality checks cover them. | Define each outcome metric's source and add data quality monitoring to the systems that feed it. |
Platform & Tooling
Weight 1 of 5. If largest gap, next diagnostic: Platform Decision| CX perspective | IT perspective | If 2+ points apart | If both at 2 or below |
|---|---|---|---|
| CX teams have the platforms they need to execute their strategy. | IT can support, secure, and maintain the platforms CX depends on. | List the platforms CX depends on and have IT rate how well it can support each. Plan around the ones where the answers differ. | Inventory the platform capabilities the CX strategy needs and the support model for each before the next budget cycle. |
| New CX tools can be evaluated and deployed in well under 12 months. | IT has a process for evaluating and onboarding new CX technology. | Walk one recent CX tool request through the IT onboarding process together and note where it stalled. | Agree a written intake and evaluation path for new CX tools, with a target time for each stage. |
| The tools agents use work well and make their job easier. | IT provides agent desktops that are reliable and fast enough. | Sit with agents for an hour together and record the friction points CX sees and the performance issues IT measures. | Measure agent desktop load times and clicks per contact for the top contact types, then fix the worst step. |
AI & Automation
Weight 1 of 5. If largest gap, next diagnostic: AI Readiness Diagnostic| CX perspective | IT perspective | If 2+ points apart | If both at 2 or below |
|---|---|---|---|
| CX has identified which interactions should be automated. | IT can assess whether the data and infrastructure support AI deployment. | Put CX's automation candidates in front of IT and have IT mark each for data and infrastructure readiness. | Rank the interaction types by volume and simplicity, then have IT assess data readiness for the top three. |
| CX defines the quality and governance standards for AI interactions. | IT builds the guardrails, testing and monitoring for AI. | Write the CX quality standard for AI interactions and map each requirement to the IT guardrail or test that enforces it. | Draft an AI interaction standard and a matching test and monitoring plan before the next deployment. |
| CX measures AI performance against customer experience outcomes. | IT manages AI model performance, accuracy and scale. | Agree one shared scorecard that puts CX outcome measures and IT model measures on the same page. | Define the customer outcome and the model measure for each AI use case before it goes live. |
Governance & Ownership
Weight 1 of 5. If largest gap, next diagnostic: Governance Model| CX perspective | IT perspective | If 2+ points apart | If both at 2 or below |
|---|---|---|---|
| CX has defined ownership for experience outcomes across channels. | IT has defined ownership for platform reliability and integration health. | Write down who owns each experience outcome and who owns each platform it depends on, and resolve every mismatch. | Name an owner for each channel's experience outcomes and for each supporting platform. |
| CX and IT have a shared governance model for technology decisions. | IT and CX jointly own the escalation path when a system problem affects customers. | Compare how CX and IT each describe the governance and escalation path, and agree one written version. | Set up a joint forum for technology decisions and a written escalation path for customer-impacting incidents. |
| Budget decisions for CX technology involve both CX and IT input. | IT can state what it costs to support each CX technology request. | Review the last three CX technology budget decisions together and record who had input and what the support cost was. | Add a support cost estimate from IT and a business case from CX to every CX technology budget request. |
What this assessment cannot tell you
- It is only as good as the people who answer. One person rating both columns records their guess at the other side. For a real reading, the CX lead answers the CX column and the IT lead answers the IT column, passing the scenario link between them.
- The gap measures disagreement, never capability. An Aligned band means the two sides answered alike, and both can be low. Read the shared weaknesses beside the band.
- The score is a position on this rubric. It does not rank you against other organizations or give a percentile, because no sourced distribution of scores exists to compare against.
- All five areas carry equal weight. It recommends actions and a next diagnostic. It never recommends a vendor.