Collaborative Software Design: How to facilitate domain modeling decisions
summary
A practical method for turning messy socio-technical problems into decisions: run low-friction collaborative modeling sessions (using event storming, domain storytelling and message‑flow maps) with a tangible case like the BigScreen cinema chain (12 countries) to expose info, surface preferences and generate at least three alternatives. Observe behavior objectively (resistance lines, ranking, dominance blindness), capture pros/cons plus fixes, make decision authority explicit (autocratic, proposal, consent) and ask “what would it take for you to go along?” to neutralize objections and reach sustainable choices.
AI-written summary · about
chapters (7)
- 0:00Collaborative design context
- 3:52Collaborative modeling tools
- 9:41Human dynamics and behavior
- 15:35Ranking and group hierarchy
- 23:02Decision-making processes
- 30:57Facilitating inclusive buy-in
- 36:52Q&A and closing
related talks
01mSoftware doesn't tolerate ambiguity
39mFrom Domain Boundaries to Software Architecture
41mThe lost art of software design
31mHow EventStorming Transformed Our Domain Modeling Process
59mSystem Architecture Design Using Model Exploration
50mHow EventStorming Transformed Our Domain Modeling Process
59mModelling Stories of the Beautiful Mess
01h 02mRethinking Enterprise Software