Business Roadmap
Product Manager
A product manager decides what gets built and why, and is accountable for whether it worked. The sequence is product fundamentals, then customer discovery, then prioritisation and roadmapping, then working with engineering through delivery, then metrics — and enough technical literacy to have a real conversation about trade-offs rather than relaying messages.
By the end: Take a customer problem through discovery, delivery and measured outcome.
The Product Manager Roadmap
Product Fundamentals~1 month
What the job is, and what it is not.
What a product manager actually does
Own the what and the why, and be accountable for the outcome. You have responsibility without authority — influence is the tool.
Product versus project management
Product owns the outcome, project owns the delivery. Conflating them is why so many PM job posts are confused.
The product lifecycle
Discovery, delivery, growth, maturity, sunset — each stage demands a different kind of decision.
Business fundamentals
Unit economics, margins and the business model. A PM who cannot read the P&L is guessing.
Working with engineering and design
Bring problems and constraints, not solutions and deadlines. Trust here is the whole job.
Customer Discovery~1 month
Find a problem worth solving before committing a team to solving it.
Customer interviews
Ask about what they did last time, not what they would like. Stated preference is unreliable.
Problem definition
Write the problem so precisely that a wrong solution is obviously wrong.
Market and competitor research
Where the product sits, who else is there, and what customers currently do instead.
Opportunity sizing
How many people, how often, how painful. This is what turns a good idea into a ranked one.
Validating before building
Prototypes, landing pages and concierge tests. The cheapest way to be wrong.
Prioritisation and Roadmapping~1 month
Deciding what not to build is most of the value you add.
Prioritisation frameworks
RICE, MoSCoW and the rest are structured arguments, not oracles. Use one, but own the call.
Writing requirements
User stories and acceptance criteria with the edge cases named. Ambiguity gets resolved by someone guessing.
Roadmapping
Communicate direction and confidence, not dates you cannot keep. A roadmap of promises destroys trust once.
Saying no
With a reason, and consistently. Every yes is a no to something else, whether or not you said it aloud.
Stakeholder management
Different audiences need different framings of the same decision. This is a skill, not politics.
Delivery~1 month
Get it built without becoming a ticket router.
Agile in practice
Standups, planning and retros as tools for a specific problem — not a ceremony to perform.
Backlog management
A groomed, ranked backlog with clear next items. An unmaintained backlog is a graveyard.
Scope and trade-offs
Cut scope, not quality or the deadline. Know what the minimum genuinely viable version is.
Working with technical constraints
Enough grasp of APIs, data and technical debt to push back on an estimate credibly.
Launch
Rollout plan, support readiness and a rollback. Launch day is a process, not an announcement.
Metrics and Growth~1 month
Find out whether it worked, honestly.
Choosing metrics
One primary metric tied to the outcome you claimed. Vanity metrics rise while the product fails.
Analytics
Funnels, cohorts and retention — enough to answer your own questions without queuing for an analyst.
SQL for product managers
Basic queries make you self-sufficient and much faster. A genuinely high-leverage week of learning.
Experimentation
A/B tests, sample size and the discipline not to peek at a running test.
Closing the loop
Report what happened, including when it did not work. This is how a PM earns future latitude.
Interview preparation
Product sense, analytics and behavioural rounds — all of which reward structured thinking out loud.
Frequently Asked Questions
Do product managers need a technical background?
Not a developer's, but enough to be useful. Understanding APIs, databases, what makes a change expensive and why technical debt matters lets you push back on an estimate credibly. PMs who cannot do this end up as ticket routers rather than decision makers.
How do people become product managers?
Mostly sideways — from engineering, design, support, marketing or analytics inside a company that already trusts them. Direct-entry APM programmes exist but are extremely competitive. The reliable route is to do product work in your current role until the title catches up.
What is the difference between a product manager and a project manager?
A product manager owns what to build and why, and is judged on the outcome. A project manager owns delivery — scope, schedule and coordination — and is judged on shipping as planned. The roles overlap in small teams, which is where the confusion comes from.
What metrics should a PM actually track?
Few, and tied to the outcome you claimed. Activation, retention and the specific behaviour your feature was meant to change beat a dashboard of everything. Vanity metrics — signups, page views, raw downloads — go up while the product fails, which is exactly why they are popular.