Continuous Discovery Habits | A book summary from Teresa Torres

Okay, so have you ever felt like you're kind of just, you know, throwing darts blindfolded when it comes to building products? Yeah, we've all been there. Yeah. Well, today we are diving deep, and I mean deep, into continuous product discovery. And to guide us on this journey, we have Teresa Torres' book, Continuous Discovery Habits. We're going to be talking all about how to build products, but not just any products. We're talking about products that people absolutely love and that, of course, make business sense. Right. And it's all fueled by data and customer feedback. So expert speaker, are you ready to help us unlock this continuous discovery thing? Absolutely. You know, think of continuous discovery as think of it like having this ongoing conversation with your customers throughout the entire product development journey. It's really about weaving their insights into every single step from that initial spark of an idea all the way to launching it out into the world. And then what happens after two? So it's not just like one and done. It's not like we're doing a research sprint. It's like this system, this constant learning, always adapting kind of thing. Exactly. OK, so. What makes this different from the way maybe a lot of us are used to that traditional product development? Yeah. So traditional methods, they often just struggle to keep pace with, you know, just the ever changing needs of customers. It's so easy to get stuck, you know, clinging to those initial ideas, even when the data is telling you otherwise. Yeah, you get married to that first idea. Exactly. And it's like a runaway train. Oh, no. Speeding towards a destination based on, well. assumptions, not really reality. So continuous discovery is about building a more agile vehicle, one that can adapt, adjust course in real time. It's like swapping out the train tracks for a winding river. You're constantly navigating, you're adjusting to the currents of customer needs. Okay, I'm liking this analogy. But how do we build this adaptable vehicle? What are the core principles, the things that drive continuous discovery? So the book really emphasizes four kind of agile principles okay and the first one is shorter development cycles but the key is frequent check-ins with your customers okay so it's like taking smaller steps on a hike so you can make sure you're still on the right path right exactly that's a great way to put it the second one is it's got to be a sustainable pace yeah this isn't a sprint it's not about you know rushing to the finish line it's about can you keep this pace up You know, building something you can maintain, you know, for the long haul. You're going the distance. You're not trying to burn out in the first mile. Exactly. Exactly. Okay. What about the other principles? I'm ready. All right. So the third principle is it's about flexibility. Okay. You're gathering these customer insights. You have to be prepared to adapt and adjust your course. Okay. Think about navigating a maze. Sometimes you're going to hit some dead ends, but you're going to find your way through. and then finally it's about prioritizing ruthlessly prioritizing okay what you build what are you actually building focusing on is this truly delivering value no more feature overload exactly so we're ditching the feature factory mindset and we're like laser focused on building the right things the right way okay this is all sounding good in theory but paint me a real world picture sure give me an example of a company that's like nailing this continuous discovery thing. Well, Spotify. Spotify is constantly experimenting with new features, new algorithms based on, you know, they're using data and feedback. Okay. For instance, the Discover Weekly playlist. Oh, yeah. Which is what, it's a curated mix of songs tailored to, you know, what you like. That came out of continuous discovery. They analyzed the listening data, conducted interviews. They discovered that people really wanted personalized music recommendations. It's so true. And Discover Weekly is like the thing that everybody loves. So perfect example of continuous discovery leading to those aha moments, those product innovations. Now the book really emphasizes this shift, this shift from an output-driven mindset to one that's all about outcomes. So break that down for us. What does that mean and why is it so important? Okay, yeah. It's about shifting your focus from, you know, okay, imagine this. You're building a fitness app. Okay. An output-driven approach might be, let's add as many workout routines as possible. Okay. Got it. But an outcome-driven approach is going to start by asking, well, what are we actually trying to achieve for our users? Right. Are we trying to help them lose weight, gain muscle, or just move their bodies more? Exactly. You've got it. Okay. It's about first identifying, what is that desired outcome? And then working backwards, like how do we get there? What are the features? What are the solutions to achieve that outcome? Got it. So it's not just about building. It's about building the right things, things that actually move the needle, both for your users and, of course, for your business. Exactly. And a great example of that is Airbnb. Okay. Early on, they realized our users aren't just looking for a place to stay. Right. They're looking for an experience, a sense of belonging. And that outcome-driven mindset led them to focus on how do we foster community? How do we create connection? And so they have their experiences. platform right where hosts can offer unique activities and tours that is such a good example because it's so true i mean when you use airbnb it's all about that it's about the experience okay let's switch gears just a little bit and talk about teamwork how does continuous discovery work when you've got a whole team of people collaboration is like key and the book talks about this thing called the product trio okay and so you got the product manager the designer and the engineer okay the three musketeers of product development exactly they each bring their own kind of perspective their own skills to the table exactly but how do you make sure that especially when you're tackling something brand new how do you make sure everybody's on the same page one powerful technique is to visualize your collective knowledge imagine creating like a map okay a customer journey map Okay. It's a visual representation of every touchpoint, all the actions, all the emotions, everything a customer experiences when they interact with your product. Okay. So we're talking about like literally creating a map of their journey, like a roadmap to understand their world. Exactly. And what's really cool is when teams do this together, they start to uncover blind spots. Oh, wow. And they gain this much richer understanding of the customer. So you're almost like... Piecing together a puzzle, right? Each member of the trio brings their own pieces, and then all of a sudden you see the full picture. Exactly. Exactly. But how do you even decide what the scope is? Because if we're building, like, let's say a language learning app, does the map just include what happens in the app? Or does it include, you know, their entire language learning journey? Like, how do you decide what the boundaries are? You're asking all the right questions. Defining the scope is crucial. Okay. If it's too broad, you just get lost in a sea of information. Right. Overwhelming. right exactly and if it's too narrow you're going to miss crucial context so in this case let's say a language learning app yeah if you only focus on what happens inside the app that might be too narrow right because you need to consider well how are they currently learning What are their motivations? Yeah. What challenges are they facing? Like, what's their life like? Yes, exactly. What are they doing even offline? So it's about understanding the whole context. OK, so maybe a good starting point for the scope is how are people currently learning languages? And then how can we, you know, enhance and personalize that whole experience? Exactly. Yeah. You got it. Finding that sweet spot for the scope is going to help your team focus your efforts and ensure you're gathering those really like. juicy relevant insights okay i love it now let's talk about one of the most i think powerful tools in this whole continuous discovery toolkit and that's the customer interview yes the art of the conversation so teach us how do we go beyond just asking customers well what do you want and actually uncover those deep-seated needs those desires that maybe they don't even realize they have traditional market research often falls into this trap of just asking those very direct questions. Like, what features would you like to see? Why did you choose our product? Right. But here's the thing. People aren't always aware of the real motivations. Oh, that's so true. We like to think we're making these rational decisions. Exactly. But so often it's our subconscious desires or biases even. Yes. Pulling the strings. It's like that saying, we are not thinking machines that feel, we are feeling machines that think. That's a great way to put it. It's true though. So what do we do? Instead of asking those direct questions, encourage storytelling. Ask open-ended questions that invite your customers to really share their experiences. Okay, examples. Give me an example. Tell me about the last time you tried to learn a new language. What happened? Walk me through that. I love that. Okay, so by, like... tapping into a specific experience, you're unlocking so much more. Like you suddenly have their emotions, you've got their motivations, their pain points, all the things. You're going beyond the surface. You're uncovering those like golden nuggets of insight. Exactly. Exactly. And as you're listening, pay attention to those little details. Yeah. The nuances, you know, does their voice change? Are their eyes lighting up? Those are the moments when the real insights emerge. It's like you can almost feel that connection, you know. Yeah. With the human on the other side of the data. It's not just like taking notes. You're really building empathy, building understanding. But once you've had all these conversations, how do you actually keep track of all those golden nuggets? I mean, that feels like it could get overwhelming pretty quickly. Yeah. And that's where the opportunity solution tree comes in. So imagine this. You've got this visual representation of your product strategy. It's a tree. okay okay and the trunk of that tree that's your desired outcome okay the branches those are your potential opportunities and then the leaves those are all the possible solutions i love this this is great so you're like mapping out the whole landscape of possibilities from the big picture to those really nitty-gritty solutions that's a great way to put it and this tree it's not static it's a living document so as you gather more insights as you test your assumptions it evolves so it's not just an artifact right it's actually a tool that's guiding you exactly love that and one of the most powerful things about it is it helps you prioritize that's huge because you can't tackle every opportunity at once so how do you decide which ones to go after first that is like the question right yes for product teams it's so easy to like get excited about all the shiny objects and then all of a sudden you're off track. And the tree helps you do that. It helps you prioritize based on, well, what's the customer impact? Is this even feasible? What's the business value? You know, does this align with our strategy? So it's like you're taking those opportunities, you're running them through this filter. Exactly. And you're like, okay, which ones are most promising? Which ones make the most sense for what we're trying to do? You got it. And then you learn more. Yeah. And you got to be willing to adjust those priorities. Sometimes you even got to prune those branches. Yeah. The ones that aren't working. Exactly. Love it. Okay. Let's talk about generating those solutions. So those leaves on the tree, all those possibilities. Yeah. The book talks about, you know, brainstorming, coming up with a ton of ideas before you even start to narrow them down. So why is quantity so important when you're brainstorming? Because it's so easy to just latch on to that first good idea. Right. But research shows that's probably not our best idea. Right. That's the one that's like right there on the surface. Exactly. So the more ideas you can generate. you start pushing past those obvious solutions. And that's when you really unlock creativity. It's like you're mining for gold, right? You've got to sift through a lot of dirt and rock before you find those golden nuggets. You got it. Exactly. Yeah. And to get to those golden ideas, sometimes it's helpful to add constraints. Oh, constraints. Yeah. So instead of just... let's brainstorm solutions how about let's brainstorm solutions using only emojis oh i love that or what would this solution look like if it had to be free okay i love that because it forces you to think differently exactly you can't fall back on your like usual bag of tricks exactly it's about embracing those limitations all right love it they actually can spark more creativity now once you have all those ideas now you have to separate the wheat from the chaff you gotta figure out What are we assuming here? Okay, yeah, assumptions, those pesky little beliefs that we don't even realize we have sometimes. Exactly. Why is it so important to uncover those, to examine them? Because our ideas are built on assumptions. And if those assumptions are wrong, the whole thing can crumble. Yeah, it's like building a house on sand, right? It might look good at first, but it's not going to withstand the storm. Exactly. So we've got to put our detecatats on, scrutinize those assumptions, make sure they're actually true. So... How do you even identify those hidden assumptions? Because they can be sneaky. One technique is to create a story map. Imagine like you're drawing a comic strip that shows how your idea would play out step by step in the real world. And as you're mapping that out, those hidden assumptions, they start to pop up. It's like you're creating a storyboard for a movie. But instead of a plot... You're mapping out like, okay, here's the experience. And then as you do that, those plot holes, those are the assumptions. Exactly. Exactly. That's a great way to put it. And once you identify those assumptions, it's time to test them. Oh, yeah. Put them to the test. Because remember, we're not trying to prove ourselves right. We're trying to see, okay, is this actually true? So we can make really informed decisions. So we're talking about the scientific method, right? Exactly. Form a hypothesis, test it out. So what are some effective ways then? to test those assumptions when you're doing this whole continuous discovery thing. You want to design these like small, very focused experiments. Okay. That allow you to see how our customer is actually behaving. Okay. And you don't need to go build a whole product. You can do simple prototypes, mock-ups, even something called fake doors. Fake doors. Okay. I need to hear more about these fake doors. What are we talking about? So let's say you want to see if people are even interested in a new feature. Okay. You could create a fake door on your website. Okay. It's a button. It's a link. Looks like it goes to this new feature. But really, it's just a message that says, hey, this is coming soon. Oh, I see. But by tracking how many people click on that fake door, you get a sense of, okay, are people actually interested in this? So you're dipping your toe in the water before you jump in. Exactly. Checking the temperature. You're seeing how deep it is. You got it. this iterative approach, this constant testing, getting feedback in these small little chunks, that is continuous discovery. So we're moving away from these big, scary launches where you're like, I hope this works. Exactly. And we're taking a much more agile, experimental approach. I love it. But once we've done all this testing, we've got all this valuable feedback from our customers, how do we actually make sure that those insights are turned into action? That is when the rubber meets the road. Right. This is where continuous discovery fuels continuous delivery. So all these insights, it's telling you what to build, how to build it, when to release it. So it's like this beautiful cycle happening. Exactly. Where discovery feeds delivery, which gives you more data, more insights. And then it just it keeps going. It's this continuous loop. And that's how you build better products. faster. Now, I'm imagining that for some teams, if they're used to that more traditional way of doing things, the more waterfall approach, this might feel like a big shift. So how do you help teams embrace this new way of working? You have to foster this culture of experimentation, continuous learning, encourage your team. You know, uncertainty is OK. Yeah. Failure. That's an opportunity to learn and celebrate those small wins along the way. So create a safe space to try new things, to experiment. Exactly. Yeah. And I feel like with continuous discovery, they're always going to be those surprises, those unexpected things that kind of pop up along the way. So how do teams handle those curveballs and still like stay on track? Well, you know, it's like you said, you're sailing in uncharted waters. You got to be ready for those unexpected winds. You know, those currents that just kind of come out of nowhere. Sometimes they're small, you know, like, OK, we just need to adjust our course a little bit. But other times they make you rethink your entire approach. Like, wait a minute, we're in the wrong ocean. OK, now you got to give me an example. Give me an example of a discovery hurricane that like totally blew a team back to the drawing board. OK, so there was this team at Duolingo, you know, the language learning app. Yeah, yeah. They were working on how do we get more daily active users? How do we get people using this every single day? And their initial hypothesis was, well, gamification. Let's add more gamification features. That'll get people more engaged. Yeah, it makes sense. I mean, games, they're designed to keep you coming back, right? Exactly. So they ran some experiments, right? They added things like leaderboards. badges and they found that yeah those things did work but in the short term people were using the app more but then they started doing some user interviews and that's when they found something really interesting okay tell me more what they find a lot of users said you know the gamification It's fun, but it's actually distracting me from the real reason I'm here, which is to learn a new language. Oh, interesting. They were so busy trying to earn points and badges that they weren't actually remembering the information. It's like those side quests in a video game, you know? Yes. They're super fun, but they totally take you away from the main story. That's a great way to put it. So this was a big deal for Duolingo. They had to take a step back. They realized, wait a minute. This outcome that we were focused on, increasing daily active users, it's not really aligned with what our users actually want. So they had to go back to the drawing board like, okay, what are we really trying to do here? Exactly. And so they shifted their focus. They said, you know what? Our outcome is going to be helping our users make real progress. We want them to actually learn the language. And that led them to prioritize different features, things that reinforce that learning, that retention. Interesting. Like spaced repetition, algorithms, personalized feedback. Okay, so a much better outcome. Much better. And it all came from listening to their users. Okay, so that's a great example of how continuous discovery, it's not just about those small tactical tweaks. It can actually lead to these really big strategic shifts that make a huge difference. Exactly. Like sometimes those surprises, they force you to re-examine the whole foundation of what you're doing. Absolutely. It's like you're a detective, right? Yeah. And you think you've got it all figured out, you know who did it, and then boom, a new piece of evidence pops up and you're like, wait a minute. Back to square one. Exactly. And that's why this iterative approach is so important because you're constantly getting new information. And you're adjusting. Okay. So we're not afraid of the surprises. We're like, okay, bring them on. This is an opportunity to learn. Yes. Okay. But I have to imagine all this discovery, all this iterating, it could start to feel a little messy. So how do you keep things organized? How do you make sure you're moving in the right direction? It's all about finding the right tools, right? The processes that work for your team. Some teams, they like to keep it really simple. Okay. Whiteboards, spreadsheets, that's it. Okay. Others need something a little more robust, maybe some software to help them manage it all. So it's about finding the right hiking gear for the journey that you're on. I like that. That's a great way to put it. But the key is no matter what you use, you've got to have a way to capture those insights, keep track of your assumptions, and document your decisions because that's how you create that shared understanding. So you're like... creating a trail map of your journey so other people can follow along. Exactly. I love that. Now, let's talk about data because obviously data plays a huge role in all of this. But how does it fit into this world of continuous discovery? It's essential, but it's not the whole story. Think of data as the ingredients, not the meal. Okay. So it gives you valuable insights. Yeah. But you have to know what to do with it. It has to be interpreted. You got to analyze it. And then you have to turn it into action. So it's not enough to just collect data. You have to make sense of it. Like, what is this data actually telling us? Exactly. And that's where the human element is so important. Because data can tell you what's happening, but it can't always tell you why. So you have to combine that data with those qualitative insights that you're gathering from your customer interviews, from your observations. You even have to use your intuition sometimes. So you're like a chef. Okay. And you have all these incredible ingredients in front of you, but you still need your skills, your creativity, your understanding of how all those flavors work together to turn those ingredients into an amazing meal. That is such a good analogy. Data without interpretation, it's just noise. It's true. It's meaningless. Okay. So it's the human element that turns it into something meaningful. So it's all about finding that balance. Exactly. Data-driven and human-centered. Absolutely. And continuous discovery. That's what helps you get there. Okay. It's how you make sure your decisions are both data-informed but also customer-centric. You're building products that are like... Smart and empathetic at the same time. They're functional, they're efficient, but they're also delightful to use. Exactly. That is the ultimate goal of Continuous Discovery, to build things that people love to use, that solve their problems, that feel intuitive and empowering, even joyful. Products that spark joy. Yes. I love it. All right, listeners, we hope this deep dive into Continuous Discovery has you feeling inspired and ready to embark on your own journey to build products that are truly customer-centric. And remember, it's not about finding that one perfect process or that one magic tool. It's about cultivating a mindset. It's about curiosity, empathy, a deep desire to understand your users. And it's about building those discovery muscles, getting stronger every single day. So go out there, embrace the unknown and start discovering.

