Customer interviews are one of the most impactful activities a product team can do. But only if we use the right methods. Customer interviews are one of the most impactful activities a product team can do. But only if we use the right methods. – Tweet This An early customer interviewing mistake is to spend your interview time exploring your solution...

I’m hosting several free events over the next two weeks. I’d love for you to join one of them. March 25th: The What & Why of Continuous Discovery In this webinar, I’ll introduce participants to the continuous discovery framework I introduced in my book Continuous Discovery Habits. We’ll cover: The difference between discovery and delivery...

When an organization shifts from delivery or feature teams to product teams, the first step is often a change to team structure. Delivery and feature teams are often structured by function—front-end teams, back-end teams, mobile teams, etc. These teams can rarely deliver value on their own. Instead, they hand off work from team to team—the back-end...

When you’re building a product, you can easily get overwhelmed by ideas. There are the ideas your product trio comes up with based on your discovery work, the ideas that come from your customers in the form of specific requests, and the ideas that come from stakeholders within your company like your customer-facing teams or CEO, to name a few. While...

Continuous discovery is not a linear journey—as much as we might want it to be. Like a lot of learning, it often feels messy and chaotic. Continuous discovery is not a linear journey—as much as we might want it to be. Like a lot of learning, it often feels messy and chaotic. – Tweet This But if you stick with it, you may eventually find you can look...

When you start interviewing customers every week, it’s easy to get overwhelmed by how much you are learning. When we use our customer interviews to collect specific stories about past behavior, every conversation can uncover dozens of unmet customer needs, pain points, and desires (AKA opportunities). I recommend teams use three different artifacts...