Product Management for Beginners: Where to Start

If you are completely new to product management — you have heard the term, you are curious, but you are not sure what the job actually involves or how to get into it — this guide is for you. It covers everything from the basics of what PM is, to the specific steps to take in your first 90 days of learning.

What Product Management Actually Is

A product manager is responsible for defining what a software product should do, and why. The PM is the person who answers: Which user problems should we solve next? How do we know a solution is working? What should we build in the next quarter, and why in that order? The PM is not a manager of other people — most PMs manage no direct reports. They are a manager of the product itself — responsible for its direction, priorities, and outcomes. Every time you use an app and think "this is well-designed — it actually solves my problem" or "why does this work this way? It's so frustrating," you are having a PM-relevant thought.

A Day in the Life of a PM

A typical mid-level product manager's day: morning — responding to Slack messages and reviewing sprint progress. Mid-morning — a user interview or user research session. Afternoon — sprint planning or a design review. Later — writing a PRD or pulling data to investigate a metric that looks off. The PM role spans strategy (where is the product going?) and execution (what is being built this sprint and why?) simultaneously. No two days are identical. The role is diverse, ambiguous, and requires shifting between very different types of thinking within a single day.

What Skills You Actually Need

You do not need coding skills, design skills, or an MBA. You do need: User research skills — the ability to run structured conversations with real users and extract genuine insight about their problems. Analytical thinking — the ability to look at data and draw the right conclusions, including knowing when the data is insufficient to draw any conclusion. Written communication — PRDs, strategy documents, and user stories are the PM's primary output. Clear writing is non-negotiable. Product thinking — the habit of always asking why a product decision was made, what user problem it is solving, and whether there is a better solution. Curiosity — PMs who are not genuinely curious about users, markets, and technology plateau early.

Your First 90 Days of PM Learning

Days 1–30: Read two books — "Inspired" by Marty Cagan (what great PM looks like) and "The Mom Test" by Rob Fitzpatrick (how to run user interviews). Do 3 product teardowns of apps you use. Write them up as 300-word structured analyses focusing on user problems and product decisions. Days 31–60: Run 5 real user interviews on any product or service. Your goal is to surface one genuine user problem you did not expect going in. Start learning SQL — Mode Analytics has a free interactive tutorial. Complete the intro course. Days 61–90: Write your first PM case study: pick a product, identify a problem through user interviews, propose and justify a solution, define what success would look like. Publish it on Notion or Medium. This is your first portfolio piece. Start researching PM courses and community — join Product Folks, GrowthX, or Lenny's Newsletter to get into the product management community.

How to Get Your First PM Role

The honest path to your first PM role has three elements: A portfolio. Two strong case studies demonstrating the full PM process. No portfolio means no credible PM candidacy for most companies. Domain credibility. Your work experience in any field is an asset — target PM roles at companies working in that domain. A 3-year finance professional applying to a fintech PM role is a stronger candidate than a generic applicant with no domain context. Network. 60% of PM roles in India are filled through referrals. Join PM communities, attend product meetups (Product Geeks, Product Folks events), and build genuine relationships with active PMs — not just to get referrals, but because the conversations themselves accelerate learning.