Well, well, well, job description woes? Who needs permission to model effectively? Master Secret & Guerrilla Modelling! Sketch silently, ask sharp questions, then watch collaboration naturally unfold. Prove its worth, not just your role. Read the full advice: buff.ly/84Wsoev XoXo CoMo

I would love to do collaborative modelling, but I am not allowed to do so because it does not fit in my job description

Job description blocking collaborative modelling? Learn Secret and Guerrilla Modelling to start collaborating visually, prove its value, and grow your influence.

collaborative-software-design.com

Well, well, well. Stuck between neutral facilitator and screaming expert? The "Hat Switch" is your key! Declare: "Architect hat ON, now OFF." Share critical insights without manipulation. Keep the team driving, not blindly crashing. Read the full advice: buff.ly/VaqNSGc XoXo CoMo

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.

How many people should I invite for a collaborative modelling sessions? - Collaborative Software Design

Worried about how many people to invite to your collaborative modeling session? Dear CoMo explains the sweet spot for group size, from discovery to decision-making, to ensure your team's success.

buff.ly

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

Everything you ever wanted to know about anarchy (but were afraid to ask) - Andrew Harmel-Law

“Patterns of Anarchy” is a collection of writings published in 1966. We should care about it as software professionals because a) Christopher Alexander quotes from it in “A Pattern Language” and b)…

buff.ly

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...

Dear CoMo - Collaborative Software Design@collaborative-software-design.com · last yr.

Check-out @rebeccawb.bsky.social her paper called Traces, tracks, trails, and paths: An Exploration of How We Approach Software Design: wirfs-brock.com/PDFs/Traces,...

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

Collaborative Software Design: How to facilitate domain modelling decisions

This talk delves into the challenges of collaborative software design, where developers and stakeholders work together to make sustainable design decisi…

buff.ly

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