Practice the daily decisions the job is actually made of, so your first ninety days feel like competence instead of guesswork.
You have been told product management is about vision and roadmaps, but nobody has shown you what the job looks like on a Tuesday. You are handed a backlog, three stakeholders who each want something different, and a team waiting on a decision you do not feel qualified to make. This course is the apprenticeship nobody gave you. Ten modules walk the whole loop: what the role actually is, how to interview customers without leading them, how to turn a vision into objectives and key results (OKRs) people can act on, how to prioritize and say no without burning goodwill, how to write a product requirements document (PRD) that survives review by the people building it, how to partner with design and data, how to instrument a feature and run an honest experiment, how to launch, how to manage upward, and how to grow your career. You will rehearse on the platform simulators — customer-interview roleplay, stakeholder triage, and a PRD critic — then ship one of five capstones: a full PM dossier, a discovery sprint, a reviewed PRD, a launch postmortem, or a portfolio case study.
Built by Lakshya Kumar
Paste this into any AI chat. Fill in the bracketed parts with your context — you'll get back a straight answer on whether this belongs on your plate.
We grant free access case-by-case — students, career-switchers, builders on a tight budget. Sign in to send us a note.
Sign in to applyFinished the tasks? Take the prompt to your AI and get tested on it. We copy the prompt and open the app — just paste it in.
Interview people without leading them, so you build against evidence instead of your own hopeful guesses.
Set objectives and key results and pick one north-star number, so the backlog stops being a wish list.
Score the work honestly, defend the cut, and give the person you turned down a reason they can repeat.
Turn a fuzzy idea into a document your developers can build from without a dozen clarifying messages.
Run sprints that help instead of perform, bring design in early, and know exactly when to pull in data.
Instrument before you ship, size an experiment properly, and learn the cases where testing is the wrong tool.
Pick a launch tier, run a beta that teaches you something, and brief support before the first ticket lands.
Write updates people actually read, disagree with your boss productively, and know which battles are worth it.
Learn what each level rewards, handle the case and product-sense interviews, and build a portfolio that proves it.
Complete all modules, then submit the required number of capstone projects. Each must earn a passing rating from an admin reviewer.
For a real product you work on (or want to): write a complete PM dossier covering vision → problem → opportunity tree → spec → prioritization → launch plan → metrics. Single document, ~20 pages, written in real PM voice. The artifact you'd hand to a new PM joining your team or a hiring manager during an interview.
Run 8 customer interviews using The Mom Test method. Analyze. Surface 3 well-validated problems + 5 nope-not-real problems. Document the methodology, the interview notes, the synthesis, and the resulting Opportunity Solution Tree. Bonus: get a teammate to attend at least 2 interviews with you.
I'm taking a course on software product management. Topics: what PM is, customer discovery (Mom Test + JTBD + opportunity solution trees), product strategy (vision + OKRs + North Star), prioritization (RICE + Kano + saying no), specs (PRDs + RFCs + ADRs), cross-functional partnership, metrics + A/B testing, launch + GTM, stakeholder management, PM career. Help me apply each concept to my own product context. I'm at [APM/PM/Senior PM] level at a [stage] company in [domain].
Write a real PRD for something you'd actually want built. Run it past two engineers; iterate. Deliverable: v1 PRD, eng feedback, v2 PRD with diff. The v1 → v2 change is the learning. Plus 1 ADR for a related architecture decision.
Pick a public product launch (your own or a famous one — Apple Vision Pro, ChatGPT, anything with public data). Reconstruct what the PM team likely did. Score against the 9-section launch checklist. Write up where they nailed it + where they fumbled. Develop a launch-thinking muscle through structured imitation.
Document one shipped initiative end-to-end in the 6-section case-study format (context, problem, decisions, tradeoffs, outcome, learnings). ~5 pages. Sanitize for public sharing. This becomes part of your career-long PM portfolio.
The follow-up. About product orgs that work.