Pisano Academy Articles

Decision Rights That Turn Feedback into Joint Action | Pisano Academy

Written by Emilia Sirin Komban | Nov 20, 2026, 8:25:29 AM

A bank's CX team identifies that customers who change their address online are calling the contact center days later because their cards are still sent to the old address. The insight is clear and well evidenced. The fix sits across digital, card operations and a third-party fulfilment process. Three months later, the theme is still in the monthly report, and each team can explain why the fix belongs to someone else.

This scenario is illustrative and does not describe a specific organization.

Ownership is the third stall point in the VoC execution gap. Our earlier telecom analysis looked at this problem in one industry. This article sets out a cross-industry model for deciding who owns what.

The Short Answer

Customer issues stall when the team that detects a problem is not the team that controls its cause, and no one has explicit authority to decide. CX accountability works when every material issue has four clearly assigned roles (detect, decide, fix and verify), a defined threshold for moving from individual follow-up to systemic change, and service levels for how quickly each step happens. Central CX teams should own the system that assigns and tracks these roles. They should not try to own every fix.

The Hand-Off Problem

Most enterprise CX teams sit in marketing, customer service, operations or a dedicated customer office. Wherever they sit, the majority of root causes lie outside their control: in pricing, billing, logistics, product design, IT systems or policy.

Research shows how often the hand-off fails. Forrester's 2025 survey of feedback and CX measurement practitioners found that "most CX teams still don't get stakeholders to act on insights", and that "because journey accountability is a gap, journey measurement falls flat" (Forrester, August 2025). Discussing XM Institute's 2025 research, Isabelle Zdatny put the consequence plainly: "If CX teams don't have authority to act on insights or equip employees across the organization with the motivation, authority, and skills to take action, there's no mechanism for them to create value" (Freshworks interview, August 2025).

Four Roles Every Issue Needs

Borrowing from decision-rights practice in other disciplines, every material customer issue should have four named roles. One person or team can hold more than one, but none should be left blank.

1. Detect

Identify and evidence the issue: volume, trend, affected segments, and verbatims.

Owner: CX / VoC team, frontline teams

2. Decide

Accept the issue, choose the response and commit resources, or explicitly decline it.

Owner: Leader of the function controlling the cause

3. Fix

Implement the change in process, policy, product or system.

Owner: Operating team (ops, product, IT, digital, partner)

4. Verify

Confirm the fix worked using agreed experience and operational measures.

Owner: CX / VoC team, with the fixing team

The decide role is the one most often missing. Detection is usually well staffed, and fixing teams exist. What is missing is an accountable person who must say yes, no or not yet, by a date.

A practitioner in a Gartner Peer Community discussion made a related point: "people appreciate knowing whether their input will be acted on, even if the answer is no" (Gartner Peer Community, 2025). That comment reflects one practitioner's experience, not Gartner research, but the principle is sound. An explicit "no" is better for the program than an indefinite silence.

Inner Loop to Outer Loop: When a Case Becomes a Systemic Issue

Rob Markey, Fred Reichheld and Jamie Dullweber distinguished between the inner loop, frontline follow-up with individual customers, and the outer loop, systemic changes driven by aggregated feedback (HBR, December 2009). Most organizations are good at the inner loop. The weak point is the transition between the two.

A practical rule is to define escalation thresholds that move an issue from the inner to the outer loop automatically. Examples include:

  • The same root cause appears in more than a set number of cases within a period.
  • A theme affects a high-value segment or a regulated process, regardless of volume.
  • Cases on the same issue are reopened or generate repeat contacts.
  • Frontline teams flag that they can resolve the symptom but not the cause.

Once a threshold is met, the issue receives a decision owner and a deadline, rather than staying in the case queue.

Journey Ownership Versus Functional Ownership

Customers experience journeys, but organizations are built around functions. Alex Rawson, Ewan Duncan and Conor Jones showed that strong touchpoint performance can mask poor end-to-end journeys (HBR, September 2013). An issue such as the address-change example above belongs to a journey, not to any single function.

There are two workable models:

Journey Owners with Convening Authority

A named leader owns each priority journey's outcomes and can convene the functions involved. They rarely own the budgets, so they need strong executive backing.

Functional Owners with Journey Metrics

Each function owns its part, but shares journey-level measures so that hand-off failures across departments are visible to everyone.

Most enterprises use a combination. The model matters less than making it explicit.

McKinsey describes one travel company where CX acted as business owner, a data-science team built the capability, the service organization was the first recipient, and an advisory board including the COO, CFO and CMO followed progress (McKinsey, February 2021). The structure worked because each role was clear before the work started.

Service Levels for Insight

Customer service teams have response-time targets. Insight rarely does. Three service levels make ownership measurable:

SLA 1

Time to Owner

From detection of a systemic issue to formal acceptance by a named decision owner.

SLA 2

Time to Decision

From acceptance to a documented decision to fix, defer, or explicitly decline.

SLA 3

Time to Verified Fix

From decision to confirmation that agreed operational and experience measures have moved.

Reporting these alongside headline scores shifts executive attention from "how are we scoring?" to "how quickly do we act?"

Closing the Loop Internally

Forrester found that while one-on-one follow-ups with customers are common, "broader communication about organizational actions in response to feedback is rare." The same applies inside the company. Frontline employees who raised an issue, and teams who supplied evidence, rarely hear what was decided. Publishing a simple log of decisions taken, and declined, builds trust in the process and improves the quality of future escalations.

XM Institute's governance framework adds a useful caution: the working groups that drive cross-functional change need members with "the authority to make decisions and commitments on behalf of the departments they represent" (XM Institute, October 2021). Representation without authority produces discussion, not decisions.

How Teams Route and Track Ownership

Tooling can make ownership visible and auditable. In Pisano's Ticket Manager, critical feedback becomes a structured ticket that can be assigned automatically to teams through configurable pools and queues, governed by roles, permissions and status transitions, and tracked against SLAs. A change log records assignments and ownership changes, and root causes identified across related cases help teams decide which issues need systemic action. Planner keeps improvement tasks linked to the feedback and reports behind them. For inner-loop mechanics, see our guide to ticket management.

Conclusion: Assign the Decision, Not Just the Task

Most CX operating models describe who collects feedback and who resolves cases. Fewer describe who must decide when a recurring problem crosses functional lines. That decision role, backed by thresholds, deadlines and executive support, is the difference between a program that reports issues and one that removes them.

The next article looks at a specific hand-off that often fails: getting customer feedback into product decisions.

Frequently Asked Questions

Who should own customer experience in an organization?

The CX team should own the program, its standards and its tracking. Each improvement should be owned by the function that controls the cause, with a named decision owner and executive governance to resolve conflicts.

What is the difference between the inner loop and the outer loop?

The inner loop is follow-up with individual customers. The outer loop is the systemic change to processes, policies or products that prevents the issue recurring.

How do you create accountability for CX across departments?

Assign detect, decide, fix and verify roles for each material issue, set escalation thresholds and decision deadlines, report service levels for insight, and give cross-functional groups members with decision authority.

 

Ready to Design Clear Ownership and Escalation?

Stop letting systemic issues stall between departments. See how Pisano automates ticket routing, enforces SLAs, and turns cross-functional accountability into measurable fixes.