Back
EP 002
34 Min
Zack Hamilton has advised more than 200 retail brands and watched companies post NPS scores in the 70s and 80s while their same-store revenue fell and first-time customers lapsed at 70%. His verdict: the score is not evil, it is dangerously incomplete.
Zack Hamilton looked at the customer experience industry and decided it was measuring the wrong things, reporting to the wrong people, and wondering why no one cared. As the creator of the Experience Performance System and host of the show Unf***ing Your CX, he argues that CX has to become a performance function, not a reporting one. On this episode of the Fini Podcast, he made the case against NPS, walked through the business case that actually wins budget, and explained why most AI support deployments stop at containment.
Meet Zack Hamilton
Zack spent over two decades advising more than 200 retail brands, including Macy's, Sephora, Home Depot, and Coach, and served as Chief Experience Officer at Aaron's. He created the Experience Performance System, a framework Fortune 500 companies use to turn customer insight into business performance, and he hosts one of the more provocative voices in the field for CX leaders tired of being treated like a call center.
Why CX programs really get defunded
Zack's first hard truth: CX programs do not get defunded because they fail, they get defunded because they become irrelevant. Practitioners get obsessed with slicing data and building dashboards, and slowly disconnect from execution. Executives do not want more dashboards. They want faster, better decisions, less risk, more growth, and less churn. If CX is not changing operational behavior, funding becomes optional, and optional programs get cut.
NPS is dangerously incomplete
Zack does not hate NPS, he calls it dangerously incomplete. It measures advocacy and sentiment after the fact, not behavior. Brands report the score and close the inner loop, but skip the hard outer loop where transformation happens, so the metric gets gamified. The danger is false confidence: he has seen companies with NPS in the 80s whose P&L is bleeding, with first-time digital customers lapsing at 70 to 80%. Meanwhile friction compounds and silent churn accelerates while the score says everything is fine. What he watches instead is decision velocity, time to identify friction, customer lifetime value, and signal health.
The one-page business case
The tool Zack teaches is a one-page business case, not a dashboard. He learned it the hard way at Aaron's, when he showed up to a prioritization session with NPS trends and customer stories and was told, good data, keep monitoring it. His cross-functional partners, by contrast, brought specific business cases that drove decisions. So he rebuilt his around a real friction: customers abandoning carts because of delivery-date uncertainty. He translated it into a problem statement with a time period, the number of customers affected, and the financial impact, then added the cost of inaction, a recommended approach, and the exact resources required. Co-created with the partner who owned the metric, it changed the conversation from sentiment to business impact. As he puts it, executives do not fund feelings, they fund returns.
AI as containment vs AI as a business system
Zack's sharpest AI point is that most teams treat it as a containment tool instead of a business system. Agents close 80 to 90% of tickets, satisfaction looks fine, and you cut human cost, so on the surface it looks great. But you have only moved the cost to serve from human to agent. That is automation of mediocrity, not transformation, because you keep resolving the same tickets instead of fixing the upstream friction that generates them. His model: AI should detect the friction, quantify the impact, recommend and complete the action, then trigger a workflow to fix the root cause. The agent is a direct reflection of the human-led system behind it.
What support leaders should take from this
Be a performance function, not a reporting one. If your work does not change decisions, priorities, or resource allocation, it is a marketing program for feelings.
Translate friction into a business problem. Name the time period, the customers affected, the financial cost, and the cost of inaction.
Do not trust a high NPS. A great score can sit on top of a bleeding P&L. Watch behavior, friction, and decision velocity.
Bring a one-page business case. Co-create it with the cross-functional partner who owns the metric, and specify the exact resources.
Use AI to fix friction, not just contain it. Closing the same tickets forever is mediocrity at scale. Feed resolutions back into fixing the upstream cause.
Earn buy-in with receipts. Nobody hands you a seat at the table. You earn it through friction identified, cases built, and results delivered.
Listen to the full episode
Zack goes deeper on decision velocity, agentic CX, and why the power hierarchy inside companies is the real barrier, in the full episode of the Fini Podcast. You can find him on LinkedIn and on his show, Unf***ing Your CX.
AI that detects friction and fixes it upstream, not just contains tickets, is what Fini is built for. Book a demo to see it on your own data.
Leo: Welcome back to the Fini Podcast. I'm your host Leo. My guest today isn't just another CX consultant. He looked at the entire customer experience industry and said this is broken: we're measuring the wrong things, reporting to the wrong people, and wondering why no one cares. His name is Zack Hamilton. He's the creator of the Experience Performance System, a framework now used by Fortune 500 companies and global retailers, and host of the show Unf***ing Your CX. Zack spent over two decades advising more than 200 retail brands, including Macy's, Sephora, Home Depot, and Coach. His thesis is simple but radical: stop managing experience, start performing it. Zack, welcome to the show.
Zack: Hey, what's up, Leo? Glad to be here and really looking forward to today's conversation.
Leo: You advised more than 200 retail brands at Medallia, so you've seen what works and what gets programs killed. What's the one mistake you see over and over that actually gets CX programs defunded?
Zack: CX programs don't get defunded because they fail, they get defunded because they become irrelevant to the business. The pattern I see is that practitioners get obsessed with measurement, slicing the data 15,000 ways for one insight, and obsessed with storytelling, dashboards, and frameworks. It's not that this is wrong, but it slowly disconnects from execution. An executive doesn't wake up wanting more dashboards. They want faster, better decisions, less risk, more growth and revenue, and less churn. If CX isn't changing operational behavior, it becomes irrelevant, and the moment CX leaders see themselves as a reporting function instead of a performance function, funding becomes optional. The brutal truth is that if your CX strategy can't influence decisions, priorities, or resource allocation, you're running a marketing program for feelings, not a performance system.
Leo: If relevance to the business is so key, how should CX leaders decide which programs are actually relevant?
Zack: It comes down to customer friction. What's getting in the way of customers achieving their goals when they interact with you? Friction isn't just upset customers, it's leakage: revenue, churn, operational risk, compliance. So first understand the friction and its root cause, then frame it as a business problem and communicate the cost of inaction to drive a decision. Sometimes the business will say we understand this friction is causing leakage but we're okay deprioritizing it for now, and that's fine. Our role is to move the business, and that comes down to decision and decision velocity.
Leo: One of your theses is that NPS is lying to CX leaders. What's wrong with NPS, and what should leaders measure instead?
Zack: People think I hate NPS, I've even gotten death threats over this, but I don't think it's evil. I think it's dangerously incomplete. The way the question is structured, it's an advocacy and sentiment metric about how customers felt after everything already happened. It doesn't measure behavior. I could say I'm a promoter and never actually recommend you. NPS was also designed as a system, the inner and outer loop, but brands report the score and close the inner loop while neglecting the outer loop, which is hard and is where transformation and prioritization happen. So it gets gamified. It doesn't tell you what to fix, what to prioritize, or what investment will move revenue or reduce churn. I know organizations with NPS in the 70s and 80s whose same-store revenue is down and whose first-time digital customers lapse at 70 to 80%. A high score creates false confidence, the CEO thinks everything's fine while friction compounds and silent churn accelerates. The metrics that matter are how fast you identify friction, decide to prioritize it, execute a change, and measure behavior change. That's decision velocity, and that's how you build trust, by how fast you fix what's broken.
Leo: If not NPS, what metrics should they use?
Zack: It depends on the business. In retail, I look at customer lifetime value, because it captures how often customers shop and how big their basket is, which is the predictability we all want. So I pair a financial metric like CLV with the operational ones: time to identify friction and decision velocity as the foundational truth of a healthy experience system. I'd also stop obsessing over survey response rates and look at signal health: surveys are one part, but behavioral and operational data are signals too.
Leo: You teach building a one-page business case instead of dashboards. Walk me through a real example.
Zack: When I was Chief Experience Officer at Aaron's, I showed up to my first prioritization session with NPS and CSAT trends and customer stories, exactly what I'd been taught, and was told this is good data, let's keep monitoring it. Meanwhile my cross-functional partners showed up with a specific one-page business case that drove decisions. So to compete for resources, I had to play the game. At my second session I brought a one-page business case for a couple of frictions, and a partner who owned the e-commerce metric said, this is the first time I'm seeing this, so validate it before I commit. That taught me the best CX leaders aren't the ones presenting the case, it's the cross-functional partner fighting for prioritization to remove the friction blocking their KPI. The example: customers were abandoning carts due to delivery-date uncertainty. We mapped what percentage were affected, the conversion loss, time to repeat purchase versus satisfied customers, and lifetime drag, then turned it into a problem statement with the time period, customers impacted, and financial impact, plus the cost of inaction over the next 6 to 12 months, a recommended approach, and the exact resources, like two two-week sprints and 40 development hours. Co-created with the partner and product team, the conversation shifted from sentiment to business impact. Executives don't fund feelings, they fund returns.
Leo: You said the biggest mistake leaders make with AI in support is treating it as a containment tool instead of a business system. What's the difference in practice?
Zack: I led the contact center at Aaron's, and contact centers are too often seen as cost centers because we report on speed to closure without influencing the org to fix frictions. With AI, I see a lot of investment in agents that solve specific issues, with high solve rates, 80 to 90%, and decent satisfaction, so on the surface it looks great, and you can cut human FTEs. But in the short term you've just moved the cost to serve from human to agent. That's not transformation, it's automation of mediocrity. The real opportunity is AI as a decision-making and execution engine, with a learning loop, and crucially, are we solving the friction causing those tickets upstream, or letting them die in the containment loop and resolving the same tickets forever? AI should detect the friction, quantify the impact, recommend and complete the action, then trigger a workflow to fix the upstream friction so customers don't need service in the first place.
Leo: Have you seen AI actually detect friction and recommend solutions for product?
Zack: That's where the industry is moving, and I see it as the next big opportunity for agentic platforms. But they need to understand the human-led performance system behind them. As agents get good at handling issues, a human-led system, the CX or contact-center leader, frames root causes into business problems, documents that system, and feeds it into the agentic layer so the agent learns and acts. The agent is a direct reflection of your human-led system, because you design what it can solve and the guardrails it works within. So I spend a lot of time helping organizations embed that experience performance system and partner it with their agentic solution to move from containment to resolution.
Leo: You predicted CX teams would mostly be AI agents within a few years, with a small human team calibrating them. If you were hired tomorrow as head of CX at a major retailer, what's the first role you'd eliminate and the first agent you'd deploy?
Zack: Experience 2.0, traditional experience management, has served its time, thank it and let it go. Experience 3.0 is agentic CX, and it's an organizational redesign, not just a CX project. My team would be mostly agents, and I'd upskill my practitioners to sit above the loop, continuously measuring and optimizing agent performance. If I had to eliminate a role, it would be the reporting analyst focused only on insights and dashboards, because I think dashboards are obsolete. The first agent I'd deploy is a friction agent that continuously monitors all customer signals, identifies friction, quantifies it financially, and turns it into the one-page business case to drive prioritization. Brands today are all about speed to decision, and some, like Nike, are decentralizing decisions to the people closest to the customer to keep pace.
Leo: On speed to decision, I've heard leaders pass a support-identified problem to a tool like Cursor and fix it within an hour. The speed is incredible now.
Zack: It's all about observation to orchestration, which comes back to decision velocity: how fast can your organization act from the moment friction is identified? Today it's ugly, the best organizations I've seen are around 55 days. One I worked with this year went from 55 days to 38, which is significant, but to become fully autonomous they'll have to get from 38 days to minutes.
Leo: It's interesting how many companies still don't know what the tech can do, especially the speed from support to product.
Zack: Here's the thing, it's not really a tech issue. Decision velocity challenges the power hierarchy. Organizations are designed so the CEO's power is through decision-making. Digital transformation ten years ago didn't fail because the tech wasn't ready, it failed because agile pods needed to make decisions, which challenged executive authority and identity. The agentic era is the same: if the CEO is no longer making those decisions, what is their identity in the redesign? The humans are talented, but the power hierarchy is being challenged.
Leo: Are executives more open to that shift now, or still resistant?
Zack: They're uncomfortable, in a good way. They know they need an AI strategy because they can see what's coming. The hesitation shows up as we need to pilot that, we need more governance, because when you make a decision you also want to insulate yourself if the outcome isn't what you wanted. So you hear a lot of pilots and a lot of who owns the outcome the agent provides. It's an organizational redesign play, and it challenges everything that got us here.
Leo: You started your podcast because you were tired of CX leaders complaining without creating change. What complaint are you most tired of hearing?
Zack: About 14 months ago, flying back from a client in Germany, I had a reinvention moment and wrote down everything I hated about the discipline. That became Unf***ing Your CX, first a LinkedIn newsletter, then a podcast after a friend pushed me to start one. What I learned was I love customer experience, I just hate what it has become. The complaint I'm most tired of is I don't have executive buy-in or a seat at the table. My translation is you haven't earned it. Buy-in was already given once, which is why your CEO invested in your role and your tech stack. The problem is you've never shown up with receipts. You earn buy-in through identifying friction, building business cases, driving financial clarity, and delivering operational results. They buy proof, not lip service.
Leo: Quick fire. Most overrated metric in support, CSAT or deflection?
Zack: CSAT.
Leo: True or false, in three years the Contact Us form will be dead.
Zack: True.
Leo: The company that wins in 2026 isn't the one with the best AI, it's the one with the best...
Zack: Decision velocity.
Leo: Zack, this was phenomenal. Where's the best place for people to follow your work?
Zack: LinkedIn is where I love to engage the community, and the podcast, Unf***ing Your CX, is on Apple, Spotify, and YouTube.
Leo: Perfect. Zack, thanks for joining us. And for everyone listening, if you want more honest conversations about what it actually takes to transform customer experience with AI, make sure you're subscribed to the Fini Podcast. We'll see you next time.
Zack: Awesome, thanks for having me, Leo.
Why does Zack Hamilton say NPS is lying to CX leaders?
He calls NPS dangerously incomplete rather than evil. It measures advocacy and sentiment after the fact, not behavior, and teams report the score while skipping the hard outer loop. The result is false confidence: companies post NPS in the 80s while revenue falls and customers lapse, so the score hides compounding friction and silent churn.
What metrics should CX leaders use instead of NPS?
Zack tracks decision velocity (how fast you go from identifying friction to acting on it), time to identify friction, customer lifetime value, and signal health across surveys, behavior, and operational data. The aim is a balance of financial outcomes and the performance of your experience system.
What is a one-page business case in CX?
It reframes a customer friction as a business problem: the time period, number of customers affected, and financial impact, plus the cost of inaction, a recommended approach, and the exact resources required. Co-created with the cross-functional partner who owns the metric, it drives prioritization because executives fund returns, not feelings.
What is the difference between AI as containment and AI as a business system?
Containment closes tickets and cuts cost but keeps resolving the same issues, which Zack calls automation of mediocrity. AI as a business system detects the friction, quantifies its impact, completes the action, and triggers a workflow to fix the upstream root cause so fewer tickets arrive in the first place.
