Dear CoMo - Collaborative Software Design
@collaborative-software-design.com
An inside track on how to facilitate domain modeling decisions. Lay out of pragmatic techniques for making collaborative design decisions, ensuring you’re getting a group’s full participation and input to solve real business problems.
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
September 25, 2025 at 2:05 PM
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.
Reposted by Dear CoMo - Collaborative Software Design
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
📅 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
September 9, 2025 at 6:00 AM
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
📅 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 -->
In this video from @amaconf.bsky.social -->
September 9, 2025 at 6:31 AM
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 -->
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.
A while ago @gienverschatse.com and @kenny.weave-it.org went on the Software Testing Unleashed podcast, hosted by @richard-seidl.com.
September 4, 2025 at 6:58 AM
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.
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.
June 10, 2025 at 11:03 AM
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.
Watch and listen to @gienverschatse.com and @evelynvankelle.bsky.social as they explore these very questions.
June 5, 2025 at 11:32 AM
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.
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
June 2, 2025 at 6:20 AM
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...
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...
May 23, 2025 at 3:23 PM
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...
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 ....
May 2, 2025 at 8:44 AM
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...
Read the answer here: collaborative-software-design.com/dear-como/le...
April 28, 2025 at 2:31 PM
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...
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...
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...
April 24, 2025 at 6:30 AM
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...
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.
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.
April 22, 2025 at 9:31 AM
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.
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.
April 15, 2025 at 12:31 PM
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 means something different to everyone! Real autonomy needs clear boundaries and context defined for specific teams/situations. Otherwise, you're just inviting confusion.
April 10, 2025 at 6:30 AM
"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 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?
April 4, 2025 at 6:30 AM
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?
Reposted by Dear CoMo - Collaborative Software Design
And for a web-friendly version see wirfs-brock.com/rebecca/pape...
April 2, 2025 at 6:57 PM
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
Well, my dear, you might find solace in the understanding and application of design heuristics. 1/12
April 2, 2025 at 2:30 PM
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
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...
Ambiguous language in team discussions is a very common problem, find out more here: collaborative-software-design.com/dear-como/am...
March 31, 2025 at 10:35 AM
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...
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
March 4, 2025 at 11:45 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.
February 24, 2025 at 11:45 AM
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
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
February 7, 2025 at 7:34 AM
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
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
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
February 5, 2025 at 3:09 PM
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
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
February 4, 2025 at 11:45 AM
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
Reposted by Dear CoMo - Collaborative Software Design
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
January 31, 2025 at 7:45 AM
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.
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.
January 29, 2025 at 10:36 AM
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.
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.