Stories on Facilitating Software Architecture & Design
Virtual Domain-Driven Design
Outreach Signals
Publishing Details
About This Podcast
Podcasting 2.0 Features
Explore Statistics
Recent Episodes
They Knew the Answer Before They Understood the Problem
We like to think architecture starts with a problem. But often, by the time we're brought in, someone has already chosen the answer — and the real work becomes figuring out how to slow things down…
We Spent Years Improving the Wrong Thing
We like to believe that if we do everything right — bring in proven methods, hire experienced people, build the feedback loops — then the system will eventually bend toward better. Marco Heimeshoff…
Everyone Had an Opinion But Nobody Changed Their Mind
We've all been in that meeting. Someone proposes a solution, someone else proposes a different one, and within minutes the room has split into camps. People stop listening and start waiting for their…
Why Drawing the Same System Reveals Different Architectures
We often assume that architects working on the same system share the same understanding of its structure. They're looking at the same code, attending the same meetings — surely they see the same…
When Method Wars Hide the Real Problem
We fight about Agile versus Six Sigma, build versus buy, in-house versus outsourced. We pick our camps and defend them with the certainty of people who've never mapped the territory they're fighting…
When Fixing an Outage Means Staying Out of the Way
We often assume that resolving a major outage requires centralised command and control—getting the right experts in a room, coordinating their efforts, and directing the recovery. But what if the…
When Explaining More Isn't the Answer
We often assume that when people resist a new architectural direction, the answer is to explain better — clearer diagrams, more detailed documents, another walkthrough of the rationale. Diana…
When the Loudest Voice in the Room Architects Your Future
We often assume that bad architectural decisions come from bad architects. But what if there are no architects at all—just a team of software developers trying to do their best, with no one in the…
The Slow Clap That Killed the Workshop
We often assume the hardest part of facilitation is designing the exercises. But what happens when hierarchy doesn't just shape the conversation — it physically stops it?That's the story Evelyn van…
When Everyone Agrees But Nobody Acts
We often assume that once we get everyone in a room and reach agreement on an architecture, the hard part is over. But what happens when the workshop goes perfectly, everyone nods along, puts their…
Misaligned Expectations: When Goals Don't Align
We often assume that once we get everyone into a room for a collaborative modeling session, the hardest part is over. But what happens when you discover—just 48 hours before kickoff—that the person…
Modernizing with Respect: Acknowledging the Best Intentions Behind Legacy Code
We have all been there: you walk into a new client engagement ready to implement modern patterns, only to find a tangle of a 20-year-old legacy system and a wall of resistance from the existing…
The Hidden Weight of Rank: How Well-Intended Improvement Sessions can Drive Teammates Away
In this episode of Stories on Facilitating Software Design and Architecture, we are joined by Paul Rayner, a seasoned consultant and expert in Domain-Driven Design and EventStorming. Paul shares a…
The true cost of "The simplest thing to do"
In software architecture, there is often a difficult tension between enforcing best practices and allowing teams the autonomy to learn through experience. One of the most common pitfalls in…
The Architect's Dilemma: What to Do When You Disagree With a Team's Decision
In this episode of "Stories of Software Architecture and Design," hosts Kenny (Baas) Schwegler and Andrea Magnorsky welcome back guests Elena and Pete to discuss the challenges of managing team…
The Path to Team-Led Architecture: From Opinions to Advice
Welcome to a new episode where we share stories from the field. For the first time, we're thrilled to welcome guests to the show!This week, we're joined by Elena Stojmilova, Technical Lead at Open…
Decision, Reversal, Frustration: Navigating Governance After an Incident
The episode explores the tension between necessary on-the-spot decision-making during a software incident and subsequent organizational governance. Andrea’s story sets the scene: a colleague makes a…
Navigating Architectural Indecision: What to do when teams stay silent
In this episode Andrew Harmel-Law, Kenny (Baas) Schwegler, and Andrea Magnorsky discussed the difficulties of facilitating software architecture decisions, particularly when teams are hesitant to…
Uncovering the Ghost Decisions in Your Architecture
In this episode, Andrew Harmel-Law, joined by Andrea Magnorsky and Kenny (Baas) Schwegler, discusses "ghost decisions," which are fundamental architectural choices that are often undocumented,…
The Reality of Systems Change: Facilitating Architecture with Transparency
In this episode, Kenny and Andrea discuss how to move from a blocking, "ivory tower" or hands-on architect role to a more facilitating one. They explore the importance of transparency as a first step…
Frequently Asked Questions
Stories on Facilitating Software Architecture & Design has published 15 episodes since November 2025, covering topics in Business, Management.
Stories on Facilitating Software Architecture & Design is currently highly active with new episodes every 2 weeks. Average episode length is 25m.
