Introduction to Product Management

Why this matters

Product management is one of the most talked-about and least understood roles in tech. It sits between users, engineering, design and the business, and the job is not to have the most opinions, it is to make sure the team builds the right thing for the right reason. Getting a clear mental model of the role early saves months of confusion.

This session lays the foundation: what a PM is responsible for, what they are not, and how the day-to-day actually looks, discovery, prioritisation, working with engineers and designers, and measuring outcomes rather than counting features. It is the orientation every aspiring PM needs before diving into the specifics.

How to execute

A do-it-this-week sequence, turn the class into a decision, not just notes.

1. 1
   Learn what a PM owns

   Understand the core responsibility, owning the “why” and the “what” (the problem, the priorities and the outcomes), while engineering owns the “how”. A PM is accountable for the result, not for issuing orders.

2. 2
   Map the day-to-day

   See how the work splits across discovery (understanding users and problems), delivery (working with engineering and design to ship), and measurement (tracking whether it moved the outcome you cared about).

3. 3
   Think in outcomes, not features

   Practise reframing any request from “build X” to “what problem does this solve and how will we know it worked?”. This single habit is what separates a PM from a feature-taker.

4. 4
   Start building the toolkit

   Note the skills the role leans on, user research, prioritisation, writing clear requirements, and stakeholder communication, and pick one to go deeper on next.