Let's talk about friction—not the kind that wears down your tyres, but the kind that makes your architectural decisions worse. In behavioural science, friction is anything that makes doing the "right" thing harder than it needs to be. Think of people who take up all the space in meetings, endless discussions about discussions, cycling back to decisions you thought were long made, or people perceived to show resistant behaviour. 1/4
=> More informations about this toot | More toots from kenny_baas@mastodon.social
When it comes to collaborative modeling, this kind of friction is a silent killer of good ideas. Do you want a free flow of knowledge? Do you want diverse perspectives to build on each other instead of clashing? Then, you need to eliminate the friction that gets in the way ruthlessly. Collaborative modelling requires the right tool for the right context to eliminate the friction that blocks knowledge sharing. 2/4
=> More informations about this toot | More toots from kenny_baas@mastodon.social
Simplicity is key, as it allows for the unhindered flow of wisdom and promotes the development of a shared understanding built upon diverse perspectives.
So, if your current collaborative modeling tool like EventStorming, Example Mapping, Domain Storytelling, Wardley Mapping or any other feels like it's creating more problems than it solves, it's time to ask some tough questions. 3/4
=> More informations about this toot | More toots from kenny_baas@mastodon.social
Are your tools actually helping, or are they just adding to the noise? Is your decision-making process truly streamlined or stuck in a loop? Perhaps it is time to switch to another one!
Next Tuesday, @selketjah and I will be diving deep into these questions at OOP Konferenze during our talk about the book we wrote. Hope to see you there! 4/4
=> More informations about this toot | More toots from kenny_baas@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini
