Modelling Stories of the Beautiful Mess
summary
Claim: treat complexity as a navigable, generative “beautiful mess” by modeling conversations and belonging before collaboration, not by imposing fixed architectures. Practical tools shown include eventstorming, context mapping, service blueprints, journey mapping, team topologies, North Star and physical boards. One large journey mapping with 5,000 people and 500 teams proves double edged—gamechanging for an executive team and a waste for another group—so keep modeling but stay ready to detach from models and celebrate incoherence as a source of emergence.
AI-written summary · about
chapters (7)
- 0:00Introduction and speakers
- 4:11Individual perspectives on mess
- 11:08Shared lens on sociotechnical modeling
- 18:14Decouple and connect in systems
- 28:11Usefulness of models
- 35:39Three wayfinding tips
- 57:29Summary and closing
related talks
41mCollaborative Software Design: How to facilitate domain modeling decisions
39mFrom Domain Boundaries to Software Architecture
01h 02mRethinking Enterprise Software
48mCritically Engaging with Models
45mSystems Thinking by combining Team Topologies with Context Maps
43mGo Ahead, Make a Mess
48mModularization — It Was Supposed to Be Beautiful but Turned Out as Usual :(
53mSoftware Design: Beyond Boxes & Lines