wardley/ch18-better-for-less/SUMMARY.md

Chapter 18: Better for Less

Core Focus

Wardley's work with UK Government's "Triple Helix" group to reform government IT. Explores doctrine phases, cognitive biases, and organizational transformation.

Government IT Problems

• Lack of engineering skills
• Over-reliance on outsourcing
• No effective cost controls
• Massive duplication across departments
• Culture prioritizing failure avoidance over results
• Projects costing hundreds of millions with poor success rates

The Mapping Gap

Critical discovery: "nobody knew what maps were." A 2013 survey found only 4 of 600 companies possessed anything resembling mapping. Most operated blind.

The "Better for Less" Paper

Six core doctrines:

1. Think big
2. Do better with less
3. Move fast
4. Commit to direction while remaining adaptive
5. Pragmatism over ideology
6. Bias toward new approaches

Doctrine Phases (Four Stages)

Phase I - Stop self-harm: Remove duplication, understand user needs, improve situational awareness.

Phase II - Context awareness: Apply appropriate tools, embrace FIRE (fast, inexpensive, restrained, elegant).

Phase III - Better for Less: Optimize flows, seek continuous improvement, inspire change.

Phase IV - Continuous evolution: Design for constant adaptation with pioneer-settler-town planner structures.

Cognitive Biases

• False consensus (assuming others know what you know)
• Confirmation bias
• Loss aversion and sunk cost
• Outcome bias
• Hindsight bias
• Survivorship bias
• Dunning-Kruger effect

Strategic Cycles

• OODA Loop vs. PDCA: familiarity determines planning depth
• JDI to DMAIC spectrum: "just do it" (unknown) to structured improvement (known)

Key Examples

Healthcare: Mapping preventative care reveals feedback loops - longer-lived populations need increased treatment, requiring medical innovation investment.

Automotive (2025): Self-driving cars, utility-based ownership. Unintended consequence: digital subscription tiers embedding social inequality through automated traffic prioritization.

OpenStack failure: Organizational hubris and misguided API differentiation strategy undermined potential as AWS competitor.

Key Takeaways

1. Without situational awareness through mapping, organizations can't eliminate duplication or apply appropriate methods
2. Actively counter cognitive biases through collaborative map-making
3. Context determines method - no single approach works universally
4. Doctrine application requires sequence: user needs and duplication first, then advanced play
5. Humility is essential - maps are imperfect learning aids, not truth
6. Map systems forward to identify unintended consequences