Product Manager in 1950s: Toyotas chief-engineer system takes shape — Section 982: Toyotas chief-engineer syste

Decides what a company should build next, and why — turning customer needs, business goals and engineering limits into one shared plan nobody else fully owns. A product manager decides what a company builds next, gathers evidence for why, and coordinates the engineers, designers, salespeople and executives who have to agree before it ships. The job sits at the intersection of technology, business and user needs, and rarely involves writing code or design work directly. Most days go to conversation — with customers, with data, and with the teams actually building the thing — rather than to producing a finished artifact of their own.

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.