We often assume that once a team has a diagram, they have a shared understanding. It's only when someone starts asking basic questions that the diagram starts to fall apart. Read, Listen or Watch more of @vanessaformicola.bsky.social her story: buff.ly/aOIQ7uj

Most decisions in software teams don't fail because people disagreed. They fail because people thought they agreed, but they didn't, and nobody found out until much later. virtualddd.com/facilitating...

There is a version of career progression that looks like success from the outside and feels like a slow erosion from the inside. You attend more meetings, write less software, and someone asks if you'd like to become an architect. Read, Listen or Watch the full story by Larissa here: buff.ly/99BtmNJ

There's a pattern that turns up in almost every struggling team. The problem gets named as a technical one, the technical fix gets applied, and nothing actually improves. Listen, watch or read about @mathiasverraes.bsky.social and many more of our @dddeu.bsky.social special stories! buff.ly/lWZiNoX

There's a certain frustration that comes from doing everything right, by the book, and still watching it fail. Not because the methods were wrong, but because the real problem was somewhere else entirely. Watch, Listen and Read @heimeshoff.bsky.social his full story: buff.ly/6bJ9wv4

We've all been in that meeting. Someone senior has already decided on a solution — maybe they read something, maybe a vendor pitched it to them — and now the conversation isn't really about the problem anymore. Read, Watch, Listen to Kim who shares how he dealt with this situation: buff.ly/xJVD0Hv

If someone brings up an alternative and you're like oh no, that's a horrible idea think about okay what assumptions may this person be making that are not being clarified. Listen, Read or Watch to @noctovis.bsky.social explaining how this and more can make for better conversations: buff.ly/F8qaXIw

There are many architecture workshops that help you figure out which bite-sized microservices you should extract from monoliths. But with everything else, you need to understand what it is you're working with before you start working with it. Check Aino Vonge Corry full story here: buff.ly/PQOgn3z

There's no such thing as a one-size-fits-all methodology like Agile, Scrum, Lean, or Six Sigma. It doesn't matter whether you're talking about project management or financing a system. Read, Watch or listen to the full story from Simon Wardley here: buff.ly/Etr9aHT

The fact that you as an individual can make a mistake, indicates that there's some kind of systematic flaw on the system. Watch, listen or read the full story from @lizthegrey.com here: buff.ly/TvVOw2m

We tend to focus on the events. There's a bug in production, but not the fact that every system is designed to get the results it gets. We have to be able to see how we are generating the outcomes we don't want. Watch, Listen or Read Diana Montalion her Story here: buff.ly/uyOhyQA

The loudest voice in the room isn't necessarily the problem — it's what the environment and culture do with it. Watch, Listen or Read @gienverschatse.com her story on "When the Loudest Voice in the Room Architects Your Future" here: buff.ly/p65Td6F

Power dynamics don't disappear in design sessions. They just go underground — and they kill collaboration. Evelyn talks about what to do when hierarchy gets in the way of good design. buff.ly/vkfW1Vb

In last week's story, @settling-mud.bsky.social told us a very relatable story when everyone seemed to agree, but nobody acted. What would you do? Watch, Read or listen to it here: buff.ly/JX3e6Y4

Beija Nigl on what happens when workshop goals don't align—and how it led to creating the Collab Prep Canvas. Check out her latest story here: buff.ly/YVpf1Kg

Our new story on Facilitating Architecture & Design explores with @bitboss.bsky.social on "Modernizing with Respect." Discover how empathy for those behind legacy systems turns resistance into collaboration. Essential for anyone leading change. Read more: buff.ly/PuRqzMn #DDD #Architecture

We've scheduled a session! @rebeccawb.bsky.social & @mathiasverraes.bsky.social will discuss 'Critically Engaging with Models'. Learn to evaluate models and their limitations. Pre-reading their essay advised. Jan 28, 8 PM CET. buff.ly/LXXZsu2

When you step into a leadership role, even unintentional misuse of power and authority can cause someone significant embarrassment and shame. Listen to @paulrayner.bsky.social talking about his experience when that happened and how he dealt with it. buff.ly/rM5OnmB

New story on Facilitating Software Architecture & Design! @paulrayner.bsky.social shares a crucial lesson on the hidden weight of rank & unintended impact during team improvement sessions. Understand power dynamics. Read more: buff.ly/rM5OnmB

If you feel that your goal is to be right, then you are wrong. Listen to Kristzina talk about her experience as a facilitating architect!

New on Virtual DDD: The cost of "the simplest thing to do". A 1-day task became an 8-month fix. Krisztina Hirth's story on architectural intervention, domain events, and letting teams learn through experience. Read more: buff.ly/clfEmYA

Going from an autocratic to a facilitating software architecture will eventually get you in that situation where you think the decision is wrong. Check out our latest story from Pete talking about how he handled that situation buff.ly/dsMhasl

What happens when an architect disagrees with a team's decision? The first instinct is often to correct them. But perhaps the first question should be inward: "Was my advice good enough?" A new story on shifting from control to influence. Read more: buff.ly/dsMhasl

Getting your first advice on an ADR can be very scary, but we recently had Elena Stojmilova tell how she managed and forever changed the way they made Architectural Decisions moving forward. Check it out in our latest episode: buff.ly/CIrHDu3

We've scheduled a fireside chat on BDD Automation Patterns with @sebrose.bsky.social & Gáspár Nagy. They'll share insights gained while co-authoring "Effective BDD" and exploring pattern authoring. 25 November, 17:00 CET. buff.ly/gnTD4X8

How do you empower teams to own architectural decisions? A story from Elena Stojmilova on the cultural shift from navigating a sea of opinions to a mature process of constructive advice. Read more at buff.ly/CIrHDu3

Next Tuesday, we will have a new Story of Facilitating Software Architecture & Design. Until then, you can check out our latest story on Governance, where @roundcrisis.com shares her story. Find us on YouTube, every major podcast platform and our own website as a blog post: buff.ly/kixklbb

An incident decision is reverted, causing team frustration. Our new story explores the socio-technical fallout of post-incident governance and how to build trust through clearer processes and supportive leadership. Read more: buff.ly/XEvsHVB

When faced with architectural indecision, what’s the right way to move forward? Dive into the full conversation on our latest episode of "Stories on Facilitating Software Architecture and Design," and hear more insights on navigating these tricky situations. Full episode: buff.ly/N5wWqny

When a team is silent on a key architectural choice, don't force it. A powerful alternative is asking for their consent to decide for them. Our new story explores this technique for navigating indecision and unblocking your team. Read more: buff.ly/N5wWqny