How many people should I invite for a collaborative modelling session? It depends! Go wide for discovery, but for decision-making, the magic number is 5-7. Learn how to manage group sizes for divergence and convergence in the latest Dear CoMo.

We scheduled a new session with Andrew Harmel-Law on anarchist thought & socio-technical design. A look at alternatives to top-down hierarchy for building better teams. 📅 23 Sept at 19:00 NZST #DDD #SocioTechnical buff.ly/Bmvoiwe #DomainDrivenDesign #SocioTechnicalSystems #SoftwareArchitecture

Collaboration, by nature, is about working with others, which means we bring our whole selves to the table—not just our technical skills. Often, the biggest challenges in collaborative software design aren't technical, they are human. In this video from @amaconf.bsky.social -->

Software development isn’t just about writing code; it’s about understanding the problem you're solving. A while ago @gienverschatse.com and @kenny.weave-it.org went on the Software Testing Unleashed podcast, hosted by @richard-seidl.com.

It's a common aspiration, Collaborative software design leading to wonderfully autonomous teams and truly decentralized decisions. Yet, the reality, as ‪@evelynvankelle.bsky.social‬ and ‪@kenny.weave-it.org‬ so thoughtfully discussed at Fast Flow Conf NL, central decisions don't just disappear.

The idea of collaborative modeling flourishing within a company is something many of us strive for. But is it a guaranteed success, and where do you even begin to plant those seeds? Watch and listen to ‪@gienverschatse.com‬ and ‪@evelynvankelle.bsky.social‬ as they explore these very questions.

Oh, the tangled web we weave when our software domains lack clear boundaries! Last week, our brilliant authors, ‪@gienverschatse.com‬ and ‪@kenny.weave-it.org‬ , tackled this very predicament head-on. - 1/6

Dear CoMo, My Team Clings to Their Ideas – Help! Well, well, well, isn't that a familiar feeling? Collaborative modelling should be a place where brilliant minds come together, stickies fly, and shared understanding *should* blossom.. Read more : collaborative-software-design.com/dear-como/te...

Sometimes you just have to share a bit of good news that makes you smile. Picture this: the bustling @amaconf.bsky.social conference, and right there, our own authors are hosting a book signing session. A real pinch-me moment! While they managed a calm exterior, I can tell you there was a ....

If we leave the judging to the cats, how can we address the shadows in collaborative modelling sessions? My authors were recently asked that question at the Agile Meets Architecture conference, where they talked about the book. Read the answer here: collaborative-software-design.com/dear-como/le...

Dear CoMo, Why does my colleague never contradict me? It sounds like your colleague might be dealing with a classic case of conflict avoidance. Now, don’t get me wrong—I don’t say that to be unkind. Read all about it at the latest Dear CoMo collaborative-software-design.com/dear-como/co...

Stop treating software design decisions like they're written in stone! There's no real 'point of no return.' You can always change your mind later. The key is having tight feedback loops to spot a wrong turn ASAP and adapt quickly, before the cost balloons. Design isn't static, neither is context.

Hot take maybe? Architects swapping between Enablement and Platform teams seems like a smart move. They learn the real-world collaboration stuff with Enablement, then build platform tools that don't force teams into awkward workflows for sharing architecture. Just build it the way teams need it.

"Autonomy" is basically just a container concept we throw around. So, can we stop telling teams to simply "be autonomous"? It means something different to everyone! Real autonomy needs clear boundaries and context defined for specific teams/situations. Otherwise, you're just inviting confusion.

It’s a common scenario in the world of architecture—decisions are made, and suddenly, you find yourself facing a wall of resistance. But let’s pause for a moment. Are your colleagues truly resisting the decision, or could it be that your own assumptions are clouding your judgment?

And for a web-friendly version see wirfs-brock.com/rebecca/pape...

Feeling lost in the labyrinth of software design decisions? Do you ever wish you had a trusty set of guiding principles to help your team navigate the complexities of architecture? Well, my dear, you might find solace in the understanding and application of design heuristics. 1/12

Why do we often find that people in our team use the same words but seem to mean different things, leading to confusion? Ambiguous language in team discussions is a very common problem, find out more here: collaborative-software-design.com/dear-como/am...

Many hesitate to lead Collaborative Modelling, thinking it's for "formal" facilitators like coaches or leads. Not so! Anyone on the team can, and should, guide these sessions—often with the best results. Don't wait. Read up and start! buff.ly/xLOzmQQ

Well, let's be honest, darlings. Resistance kills efficiency in design decisions. It's like trying to bake a cake with half the ingredients—you're just not going to get the results you want. When people aren't engaged and feel their opinions don't matter, the quality of our design decisions suffers.

Dear CoMo, What can I do if people keep interrupting each other? You've hit upon a common challenge in collaborative settings, and it's admirable that you're seeking ways to address it. Interrupting can derail even the most well-intentioned group. https://buff.ly/41fMw9r

Yesterday at OOP, @gienverschatse.com and @kenny.weave-it.org illuminated why development teams must evolve into product teams! They eloquently argued that being part of opportunity selection, requirement engineering, and design is key to success. This shift isn't.. https://buff.ly/40IsF0Z

