Learn how to identify customer problems, define product strategy, prioritise opportunities, work with design and engineering teams, launch products and measure business outcomes. Build the strategic, analytical and execution skills required to become an industry-ready Product Manager.
A Product Manager is responsible for guiding a product towards business success by understanding customer needs, defining product direction, making prioritisation decisions and aligning cross-functional teams around measurable outcomes.
Research customer needs, behaviours, frustrations and unmet expectations. Identify the problems worth solving.
Set product vision, strategy, objectives and priorities that connect customer value with business goals.
Collaborate with engineering, design, marketing, sales and operations to deliver useful product experiences.
Monitor adoption, engagement, retention, revenue and customer satisfaction to guide continuous improvement.
These roles frequently collaborate, but their primary accountabilities differ.
| Dimension | Product Manager | Project Manager | Product Owner |
|---|---|---|---|
| Primary focus | Product value and outcomes | Project delivery and coordination | Maximising value delivered by the Scrum team |
| Key question | What should we build and why? | How will we deliver the project? | What should the team work on next? |
| Typical activities | Strategy, discovery, prioritisation and product performance | Timeline, resources, dependencies and risks | Product backlog, goals and backlog ordering |
| Typical deliverables | Vision, strategy, roadmap and product outcomes | Project plan, schedule and status reports | Product backlog and sprint-related decisions |
| Success measures | Customer value and business impact | Delivery against project constraints | Value of product increments |
In some organisations, one person may perform multiple responsibilities. The Product Owner is a defined accountability in Scrum; Product Manager is a broader organisational role.
Product Management is a continuous cycle. Teams revisit earlier decisions as customer feedback, market conditions and product data evolve.
Product vision, market positioning, business models and competitive strategy.
Customer research, interviews, personas, journey maps and usability.
Metrics, funnels, retention, experimentation and data interpretation.
Trade-offs, impact assessment, effort estimation and roadmap decisions.
Software development, APIs, databases, architecture and technical constraints.
Stakeholder alignment, negotiation, storytelling and decision-making.
Follow these stages to build a balanced foundation in business, customers, product strategy, technology and execution. Expand each stage to explore concepts, practical skills, tools and outcomes.
Mark each stage complete after you have practised its key concepts. Progress is saved in this browser.
Begin by understanding what a product is, how products create value and how Product Managers contribute across the product lifecycle.
Physical products, digital products, platforms, services and internal products.
Responsibilities, decision-making, accountability and cross-functional collaboration.
Introduction, growth, maturity, decline and continuous product evolution.
Focus on user problems, value creation, outcomes and long-term product health.
Understand the relationship between customer demand, product value and market adoption.
Distinguish ongoing product ownership from time-bound project delivery.
Product decisions must make sense for customers and the business. Learn how organisations generate revenue, compete and evaluate opportunities.
B2B, B2C, SaaS, marketplace, subscription, freemium and transaction-based models.
Subscriptions, licensing, advertising, commissions and one-time purchases.
Customer acquisition cost, lifetime value, gross margin and payback period.
Customer groups, target markets, ideal customer profiles and buyer personas.
Competitor positioning, strengths, weaknesses, pricing and differentiation.
TAM, SAM and SOM; market opportunity and demand estimation.
Strong products begin with a clear understanding of customers. Learn to discover problems instead of jumping directly to feature ideas.
Prepare questions, conduct interviews, probe for behaviour and capture insights.
Design questionnaires and collect structured customer feedback.
Represent meaningful user segments, motivations, behaviours and pain points.
Understand what users say, think, do and feel in a given context.
Understand the progress customers are trying to make in a particular situation.
Compare competitor experiences, feature gaps, pricing and positioning.
Map user touchpoints, friction, emotions and opportunities across a journey.
Check problem frequency, severity, willingness to solve and target audience fit.
Product strategy translates business direction and customer opportunities into a coherent set of choices about where to compete and how the product will win.
Describe the future state and the value the product aims to create.
Define the product's purpose and the customers it serves.
Define target users, differentiation, value proposition and strategic choices.
Communicate how the product is distinct from alternatives in the market.
Set Objectives and measurable Key Results to align teams around outcomes.
Identify a key measure that represents delivered customer value.
Product discovery reduces the risk of building something customers do not need. Learn to explore opportunities, test assumptions and validate solutions with evidence.
Convert research findings into customer problems and product opportunities.
State assumptions about user behaviour, product value and expected outcomes.
Empathise, define, ideate, prototype and test potential solutions.
Connect desired outcomes with opportunities, solutions and experiments.
Build low-fidelity and high-fidelity representations of product experiences.
Define the smallest useful product or experiment to test key assumptions.
Define hypotheses, success metrics, test groups and decision criteria.
Usability testing, landing-page tests, fake-door tests and concierge experiments.
Product teams always have more ideas than available capacity. Learn to evaluate opportunities, make trade-offs and communicate a clear product roadmap.
Prioritise using Reach, Impact, Confidence and Effort.
Evaluate ideas through Impact, Confidence and Ease.
Classify requirements as Must, Should, Could and Won't have for now.
Understand basic, performance and delight attributes in customer satisfaction.
Compare potential customer or business value against implementation effort.
Communicate priorities, strategic themes, dependencies and intended outcomes.
Organise opportunities, initiatives, epics, features and user stories.
Balance impact, urgency, cost, risk, dependencies and strategic alignment.
Use a consistent scoring scale and time period. The score is a decision aid, not a replacement for product judgement or strategic context.
Product Managers do not need to become professional designers, but they should understand user experience principles and collaborate effectively with design teams.
Usability, accessibility, information architecture and interaction design.
Visual hierarchy, typography, colour, spacing and interface consistency.
Map the steps users take to complete important product tasks.
Create low-fidelity layouts to explore structure and content.
Build clickable prototypes to test user interactions and flows.
Observe users, identify friction and evaluate task completion.
Understand inclusive design, contrast, keyboard navigation and accessibility needs.
Understand reusable components, patterns and design consistency.
Product Managers should understand enough technology to evaluate feasibility, discuss trade-offs and make informed product decisions. Deep programming expertise is not required for every PM role.
Requirements, design, development, testing, deployment and maintenance.
Understand client-side interfaces, server-side logic and application layers.
REST APIs, requests, responses, authentication and third-party integrations.
Relational databases, tables, records, relationships and data storage.
Understand cloud hosting, scalability, availability and deployment concepts.
Understand engineering compromises and their long-term product impact.
Learn basic authentication, authorisation, privacy and data protection concepts.
Balance performance, scalability, cost, reliability and delivery speed.
Product Managers collaborate with engineering and design teams throughout delivery. Learn the principles and workflows used to build, test and release products iteratively.
Iterative delivery, feedback loops, adaptive planning and collaboration.
Accountabilities, events, artefacts, sprint goals and product increments.
Define features from the user's perspective and communicate their value.
Specify testable conditions for feature completion and validation.
Clarify, split, estimate and prioritise upcoming work.
Align the team on sprint goals and selected work.
Visualise workflow, limit work in progress and improve flow.
Coordinate releases, dependencies, testing, rollout and communication.
Product analytics helps teams understand how users discover, adopt and engage with products. Learn to connect user behaviour with product and business outcomes.
Define adoption, engagement, conversion, retention and revenue measures.
Understand how users arrive and experience their first meaningful value.
Sessions, feature usage, frequency, depth and meaningful activity.
Measure returning users, customer retention and cancellation behaviour.
Identify conversion and drop-off across key user journeys.
Compare user groups over time based on shared characteristics or behaviour.
Design controlled experiments and interpret outcomes carefully.
Build and interpret reports that connect metrics with product decisions.
Building a product is only part of the job. Learn how to position, launch, communicate and grow a product with the support of marketing, sales, operations and customer success teams.
Define target customers, positioning, channels and launch objectives.
Communicate product differentiation and customer value.
Understand cost-based, value-based, competitive and subscription pricing.
Coordinate launch readiness, release communications and operational dependencies.
Prepare product messaging, demonstrations, FAQs and sales material.
Support onboarding, adoption, satisfaction and ongoing customer value.
Explore acquisition, activation, retention, referral and monetisation opportunities.
Measure launch performance against adoption, conversion and revenue goals.
A strong Product Manager portfolio demonstrates how you think, make decisions, prioritise trade-offs and measure outcomes. It should show your reasoning, not just polished screens.
Analyse existing products and propose improvements backed by evidence.
Show product vision, positioning, objectives and strategic choices.
Present research plans, interview insights, personas and opportunity maps.
Show prioritisation, trade-offs, user stories and roadmap decisions.
Present metrics, hypotheses, experiment design and outcome interpretation.
Practise product sense, strategy, execution, analytics and behavioural questions.
No roadmap stages match your search.
Product Managers work across research, design, delivery, analytics and communication tools. Learn the tools that match your target role and product environment.
| Tool / Category | Primary Purpose | Priority | What to Learn |
|---|---|---|---|
| Jira | Product backlog and Agile delivery | Highly useful | Epics, stories, boards, workflows and sprint planning |
| Confluence | Product documentation | Highly useful | PRDs, decision logs, specifications and team knowledge |
| Figma | Design collaboration and prototyping | Highly useful | Wireframes, prototypes, user flows and design feedback |
| Miro / FigJam | Discovery and collaborative workshops | Useful | Journey maps, brainstorming and opportunity mapping |
| Productboard | Product discovery and prioritisation | Role-dependent | Customer feedback, idea scoring and roadmaps |
| Amplitude | Product analytics | Role-dependent | Funnels, retention, cohorts and behavioural analysis |
| Mixpanel | Product usage analytics | Role-dependent | Events, user journeys, conversion and engagement |
| Google Analytics | Digital product and web analytics | Useful | Acquisition, traffic, events and conversion |
| SQL | Direct product data analysis | Strong advantage | Filtering, joins, aggregations and cohort queries |
| Postman | API exploration and testing | Technical PM advantage | Requests, responses, headers and authentication |
| Excel / Google Sheets | Analysis and prioritisation | Essential | Formulas, scoring models, charts and business cases |
| Power BI / Tableau | Business intelligence and dashboards | Role-dependent | Metrics, visualisation and reporting |
Frameworks provide structure for decisions. They should support product judgement, not replace customer understanding or evidence.
| Framework | Purpose | When to Use |
|---|---|---|
| RICE | Feature prioritisation | Compare opportunities using reach, impact, confidence and effort. |
| ICE | Idea scoring | Quickly compare ideas using impact, confidence and ease. |
| Kano Model | Customer satisfaction | Understand basic, performance and delight product attributes. |
| MoSCoW | Requirement prioritisation | Separate essential requirements from lower-priority scope. |
| Jobs to Be Done | Customer understanding | Understand the progress customers want to make. |
| Design Thinking | Problem and solution exploration | Explore customer problems and test possible solutions. |
| Opportunity Solution Tree | Product discovery | Connect desired outcomes to opportunities and experiments. |
| North Star Framework | Product measurement | Align teams around a meaningful measure of customer value. |
| OKRs | Goal setting | Align product objectives with measurable results. |
| AARRR | Growth analysis | Understand acquisition, activation, retention, referral and revenue. |
Build projects that demonstrate product thinking, customer research, strategy, prioritisation, design collaboration and analytical decision-making.
Analyse a food delivery app's onboarding, search, checkout and order tracking experience.
Identify friction in an online shopping journey and recommend product improvements.
Research a target market and create evidence-based personas for a digital product.
Identify onboarding friction and design a simpler first-time user experience.
Compare competing products, positioning, pricing and customer segments.
Create a Now–Next–Later roadmap based on user problems and strategic goals.
Build a scoring model to compare product opportunities and explain trade-offs.
Prepare a PRD for a new feature with goals, scope, requirements and acceptance criteria.
Compare pricing tiers and evaluate revenue, conversion and customer value implications.
Track activation, engagement, retention and conversion for a sample digital product.
Design an experiment to compare two onboarding or checkout experiences.
Define a new banking feature with research, user flows, requirements and a prototype.
Investigate churn patterns and propose product interventions to improve retention.
Develop a launch plan covering positioning, target audience, pricing and channels.
Take a product opportunity from discovery and strategy through design, delivery, launch and measurement.
Understand how the different skills connect through one practical product scenario.
An online learning platform has strong new-user registrations, but many learners stop using the platform within the first two weeks. The business wants to improve learner engagement and subscription retention.
| Stage | Product Manager Activity | Expected Output |
|---|---|---|
| Problem discovery | Interview learners and analyse usage behaviour. | Problem statement and research insights |
| Opportunity analysis | Identify where learners lose motivation or encounter friction. | Opportunity map and journey analysis |
| Strategy | Define the retention objective and target learner segment. | Product objective and success metrics |
| Prioritisation | Compare potential improvements by impact, confidence and effort. | Prioritised product opportunities |
| Solution design | Explore learning reminders, progress indicators and personalised plans. | Wireframes and prototype |
| Delivery | Collaborate with engineering and design teams on implementation. | Stories, acceptance criteria and release plan |
| Launch | Roll out the feature to a selected learner segment. | Launch and communication plan |
| Evaluation | Compare retention and engagement against the baseline. | Product performance report |
Percentage of new users who complete a meaningful first learning action.
Number of learners who engage with the platform during a week.
Percentage of a user cohort that returns in the fourth week.
Product Management offers multiple specialisations. Your direction can depend on your technical background, industry knowledge and strengths.
Supports discovery, requirements, product analysis and delivery activities.
Owns product outcomes, strategy, prioritisation and cross-functional alignment.
Works closely with engineering on APIs, platforms, infrastructure and technical products.
Focuses on acquisition, activation, conversion, retention and monetisation.
Manages data platforms, analytics products, data capabilities and related experiences.
Builds internal platforms and capabilities used by other product and engineering teams.
Leads complex product areas and drives strategic decisions across teams.
Oversees multiple product areas and supports product managers.
Leads product strategy, organisational capability and portfolio-level outcomes.
This is an illustrative schedule for a learner studying consistently alongside practical assignments. Adjust the pace according to your background and target role.
| Weeks | Focus Area | Learning Outcome |
|---|---|---|
| 1–2 | Product fundamentals and business models | Understand product roles, lifecycle, business models and market basics. |
| 3–4 | Market research and customer discovery | Conduct interviews and identify validated customer problems. |
| 5–6 | Product vision, strategy and discovery | Define product direction, objectives and solution hypotheses. |
| 7–8 | Prioritisation and roadmapping | Use RICE and create a product roadmap. |
| 9–10 | UX, technical fundamentals and PRDs | Create wireframes, requirements and delivery-ready documentation. |
| 11–12 | Agile and product delivery | Manage a backlog and understand release workflows. |
| 13–14 | Product analytics and go-to-market | Define metrics, experiments and a launch plan. |
| 15–16 | Capstone, portfolio and interviews | Present an end-to-end product case study. |
Estimate how long your learning plan may take based on your weekly study commitment.
Evaluate whether you can apply the skills independently. A completed checklist should reflect practical experience, not just familiarity with terminology.
Attempt these questions to check your understanding of core Product Management concepts.
Product interviews often assess structured thinking, customer empathy, strategic judgement, analytical ability and communication.
| Term | Meaning |
|---|---|
| PM | Product Manager or Product Management, depending on context. |
| PMF | Product-Market Fit. |
| MVP | Minimum Viable Product. |
| PRD | Product Requirements Document. |
| OKR | Objectives and Key Results. |
| KPI | Key Performance Indicator. |
| DAU | Daily Active Users. |
| MAU | Monthly Active Users. |
| CAC | Customer Acquisition Cost. |
| LTV / CLV | Lifetime Value or Customer Lifetime Value. |
| ARPU | Average Revenue Per User. |
| RICE | Reach, Impact, Confidence and Effort. |
| GTM | Go-to-Market. |
| JTBD | Jobs to Be Done. |
| UX | User Experience. |
| UI | User Interface. |
| PO | Product Owner. |
| ARR | Annual Recurring Revenue. |
| MRR | Monthly Recurring Revenue. |
| Churn | The rate at which customers or users stop using or subscribing to a product. |
| PRD | Product Requirements Document. |
Yes. Product Management is a cross-functional role, and many Product Managers come from business, design, consulting, analytics and customer-facing backgrounds. You should still understand basic software development concepts and technical trade-offs.
Coding is not mandatory for most general Product Manager roles. However, understanding APIs, databases, software architecture and development workflows helps you collaborate with engineering teams. SQL is a useful additional skill for data-driven roles.
Product Manager is generally a broader role focused on product direction, customer value and business outcomes. Product Owner is a defined accountability in Scrum focused on maximising product value, including effective Product Backlog management.
No. An MBA can be useful for some business and strategy roles, but it is not a universal requirement. Product knowledge, customer understanding, analytical ability and evidence of execution are also important.
Start with Excel or Google Sheets, Jira, Confluence and Figma. Then explore product analytics tools such as Amplitude or Mixpanel. Learn SQL if your target roles involve data-intensive product decisions.
A prototype is used to explore or test a design or concept. An MVP is a minimum product or experiment designed to test important assumptions and deliver enough value to learn from real use. The exact form of an MVP depends on the product context.
Start with two or three well-documented projects. Show your research, problem definition, prioritisation, product decisions, design collaboration and measurement approach. Depth and reasoning matter more than the number of projects.
Product Managers work in SaaS, fintech, banking, e-commerce, healthcare, education technology, logistics, telecom, media, enterprise software and many other sectors.
You can specialise in technical product management, growth product management, data products, platform products, AI product management or product leadership.
Explore these resources to deepen your knowledge of product discovery, strategy, roadmapping, Agile delivery and product analytics.
Explore product discovery, prioritisation, roadmapping and product delivery practices.
Explore Product Management Handbook →Learn about continuous discovery, customer feedback and opportunity prioritisation.
Explore Product Discovery →Understand Scrum accountabilities, events, artefacts and the framework.
Read the Scrum Guide →Explore product management practices, strategy and disciplined Agile concepts.
Explore Product Management Practices →Explore product discovery, delivery, business acumen and product management competencies.
Explore GitLab PM Resources →Explore product discovery, roadmapping and prioritisation guides.
Explore Productboard Resources →Learn how to understand user acquisition, engagement and digital product performance.
Explore Analytics Help →Develop familiarity with interface design, prototyping and collaborative design workflows.
Explore Figma Resources →Explore related roadmaps to build complementary business, analytical and technical skills.
Explore data science, statistics, Python and machine learning.
Explore Roadmap →Explore AI engineering, machine learning systems and deployment.
Explore Roadmap →Explore requirements, business processes, SQL, Excel and business intelligence.
Explore Roadmap →More roadmaps from the edSlash series can be added here as their pages are published.
© 2021 edSlash. All Rights Reserved.
