Frame the problem
Separate a requested feature from the underlying user or business problem before committing to a solution.
Beginner · self-paced · free course
Product Management Foundations
Build the mental model behind product decisions: understand users and markets, choose problems and bets, reduce uncertainty, shape solutions with specialists, measure outcomes, launch, and learn what to do next.
15 connected modules450 published learning unitsNo prior PM title requiredReal lesson preview below
This course builds broad PM capability. It does not provide an accredited credential, guarantee a Product Manager job, or replace real product experience.
Is Foundations your gap?
Start here when the missing piece is product judgment itself
Foundations is useful when you know some PM words but cannot yet connect evidence, choices, trade-offs, delivery, and measurement into one reasoning system. Different learners enter for different reasons.
Aspiring PM
Build the discipline before optimizing a resume or memorizing interview frameworks.
New PM
Connect scattered tactics into a coherent way to choose, explain, and revisit product decisions.
Designer or engineer
Understand the product-decision layer around specialist work without pretending you need to become a PM.
Builder or founder
Add discipline around users, uncertainty, scope, metrics, and learning instead of shipping from instinct alone.
It may not be your next step if…
- • You already reason confidently across these fundamentals and need specialist depth: use the Product Discovery course.
- • Your main bottleneck is proving existing capability in a job search: use Land Your First Product Role.
- • You are unsure what to learn across the broader PM ecosystem: use the Product Management Learning Path.
Foundations map
Product Management is a chain of decisions, not a pile of artifacts
The modules form one loop: understand reality, choose what matters, shape the solution with specialists, steer with evidence, then learn from what actually happens. A PRD, roadmap, experiment, or dashboard is useful only when it improves one of those decisions.
1. Understand the context
Who are we creating value for, and what is the PM accountable for?
Build a reality-based view of the role, the user, the market, and the boundaries of Product Management before choosing solutions.
2. Choose what matters
Which problem, opportunity, or bet deserves scarce product capacity?
Connect vision, discovery, validation, and strategic trade-offs so a plausible idea becomes an evidence-backed choice.
3. Shape with specialists
How should the solution be shaped with Design, Engineering, and stakeholders?
Understand usability, technical constraints, collaboration, and influence well enough to make better trade-offs without replacing specialist expertise.
4. Steer with evidence
How will we know whether direction and delivery are producing the intended outcome?
Use metrics as evidence and roadmaps as communication tools, not as substitutes for judgment or fixed feature contracts.
5. Launch, learn, and iterate
What should change after the product meets real users and the market?
Treat launch as the start of a learning loop: collect feedback, observe behavior, update assumptions, and choose the next iteration deliberately.
Learning transformation
What you should become better able to do
Knowing a framework name is not the same as applying it. The course repeatedly moves from vocabulary toward contextual reasoning: know the concept, apply it to evidence, make a choice, then identify what would change that choice.
Choose evidence
Match the evidence you gather to the uncertainty you are trying to reduce instead of collecting research by habit.
Compare product bets
Explain why one opportunity should win when impact, confidence, effort, timing, and strategic fit pull in different directions.
Narrow the solution
Reason about validation and MVP scope before treating the full imagined feature set as the starting point.
Define useful signals
Distinguish outcomes from outputs and interpret product metrics with enough context to avoid reacting to vanity numbers or measurement noise.
Work across functions
Collaborate with Design, Engineering, GTM, and stakeholders while respecting where specialist decisions belong.
Explain direction
Use strategy and roadmaps to communicate choices, assumptions, and trade-offs rather than presenting a feature list as certainty.
Learn after launch
Turn launch signals, feedback, and observed behavior into the next hypothesis or product decision.
Know
I can explain what an MVP or outcome metric means.
Apply
I can use the concept in a concrete product situation.
Decide
I can justify one option despite imperfect information.
Reflect
I can name the evidence that would change my decision.
Learn before you decide to continue
The preview below is pulled from the published first lesson, What product management is (and isn't). It starts with the course's core distinction: Product Management is about maximizing user and business value through decisions, not merely managing tasks.
Real CraftUp lesson
What product management is (and isn't)
Try the quiz questions taken directly from the published CraftUp lesson for this module.
Quick practiceThe guide continues below
Want another challenge? Practice another round.
Real CraftUp curriculum · no sign-up required
Try the reasoning
Exercise: a request is not yet a product decision
Scenario
A customer says: “Add CSV export. We need it this sprint.”Twelve mid-market customers have mentioned reporting handoffs; four currently copy data manually into a weekly report, and one says the workflow is painful enough to reconsider the product.
- 1. What underlying problem might the request be pointing to?
- 2. What evidence would you gather before choosing CSV export as the solution?
- 3. What would you refuse to commit to yet?
Compare your reasoning
Problem: the evidence points to a reporting or data-handoff problem, not yet to “missing CSV” as the problem. The requested format is one proposed solution.
Next evidence: inspect the current workflow, frequency, recipients, downstream tools, failure cost, and why customers chose manual copying. Then test whether CSV, an API, scheduled reports, or a narrower workflow change solves the important part with less cost or risk.
Do not commit yet: a specific feature, sprint, or architecture. First reduce uncertainty about the problem and the smallest useful response; then bring feasibility and opportunity-cost trade-offs into the decision.
Artifact: a one-page product decision note
The output is not a template for template's sake. It makes the reasoning inspectable so another person can challenge the evidence, trade-off, or success condition.
Decision: Investigate reporting handoff before committing to CSV export
User/problem evidence: 12 mentions; 4 manual weekly workarounds; 1 churn signal
Outcome sought: Reduce recurring reporting effort and failure risk
Options: CSV export / scheduled report / API / workflow change
Biggest uncertainty: Which downstream job and tool actually create the pain?
Next evidence: Observe 5 workflows + quantify frequency/cost
Guardrail: Do not create a brittle export path that increases support or data risk
Reusable blank structure
Decision:
User/problem evidence:
Outcome sought:
Options and trade-offs:
Biggest uncertainty:
Next evidence:
Success signal:
Guardrail:
Full curriculum
See the learning job of every module before you start
The current curriculum contains 15 connected modules and 450 published learning units (30 per module). The sequence is intentional; the inventory is depth to navigate, not a score to complete as quickly as possible.
1. Understand the context
Introduction to Product Management
What is a PM actually responsible for, what is outside the role, and how does product judgment differ from task coordination?
Representative lessons
- • What product management is (and isn't)
- • Product management vs adjacent roles
- • The product lifecycle overview
- • How to structure your day as a product manager
Understanding Users and Markets
Whose problem are you solving, how do people solve it today, and what market context should change your assumptions?
Representative lessons
- • Why user & market understanding matters
- • The difference between user needs and wants
- • How to calculate TAM, SAM, and SOM for market sizing
- • Understanding competitor types
2. Choose what matters
Product Vision and Strategy
What future are you trying to create, and which choices move the product toward it instead of creating a feature factory?
Representative lessons
- • Why vision matters
- • Mission vs vision vs strategy vs tactics
- • What makes a strong product vision
- • Examples of great product visions
Opportunity Discovery and Ideation
Which problem or opportunity deserves exploration before a team commits to delivery?
Representative lessons
- • Discovery vs delivery: two sides of product development
- • The cost of building the wrong thing
- • What makes a good product opportunity
- • Where opportunities come from
Validation and MVPs
Which assumptions are risky enough to test first, and how can you reduce uncertainty before building the full solution?
Representative lessons
- • Why validation matters
- • What validation means in product management
- • Different types of assumptions
- • Qualitative vs quantitative validation
Strategic Decision-Making for PMs
How do you choose when evidence is incomplete, trade-offs conflict, and every option has an opportunity cost?
Representative lessons
- • Why PMs need to think strategically (even at junior level)
- • The link between company goals and day-to-day product choices
- • What are product bets?
- • Why prioritization is strategy in action
3. Shape with specialists
UX Fundamentals and Prototyping
How can users actually access the product's value, and what should a PM understand without trying to replace Design?
Representative lessons
- • Why UX matters for product managers
- • PM's role in UX
- • Core principles of UX design
- • Usability heuristics: Nielsen's 10 principles
Working with Engineering and Technology Basics
Which technical constraints and trade-offs should shape the product decision without turning the PM into the engineer?
Representative lessons
- • Why PMs need technical literacy
- • PM's role with engineering
- • Understanding the software development lifecycle
- • Frontend vs backend vs infrastructure
Principles of Effective Collaboration (Avoiding Process Pitfalls)
How do Product, Design, and Engineering make decisions together without mistaking process for progress?
Representative lessons
- • Why working principles matter
- • The myth of 'Process First'
- • Collaboration over ceremony
- • Building shared understanding of goals
Stakeholder Management and Communication
How do you create alignment across different incentives and constraints when you do not have direct authority?
Representative lessons
- • Why stakeholder management matters
- • Who are stakeholders?
- • Internal vs external stakeholders
- • The product manager as a bridge
4. Steer with evidence
Metrics, Analytics, and Data Literacy
Which numbers represent meaningful evidence, which are noise, and what should you investigate before reacting?
Representative lessons
- • Why data literacy is a core PM skill
- • The role of data in product management
- • Qualitative vs quantitative data
- • Leading vs lagging indicators in product management
Building and Communicating Effective Roadmaps
How do you communicate direction and trade-offs without turning a roadmap into a list of promises?
Representative lessons
- • Why roadmaps exist
- • Understanding roadmaps vs backlogs
- • roadmap as a communication tool
- • Time-based vs outcome-based roadmaps
5. Launch, learn, and iterate
Product Launch and Go-to-Market
How do you coordinate a launch as a multi-team process and preserve space to learn after release?
Representative lessons
- • What a product launch really is
- • Why go-to-market matters for product managers
- • Types of product launches
- • Internal alignment before launch
Customer Feedback and Continuous Discovery
How do you keep product decisions connected to changing customer reality instead of relying on one-off research?
Representative lessons
- • Why continuous discovery matters
- • The PM's responsibility for feedback loops
- • Types of feedback sources
- • Active vs passive feedback
Product Iteration and Growth Loops
How do you turn post-launch behavior and feedback into the next decision rather than simply shipping more features?
Representative lessons
- • Why iteration is the real work of PMs
- • Iteration vs pivot: understanding the difference
- • The build-measure-learn loop
- • Continuous vs episodic iteration
Course truth
What the lesson count means-and what it does not
The current Foundations product contains 15 modules and 450 published learning units. The course is structured in sequence, and module pages let you inspect the lesson inventory and try a real published lesson.
The count is not a claim that more lessons make the course better, and it is not a professional qualification. Use the arc map to understand the discipline first; use individual lessons to practice the decisions you are weakest at.
Current product data marks the Foundations lessons as non-premium. The public web experience exposes the curriculum and a real lesson preview; the complete interactive course experience continues in CraftUp.
Choose the right next step
Foundations is one route, not the answer for every visitor
Foundations is my gap
Preview the first module and begin with the PM decision model.
Start Foundations →I already know the basics
Diagnose which PM capability deserves deeper practice instead of repeating broad fundamentals.
Use the PM Skills diagnostic →My real problem is getting hired
Work on evidence, positioning, applications, networking, and interviews rather than relearning the whole foundation.
Go to the career course →I do not know what to learn next
Use the Learning Path to sequence courses, resources, skills, and practice across the broader ecosystem.
Open the Learning Path →Frequently asked questions
Who should start with Product Management Foundations?
Start here when your main gap is Product Management judgment itself: connecting users and markets, strategy, discovery, validation, cross-functional work, metrics, roadmaps, launch, and iteration into one decision system.
Do I need prior Product Management experience?
No. Foundations is a Beginner course and starts with what Product Management is and is not before moving through user and market understanding, strategy, discovery, delivery collaboration, measurement, launch, and iteration.
Do I need to complete all 450 lessons before the course is useful?
No lesson count is a professional milestone. The current curriculum contains 15 ordered modules with 30 short learning units each. Use the sequence to build the mental model, then use individual lessons to strengthen the decisions you are weakest at.
Is Product Management Foundations free?
Current CraftUp product data marks all 450 Foundations lessons as published and non-premium. The public web page exposes the curriculum and a real published lesson preview; the complete interactive course experience continues in CraftUp.
Does this course provide an accredited Product Management certification?
No. Foundations is a learning course, not an accredited credential, and course completion is not equivalent to professional Product Management experience.
How is this different from Land Your First Product Role?
Foundations builds the underlying Product Management capability. Land Your First Product Role focuses on packaging real evidence, applications, networking, and interview execution when the capability base is already strong enough.
What should I do after Foundations?
Use the gap you uncover to choose the next step: deepen a specialist area such as Product Discovery, use the PM Skills diagnostic, follow the broader Product Management Learning Path, or move into career preparation if hiring execution is now the bottleneck.
Download App
Ready to become a better product manager?
Build your product skills with short, practical lessons you can fit around your day.
Start with our free courses and upgrade anytime.
