Intermediate–Advanced 6 topic areas 53+ exercises

Product Manager (IT)

Product managers in tech must communicate with engineers, designers, executives, customers, and sales teams — often on the same day. This demands precision: a vague user story wastes a sprint, and an unclear PRD ships the wrong feature. This path builds the vocabulary and written communication patterns to write crisp product requirements, present roadmaps confidently, run effective discovery conversations, and align diverse stakeholders around a shared direction.

Topics covered

  • PRD writing
  • user story language
  • roadmap communication
  • stakeholder management
  • OKR writing
  • product discovery

Vocabulary spotlight

4 terms every Product Manager (IT) should know in English:

PRD n.

Product Requirements Document — a document that describes the purpose, features, and constraints of a product or feature to be built

"Before the sprint planning, the PM circulated a PRD so the engineers could estimate the work."
roadmap n.

A high-level plan showing what a product team intends to build and when, aligned with strategic goals

"The roadmap shows three themes for this quarter, but the sequence can still shift based on discovery."
OKR n.

Objectives and Key Results — a goal-setting framework that pairs a qualitative objective with measurable outcomes

"Our OKR for Q3 is to improve activation — the key result is getting 60% of new signups to their first value event within 24 hours."
RICE score n.

A prioritisation framework scoring features by Reach, Impact, Confidence, and Effort

"When we ran RICE scoring, the onboarding improvement ranked higher than the new export feature despite louder stakeholder requests."
hypothesis n.

A specific, testable belief about user behaviour or business impact that guides product decisions

"Our hypothesis is that reducing the sign-up steps from five to three will increase conversion by 20%."
product discovery n.

The ongoing process of validating whether a proposed solution addresses a real user problem before building it

"We ran two weeks of product discovery with customers before committing the engineering team."
Open full glossary →

📚 Vocabulary Reference

Key terms organised by category for Product Manager (IT)s:

Planning

PRDuser storyacceptance criteriaepicinitiativeroadmapnow-next-lateropportunity solution treeproduct briefone-pager

Prioritisation

RICE scoreICE scoreMoSCoWimpact vs effortopportunity sizingstory pointstech debthypothesisassumptionexperiment

Goals & Metrics

OKRKPInorth star metricactivation rateretentionchurnNPSCSATARRLTV

Discovery

product discoveryuser interviewjobs to be donepain pointpersonaempathy mapprototypeusability testpivotvalidated learning
Study full vocabulary modules →

Recommended exercises

Real-world scenarios you'll practise

  • Writing a PRD that gives engineers enough context to build without over-specifying the solution.
  • Presenting the quarterly roadmap to executives who want certainty in a world of uncertainty.
  • Running a product discovery interview that uncovers the real job-to-be-done behind a feature request.
  • Writing a launch announcement for a new feature that excites customers without overpromising.

Recommended reading

Explore another role

📋 Technical Program Manager (TPM)

Open path →