3 Reasons Why Classic Product Management Is Inspired by the Assembly Line
Everyone believes they have adopted Silicon Valley product culture. They hire product managers, follow "Agile" frameworks, complete sprints, and measure velocity.
Yet when you look closer, we are once again trying to fit everything into a box, explain everything through a process or a document.
We added a layer of customer-centricity compared to pure engineering-led organisations, but fundamentally, we just implemented the latest patch on top of Henry Ford’s 20th-century factory floor foundations.
We digitalised Taylorism.
We created the Feature Factory.
1. From Stopwatches to Jira Tickets: Atomizing Work to Chase Velocity Over Value
In Taylorism: Frederick Taylor measured workers' operations with a stopwatch, breaking down skilled craftsmanship into tiny, repetitive physical tasks. The goal was to maximise local station output, turning human beings into predictable, specialised cogs in a larger assembly line without giving them any visibility into the broader production strategy.
In Classic PM: Complex initiatives are broken down into micro-tickets, user stories, and two-week sprint tasks in tools like Jira. Product teams clear cards off a board and optimise for output metrics, such as sprint velocity to reassure leadership that people are staying busy. This atomisation strips away strategic context, reducing subject-matter experts (engineers and designers) to digital assembly-line workers who deliver output rather than business ROI.
2. "Thinking" at the Top, "Executing" at the Bottom: Proxy Governance & The Loss of Context
In Taylorism: Scientific Management enforced a strict binary divide between the "planning department" and the factory floor. Foremen and time-study analysts acted as supervisory middle layers, extracting knowledge from workers and handing them pre-digested operational instructions. By keeping laborers isolated from the broader business strategy and manufacturing logic, Taylorism deliberately replaced artisan intuition with mindless compliance, turning workers into interchangeable operators.
In Classic PM: Modern Product Management promises empowered teams, but in practice, the Product Manager often acts as an artificial proxy between leadership, customer reality, and the delivery team. Designers and engineers are shielded from raw business goals and direct customer contact, receiving only digested "User Stories" or pre-packaged ticket specifications. When builders are left exposed only to the ticket description rather than the overarching vision, it creates functional stupidity: flawlessly executing tasks without purpose or strategic authority to challenge them. This structural bottleneck strips strategic muscle from design, engineering, and marketing, turning skilled builders into the modern, passive operators of a digital factory.
3. The Separation of "Standardised Process" from "Actual Knowledge"
In Taylorism: Frederick Taylor believed that individual workers' tacit knowledge and artisan craftsmanship were inherently inefficient, unpredictable, and unreliable. His solution was to systematically extract knowledge from the shop floor, codify it into rigid Standard Operating Procedures (SOPs), and enforce strict adherence through overseers. Compliance with the dictated method replaced creative intuition, turning craftsmanship into mechanical execution.
In Classic PM: The "Agile / Scrum Framework" is frequently converted into a universal, copy-paste playbook leading to meeting rituals, tickets, sprints, and story-point estimation. The team's actual domain expertise, deep technical intuition, and creative problem-solving are subordinated to following the ritualised process. Product development becomes a compliance exercise where adhering to the framework takes precedence over building the right solution.
Why Does Classic PM Persist?
It carries Silicon Valley prestige: It is the default playbook popularised by Big Tech and heavily promoted across the tech industry. This playbook is sustained by a massive coaching ecosystem: the global product management market is projected to reach USD 49.3 Billion, while the Agile transformation market is forecast to cross USD 140 Billion by 2032 (Verified Market Research).
It provides a comforting illusion of control: It breaks complex, uncertain initiatives into bite-sized tasks and monitors progress through neat, predictable metrics. By converting ambiguous strategy into Jira tickets and sub-tasks, it gives leadership a false sense of risk management, predictability, and governance.
It is the unquestioned default status quo: It has become the standard corporate baseline expected by founders, boards, and the workforce alike. As a result, organisations rarely challenge its inherent flaws until accumulated friction and wasted capital become too acute to ignore, at which point they often hire expensive consultants and coaches rather than reforming their core product organisation.
Do we need a different approach in the Age of AI and Gen Z?
Yes, Classic PM is rapidly becoming obsolete, particularly due to the convergence of AI tools and Gen Z workplace dynamics.
AI eliminates the "Assembly Line Executor": Just as robots replaced workers on the assembly line, AI is taking over coding and routine design tasks. As a consequence, value shifts toward human judgement and strategy. When you can build more (and still spend large amounts of money on tokens), having the right product direction matters more than ever.
Gen Z rejects "Functional Stupidity": Gen Z workers consistently push back against bureaucracy and heavy processes. They demand purpose, clear context, and autonomy. Forcing high-potential young talent into sprint-assembly lines could lead to rapid turnover and quiet quitting.
What to do? 4 keys to shift your approach:
Restore Context: Be obsessed with sharing the big picture: the vision, the North Star, and the project boundaries. Invest time in communicating these strategic foundations rather than pouring hours into meeting rituals and ticket writing.
Measure Impact, Not Volume: Track how development translates into actual product impact (through the product attribute profile). Only then can you evaluate whether your strategy is converting into real ROI.
Shift from Static Linear Orgs to Dynamic Systems Orgs: Move away from a single-mode product organisation (all legacy org. including Classic PM) to a modular, multi-mode organisation (Design × Engineering × Marketing) where the trade-off owner acts as the playmaker between functions.
Practice Systems Thinking: Recruit Systems Thinkers who solve problems based on deep context and fundamental principles rather than relying on past execution patterns.
What do you think? Do AI and Gen Z demand that we fundamentally rethink how we structure product organisations, or is Classic PM still the least bad system we have?
