Product Manager in 1931: Neil McElroy's 'brand man' memo at P&G

'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.

Do you need an engineering or technical background to become a product manager? No, though it helps in software-heavy roles. Many product managers come from engineering, but plenty arrive from design, marketing, consulting or customer support instead. What matters more than a specific degree is being able to read data, write clearly, and hold your own in a room with engineers without needing to write the code yourself.