This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
If youve been reading Product Talk for a while, you probably already know that the majority of the stories we share in the Product in Practice series focus on how product teams are adopting continuous discovery habits in their work. Do you have a Product in Practice story youd like to share? But not today.
I was asked to give a ten-minute overview of my continuous discovery framework and then participated in a fireside chat where the host, Cecilie Smedstad , asked me to go deeper in a few areas. Discovery is a team sport. Its not the exclusive domain of product managers. How are we building production-quality software?
How product managers can adapt core responsibilities across different organizations and contexts Watch on YouTube TLDR Through his research and practical experience at MasterCard, Nishant Parikh identified 19 key activities that define the role of software product managers.
This is the year when Im going to adopt continuous discovery , you might be saying to yourself. Im going to transform my product team and our entire approach to making product decisions! This is why Teresa likes to talk about continuous discovery habits. Whats something you can do today or this week?
Introduction to customer satisfaction surveys Customer satisfaction surveys are vital tools for understanding what customers think, feel, and experience. Surveys provide a range of insights, from quick feedback after a purchase to in-depth assessments of brand loyalty. Types of customer satisfaction surveys and their use.
A regular cadence of assumption testing helps product teams quickly determine which ideas will work and which ones won’t. And sadly, most product teams don’t do any assumption testing at all. In this article, I’ll cover assumption testing from beginning to end, including: Why should product teams test their assumptions?
Productdiscovery is becoming a trendy topic in the world of digital products. This article will cover the ins and outs of productdiscovery. What is ProductDiscovery? Productdiscovery is often defined in comparison to product delivery. Understanding Project-Based Discovery.
Identifying and testing assumptions is a critical part of continuous discovery. But what happens when your assumption tests don’t go as planned? Tweet This Today’s Product in Practice is a lesson in perseverance. Tweet This Today’s Product in Practice is a lesson in perseverance.
“Product thought leaders talk about an ideal way of working. I realize that many product people have never worked in a product trio , don’t have access to customers, aren’t given time to test their ideas, and are working in what Marty Cagan calls “features teams” or “delivery teams.” product outcomes).
Working as a product trio is the foundation for discovery. Without input from a product manager, a designer, and an engineer, it’s difficult for us to account for the cross-functional perspectives we need to build successful products. However, most companies tend to have more engineers than product managers or designers.
How AI captures customer needs that human product managers miss Watch on YouTube TLDR In my recent conversation with Carmel Dibner from Applied Marketing Science, we explored how artificial intelligence is transforming Voice of the Customer (VOC) research for product teams.
The larger and more complex your company is, the more challenging it can be to introduce continuous discovery. Sandrine Veillet ’s Product in Practice story perfectly exemplifies this. Sandrine Veillet ’s Product in Practice story perfectly exemplifies this. Do you have a Product in Practice story you’d like to share?
For years, I’ve shared that Product Talk’s primary outcome is to increase the number of product teams who adopt a continuous cadence to their discovery work. It’s what motivates me to launch new courses and refine our existing lineup. That’s why in 2022, we launched our first ever CDH Benchmark Survey.
In addition to delivering a keynote at the Product at Heart conference (in case you missed it, you can find the video and transcript of that presentation here ), conference co-organizer Petra Wille also invited me to participate in a fireside chat at the Leadership Forum event. Introduction: What Is ProductDiscovery?
It won’t surprise you to hear that I use the same continuous discovery habits that I wrote about in my book to run my business. My primary objective across my business is to increase the number of product trios who adopt a continuous cadence to their discovery work. Turning My Content Into a Product. That was a start.
In the book, the authors recommend that for any new product idea, we need to consider the monetization potential from the very beginning. Assessing a customer’s willingness to pay is a critical discovery activity that directly ties to our viability assumptions. With demand testing, we want to observe actual behavior.
Welcome to JEDI Training for Continuous Discovery Teams. I work as a productdiscovery coach. I’ve had the luxury of working with teams all over the world, and I teach them a structured and sustainable approach to continuous discovery. Here’s how I’m redefining JEDI training in a product context.
I’m disappointed to see the rise of generative AI tools that are designed to replace discovery with real humans. But when we use generative AI to replace customer interviews , to generate opportunity solution trees , or to do our thinking for us, we fundamentally misunderstand the purpose of discovery. Don’t get me wrong.
Committing to continuous discovery means changing the way your product team operates. Continuous discovery means not making decisions purely based on your intuitions or stakeholder requests, but finding ways to integrate touch points with customers into your work every week. Tweet This This can sound overwhelming.
“I get that the continuous discovery habits framework works well for mature products, but does it work for early-stage startups?”. I spent all of my full-time employee experience at early-stage startups (many of them pre-product) and I relied on these same habits to figure out what to build. This question always surprises me.
It’s true that discovery takes time. Interviewing customers , building opportunity solution trees , running assumption tests —these are all activities that take your attention away from delivery. But I’m also a firm believer that discovery doesn’t come at the expense of delivery. Teresa Torres: Hi, everyone.
Productside | Product Management Courses & Training How WellNest Rebooted Product Strategy (eBook Preview) When product teams get stuck in backlog chaos, stakeholder noise, and reactive shipping, its not a process problem. Its a product strategy problem. Their current approach lacks a cohesive product strategy.
Productside | Product Management Courses & Training Writing Effective Product Requirements to Drive Outcomes Most product managers dont set out to write bad requirements. Thats what turns a request into a real requirementand thats the foundation of writing effective product requirements. So what happens?
Can a single course change your career trajectory? For Mike Donovan , Senior Vice President of Product at Sauce Labs , the answer to that question is a resounding yes. Can a single course change your career trajectory? Mike began his career as an engineer and transitioned into product about five years ago.
To deliver high-quality online courses we were patching together several different tools to create a good student experience. We used Teachable as our course platform, Slack for our community, Zoom for our live sessions, Google Calendar to send out course invites, Miro for collaboration, and Mailchimp to send out course emails.
Last week, I was in Cleveland for the Industry Product Conference. I spoke about the three mindsets that help a team find success as a continuous discovery team. Becoming a successful discovery team. Product management is changing. Product managers are evolving from focusing on outputs to outcomes. Tweet This.
How do you know that you are doing discovery well? If you want to improve your discovery process, what outcomes help you track your progress? I like that teams are trying to take an outcome-focused mindset to their discovery practice. The good news is setting discovery outcomes is no different from setting any other outcome.
Productside | Product Management Courses & Training Breaking the Silos: How Product and Engineering Build Better Together In Season 3 of Productside Stories , we sat down with Guy Gershoni , Head of Engineering at genesIT, for a candid conversation on what it really takes to build great products in todays complex tech environments.
I’m co-teaching a design course at Northwestern with my friend Jeff Merrell. In this context, solutions aren’t product solutions, but rather internal programs and processes that effect change within the organization. I realized that they perfectly summarized what matters to me in discovery, so I decided to share them with you.
I am so excited to announce Continuous Discovery Habits is finally here! This book is designed to be a product trio’s guide to a structured and sustainable approach to continuous discovery. It’s the culmination of my work over the past eight years helping hundreds of product teams adopt successful continuous discovery habits.
A few months ago, fellow Product Talk coach Hope Gurion and I sat down to discuss why there’s no single right way to do discovery. In this third and final conversation in the series, we discussed two core principles of continuous discovery : why it’s essential to set up compare and contrast decisions and surface and test assumptions.
Hello, Product Talk readers! It’s time for another installment of Product in Practice. In this series, we highlight the impressive work that forward-thinking product teams are doing. Find our other Product in Practice posts here. During her tenure as a data scientist, Lisa built two predictive products. Tweet This.
For years, I’ve shared that Product Talk’s primary outcome is to increase the number of product teams who adopt a continuous cadence to their discovery work. It’s what motivates me to launch new courses and refine our existing lineup. But first, I want to tell you why this survey matters. It has guided our work.
Taking charge of a product management team can feel like juggling flaming torchesthrilling, but also risky if you dont have the right game plan. Why the First 90 Days Matter When you lead a new product team, your opening move sets the tone. Your product managers wonder if youll champion them. Roger : Absolutely.
Leading a product team (or several teams) comes with its own set of challenges that’s often similar to but distinct from the hurdles individual product contributors face. That’s why it’s especially enlightening when you encounter a product leader who is willing to openly share the challenges they’ve faced. Teresa: Okay.
Photo by UX Indonesia This ‘complete’ guide to usability testing follows an overview in my UX research methods playbook articles. Introduction If you’re responsible in some way for a digital product or system, you should be doing usability testing — whatever your sector, industry or role. But what is usability?
The opportunity solution tree helps visualize all the work that goes into continuous discovery. And while opportunity solution trees have become increasingly common among product teams, there’s still plenty of room for customization, both in the way you set up your trees and the tools you use to build them.
– to come back on to the podcast and chat about how to make sure that, despite everything that’s going on, you continue to incorporate discovery into your practice. Then there’s the second piece of it: What’s the part of Discovery that’s going to stay stable over time? Customer Discovery.
Visualizing discovery work with an opportunity solution tree has been a game-changer for both me and the teams that I work with. This sets the scope for our discovery. From there, an effective team is doing two key research activities week over week. Assumption testing is evaluative. Assumption testing is evaluative.
I teach two courses at Northwestern University. I want to share a little bit more about the work that I am doing there as I think it’s relevant for people working at companies who are starting to adopt continuous discovery practices (in other words, many of you). This course is a 3-day seminar and our students are working executives.
Each week I tackle reader questions about building product, driving growth, and accelerating your career. Laura and her team spend every working hour researching, designing, and experimenting with ways to measure and improve team velocity (while avoiding burnout). Product velocity is about speed and direction.
Yet most product managers still rely on long documents, jargon-filled briefs, and clunky slide decks that dont land with the people who matter. Its a technique borrowed from the world of film and designbut it might just be the most underrated tool in a product managers toolbox. Lets talk about whats getting in the way.
Its one thing to iterate on an existing product. Its a whole other challenge to identify brand-new products to offer. The same is true for API products. They still exist, even when your product is an API. And just because APIs are slightly more technical products, that doesnt mean that you cant apply discovery to them.
One of the most common responses I get when I talk about continuous discovery is: “That would never work in my organization.” But after working with thousands of product people and organizations of all kinds, I can tell you that everyone is capable of making progress on their continuous discovery journey. What Is Discovery?
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content