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
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?
Identifying and testing assumptions is a critical part of continuous discovery. But what happens when your assumption tests don’t go as planned? Amanda Wernicke , Craig Fogel , and Jason Ruzicka knew they needed to test assumptions with users, but found that a virtual assumption test over Zoom wasn’t working for them.
Ellen says they examined different risks and things they’d have to test out. This reframing helped them more easily identify specific areas to run usability tests. When they were discussing the riskiest part of the feature, the Android team said, “Well, we can actually just build this one piece in an hour and put it in a test build.”
Doug joined us in episode 518 and is back to share battle-tested strategies that will help you fix problems faster and smarter. While corporate environments often expect perfect planning and immediate success, true innovation requires multiple cycles of creation, testing, and refinement. hours every day dealing with problems.
Speaker: Ben Epstein, Stealth Founder & CTO | Tony Karrer, Founder & CTO, Aggregage
In this new session, Ben will share how he and his team engineered a system (based on proven software engineering approaches) that employs reproducible test variations (via temperature 0 and fixed seeds), and enables non-LLM evaluation metrics for at-scale production guardrails.
This allows for immediate testing and validation of the user experience. The team’s creative energy feeds into the AI tool’s capabilities, while external validation helps refine and improve the outputs from both human and AI contributions. What makes this process particularly valuable is its flexibility.
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. Ok, that’s great for UX theory nerds.
Question: How do you test a customer’s willingness to pay for a solution? A Better Approach: Run a Demand Test We can simulate the buying experience and see if it resonates with people. With demand testing, we want to observe actual behavior. They can test demand by asking for letters of intent. Let’s dive in.
Katarzyna Malecka shares user testing strategies for all budgets, including 3 case studies and key insights to improve product development. Read more » The post Balancing budget for user testing in product management: three case studies appeared first on Mind the Product.
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!
In this article, Hermann Antonov, Head of Product at CSI, shares his approach to creating an effective test case for hiring Junior Product Managers, offering insights on the desired candidate qualities, search outcomes, and feedback from candidates.
Product Verification In discussing product verification, Nishant highlighted how this crucial activity has transformed dramatically with the adoption of different development methodologies, particularly in the software industry. Conclusion Software product management is far more nuanced and context-dependent than many realize.
For instance, a general example of successful experimentation could involve testing a new onboarding flow for a SaaS product. By running an A/B test on two variations of the onboarding process, a team might identify a version that reduces drop-offs and increases user engagement.
February 4th: Assumption Testing: Quickly Find Your Winning Ideas In this one-hour webinar, I’ll introduce several tactics for how to quickly determine which ideas will work and which won’t. Register here. Register here. How to Find Future Events Finally, dont miss out on any of our upcoming events!
Speaker: Anindo Banerjea, CTO at Civio & Tony Karrer, CTO at Aggregage
Key Learning Objectives: How to leverage human feedback and observability frameworks to detect when the system generates incorrect output and as the basis for accuracy improvements 📈 How the use of playgrounds integrated into the administrative console of the application can isolate the source of the error 🔍 How building a robust regression (..)
What You’ll Learn: Fail Fast, Learn Fast: The value of testing quickly. He reflects on how getting feedback early can prevent costly mistakes and save precious time and resources, especially for startups with limited runway. If youve ever wondered how to avoid wasted effort, this episode will provide the answers.
Learn key A/B testing pitfalls and best practices in e-commerce CX through real-world case studies, ensuring effective experiment design for impactful customer experiences. Read more » The post Beyond launch metrics: Two case studies in crafting A/B tests appeared first on Mind the Product.
December 11th: Identifying Hidden Assumptions: The Key to Faster Discovery Cycles Every week, I hear from people who can’t believe that product teams can actually test multiple ideas in just one week. This skepticism usually comes from those who are still navigating a project-based approach to idea testing.
It emphasizes the importance of understanding users and building, testing, and iterating quickly. These are some of the questions on the quiz that Eva and her CEO created to test employees’ understanding of Continuous Discovery Habits. Introducing Continuous Discovery Habits to Passion.io Click the image to see a larger version.
But too many teams don't know what to test, which leads to poorly designed experiments and unclear results. She’ll walk us through the entire process, from deciding what to test to sharing the results with stakeholders, to illustrate what strong experimentation practices look like and how they can be implemented in every organization.
Hurry and Read more » The post Rerun: Lessons from building the UK’s test and trace app – Randeep Sidhu on The Product Experience appeared first on Mind the Product. The speaker line-up is shaping up nicely and tickets are selling fast. Join us for our smash-hit conference on 20 October.
Key Product Management Lessons: Trust, Testing, and Breaking Bubbles Anya shared several pivotal lessons from her product management journey that challenge conventional wisdom. This demonstrates how innovative product development can create value for multiple stakeholders while addressing larger industry challenges.
Amanda and Craig iterate on assumption tests Amanda and Craig both work at Convo , where they were trying to run assumption tests with Deaf users via Zoom. They shared their story about going through several iterations of assumption tests until they found something that worked. Read more about Sergios story here.
A good baseline is the DACI personality test or reflecting with your coworkers that you already have good relationships with. Hypothesis Devise basic tests that help you to quickly identify the kind of person the receiver is and how to interact with them. Over-time, you can evolve your tests to be faster and more in tune with you.
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. Testing in production –– why it’s important, and the many ways you can deploy your features safely and efficiently.
Usability testing : Observe how real users interact with your product while they perform specific tasks to help you identify usability issues. A/B testing : Compare two versions of your product or design to determine which performs better with users. Beyond these options, you can also dig even deeper with hypothesis testing.
Additionally, working on the MVP would have allowed us to build, test and improve the product iteratively within the deadline. Hence, we started to add each of the requested features to our kiosk and tested the result with the passengers. Testing hypothesis and product design are essential in mitigating and adapting to usability risk.
See more customers Janna says that customer testing should be the bread and butter of modern product management; not the cherry Read more » The post Sunday Rewind: How to be a better product manager this new year appeared first on Mind the Product. Heres what Janna suggested back then, her advice is just as applicable today.
The proposals were better, the team had a vested interest to make them work and it was much easier to get the CEO on board, even if it was a feature or test they would not otherwise have supported. I did my best to support my point, but without actually testing it, it boiled down to the CEO’s view against mine.
Speaker: Teresa Torres, Internationally Acclaimed Author, Speaker, and Coach at ProductTalk.org
As a result, many of us are still stuck in a project-world rut: research, usability testing, engineering, and a/b testing, ad nauseam. Industry-wide, product teams have adopted discovery practices like customer interviews and experimentation merely for end-user satisfaction.
This week, we’re looking towards 2025, seeing what Anthropic has been up to, and spotlighting automated tests for mobile apps. Our content series gives you the lowdown on what’s been happening in the tech world this week and what it could mean for product professionals.
Assumption testing is at the heart of what good continuous discovery teams do week over week. But before we can test our assumptions, we have to identify them. The challenge is that we need to be able to see our assumptions before we can test them. It’s how we evaluate which ideas will work and which won’t.
At the end of the project, we might do some validation research to validate the design (through usability testing) or the final delivery (through A/B testing ). Good product discovery teams engage in two key activities week over week: customer interviewing and assumption testing. The Need for Continuous Discovery. Tweet This.
Building Durable Products: When to Reinvent vs. Retire Some products stand the test of time, while others become bloated or irrelevant. Key debate: How do you convince leadership that sustainability isnt just an ethical decision, but a business growth strategy? How do you decide whether to refine an existing product or move on?
Apply tested plays to your funnel - Use real-world scenarios, triggers, actions and expected results to improve your entire funnel. Use our proven data-driven plays to grow your pipeline and crush your revenue targets. Close more deals with these winning plays!
By collaborating with residents and testing new formats or themes, we could design events that truly resonate and foster a sense of belonging. Test new approaches, such as shifting certain tasks to the evening or using a timer to prioritize key activities. Initially, their prototype underperformed in user testing.
In what ways can you implement rapid prototyping and testing in your current product development cycle? .” – Winston Churchill Application Questions How can you create a “no bad ideas” culture within your product development process? What obstacles might you face, and how can you overcome them?
Raiza previously worked on AI Test Kitchen and has a background in startups, payments, and ads. .” NotebookLM started as a 20% project and has grown into a product that’s spreading across social media and has a Discord server with over 60,000 users.
Prototyping Prototyping involves creating representations of your ideas to test with real users. Things to do: Define what to test: Identify the focus of your prototype testing — this could be testing the usability of a particular part of your solution. depending on what you’re testing. Image by NNGroup.
New ways to test, learn, and iterate to improve feature adoption. In this guide, you’ll learn: 7 detailed steps to infuse data-power into your conversion process. How to define the right events. How to shine a light on where customers drop off.
This can include user research and discovery, heuristic evaluation, and results of usability testing. Usability testing of newsolution How are you sure this solution will work better for us? So its vital to include a section that will describe what testing activities you plan to conduct to ensure that your design performs well.
By using prototypes wisely, product teams can figure out what truly meets customer needs and test solutions before launching them in the market. Fifty-one percent of the design experience should be spent in the prototyping, testing, and iterating phase.
Testing and experimentation: Braze allows you to test your content, design, and timing to see which resonates better with customers. Cross-channel messaging: From SMS to email and in-app messaging , Braze empowers you to deliver multichannel messages that help you meet customers where they are.
What’s the smallest thing we can deliver to test this idea? When faced with a long list of potential features or bug fixes, ask: What’s the problem we’re solving? How does this align with our overall goals? Outcome-focused thinking doesn’t just create better products—it builds trust with stakeholders who see you driving results that matter.
New ways to test, learn, and iterate. In this guide, you’ll learn: 7 detailed steps to infuse data-power into your conversion process. How to define the right events. How to shine a light on where customers drop off.
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