Making sustainable design decisions for our architecture that are embraced by everyone is the ultimate goal. Yet in reality, this process is far from straightforward due to the complexities of group dynamics. Cultural differences, conflicts of opinions, cognitive biases, and polarities within the group can cause resistance behavior, ranging from sarcastic jokes to stopped communication or leaving the session. With these challenges, it is no wonder many organizations resort to a more autocratic form of decision-making, where one person, typically the architect, analyses and makes the decision.
In order to combat these challenges and promote collaborative decision-making, it is essential to understand the context in which a software system lives, which necessitates effective communication between developers and the business. However, communication too is fraught with its own set of challenges: misunderstandings, fear of speaking up, growing tensions, and potential conflict.
Join us with Kenny Baas-Schwegler in this hands-on session, where we explore how to bridge this gap through the use of collaborative modelling, different models of decision-making, and facilitation techniques that aim to foster collaboration between developer teams and domain experts. This hands-on will give you a glimpse and a starting point of skills and methods needed to navigate complex group dynamics and lead productive, collaborative software design sessions.
In this meetup, I will present you with a small design challenge for you to collaboratively model. Through that excercise I will introduce you to some facilitation techniques from our book "Collaborative Software design". Such as working with climate reports to trigger hidden group conflicts, visualising trade-offs of different models with the pro-con-fix list, and taking group decisions with full buy-in using Deep Democracy.