Architecture Transformation Challenges
summary
Argues change fails because humans and incentives matter, not tech; identifies archetypes like the professional tech skeptic and legacy lover and warns against motivations such as CV-driven or shiny‑toy play. Recommends concrete patterns: grow adoption organically, run a separate innovation lab or sandbox playground, try a one‑off know‑how leapfrog (skip generations), or hijack a project so new architecture ships as a feature; use 1% rollouts, prove value in ~3 months, and avoid wasting €10–50M on lipstick‑on‑pig efforts.
AI-written summary · about
chapters (43)
- 0:00Intro
- 1:00Story arc
- 1:40Conference experience
- 2:50Reality hits
- 3:25Why is it hard
- 4:00Stereotypes
- 4:35Professional Tech Skeptic
- 6:00Legacy Lover
- 7:00Vendor Agent
- 7:50Process Protector
- 8:20Yeasayer
- 9:30The negative view
- 10:30The perceptive view
- 11:25The legacy lover
- 12:45The process protector
- 14:20The vendor agent
- 15:00The distractor
- 19:00Community status
- 19:50Good reasons
- 21:00Make up your mind
- 21:45Bike to work
- 23:35Economics
- 24:25Patterns
- 25:00Organic
- 26:20Slow
- 26:40Playground
- 27:50Design Sprint
- 28:05Knowhow leapfrog
- 29:10People director
- 30:10Benchmarks
- 31:15Mixed results
- 33:00Easy to innovate
- 33:25Not a separate business model
- 34:45People
- 35:30Hijacking
- 36:20Risk
- 37:00Sneaky
- 37:15HR motivation
- 39:30Conway maneuvering
- 40:30Summary
- 40:45Importance of allies
- 41:25Disrupt with care
- 42:25QA session
related talks
42mThe Architecture of Change
43mThinking Architecturally
45mArchitecture: The Stuff That's Hard to Change
45mTeam and Software: Making an Impact as an Architect
59mDeliberate Architecture
25mLeapfrogging from Good to a Great Architect
43mArchitect(ure) as Enabler of Organization’s Flow of Change
02mHigh-performance teams