Product Manager in 1986: Takeuchi and Nonaka describe teams like a rugby scrum

The role traces to a 1931 memo at Procter & Gamble, where a young executive proposed assigning individual 'brand men' to compete for a single product's success. Technology companies adopted a version of the title from the 1980s onward, and the discipline was reshaped again by the agile and lean movements of the 2000s and 2010s, which replaced long specification documents with fast, iterative shipping and constant customer feedback.

'Product manager' means something different at almost every company that uses it — sometimes a strategist, sometimes a glorified project coordinator, sometimes both in the same week. There is no licence, exam or professional body governing the title anywhere in the world, and no two job descriptions read quite alike. What holds the profession together is not a credential but a recurring set of judgment calls about what is worth building at all.

What does a product manager actually do all day? Far less building than the title suggests. A typical day mixes reviewing usage data, talking to customers or sales teams about what they need, writing or refining a specification for engineers, and sitting in planning meetings to decide what gets built next and what gets cut. Very little of the day involves writing code, drawing a screen, or shipping anything personally.