Resume



This book is based on the premise that successful products are created through continuous feedback and offers a structured and sustainable process for incorporating customer feedback at every stage of product development. It explores continuous discovery techniques, from building experience maps to testing assumptions, with the goal of creating products that meet customer needs and generate value for businesses. The book provides a practical approach with real-world examples, along with tips and strategies to overcome common obstacles faced by product teams.








Detailed Summary: Continuous Discovery Habits



This document summarizes the key themes and most important ideas from the book “Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value” by Teresa Torres.



Key Themes:



Continuous Discovery Mindset: The book emphasizes the importance of cultivating a specific mindset for continuous discovery, including a focus on outcomes, collaboration, visual thinking, experimentation, and a customer-centered approach.



The Product Trio: Torres advocates for a core discovery team composed of a product manager, a designer, and a software engineer, referred to as the “product trio.” This trio collaborates closely throughout the entire discovery process.



Common Framework for Continuous Discovery: A framework is presented to guide teams through the discovery process. This framework focuses on defining outcomes, discovering opportunities, structuring the opportunity space, prioritizing opportunities, and testing assumptions.



Importance of Outcomes: The book distinguishes between outcomes and products. Teams are encouraged to define success based on the value created for customers and the business (outcomes), rather than simply shipping code (products).



Discovering Opportunities: Methods are taught to discover opportunities through the creation of experience maps and conducting customer interviews. The importance of asking story-focused questions and understanding real customer behavior is emphasized.



Structuring the Opportunity Space: The concept of an Opportunity Solution Tree (OST) is introduced as a tool for organizing and visualizing the opportunity space. The OST helps teams break down large challenges into smaller, more manageable opportunities.



Prioritizing Opportunities: A framework is provided to evaluate and prioritize opportunities using criteria such as opportunity size, market factors, company factors, and customer factors.



Idea Generation: The idea generation process is explored, highlighting techniques like individual ideation, inspiration from analogous products, and group evaluation.



Testing Assumptions: The concept of assumption testing is introduced as a means to validate ideas. It explains how to identify, prioritize, and test assumptions using techniques such as assumption mapping and experimentation.



Collaborating with Stakeholders: Guidance is provided on how to involve stakeholders in the discovery process, share learnings, and manage expectations.



Conclusion:



“Continuous Discovery Habits” provides a practical and actionable framework for product teams to discover products that create value for both customers and the business. By adopting the habits and mindsets described in the book, teams can enhance their ability to identify opportunities, validate ideas, and deliver successful products.