Beginner Product Manager
Everything you need to understand what product management actually is, the foundational skills, and how to operate effectively in your first PM role. Start here if you're new to PM, transitioning from another role, or want to refresh your fundamentals.
- βUnderstand the PM role, the different types of PMs, and what the job actually involves day-to-day
- βWrite crisp PRDs, run effective discovery, and ship features that actually get used
- βBuild credible relationships with engineering, design, sales, and leadership
- βDevelop the core skills hiring managers test for: prioritization, communication, influence, and judgment
- Skim the full concept list below β it's a curated progression, not a random pile.
- Pick any concept that's relevant to what you're working on right now and read it end-to-end (5-15 min each).
- Don't skip the interview questions at the bottom β they double as the best self-test.
- Follow the related concepts links to build the mental graph.
Curriculum (35)
π§What is Product Management
The role that owns the 'what' and 'why' of a product β and answers for its outcomes.
π§¬The Three Types of PMs
Builder, Tuner, and Innovator β knowing your archetype changes how you should be evaluated, hired, and grown.
πͺͺPM vs Program Manager (vs TPM, APM, GPM)
The titles get confused constantly. Here's what each one actually does β and how to read job descriptions correctly.
ποΈDelivery, Feature, and Product Teams
Three team archetypes β and your career depends on knowing which one you're actually on.
πThe History of Product Management
From P&G in 1931 to the AI PM of 2026 β a 90-year arc that explains why the role is what it is today.
π£οΈThe Languages of Product Management
Great PMs speak engineer, designer, marketer, and exec β fluently. Mediocre PMs speak only their native tongue.
πͺCore PM Skills
The five skill areas hiring managers actually filter on β and where to invest your practice time.
π A Day in the Life of a PM
Not glamorous, mostly meetings, lots of writing, and a few moments of real judgment that justify the salary.
πWriting PRDs (Product Requirement Docs)
The PRD isn't a spec β it's a tool for alignment. Modern PRDs are 1-2 pages, opinionated, and focused on the user problem.
π§ΎWriting Better Specs
Specs that ship: shorter, sharper, and structured around the questions engineers actually have.
πProduct Discovery Basics
Discovery is how you decide what to build before you waste a quarter building the wrong thing.
π€Customer Interviews β The Basics
The single highest-ROI activity in product management. Almost every PM is bad at it.
π§Knowing Your Users
Personas, JTBD, segments, and the disciplined practice of staying connected to the people you build for.
π§βπ€βπ§User Personas
Done right, personas are decision tools. Done wrong, they're laminated posters that no one references.
βοΈWireframes for PMs
Low-fidelity sketches that align the team faster than a long PRD ever could.
ποΈInformation Architecture
How content is structured, named, and findable. The unsexy layer that determines whether your product feels coherent or chaotic.
π¨Working with Design
The PM-designer relationship is the single most leveraged partnership for a PM. Get it right and the team flies.
βοΈWorking with Engineering
Engineers respect specifics, technical curiosity, and honesty about trade-offs. They lose patience with vagueness and changed minds.
π€Stakeholder Management
Half your job is managing people who don't report to you. Stakeholder management is the meta-skill that makes everything else possible.
πͺRunning Meetings
Most PM meetings are wasted. The fix isn't shorter meetings β it's clearer purpose, sharper structure, and the discipline to skip the meeting when an email would do.
π How to Say No
The most underrated PM skill. Done well, saying no makes you more respected, not less liked.
πThe LNO Framework
Shreyas Doshi's deceptively simple task-classification system: Leverage, Neutral, Overhead. Use it daily.
π―OKRs Basics
Objectives and Key Results β the goal-setting framework that almost every tech company uses and most use badly.
πͺPrioritization Frameworks
RICE, ICE, MoSCoW, Kano β the frameworks every PM has heard of, and the one that actually matters most.
πMetrics 101 for PMs
AARRR, funnels, leading vs lagging β the basic vocabulary of measuring a product. Master this in week 1.
βNorth Star Metrics
One number to align the company. Done right, it's a strategic lever. Done wrong, it's vanity.
π§ͺMVP β The Most Misused Term in Tech
The Minimum Viable Product was never 'a stripped-down v1.' It was a test of a specific hypothesis.
πStorytelling for PMs
The PM's superpower. People don't remember frameworks; they remember stories. Master narrative and you'll drive 10x more alignment.
πͺGiving and Receiving Feedback
The skill PMs use most often and practice least. Senior PMs make giving and receiving feedback a habit, not an event.
πThe Deadly Sins of PM
A cheat sheet of the failure modes that derail PM careers β most of which are completely avoidable.
πHow to Succeed as a PM in a Feature Factory
Most jobs are feature factories. Here's how to thrive β and how to gradually transform the team into a real product team.
πͺBecoming a PM (from scratch)
The most-asked question in PM Twitter. Here's the actual path β including the parts nobody talks about.
πTransition from Designer to PM
Designers have natural PM superpowers β and one big gap. Here's how to make the jump.
πIs an MBA Worth It for PM?
The clichΓ© says no; the data says it depends. Here's when the MBA path actually compounds.
π§How to Be Indistractable
Most PM days are stolen by Slack, meetings, and other people's urgencies. The ones who reclaim their time win.