Well, dearies, let's face it, none of us are quite as brilliant at making decisions as we'd like to believe. We try our best, bless our hearts, but sometimes... well, you know. We all have those moments where we look back and think, "What on earth was I thinking?" It's a human thing, after all.1/3

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. A Thread 1/6

Collaborative software design catalyst : Let participants engage in an impromptu networking check-in. As a topic for the impromptu networking, you can discuss any questions they have on the meeting topic. Having coffee and snacks during impromptu networking helps make people more relaxed.

Collaboration, just like all of the other values and principles from the Agile Manifesto, are all very big container concepts that have a lot of room for interpretation and misinterpretation. Check out the full video on our website: https://buff.ly/3CpzrAp

Decision-making challenges? You know that feeling when you're trying to make a decision, and you feel like you're not getting everyone on board? Here's a helpful tip to use the next time you face design or architectural decisions.

Sensemaking is a powerful tool during decision-making, enabling you to track participant confidence throughout the process. This example demonstrates how Kala's confidence grew as she deepened her domain knowledge through collaborative modeling. 1/2

Are your team's design sessions with stakeholders more frustrating than finding a semicolon in a haystack after a long day of coding? You see the shining potential of collaborative modeling, but in practice, it feels like herding cats with conflicting agendas. 1/5

It's like everyone arrives at the meeting with shadows, blocking the flow of collaborative modelling sessions. These shadows represent the hurts they carry, the fears they harbour, and the ingrained beliefs that colour their perspective. These unseen burdens can weigh down teamwork, Influe....

Dear CoMo, My team wants to adopt any shiny new framework or tool that pops up. How can I stop this? Ah, the untamable attraction to new shiny things. Personally, I am more drawn to actual shiny things rather than frameworks, but hey you can read my answer here: https://buff.ly/3Pvw8uC

Dear CoMo, My team is brilliant. Top-notch engineers, cutting-edge tools... but they keep getting stuck in these endless design debates, especially when stakeholders get involved! It's like they speak different languages. What's the secret to getting them to actually collaborate? #SoftwareDesign

How can inclusive decision-making and empowering teams lead to smarter outcomes? Join @evelynvankelle.bsky.social , @selketjah.bsky.social , @kenny.weave-it.org and Xin Yao as they explore @collaborative-software-design.com .

The outcomes of design decisions can be deceiving. Decisions should stand on their own, not be judged by what follows. In hindsight, it's too easy to claim foresight. What seems clear now was anything but back then. Avoid the trap of "resulting."

Ever feel caught between planning and action? Or between stability and change? Maybe you’ve debated diving into code versus spending more time modeling. These aren’t just choices—they’re polarities. A thread!

Dear CoMo, There are people in the group who stay quiet all the time. How do I ensure they speak up? This is a question I hear often. The goal of a collaborative session isn’t to make sure everyone speaks— check out why in my new advice column: https://buff.ly/3VA6Uyx

Who are our stakeholder when doing collaborative software design? When you're tackling a complex problem, you don’t just want the right people in the room—you want the unexpected ones too. They aren't always who you think they are, and misconceptions can limit your efforts. Let’s break it down:

Dear Como, can I be both facilitator and participant during an EventStorming session? Ah, the age-old question: Can you be both a facilitator and a participant during an EventStorming session? Check out my next advice: https://buff.ly/3ZAkxAs

When we dive into collaborative modeling, decisions—big or small—are made constantly. Whether it’s placing boundaries in software design, naming domain events, or aligning teams with domains, cognitive biases are always in the room. And you know what? That’s not a bad thing. A Thread!

How can I get people to fully support design decisions and feel included in the process? Wouldn’t it be wonderful if everyone simply agreed with every decision? Check out the latest Dear CoMo: https://buff.ly/3Z5HWYR

Dear CoMo, How can I make contributions of people in meetings more equal? Now that would be the dream, right? Unfortunately, there always seems to be that somebody who takes up the most air time, always reacts first. Sounds familiar? Read all about it: https://buff.ly/4fzgSZ1

Definitely! They are perfect companion pieces, right @kenny.weave-it.org ?

Arrived in the post! I've been having a lot more architectural & advice conversations, sessions and workshops with teams in the last couple of years. I think they've gone well, but I feel a need to level up. This and @facilitatingswarch.bsky.social should help a bit! 🤞

When collaborating on software design, you’re bound to encounter conflicts—it’s almost a given. But here’s the thing: not all conflicts are bad. In fact, many are just task-based disagreements, the kind that naturally pop up when smart people tackle complex problems together. A thread....

Wondering what all the fuss is about collaborative modeling? Let me break it down for you in plain terms. A thread!

Dear CoMo, How can I convince my company or colleagues to start doing collaborative modelling? Getting your company on board with collaborative modeling can be tricky, but the following Dear CoMo column has some clever, low-key ways to start. https://buff.ly/4elvDgA

Last Friday, I shared the very first "Dear CoMo" advice column, tackling the question: "I have this colleague who always takes over meetings and hijacks discussions. What can I do?" Now, we want to hear from you! How would you handle this situation? Drop your thoughts in the comments below.

Imagine a room filled with energy, where participants gather around a table stocked with a facilitator's toolbox full of modeling tools, styles, and heuristics. This toolbox isn't just a collection of items; it's essential for guiding the group toward sustainable design decisions.