Mind the gap: Making service journey improvement stick

Remember that childhood game of jumping over cracks in the sidewalk? Step on a crack, break your mother’s back. It sounds silly now, but there’s something in it. You learn early on to avoid the gaps. Because once something falls in, it’s gone.

That’s not so different from how most service organizations operate today. A spike in complaints. A drop in CSAT. A leadership directive. Call in the team to build a journey map, fast. They identify solutions, present the findings, and then…

Nothing.

The project ends, but the underlying system stays the same.

It all falls through the cracks. Or rather, into the structural gap at the root of the pattern: insights don’t have anywhere to go.

That’s because most organizations still lack the clear ownership and cross-functional discipline needed to continuously manage and improve journeys.

The 2026 Strategic Roadmap for Customer Service Journey Management — a research report by Gartner® analysts Christopher Sladdin and Daniel O’Sullivan, published March 23, 2026 — takes a hard look at why that pattern persists and what it takes to break it. The answer is not another one-off fix. It’s structure, ownership, and a real journey management discipline.

Here are our key takeaways from the Gartner report.

The structural gap where insights get lost

Improving the customer experience is the number one priority for service and support leaders heading into 2026. And yet most of those efforts will stall. Not because organizations lack insight, but because insight doesn’t have anywhere to go. In other words, they get lost in the cracks.

Most organizations lack clear ownership and the cross-functional discipline needed to continuously manage and improve journeys. There is no dedicated function accountable for the end-to-end experience between projects, and no one owns the problem when the sprint ends.

Because the underlying way of working never changes, the cost compounds: in customer effort, in avoidable contacts, and in the energy of teams who have mapped the same pain point three times and watched it come back a fourth.

What the structural gaps actually look like

Customers experience service as a continuous event, not a channel. They don’t care whether their problem started in a mobile app, escalated through an IVR, and ended with a call center agent. They experience it as a single thing and judge it holistically.

Service organizations, meanwhile, are built around channels. Contact center teams optimize for call handling time. Digital teams optimize for containment. Each function manages its slice of the experience in isolation, against its own metrics. The customer’s end-to-end journey falls into the gap between them.

As per our understanding, Gartner identifies four interlocking failure modes that sustain that gap:

• Journey improvement is treated as a project, not a discipline. Efforts are reactive and deliver one-time results. Nobody owns the journey between sprints.

• Nobody owns end-to-end improvement. When a journey spans three teams, it effectively belongs to none of them.

• Cross-functional stakeholders are absent. The functions that shape service journeys upstream, such as product, marketing, IT, and finance, rarely participate in improvement efforts at all.

• Data is siloed and assumption-based. When channel and operational systems do not talk, teams fill the gaps with opinion rather than evidence.

The report maps these issues against a current state and a future state.

The current state is reactive journey analysis, mapping conducted at a single point in time, and improvement driven by assumption rather than integrated data. Journey work happens when the pain is acute enough and stops when the immediate problem is patched. Progress does not compound. Each effort largely starts from scratch.

The future state is proactive, data-driven journey management: a dedicated journey management office with the authority to drive iterative, long-term improvements across channels and functions. Continuous improvement cycles, not campaigns.

The obstacle between these two states is not technology. Most organizations already have adequate tools to get started. What is missing is structural: the right people in dedicated roles, the right processes running continuously, and the cross-functional authority to act on what the data shows.

What the future state actually requires

At the center of that future state is a dedicated journey management office: a structural function staffed by full-time journey managers, each responsible for one or two high-priority journeys. Instead of a committee, working group, or project team that dissolves when the engagement ends, this office ensures improvement compounds and accountability is named. It coordinates data analysts and cross-functional stakeholders through a continuous cadence of workshops, sprints, and quarterly reviews.

The report includes a detailed job description for the journey manager role and recommends that those leaders initially report directly to the head of service, giving them the authority to drive change from day one.

Three operational commitments define the future state.

1. Cross-functional authority comes first. Journey teams must include stakeholders from IT, marketing, finance, and product, not just service. Without that mix, teams can identify problems upstream of the service interaction but lack the mandate to act on them. Diagnosis without authority is just documentation.

2. The second is a continuous improvement cadence. At the leadership level, this means quarterly reviews. At the journey team level, it means weekly check-ins. This is not a program with a launch date and a sunset clause. It is an ongoing operational rhythm, the kind that starts to feel less like a change initiative and more like how the organization works.

3. The third is data-driven prioritization. Leadership selects journeys for improvement using metrics, not by responding to whichever problem is making the most noise. That shift from reactive to proactive is what turns journey management from a CX project into something that holds up in a budget conversation.

What this signals for 2026 and beyond

The Gartner research’s strategic planning assumption is worth stating plainly: by 2028, 30% of customer service and support organizations will embed a customer journey management discipline, complete with a fully staffed journey management office, within the function.

Thirty percent is not a majority. But that leading cohort will spend the next two years building structural capability while others continue running one-off projects. The gap between them will compound.

Journey management is not a feature that can be bolted on later. It requires the kind of organizational infrastructure that takes time to build: trust between functions, shared data, and a reporting cadence that survives leadership change.

For service leaders, this creates a strategic question: are you in the first 30%, or are you waiting to see if it matters?

The research suggests four questions worth asking your organization now:

1. Who is accountable for the end-to-end service journey, not a channel or project, but the journey itself, continuously?

2. When did you last make a service journey improvement driven by structured, cross-functional analysis rather than a complaint spike or a CX dip?

3. Can you connect journey investments directly to business outcomes in a way that holds up in a CFO conversation?

4. If your journey manager left tomorrow, would the discipline survive, or would it leave with them?

If any of those answers are uncomfortable, the Gartner roadmap gives you a concrete starting point. The short-term actions are deliberately accessible: prioritize two journeys, recruit one or two journey managers, establish a reporting cadence, and begin the first improvement cycle. Advanced data maturity and sophisticated orchestration technology are not prerequisites. Organizations can start now, with what they have.

What to do next

The full Gartner report covers the complete migration plan from current state to future state: journey team structure, quarterly review cadence, a technology investment matrix, and job description templates for both the journey manager and head of journeys roles. It is a practical operating document, not an executive summary.

TheyDo is offering complimentary access to the report for customer service and CX leaders who want to read the research in full. Register to access the complete Gartner analysis via the licensed reprint link below.

If you are accountable for service journey quality and for the operational costs that follow from it, this is the research worth your time.

Source attribution

2026 Strategic Roadmap for Customer Service Journey Management, Christopher Sladdin, Daniel O’Sullivan, 23 March 2026, Gartner, Inc.

Disclaimer

Gartner is a trademark of Gartner, Inc. and/or its affiliates

Gartner does not endorse any vendor, product, or service depicted in its research publications and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research and advisory organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.