article thumbnail

Product Discovery Basics: Everything You Need to Know

Product Talk

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.

article thumbnail

Product in Practice: Introducing Opportunity Solution Trees at Texthelp

Product Talk

Based on the information she provided, she tasked the participants with creating opportunity solution trees, drawing experience maps, enriching their trees with opportunities and solutions, and mapping assumptions to test. For example, in a field test with users, they saw that there was some confusion with icons in their product.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Discovery Hand-Offs Kill Momentum: Here’s What to Do Instead

Product Talk

This means that by the time it gets to the engineers, the message is unrecognizable. It’s no wonder we end up with software that doesn’t work for our customers. However, not everyone on the team can take part in every interview or every assumption test. These visual exercises facilitate the work of discovery. Tweet This.

article thumbnail

Here’s Why You Should Write Unit Tests

Modus Create

Software engineers have been testing ever since they could write code. However, the ability to automate software tests commercially emerged only in the 1980s with the introduction of AutoTester. In this article, we will explain why you should write unit tests. . What is Unit Testing?

article thumbnail

Product in Practice: Finding the Best Way to Communicate with Different Stakeholders

Product Talk

Her continuous discovery journey hasn’t just been about interviewing customers or prototyping to test assumptions. Lisa and her team were able to convince their leadership to allow them to run a one-month beta launch with a limited set of customers to test out their new feature. How do you know what engineers care about most?

article thumbnail

When to Use a Holdback Pattern

Split

10 is about 3) but a longer test set-up would be more sensitive: more visitors can enroll in the experiment and some effects compound. If you run a balanced 50/50 test, you know which variant offers the most short-term positive value, or which one is the most promising overall. Wouldn’t that mean three times less power?”

article thumbnail

Agile Laws & Distributed Teams

The Product Coalition

Brooks’ Law Frederick Brooks stated in his 1975 book The Mythical Man-Month: Essays on Software Engineering that “adding manpower to a late software project makes it later.” Exercising more command & control to counter complexity does not work as any experienced leader will note. imposed from the outside?—?with

Agile 83