To ensure clarity survives handoffs from marketing to service reps, CareFirst invested in overhauling internal service center technology. By reducing the number of screens an employee needed to navigate to answer one question, they improved both the employee and customer experience simultaneously.

To prevent a culture of blame, Sierra holds public "lessons learned" sessions for any failure, from lost deals to bugs. This frames failure as a collective responsibility of the team, not an individual's fault. The focus is on fixing the underlying system, fostering paranoia about processes, not people.

CareFirst views internal health as a direct predictor of external customer satisfaction. Challenges identified in employee engagement surveys, such as friction with internal IT systems, are treated as CX risks. The philosophy is that if employees are struggling with their tools, that friction will inevitably be passed on to the customers they serve.

Focus on the root cause (the "first-order issue") rather than symptoms or a long to-do list. Solving this core problem, like fixing website technology instead of cutting content, often resolves multiple downstream issues simultaneously.

Traditional business culture rewards immediate action. For continuous improvement to succeed, you must instead reward the counterintuitive behavior of slowing down to thoroughly define a problem first. This prevents teams from wasting time solving the wrong issues.

The value 'seek pain' encourages employees to proactively find what's broken and have difficult conversations. This counterintuitively minimizes pain by preventing it from accumulating over time, such as delaying a necessary pivot or firing.

Customer issues are rarely isolated events. They often originate from internal process or technology failures. When an employee lacks access to the right data or faces a flawed internal system, the negative impact is directly transferred to the customer. Fixing CX requires looking inward at employee tools and journeys first.

Dedicate a recurring 'Customer Day' not only for user interviews but for the team to step back from tactical work. Use this time to synthesize existing data, analyze market trends, and refocus on the core 'why' behind the product, preventing the team from getting lost in the weeds of feature development.

Don't view customer escalations as a nuisance; they are a valuable gift. Each one provides a critical opportunity to find and fix not just a specific bug, but the underlying process failure that allowed it to happen. Leaders should actively encourage customers to escalate issues directly to them.