Prototype Validation Tests

Testing ideas before anyone writes production code: assumption maps and pass thresholds, clickable prototypes, fake doors, concierge and Wizard of Oz tests, a weekly session rhythm, and evidence strong enough to justify a build.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Prototype Validation Tests, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

197

Starter tasks

🧩 Product Management

Prototype Validation Tests

Testing clickable prototypes, fake doors and concierge versions with users to validate demand and usability before engineering builds anything.

  1. Assumption map ranked by risk and evidence
  2. Matching each assumption to a test method
  3. Hypothesis cards with pass and fail thresholds
  4. Prototype fidelity choice for the first round
  5. Participant screener for prototype sessions
  6. Consent, recording and data handling for test sessions
  7. Prototype testing tool stack
  8. Validation results log
  9. Honesty rules for fake door and concierge tests
  10. Weekly prototype session rhythm
  11. Standing participant panel
  12. Same-day debrief after every session
  13. Monthly validation readout for stakeholders
  14. Prototype version archive
  15. Participant incentive tracking
  16. Quarterly check of test calls against real outcomes
  17. Observer rota for engineers and stakeholders
  18. Open assumptions backlog
  19. Writing neutral usability tasks
  20. Moderating a think-aloud prototype session
  21. Reading task success, time on task and SUS
  22. Sample sizes and confidence for small tests
  23. Building your first clickable prototype
  24. Running unmoderated remote prototype tests
  25. Telling polite interest from real demand
  26. Fake door test for a planned feature
  27. Landing page smoke test for a new product
  28. Concierge test with five customers
  29. Wizard of Oz test for an automated feature
  30. First-click and five-second tests on key screens
  31. Head-to-head test of two prototype concepts
  32. Pre-order or letter of intent test
  33. Go, pivot or stop call after a test round
  34. Prototype test day with ten customers
  35. Five-day design sprint ending in a test
  36. Guerrilla tests at a trade show or meetup
  37. Evidence pack for the build decision
  38. Investor demo backed by test evidence
  39. Validation on a solo founder's budget
  40. Testing with existing customers without denting trust
  41. Concept tests for creative work
  42. Playtesting a game or interactive prototype
  43. Running prototype tests for a client
  44. Prototype sessions with busy B2B buyers
  45. Testing a prototype across markets and languages
  46. Accessibility testing with assistive technology users
  47. Simulated AI responses in prototype tests
  48. Two-week diary test of a prototype
  49. Benchmarking a redesign against the live product
  50. Prototype validation playbook and coaching

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Assumption map ranked by risk and evidence

Every idea rests on a stack of beliefs: that the problem is painful, that people will find the feature, that they will understand it, that they will pay. Writing those beliefs down and plotting each by how much the idea depends on it and how little evidence you have shows which one to test first, so the first prototype answers the question that could sink the whole plan.

First tasks

  • List every assumption the idea depends on in one shared document
  • Rewrite each assumption as a sentence a test could prove false
  • Plot the assumptions on an importance against evidence grid
  • Circle the three riskiest and confirm them with design and engineering @priority(high)

Matching each assumption to a test method

Different assumptions need different tests: a fake door says whether people want something, a clickable prototype says whether they can use it, and a concierge service says whether the outcome is worth anything to them. Picking the method per assumption, rather than defaulting to the same usability test every time, avoids months of polished prototypes that answer the wrong question.

First tasks

  • Write the top three assumptions at the head of a new matrix
  • Pair each with a fake door, prototype, concierge or Wizard of Oz test
  • Estimate days and participants for each test option
  • Book the first two tests into the team calendar

Hypothesis cards with pass and fail thresholds

Without a number agreed in advance, every test result gets read as encouraging. A hypothesis card that states the assumption, the test, the metric and the threshold (for example, at least 4 of 6 participants complete checkout unaided, or a 3 percent click rate on the fake door) means the team decides what success looks like before the data has a chance to flatter anyone.

First tasks

  • Draft a hypothesis card format with metric and threshold fields
  • Fill in a card for the first scheduled test
  • Agree pass and fail numbers with the product lead before sessions start
  • Store the signed cards in the same folder as test results

Make it yours.

Install Prototype Validation Tests, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.