Teresa Torres on Why Customer-Centricity Without Business Value Is a Disservice

Customer Value Alone Is a Dead End

Teresa Torres doesn't mince words when it comes to the UX community's blind spot. "There's this belief that if I just create value for my customers, I've done my job," she says. "Whereas what I think is really important is to make sure we're creating both customer value and business value, and that if we're not doing both, we're doing a disservice to our customers."

It sounds counterintuitive—how is ignoring business value bad for users? Torres cuts through the wishful thinking: "If I create customer value but I don't create business value, what happens? My product is going to get shut down. Companies aren't charities." After 13 years coaching product teams and selling 750,000 copies of Continuous Discovery Habits, she's watched this pattern destroy products that users genuinely loved.

Her framework starts with outcomes, not features. Teams must understand how their product generates revenue or reduces costs, then map customer needs to those business levers. "Every product team understands how to create value for the customer so that they're satisfied, but also creates value for the business," she explains. "And that usually means the customer is so satisfied they're gonna open their wallet and pay for something."

The 100-Person Startup and the Three-Person Team Face Identical Problems

Torres spent her early career as employee number 10 at one startup, number 23 at another—deep in the zero-to-one trenches of the San Francisco Bay Area. When she began coaching at larger companies, imposter syndrome crept in. "What can I teach these companies? The largest company I ever worked at had 100 people," she recalls. The fear evaporated within weeks.

"I quickly learned it's the same problem. It's the same challenge, right?" Whether you're hunting for product-market fit or optimizing retention at scale, the mechanics don't change. "Ultimately in product, we're trying to get customers to behave in a certain way. Hopefully in a way that creates value for them, but ultimately we're trying to get them to behave in a certain way. And it doesn't matter if it's 0 to 1 or if it's 99 to 100."

It's really about humans and getting humans to do things and helping humans understand things. And helping humans get more value out of things.

— Teresa Torres

Her coaching practice emerged from witnessing "the exact same mistakes everywhere" at early-stage startups: product teams barely knew their customers, rarely spoke to them, and leaned entirely on founder vision. "Which can get you somewhere," she notes drily, "not always where you intend." The shift from outputs to outcomes—from shipping features to driving measurable impact—has pushed decision-making down to product teams who weren't equipped for it. Torres built her practice to close that gap.

Why A/B Testing Teaches You That You Already Failed

Torres loves A/B testing as a measurement tool. She hates it as a learning tool. "Teams build a bunch of stuff and they A/B test it. And then they learn they built the wrong thing," she says. "You just did all the work before you learned you were on the right track."

Eric Ries hinted at the alternative in The Lean Startup, but most teams missed it: you don't have to test your whole solution. Break it into underlying assumptions and test those first. "We can assumption test much quicker. We can test multiple ideas. I think that really unlocks just better decision-making," Torres argues. This is the practical difference between continuous discovery and project-based research—small, rapid cycles instead of large usability studies that arrive too late.

The rise of internet-native companies made this shift possible. "Our ability to measure impact has just gone through the roof. We literally can measure where we're losing people, where people fall off, what's not going as expected," Torres notes. That visibility surfaced an uncomfortable truth: things don't always have the impact teams expect. Assumption testing lets you learn that before the design work, before the engineering sprint, before the A/B test reveals you wasted months.

The Three Walls Every Interview Team Hits

Torres didn't set out to invent a framework. She started coaching teams to interview customers and watched them hit the same three walls. First: "You have to know what to ask, which a lot of people don't. Our intuition doesn't always get us reliable feedback, so there's sort of this art of interviewing."

Second: synthesis paralysis. "Everybody's a little bit different. There's a ton of things you could do. How do we decide what to do? Or worse, everybody looks exactly the same, which means you're probably falling prey to confirmation bias and not actually learning from your customers."

Third: the business wants something shipped tomorrow. "It's great. This is interesting. But my business wants me to ship something tomorrow. And I need to start building."

I started to look at how do we add scaffolding around these three things? How do we help teams ask the right questions? How do we help them synthesize what they're learning and make it really actionable? And then how do we help them determine if their ideas for what to build are actually addressing those things?

— Teresa Torres

Her framework emerged organically: start with an outcome, interview to surface unmet needs and pain points, synthesize strategically to decide where to play, then evaluate solutions through assumption testing. "Does a solution address this need in a way that drives our business outcome?" That's the only question that matters.

Local Maxima Versus the Mountain Next Door

Torres draws a distinction between optimization and discovery that mirrors the difference between tactics and strategy. Changing a call-to-action button can yield a 400% conversion lift—she's not dismissing those wins. "I think we often underestimate those wins," she says. But there's another scope: "Are we even in the right ballpark? Did we build the right thing? Is this the right value? Can we get a better value fit?"

Conversion rate optimization won't answer those questions. "That's where like I need to understand the humans I'm impacting, the humans I'm designing for and hopefully with." She calls this step-function change—not necessarily bigger impact, but a different kind. "Instead of being in this lane optimizing it, we might learn there's a lane right next to us."

All of her habits apply at both levels. Optimizing a checkout flow? Interview recent purchasers about their experience. Deciding whether to add new products? Interview people about what they're looking for and assumption-test new offerings. "My goal was to look at what's the underlying framework that underpins all of our work," Torres explains. "And it's really like, I really draw from problem solving and decision making research because I feel like that's what makes this work."

I named the book Continuous Discovery Habits because I want people to think about it as a collection of habits. It's not a rigorous process or framework that you adhere to perfectly. It's here's some tools in your toolbox.

— Teresa Torres

The word "continuous" matters. Products are never done. There's always more engagement to drive, more customers to acquire, more retention to improve. Fast feedback loops with customers—designing with them, creating with them—are the only way to ensure what you're building actually matters. Torres has spent over a decade helping teams make that shift, one habit at a time.