← Noesa

Product decisions, understood

For Founders, product managers, designers, and developers using AI to build features who need to decide what should exist and how to know it works. · 15 days · Concepts

A 15-day course
One short lesson a day · go at your own pace
Log in to start
The days
Listen to the whole course · 77 min
  1. 1Name the problem before the solutionBy the end you can rewrite a feature request as a problem statement with a user, situation, struggle, and consequence. Listen · 5 min
  2. 2Identify the user and jobBy the end you can name a specific user and the progress they are trying to make in a particular situation. Listen · 5 min
  3. 3Separate symptoms from root causesBy the end you can distinguish a visible symptom from a supported cause and select evidence that could separate competing explanations. Listen · 5 min
  4. 4Write outcomes, not featuresBy the end you can define a behavioral outcome with a population, direction, measure, and time window. Listen · 5 min
  5. 5Find the riskiest assumptionBy the end you can list an idea's assumptions and identify the one whose failure most threatens the intended outcome. Listen · 5 min
  6. 6Decide what evidence would change youBy the end you can define a decision threshold and name evidence that would support, weaken, or overturn an assumption. Listen · 5 min
  7. 7Compare opportunities before prioritizingBy the end you can compare product opportunities using consequence, frequency, confidence, and strategic fit without collapsing them into a false precise score. Listen · 5 min
  8. 8Define the smallest useful testBy the end you can design a test that isolates one risky assumption with a real behavior, threshold, and limited exposure. Listen · 5 min
  9. 9Read behavior, not complimentsBy the end you can rank product evidence by its distance from the target behavior and identify what each source cannot prove. Listen · 5 min
  10. 10Design constraints and edge casesBy the end you can state product constraints and trace edge cases through trigger, state, user consequence, and recovery. Listen · 5 min
  11. 11Make trade-offs visibleBy the end you can compare options by naming who gains, who pays, what is reversible, and which value the choice protects. Listen · 5 min
  12. 12Define quality before buildingBy the end you can write a quality contract with outcome, behavior, boundaries, evidence, and release gates. Listen · 5 min
  13. 13Decide what not to buildBy the end you can reject, defer, or remove a feature with a reason, revisit trigger, and protected outcome. Listen · 5 min
  14. 14Learn from a failed releaseBy the end you can compare expected and observed behavior, locate which assumption failed, and choose a proportionate response. Listen · 5 min
  15. 15Direct AI from problem to proofBy the end you can brief AI with a decision record, inspect its proposal against evidence and gates, and accept, revise, or reject the work. Listen · 6 min