Blending Product Thinking with Architecture
summary
Argues that architecture must be tied to concrete product assumptions and shows specific practices that change decisions: use story mapping and simple visual storyboards, plot decision bubbles with cost-of-being-wrong, and apply explore expand extract to pick different architectures for family business or adventurous travel use cases. Demonstrations include CRC cards domain modeling, microservices plus chaos and fault tolerance trade-offs, a trading-platform example where matching cost drove experiments, and cheaper alignment results than coding first.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:02What is Architecture
- 8:37Storyboarding
- 13:55Explore Expand Extract
- 16:43Explore What You Want to Move
- 18:59Understanding Assumptions
- 21:20Questions
related talks
47mBlending Product Thinking with Architecture
01h 02mThinking Like an Architect
33mSet Design: Putting the "Art" in "Architecture"
24mBusiness Value Over Architecture?
01h 01mArchitecture: The Stuff That's Hard to Change
42mThe Power of Visualizing Constraints in Software Architecture
41mArchitecture and Agility: A Shared Skillset!
24mThe too many faces of Architecture