Usability testing practice exercise for product managers

What is the challenge scenario?

Usability testing replaces opinion debates with evidence. The bootcamp frames it plainly: you do not need a research team or weeks of lead time, you need a clear flow to test, the right few participants, tasks that reveal behavior, and a way to turn what you see into decisions.

The exercise asks you to design a complete, repeatable test you could actually run in days, covering goals, recruiting, tasks, moderation and a prioritized output of issues and fixes, rather than any one piece of the process in isolation.

Builders Camp rates this challenge beginner difficulty and lists it at 60 minutes, which makes it approachable even if you have never run a formal usability session before. The structure is deliberately end to end, so a beginner still leaves with a real, usable plan rather than a single isolated skill, and the same plan can be reused on a completely different flow the next time a real decision needs evidence instead of opinions.

What are you asked to do?

Pick one flow to test, onboarding, checkout, or a key feature, and state what you are trying to learn and what it works would mean as your success criteria. Define who you need, five participants is plenty, and write a two to three question screener that avoids recruiting the wrong people or your own team. Write three tasks as goals rather than instructions, so they reveal real behavior instead of politely following a path you hinted at. Run the session, or a dry run, and for each task record what the participant did, where they hesitated or failed, and a direct quote, staying neutral rather than rescuing them. Close by turning the observations into a ranked list of issues, each with a severity rating and a specific fix or follow up experiment.

What does a strong answer cover?

This bootcamp does not publish a rubric for its practical challenge, so check your own draft against the curriculum's own questions instead of a worked solution:

• Are the three tasks written as goals rather than instructions that hint at the path a participant should take?
• Does the screener avoid recruiting the team's own people or participants who do not match the target user?
• Do the recorded observations capture what the participant actually did and where they struggled, rather than a general impression of the session?
• Does the fix list rank issues by severity with a specific next experiment attached to each one, rather than a flat list of complaints?

Skills this exercise practises

Defining a testable success criterion before running a session, writing a participant screener that filters out the wrong people, writing tasks that reveal behavior instead of opinions, and turning raw observations into a prioritized, actionable fix list.

Which bootcamp does this challenge come from?

This is the practical challenge from Usability Testing for Product Managers, Builders Camp's one week bootcamp on planning and running usability tests that turn findings into product decisions, led by Andre Albuquerque. Completing it counts toward that bootcamp's certificate. The how to run customer interviews and discovery interview script guides both cover the recruiting and questioning skills this exercise depends on, and how to validate a startup idea puts usability testing into a broader validation context. The customer survey practice exercise elsewhere in this series practises the companion skill of collecting feedback at scale rather than one session at a time.

Builders Camp runs live and self paced bootcamps in product management and AI product building. See the Usability Testing for Product Managers bootcamp for current cohort dates and the full self paced curriculum.