Output is what ships: features, screens, releases. Outcomes are what changes for the business and the customer because of what shipped: a problem solved, a behaviour moved, a number that goes the right way. A product manager is measured on outcomes. Shipping a feature nobody adopts is motion, not progress.

This is the single most useful idea in the role. It reframes every decision from "what should we build?" to "what result are we trying to create, and is this the cheapest way to get it?" Often the best move is to build less, or nothing, and the discipline to notice that is what separates a PM from a backlog administrator.

The PM owns the "what" and the "why": which problem the team solves next, for whom, and how you will know it worked. They bring three things together: what is valuable (business + customer), what is feasible (engineering), and what is usable (design), and they make the call when those pull apart.

The PM is not the team’s manager: engineers and designers are peers, not reports. They are not the "idea person" who hands down solutions; that wastes the team’s judgement. And they are not a project manager whose job is a Gantt chart and status updates. A PM who only writes tickets and chases dates has quietly become a feature factory.