Product Foundations
Walk into a company with no product process and produce something useful in your first week.
You are the first product hire. Nobody hands you a brief. There are app store reviews, a support inbox, an engineer who is busy, and a founder who wants an answer on Friday. Everything in this level happens inside that building.
- 8
- chapters
- 24
- lessons
- 24
- things you build
- ~31h
- of material
You have never held a product title, or you have one and nobody ever taught you the job.
What you will be able to do.
Turn a pile of unstructured feedback into a claim you can defend in a room
Read any interface and name the business decision behind it
Pick a metric that cannot be gamed, and the counter-metric that keeps it honest
Write one page that a busy founder actually finishes, and survive the questions
8 chapters, 24 lessons.
Lessons open in order. You can go back to anything you have already reached, and forward one step at a time.
- 1
What the job actually is
Not the job description. The job: deciding what gets built, on incomplete information, with authority over nobody.
- 2
Reading a product
Every screen you use is the fossil of an argument someone won. Learn to read the argument off the interface.
- 3
Users and their jobs
Who this is for, what they are actually trying to do, and how to find out without a research team.
- 4
How the business works
Where the money comes from, and why the answer to “should we build this” is usually financial.
- 5
Metrics that hold
Choosing a number you can be measured against without the product getting worse.
- 6
Turning signal into a claim
You have evidence. A pile of evidence is not a decision. This is where most product work quietly dies.
- 7
Writing it down
The work is worthless if it does not change what someone does. This chapter is the last mile.
- 8
Defending it
The room where it gets decided, and how not to lose it by bluffing.
The Friday memo
One page to the founder: what is actually broken, who it hurts, what you would do first, and how you would know it worked. Judged the way a real first memo is judged, which is whether anything changes because of it.
- A one-page memo, published to your portfolio
- The evidence log behind every claim in it
- A five minute walkthrough you record yourself giving
- Three project articles: your flow teardown, retention analysis, and final case study
Finishing every lesson unlocks Level 02 straight away, free. The Apprentice badge itself is reviewed by a practising product manager and is part of the one time community fee.
Submit your capstone
Share your project, supporting evidence, and published write-ups. Your level is included automatically so the reviewer has the right brief.