Software architecture is a team sport. Yet, many architecture decisions are still made by a small group of experts, while critical knowledge remains fragmented across teams, domains, and organizational boundaries. The result: bottlenecks, misunderstandings and slow architectural evolution.

Collaborative Modelling (CoMo) in software design offers a different approach. Rather than relying on a single technique, it brings architects, developers, domain experts, and other stakeholders together to build a shared understanding of systems, their context, and the challenges they face. Practices such as EventStorming demonstrate the power of collaborative modelling, but they represent only a small part of a broader set of collaborative modelling techniques.

At its core, Collaborative Modelling in software design is not about creating better models – it is about enabling better conversations that lead to better architecture!

This talk explores three practical reasons why collaborative modelling has become an essential architectural practice:

1) Creating shared understanding across teams and domains.
2) Early discovery of assumptions, misunderstandings, and hidden risks, before they become expensive
3) Reducing architectural bottlenecks by distributing knowledge and responsibility.

Participants will discover the principles behind collaborative modelling and explore where these practices create the greatest impact. They will learn how collaborative modelling helps teams make more informed decisions, align architecture with business needs, and evolve complex systems more effectively. They will leave with practical ideas for making architecture a shared capability rather than the responsibility of a few individuals.