The first 90 days plan helped
Started a new PM job last month and used the plan directly. It made the first weeks much calmer.
Browse
Learn how product managers frame problems, talk to customers, prioritise, build roadmaps and work with engineering to ship outcomes
Created by Daniel Adeyemi
Product management is one of the most talked about roles in tech and one of the least clearly taught. New product managers often learn by trial and error, picking up frameworks without understanding when they apply. This course gives you a clear, practical foundation in what product managers do and how to do it well.
We follow one running example, a scheduling tool for small clinics, through a full product cycle: understanding a problem, talking to customers, choosing what to build, planning a roadmap, working with design and engineering, launching and measuring results.
This course is for aspiring product managers, people who have just moved into the role, and designers, engineers or analysts who work closely with product managers and want to understand the job. No prior product experience is needed.
Every section includes a template: a problem statement, an interview guide, a prioritisation sheet, a roadmap, a one page spec and a launch checklist. You can use them straight away in your own work.
Product manager teaching the fundamentals of shipping the right thing, one decision at a time
I have worked as a product manager on B2B and consumer software, mostly in teams of five to fifteen engineers. My day is spent talking to customers, deciding what not to build, writing specs and keeping engineering, design and the business pointed at the same problem.
I teach the fundamentals that new product managers rarely get taught directly: framing problems, writing clear specs, prioritising with evidence, running a roadmap that survives contact with reality, and measuring whether a release worked.
My courses use one running example product, so the frameworks always land on something concrete. I share my own templates and the mistakes that taught me why they look the way they do.
Started a new PM job last month and used the plan directly. It made the first weeks much calmer.
I moved from support into product and this gave me a structure for everything I was doing by instinct. The problem statement template is gold.
The one page spec and launch checklist are now standard in my team. Short lessons that respect your time.
Saying no with reasons and the trade off meeting role play were the most useful lessons for me.
Our team was measured on features shipped. After this course I proposed outcome metrics and leadership agreed.
Explains frameworks with when to use them and when not to. That is rare.
The clinic scheduling case kept frameworks grounded. I wanted a bit more on B2C products.
Prioritisation section was honest about the limits of scoring models, which I appreciated.
If you have been a PM for a few years, much of this will be familiar. Good for my junior colleagues though.