This part of the Lean User Tests series focuses on acquiring the right candidates for the interviews, answering questions like:
There are differences in approaching candidates in the B2B versus the B2C space. However, the following general principles apply to all user interviews.
In a world where data-driven decision making is often prevalent, some people feel uncomfortable with agile methodologies as those provide only a few useful metrics. One of those few, however, is the cycle time from idea to shipping a valuable product increment to your customers.
If you want to optimize this metric for your organization, speeding up your product discovery process is essential. And this requires two things: a) rapid prototyping and b) people to test your prototypes with. That’s the main reason why running user tests continuously is so important.
Learn how to best organize and run user tests in this series of six blog posts. Today, we start with answering the “why” question and what huge benefits user tests will provide to your product discovery and delivery process.
When dealing with product roadmap failure, stop debating whether you are doing product roadmaps “right”, or whether roadmaps are evil. Look instead at the job you are hiring your roadmap to achieve. And then ask if the roadmap is the best tool for the job.
New to Product Management? What is a product roadmap? For a standard definition see here.
Customer care as an entity, its function, and status within a company, can act as a good litmus test for a company’s culture, its product management, and thus its potential for innovation and agile change.
If customer care is regarded solely as a cost center that needs to be outsourced, agile change is unlikely to happen in that organization.
Building a valuable, usable and feasible product does not happen overnight. These are my four core learnings from focusing on customer value, looking back at the projects I have been pursuing over the years.
