iiinova — where your digital self keeps evolving

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 04/02/2026

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

collaborative-software-design.com

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.

021

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 19/01/2026

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

010

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 09/09/2025

These 'shadows' are a natural part of any group dynamic and can significantly affect how we work together. What are some of the hidden challenges you've encountered in your own collaborative sessions?

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 09/09/2025

@evelynvankelle.bsky.social and @kenny.weave-it.org discuss how a lot of what's going on in a team is like the unseen part of an iceberg. We only see the surface—the ideas being shared—but beneath the waterline are individual perceptions, emotions, and disagreements.

111

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 09/09/2025

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

110

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 04/09/2025

We discussed why we need to move away from rigid handoffs and embrace a more collaborative approach. The conversation explored how to build a shared understanding across teams, which ultimately leads to better outcomes and a healthier work environment.

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 04/09/2025

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.

142

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 10/06/2025

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.

011

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 05/06/2025

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.

000

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/06/2025

If these challenges resonate with your own experience and you're ready to embark on this journey yourself, we invite you to explore our website! - 7/7 collaborative-software-design.com

collaborative-software-design.com

000

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/06/2025

While two days was just the beginning of their journey, it undeniably sparked the right conversations and forged a shared understanding, empowering them to continue on their own. - 6/7

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/06/2025

smaller groups to brainstorm ideal future models. We wrapped up with a 'pro, con, fix' walk-by, not just to highlight differences, but to uncover those crucial similarities – the golden threads that can help untangle a 'Big Ball of Mud' and start extracting those much-needed boundaries. - 5/7

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/06/2025

Well, that's when the value diminishes and the correctness of the software itself becomes suspect, making every change a Herculean effort and dragging down your time to market. Sound familiar? Our workshop kicked off with a full day of Big Picture EventStorming, then shifted to - 4/7

110

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/06/2025

Communication becomes a muddled mess, slowing down vital refinements and leaving everyone scratching their heads. And when the design doesn't truly reflect the domain model? - 3/7

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/06/2025

They spent two intense days with 24 engineers and stakeholders, guiding them through the labyrinth of domain modeling. You see, without those well-defined boundaries, engineers often shoulder an immense cognitive load. - 2/7

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/06/2025

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

120

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 23/05/2025

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

011

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/05/2025

collaborative software design, drawing right from their book. It sounds like an incredibly rewarding few days for them! For anyone interested, I'd gently suggest keeping an eye out for the conference recordings once they're released. There's bound to be plenty of food for thought in there.

000

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/05/2025

extended an invitation for a Team Topologies panel alongside the very bright @lina-plummer.bsky.social, @simon.bvssh.com, Carola Lilienthal, @esilva.net and facilitated by @bitboss.bsky.social . Plus, our authors got to share their passion and knowledge during a talk on ...

120

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/05/2025

lovely mix of humility and sheer excitement bubbling underneath. For one of them, it was even the fulfillment of a long-held childhood dream – isn't that something? We're so grateful to the wonderful team at Agile Meets Architecture who made this happen. And as if that weren't enough, they also ...

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/05/2025

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

120

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 28/04/2025

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

010

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 24/04/2025

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

001

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 22/04/2025

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.

021

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 15/04/2025

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.

141

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 10/04/2025

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

162

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 04/04/2025

In the morning, you’ll have the opportunity to have your book signed, and in the afternoon, you can attend their talk to understand more about collaborative software design and how to facilitate domain modeling decisions.

000

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 04/04/2025

What behaviours are you actually observing? Because sometimes, what appears to be resistance is merely a desire for clarification or a different approach. Why not join Evelyn and Kenny at Agile Meets Architecture today?

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 04/04/2025

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?

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

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

wirfs-brock.com

000

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

By embracing and applying design heuristics, you can gain significant guidance, make more informed decisions, and ultimately steer your team towards more effective and sustainable software architecture. 11/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

This practice will enable you to refine your existing heuristics and cultivate new ones over time, effectively building your own invaluable toolkit of design wisdom. So, dear reader, please don't feel overwhelmed by the intricate nature of software design. 10/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

It's crucial to recognise, my dear, that your personal collection of heuristics will be unique to you, shaped by your individual experiences, observations, and acquired knowledge. It can be immensely beneficial to maintain a record of your insights and reflections following each design session. 9/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

These heuristics can prove particularly valuable when defining bounded contexts, which are specific areas within your software where a particular model and vocabulary are consistently applied and understood. 8/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

> Similarly, give consideration to structuring your bounded context based on the existing departments or teams within your organisation. Their defined responsibilities and areas of expertise can frequently mirror logical divisions within the models. 7/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

> When distinguishing between different bounded contexts of your system, try to organise them according to the language used within the business domain. Discrepancies in terminology used by various teams or stakeholders can often signal the need for different bounded contexts. 6/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

past experiences to address common design dilemmas. Here are a few examples of these helpful guiding principles that can illuminate your design path: 5/12

110

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

undertaking lengthy and exhaustive analyses, particularly when the clock is ticking and timely decisions are paramount. Just as a seasoned artisan relies on instinct and accumulated wisdom alongside precise techniques, software designers can effectively utilise heuristics, drawing upon 4/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

Now, I can almost hear your concerns echoing across the digital waves: won't relying on these so-called "shortcuts" compromise the quality of our work? Rest assured, dear friend, that employing design heuristics doesn’t inherently lead to inferior results compared to 3/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

Think of them as practical rules of thumb or clever mental shortcuts that can significantly assist you when making crucial design choices for your software systems. 2/12

100

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 02/04/2025

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

111

Dear CoMo - Collaborative Software Design @collaborative-software-design.com · 31/03/2025

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

011