Widget Factory vs Film Crew
Definition
A framing (translated by 陈皓 from a StackExchange answer on why BAs/PMs often out-earn programmers) that identifies two fundamentally different organizational cultures for software companies: the Widget Factory and the Film Crew. They rest on opposite assumptions about people — McGregor’s Theory X vs Theory Y — and produce opposite hierarchies, pay structures, and abilities to attract talent.
Core Ideas
Widget Factory (Theory X)
Assumes people are inherently lazy and avoid work, so managers must drive them with process, supervision, and incentives. Consequences:
- Tree-shaped hierarchy, not horizontal roles; the manager’s capability is continually reinforced while each team member is easily replaceable.
- Software is treated like manufacturing: BAs write specs under a PM-supervised process, and interchangeable programming/testing “resources” execute a pre-set, budget-driven plan (defined by PM + BA in the initial business case).
- Recognizable by its vocabulary — resource (including people as “resources”), process, operating efficiency, uniformity, repeatability, tightly controlled resource use, sharply defined roles and inputs/outputs. Indifferent to the actual craft of building software.
- Pay: value is assumed to derive from PMs/BAs, so they sit atop the hierarchy and earn more; once requirements become working code, the dev team is treated as commoditized factory workers. PMs/BAs often withhold original project information, forcing the team to manufacture justifications for their value.
Film Crew (Theory Y)
Assumes people are intelligent, creative, and self-motivated — they self-regulate and enjoy work without external threat. Consequences:
- Individual professional excellence beats orchestrated coordination; managers can’t substitute for each person, and rigid tree hierarchies don’t work — people cooperate in more complex, vertical roles (everyone needs both management and technical ability).
- Led by a Director who understands every piece needed to assemble great software: assembles an outstanding team, keeps it cohesive, and guards the Vision, provides direction, and focuses energy. Every member is a “star,” and the Vision drives the budget.
- Equal access to primary/original information, encouraging everyone to form judgments and choose their own path to the Vision. Leadership is based on capability, not job role; pay reflects the value a person creates. The PM role shrinks to administrative/external-liaison support, and much of the BA role is absorbed by the team (or the Director early on).
The takeaway
Most in-house and consulting software shops run as Widget Factories, dependent on process to grind out mediocre software, where PMs/BAs out-earn programmers on the assumption they create more value — and programmers can’t easily prove the management wrong. But:
Successful software companies trend toward the Film Crew model — anything else undermines their ability to attract top talent, and only top talent creates great software. There, a good programmer out-earns BAs and PMs by a wide margin.
Note (陈皓): Widget Factory ≠ Waterfall and Film Crew ≠ Agile/Scrum — a shop can “do Agile” and still be a Widget Factory in essence.
Relationships
- Stakeholder Management and Role Clarity — an opposing lens: where role frameworks clarify vs where they entrench hierarchy
- Work Culture & Management — the two cultures are competing operating systems for a software org
- Agile — explicitly not the same axis; Agile practices can sit inside either culture
- Talent Retention — what the widget-factory view of engineers costs over a few years of hiring
- Respect Over Diversity — subjective review criteria as the mechanism by which the culture judges people
References
- 软件公司的两种管理方式