Skip to main content

AI Advisor · By the author

Prototype & MVP Advisor

Dr. Greg Watson

Coaching on your solution concepts, your prototype plan, and what your feedback really shows.

Coming soon

About this AI advisor

Bring your design criteria and solution concepts, your prototype plan (for example from the Prototype Planner in 4.2.2), or the feedback you gathered. The advisor checks that each concept answers the problem you documented, that your prototype asks one clear question honestly, and that your conclusions are no bigger than your observations.

It works for a workplace process, a community service, or a venture alike, and it ends with a responsible next step: iterate, simplify, pause, or stop, which leads into experimentation in Module 5.

Treat it as a coach, not a grader: it gives feedback on your thinking, and the work and the decisions stay yours. Don't paste names or private details about the people who tried your prototype.

What to bring

  • Your problem statement and the design criteria you drew from it (4.2.1).
  • Two or three solution concepts, not just your favorite (4.1.3).
  • Your prototype plan, or what you observed and heard when people tried it (4.2.2, 4.2.4).

What the advisor does

  • Traces each concept back to the problem and design criteria, and flags features that skip past the outcome (4.2.1, 4.3.1).
  • Checks that your prototype asks one clear question, uses the simplest form, and is labelled honestly (4.2.2).
  • Tests whether your MVP is the smallest responsible offer you could actually deliver and support (4.2.3, 4.2.5).
  • Separates what people said from what they did, and keeps small observations to small conclusions (4.2.4, 4.3.2).
  • Looks at accessibility and unintended consequences, and ends with a next step: iterate, simplify, pause, or stop (4.1.5, 4.3.3).

What it won't do

  • Grade you, or pick the "winning" concept for you.
  • Invent user feedback, test results, or data.
  • Approve tests involving health, safety, food, or private data: it points you to the right approvals.

How to use it with the book

Use it twice: on your prototype plan before testing (4.2.2), and on your feedback afterward (4.3.3).