The Influence of Early 1900s on Modern Work Practices

The importance of the early 1900s to how work is conducted today cannot be overstated, especially in America. The developments during this period have shaped corporations, business processes, and defined project management.

Two key forces defined this era:

• Scientific Management (Taylorism) as defined by Frederick Taylor
• Henry Ford and his production methods

These forces have profoundly influenced organizational work practices, akin to how dams influence the flow of water.

The Shift in Workforce Dynamics

Prior to Taylor's principles, workers often embodied the role of tradesmen, possessing a deep understanding of the products they worked on. Creativity and judgment were integral to their craftsmanship.

Taylor proposed that organizations could save on costs by having a few knowledgeable employees manage the intellectual aspect of work, while the majority performed manual tasks based on established guidelines. This allowed for a workforce that could be paid less, as they were primarily executing predefined actions.

When Henry Ford implemented these principles, the initial response from workers was overwhelmingly negative. Reports state that he had to hire almost a thousand individuals to maintain a stable workforce due to high turnover rates. The reduction in dignity and expertise led workers to resist this new system.

Implications for Software Development

This dichotomy between the few who manage intellectual endeavors and the many who conduct manual operations translates into modern work environments, including software development.

NASA's software development for the Apollo spacecraft serves as a notable example. They applied manufacturing practices to software development, hiring numerous coders while leaving the design to a smaller group of engineers. This approach resulted in low-quality code and lengthy verification processes, ultimately concluding that more programmers do not equate to faster development.

Today's organizations often mirror this model, with "architects" responsible for software design and "coders" executing given tasks. Unfortunately, this leads to a concentration of knowledge among few while coders are deprived of the opportunity to contribute meaningfully. As a consultant, I observe that this trend persists and is even intensifying.

The Risk of a Divided Labor Force

When software development is approached this way, developers become interchangeable parts. If a developer only knows how to write code as instructed, their value diminishes, and they can easily be replaced by someone with similar skills.

This trend negatively impacts developers’ problem-solving abilities. The loss of the tradesman-like skills leads to a workforce less capable of addressing issues when they arise. The intellectual processes are reserved for architects, which hampers the overall quality of software development.

Organizations benefit in the short term from cheaper labor but expose themselves to long-term risks. The reliance on a few individuals for critical decisions creates vulnerabilities. A single departure can severely impact productivity, as knowledge isn’t widely shared among team members.

A Call for Change

We must reevaluate our systems that strip individuals of the creative and problem-solving capacities essential to their roles. Rather than operating strictly within narrow confines defined by management, architects should be engaged in coding, and coders should be given opportunities for design input.

This shift can cultivate a stronger, more capable workforce—one that can adapt, innovate, and ultimately drive success in organizations.