Product Talk

article thumbnail

Ask the Community: How Do You Shift From Functional Teams to Value-Driven Teams?

Product Talk

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 engineers design the data model and system architecture, the front-end engineers build the interface elements, the mobile engineers work toward feat

article thumbnail

Tools of the Trade: Using Pendo to Manage Customer Requests

Product Talk

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 some of these ideas are unsolicited and may not relate to your current outcome or the opportunities you’re pursuing, that doesn’t mean you want to i

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Product in Practice: Adopting the Discovery Habits is An Iterative Process

Product Talk

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 back and see how much you’ve progressed.

article thumbnail

The Interview Snapshot: How to Synthesize and Share What You Learned from a Single Customer Interview

Product Talk

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 to keep track of what they are learning from their customer interviews: The interview snapshot: This artifact summarizes what you learned from a sing

article thumbnail

Product in Practice: Introducing Opportunity Solution Trees at Texthelp

Product Talk

There are all kinds of ways to introduce continuous discovery habits. If you’ve been at your company for a while, you might get inspired after reading a book or attending a conference. If you’re joining a new company, you might want to try a new tactic out with your new team. And if you’re really excited about an idea, you might look for opportunities to share it outside your company with the broader product community.

article thumbnail

Product in Practice: Bringing the Discovery Habits to WebMD

Product Talk

The larger and more complex your company is, the more challenging it can be to introduce continuous discovery. It’s not just about training people to conduct interviews , use opportunity solution trees , or test assumptions —though those are all important activities—it’s also about convincing them of the value of these activities and getting the people they work with on board as well.

article thumbnail

Ask the Community: What’s a Mistake You Made Early in Your Continuous Discovery Journey?

Product Talk

You’ll often hear Teresa say that there’s no single right way to do continuous discovery. Something she might not say as often (that’s just as true) is that there’s no single wrong way to do discovery , either. Because discovery involves changing the way you work on an individual, team, and even company level, it’s all too easy to make mistakes and missteps.