Everybody All Together: The Lean Secret

Definition

At the heart of Lean architecture is an "all hands on deck" mentality where every stakeholder — domain experts, end users, developers, testers, business, and architects — engages together from the project's start, working in parallel rather than sequential phases. This practice, called "the Lean Secret," directly addresses the sources of delay and rework that dominate traditional software projects: handoffs, wait states, and isolated decision-making.

In the Book

Coplien and Bjørnvig repeatedly invoke this principle across Chapters 1 and 3. Traditional software development organizes like a Henry Ford assembly line, with specialists handing artifacts down the line in sequence. But software has no equivalent to the laws of physics that constrain manufacturing. Domain experts, interaction designers, developers, and testers all drive aspects of the architecture, and their decisions are interdependent. A decision the architect makes requires input from the interaction designer; the designer needs feedback from developers about feasibility; the developers need clarity from domain experts.

When these roles work sequentially in stovepipes, the result is months of delay: architects write memos, wait for designer feedback, receive conflicting advice, make assumptions, then hand down documents that collide with implementation realities. A team that brings all roles together — like an insect swarm, not a factory line — can compress architecture from months to days or weeks. The stakeholders work together in a single sprint, co-located, able to ask clarifying questions in seconds. Trust among team members becomes the first thing you build.

Why It Matters

This principle collapses the feedback delay that traditionally makes architecture "hard." It also produces two higher-order effects: decisions reflect genuine stakeholder insight instead of architect assumptions, and the team develops shared mental models that sustain adaptation throughout the project's lifetime. A team organized around sequential handoffs must rebuild context after every phase transition. A team working all together, continuously, internalizes shared understanding that becomes tacit knowledge — the bedrock of effective agile change.