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
Guest Post by: Marvin Mathew (Mentee, Session 11, The Product Mentor) [Paired with Mentor, Jordan Bergtraum]. Ruthless prioritization translates to product teams spending time building the right thing at the right time. Each feedbackloop has a minimum of four stages. The feedbackloop process is.
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.
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.
January 7th & 22nd: ProductDiscovery Discussion Sessions for Senior Leaders Ive been hosting monthly productdiscovery discussion sessions for senior leaders (think executives, VPs, CPOs) about the challenges they face managing continuous discovery teams. Id love for you to join one. Theyve been a ton of fun.
Speaker: Ben Epstein, Stealth Founder & CTO | Tony Karrer, Founder & CTO, Aggregage
When tasked with building a fundamentally new product line with deeper insights than previously achievable for a high-value client, Ben Epstein and his team faced a significant challenge: how to harness LLMs to produce consistent, high-accuracy outputs at scale.
A custom ChatGPT model that helps accelerate product innovation Watch on YouTube TLDR In this episode, I interview Mike Hyzy, Senior Principal Consultant at Daugherty Business Solutions. He explains how to conduct an AI-powered design sprint that transforms product concepts into clickable prototypes in just hours instead of weeks.
December 5th: ProductDiscovery Discussion Sessions for Senior Leaders I’ve been hosting monthly productdiscovery discussion sessions for senior leaders (think executives, VPs, CPOs) about the challenges they face managing continuous discovery teams. Don’t miss out— register here ! They’ve been a ton of fun.
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?
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?
Speaker: Tony Karrer, Ryan Barker, Grant Wiles, Zach Asman, & Mark Pace
Some takeaways include: How to test and evaluate results 📊 Why confidence scoring matters 🔐 How to assess cost and quality 🤖 Cross-platform cost vs. quality trade offs 🔀 and more!
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.
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.
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.
Over the past several weeks, we’ve been exploring what a product trio is , how decision-making works in product trios , and why more roles aren’t included. Today, we are going to tackle how user researchers fit into this puzzle. Why aren’t user researchers included in product trios? Project research isn’t bad.
Nowadays, tech teams are adopting certain processes to enable them to deliver better products faster. Continuous development takes things further by giving product teams more autonomy and freedom to test out their ideas and experiment with new features in production by choosing who they want to test on.
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?
Listen to the audio version of this article: [link] What is ProductDiscovery? Productdiscovery is the process of “figuring out a solution to a problem we’ve been asked to solve,” writes Marty Cagan. [1] The solutions, finally, are the products or product capabilities that help solve the customer needs.
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.
Think of Net Promoter Score (NPS) software as a tool to measure your customers’ feelings about your product, and categorize them based on their level of loyalty (promoters, neutrals, and detractors). The great advantage of these tools is that they streamline the creation, distribution, and analysis of NPS surveys.
Experimentation allows product managers to make decisions based on data rather than mere intuition. But too many teams don't know what to test, which leads to poorly designed experiments and unclear results. How can a product manager be certain they’re making effective decisions when it comes to experimentation?
A product manager’s guide to breaking free from reactive problem solving Watch on YouTube TLDR In my recent conversation with Doug Hall, master of turning chaos into clarity, we explored how product managers and innovation leaders can break free from reactive problem-solving and create more value through proactive innovation.
“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).
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?
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?
In fact, the entire way product managers work has completely changed. The work/life balance of PMs is being tested; managing a product team and various roadmaps virtually adds to the list of current challenges. Meanwhile many professionals are exploring if pivoting into product management is a career path for them.
Engineers are often reluctant to participate in discovery. But there are many reasons why engineers are one of the essential members of the product trio. Their perspective is valid and can lead to meaningful product improvements. By getting involved in continuous discovery. And this is a good thing.
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.
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.
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.
These days, a simple A/B test can seem to incorporate the whole alphabet, and making a decision from that data isn't as easy as A, B, C either. How do we know we are testing the right thing? How can we shorten the time it takes to do the tests while gaining larger amounts of data? A Live/On-Demand Masterclass.
Imagine launching a product feature that no one uses. Because productdiscovery was skipped … or done poorly. Productdiscovery process is the foundation of building successful products. Yet, many teams rush into development without properly testing ideas, leading to wasted effort and failed launches.
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. That’s why in 2022, we launched our first ever CDH Benchmark Survey. I am thrilled to announce we are running the survey again and I need your help.
How an AI-powered fashion startup achieved product-market fit Watch on YouTube TLDR In this episode, we’re joined by Anya Cheng, former product leader at Meta, eBay, McDonald’s, and Target, and current founder of the AI-powered fashion startup Taelor. ” The problem?
Why market research is product managers’ secret ingredient for successful products Watch on YouTube TLDR Market research is a key part of product development and management. Introduction In the world of product management and innovation, market research is like a compass.
Speaker: Franziska Beeler, Head of Cloud Academy, and Tendayi Viki, Associate Partner, Strategyzer
When testing new business and product ideas, choosing the right experiment is just the beginning. You'll come away from the webinar understanding how to: Formulate strong hypotheses for your business and product ideas. After we have chosen our experiment, it’s important that we spend some time designing it well.
If you are working on your discovery habits, check out the lineup and come join one. This event is a great fit for product managers, designers, engineers, and any other roles involved in building digital products who are using opportunity solution trees to manage their discovery efforts (or would like to). Register here.
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.
Continuous discovery is not a linear journey—as much as we might want it to be. Continuous discovery is not a linear journey—as much as we might want it to be. That’s certainly the case for Kelsey Terry , who’s sharing her story in today’s Product in Practice. Do you have a Product in Practice story you’d like to share?
Opportunity solution trees help product teams chart the best path to their desired outcome. They keep the team aligned as they manage the messy cycles of continuous discovery. How do you test to make sure your opportunity is not a solution in disguise? How does an opportunity solution tree connect to a product roadmap?
Every SaaS business has a strategic responsibility to improve Conversion Rate Optimization—and the key to improving conversion in your product is to never stop asking questions. New ways to test, learn, and iterate to improve feature adoption. If you’re stuck wondering: “What causes most users to leave?” How to define the right events.
“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.
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?
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.
Every business has a strategic responsibility to improve Conversion Rate Optimization—and the key to improving conversion in your product is to never stop asking questions. New ways to test, learn, and iterate. If you’re stuck wondering: “What causes most users to leave?” Or, “Are there any specific places people get stuck?”
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