Holistic Engineering: Organic Problem Solving for Complex Evolving Systems

Phenomena in the Wild

Late projects and architectures drifting from original designs are common in software development. These issues often stem not from technical failures, but from non-technical forces like misaligned reward systems and overlooked human dynamics that impact technical decisions.

Why This Matters

Traditional engineering approaches often focus solely on technical solutions, ignoring the significant influence of organizational and human factors. This disconnect leads to projects failing not due to flawed code, but because the system doesn’t account for how people and the organization actually operate, resulting in substantial cost overruns and project delays.

Key Insights

• Shared “kitchen sink” utilities libraries are common: These libraries accumulate features from many teams, increasing complexity and blast radius.
• Domain Identity Crisis: Teams create single domain models for diverse business needs, violating domain-driven design principles.
• Holistic Engineering: Treats projects as organic socio-technical systems, considering both internal and external forces.

Practical Applications

• Use Case: A financial institution uses Holistic Engineering to map internal approval processes, reducing project delays caused by bureaucratic bottlenecks.
• Pitfall: Ignoring career incentives can lead to over-engineered solutions as developers prioritize demonstrating technical skill over practical efficiency.

References:

• https://www.infoq.com/articles/holistic-engineering-organic-problem-solving-complex-systems/