You already know how to break a feature down and ship it. The gap between that and senior-level planning is usually not skill. It is sequence. Most engineers jump to a solution the moment the ask arrives. The step that belongs in between is the one this course drills: frame the problem, force the disagreement early, then commit with numbers you can defend. In this course you will practice that sequence on a badly formed ask until the habit holds.
Start lesson one: Frame the problem before you propose a solution →
This course is being written as you work through it. Lesson one is ready. Ask your teaching agent for the next one when you have drafted your one-pager.
Getting the problem stated before anyone proposes a solution.
Turning an agreed problem into a proposal a team can review.
Putting a number on it without lying. to them or to yourself.
Turning a plan into something you and other people have actually signed up to.
The same sequence run backwards, for when the plan already exists and it is not yours.
Every claim on these pages links to its source. If a source looks wrong or out of date, check the resource list and tell your teaching agent. The course is meant to be corrected.