Skip to content

Product Engineering

Engineering serves a user problem. Start there.

user problemrequirementsMVPtechnical debtroadmapsmetricsexperimentsprioritization

Lessons

  1. 36.1Problem first: start from the user, not the technologyBefore you build anything, find out who is struggling and why. The best code for the wrong problem is still wasted. 30 min
  2. 36.2MVPs and technical debt: shipping fast without going bankruptHow to ship fast with shortcuts, and how to keep those shortcuts from quietly slowing everything down later. 30 min
  3. 36.3Metrics and experiments: knowing whether a change actually helpedShipping a change isn't the goal. Here's how to tell whether it actually helped, or just looked like it did. 30 min

On the job: try it on your own project

Pick the next feature on your roadmap. Before any code, write the user problem in one sentence, who has it, and how you know. Ask Claude Code to list what the smallest useful version would need and what debt it would create. Write a one-page MVP brief with one success metric and the result that would make you stop or change course.

Can you do this now?

0/4. Anything you can't tick yet: reopen that lesson's practice ladder.