Product Management
A product manager is responsible for deciding what a product team builds and why they’re building it. They are the intermediary between users, the business, and the engineering team. Product management is one of the harder roles to break into without prior experience. Most PMs come from adjacent roles such as software engineering, design, customer success, or data analysis. This path focuses on building the skills that transfer.
The job in practice
A product manager talks to users to understand their problems, works with data to understand what is happening in the product, writes documents that define what should be built and why, and works with an engineering and design team to build and ship it. After it’s been shipped, they measure whether it worked and what needs to change. The role is not about having creative ideas, and instead it is about making decisions based on evidence.
What it is not
Product managers do not manage engineers. As the name suggests, they manage the product itself. They have no direct authority over the team and instead they earn influence through the quality of their thinking and the clarity of their communication. They are also not project managers, although they often end up doing project management work. The core of the job is deciding what to build, not tracking whether it is getting done on time.
Why talking to users is a skill
Asking users about a product is always mired in difficulties. When asked ‘would you use this’, users are prone to say yes to avoid awkwardness or conflict. When asked what features they want, users often describe solutions rather than problems they’ve experienced that could be solved by your decision-making around the product. Good user research is interested in past behaviour, not imagining future behaviour. It also looks for patterns across multiple conversations and pieces of research, not focusing on individual opinions.
How to practise
Pick a product you use and interview five people who also use it. Without projecting your own answers, ask them to walk you through the last time they used it, trying to find out what frustrated them and what they were trying to accomplish. Synthesise the five interviews into three to five common themes that broadly cover the feedback the users gave. This is the skill loop that experienced PMs use throughout their careers.
What a product spec is for
A product requirements document (PRD), also known as a product spec, is a written description of a problem, who has it, why it matters, what success looks like, and what constraints exist. It is not a list of features of the product. Good PRDs can be read by engineers, designers, and stakeholders, and they provide enough context for the team to make good decisions without the PM in the room.
The most important section
What constitutes success? And how do you measure it? This is the most important piece of information when writing a PRD or product spec. ‘Users can find what they are looking for faster’ is not a good success metric. ‘Median time-to-first-search-result-click decreases from 45 seconds to 30 seconds within 30 days of launch’ is a good success metric. If you can’t define what success looks like and how that will be measured, you do not yet understand the problem well enough to write a spec.
Why prioritisation is hard
It’s likely that there will always be more potential work than the team can do. Prioritisation is the job of deciding what to do first, which inevitably means deciding that some things can’t get done at all. Most PM interviews involve a prioritisation question, since most PM failures involve poor decisions around prioritisation. The framework matters less than the ability to be explicit about trade-offs and make a defensible case. Communication is a really key skill here.
Frameworks worth knowing
ICE (Impact, Confidence, Effort) is a lightweight scoring model useful for making quick decisions, while RICE adds Reach to the calculation. The opportunity scoring framework focuses on how important a problem is versus how well the existing product solves it. The most important thing is to be explicit about what you are optimising for and how these decisions are being made. Prioritisation that cannot be explained is just gut feeling with extra steps.
The relationship that determines how fast you ship
Delivery speed and quality are highly dependent on the relationship between a product manager and the engineering team. Engineers need to understand the problem they are solving, not just the specification. They should be involved early enough to flag when a proposed solution is ten times harder than an alternative that achieves the same outcome. A PM who hands over a spec and disappears creates more work further down the line, whereas a PM who is available, clear, and decisive enables fast teams.
What engineers respect
Engineers value clarity about what matters and what is flexible, and that any decisions made are communicated quickly. A product manager who’s willing to change the plan when an engineer finds a better way to solve the problem will have more career longevity than one who’s committed to their own insights at all costs. Engineers want to see accurate scoping and no last-minute scope creep. Product managers should know enough about how software is built to know when a request is straightforward versus when it requires significant architectural change.
Why data fluency is now a core PM skill
Stakeholders and intuition used to be the driving force behind decision making. Now, data-informed product management uses instrumentation, dashboards, and experiments to distinguish between things that feel true and things that are true. PMs who can write SQL queries, interpret A/B test results, and build their own dashboards are significantly more effective than those who rely entirely on data analysts.
What to learn
Most product analytics in practice fall into three categories: conversion, retention and testing. Make sure you understand conversion funnels: where are users dropping off between first visit and completing the core action? Understand retention: what percentage of users return after their first week? Learn what an A/B test is, how to determine if a result is statistically significant, and what sample size you need before you start.
