---
id: "contrarian-triangle-inefficiency"
type: "contrarian-insight"
source_timestamps: ["00:03:37", "00:03:52"]
tags: ["organizational-design", "agile", "contrarian-insight"]
related: ["framework-sequential-bottleneck", "claim-figma-stock-tanked"]
challenges: "The established best practice that separating product, design, and engineering into distinct, siloed phases is the optimal way to build software."
sources: ["s48-markdown-design-meeting"]
sourceVaultSlug: "s48-markdown-design-meeting"
originDay: 48
---
# The Product-Design-Engineering triangle was always broken

## Contrarian Position

The tech industry **idolized the 'Product, Design, Engineering' triad** in the 2010s. [[entity-nate-b-jones|Jones]] points out this model **rarely worked seamlessly in practice** — it was plagued by:

- Sequential bottlenecks ([[framework-sequential-bottleneck]]).
- Unbuildable designs that required late-stage compromises.
- Slow iteration cycles (10+ weeks).
- Handoff loss between phases.

**Moving design to the command line doesn't disrupt a working system — it fixes a fundamentally broken legacy workflow.**

## What It Challenges

The established best practice that separating product, design, and engineering into distinct, siloed phases is the optimal way to build software.

## Why It's Spicy

For 15 years, every tech-org playbook prescribed the triad as gold standard. Jones reframes it as a **historical accident** that survived despite its dysfunction because no alternative existed. Now that [[concept-command-line-design|command-line design]] exists, the triad's structural weakness is exposed.

This directly underwrites [[claim-figma-stock-tanked]] — Figma optimized for a workflow that never actually worked.

## Counter-Perspective from Enrichment

- Engineering literature shows AI tools sometimes **create new silos** (MLOps data unification needs, hardware-in-the-loop verification persists).
- The bottleneck **moves** rather than disappears.
- Some problem domains (regulated industries, complex hardware-software systems) may still require staged review by distinct disciplines.
- INCOSE-style verification rigor doesn't vanish just because design becomes code.

## Synthesis

Jones's contrarian punch is correct directionally: the *generic* triad-as-best-practice claim is overrated. But the triad's **decomposition of concerns** still matters; it's the **sequential, siloed implementation** that AI dismantles.

## Related
[[framework-sequential-bottleneck]] · [[claim-figma-stock-tanked]] · [[concept-command-line-design]]