TL;DR: Lean User Tests – How to Find the Right Candidates
This part of the Lean User Tests series focuses on acquiring the right candidates for the interviews, answering questions like:
- How many applicants are required to fill an interview slot?
- How to reach out to prospective candidates among your user base?
- How to set up the application form?
There are differences in approaching candidates in the B2B versus the B2C space. However, the following general principles apply to all user interviews.
Age of Product’s Food for Thought of May 8th, 2016 covers Scrum’s Achilles heel — technical debt —, why whole organizations need to become agile and just isles within, the KPIs of culture, and that Scrum mums are overprotective and don’t scale.
We also explore the dark art of software estimation, the 10 success factors of great product teams and their metrics, and how to engage engineers in the design process.
Last, but least, we learn about the best practices of creating products at The Guardian, the biology of leadership, and the last decade’s most memorable IT disasters and what we can learn from them.
Age of Product’s Food for Thought of May 1st, 2016 covers tips & tricks for writing awesome user stories, why 90% of feedback is usually crap, dives into the old discussion — estimations in story points or hours? —, and how to manage developers if you have no clue about coding.
We also explore why effective people think simply, and how to find product-market fit or decide when to pivot. We dive deep into Google design sprints and product storyboards.
Last, but least, we cover data-driven product design at the BBC, why so many smart people are unhappy, and we share a list with 25 geniuses that will or might change our world. (Or probably, they will just fail in the process like you and me, too.)
TL;DR: Lean User Testing – How to Run User Tests Successfully
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.
Age of Product’s Food for Thought of April 24th, 2016 covers how to get an agile product roadmap right, the attention “agile” is enjoying in HBR, eleven habits of high-performing agile teams, and why human psychology is usually an impediment to agile adoption.
We explore ways to talk management out of business plans when innovating, how to create a culture for innovation IDEO style, why product should talk more to sales, and what makes people love your products.
Last, but least, we cover continuous user testing, how to retire products with style, that you’re absolutely not to blame for procrastination—it’s in your genes—, and how Amazon turned a dud into a mega-seller: Echo.
Age of Product’s Food for Thought of April 17th, 2016 covers agile leadership in five sketches, in lessons from the US Marine Corps, and a podcast with Jeff Sutherland. We also dive deeper in Kanban and agile metrics.
We explore scaling agile, why women in product management are underrepresented, and how to create a Lean Startup culture in your organization. We also learn more about product managers vs. product owners.
Last, but least, we cover the surprising psychology of choice, and why you shouldn’t ship the org chart, but build great products instead. Also, Astro Teller explains why celebrating failure is so important for moonshots and why luck has got to do much more with success than you might believe.