Kenny (Baas) Schwegler
banner
kenny.weave-it.org
Kenny (Baas) Schwegler
@kenny.weave-it.org
Co-author Collaborative Software Design: How to facilitate domain modeling decisions. Independent consultant & trainer specialised in technical leadership, software architecture, and #sociotechnical systems design. #DDD #TeamTopologies #DeepDemocracy
October 1, 2025 at 7:16 AM
What if you could ditch the prepared slides and adapt your talk to the audience in real time? That's what I got to experiment with yesterday at the Frontify software talks meetup in St. Gallen.

My talk was about technical leadership and facilitating better architectural decision-making. Instead ->
September 19, 2025 at 5:26 AM
I'm looking forward to speaking at the Software Talks meetup at Frontify in St Gallen near Zurich this Thursday. Being back in Switzerland is always a pleasure and I will be talking about Technical Leadership for Architectural Decision Making.

Too often, architectural discussions turn -->
September 16, 2025 at 6:30 AM
Back in a training session today with @evelynvankelle.bsky.social, talking about the book @gienverschatse.com, she, and I co-authored.

Today was all about what surfaces when we tackle software design and architecture challenges. A big part of that is resistance. If we want to make sustainable
-->
September 9, 2025 at 1:21 PM
It's strange to think that patriarchal norms can affect the way we build software, but they do.

I'm happy to share that the article my wife, Vanessa, and I wrote has been published in the @nljug.bsky.social Java magazine. It was our first time writing an article together, and it was...
September 3, 2025 at 9:45 AM
So, imagine this: one complex design problem, four different collaborative modeling tools, four facilitators, and 45 minutes to solve it with a group of 8! That was the intense setup Krisztina, ‪@maxsc.bsky.social‬, ‪@hschwentner.bsky.social‬, and I ran at the DDD Europe hands-on labs.
June 25, 2025 at 9:22 AM
Good news for those interested: my Domain-Driven Design for Product Management course on June 23rd and 24th in Utrecht (in Dutch) is confirmed and running!

Meanwhile, I'm heading to Domain-Driven Design Europe today. - 1/
June 4, 2025 at 6:03 AM
Ever feel like your brain is overflowing when making architectural decisions that impact other teams in the organisation? It's a common challenge, especially as teams become more autonomous. 1/4
June 3, 2025 at 7:18 AM
Teams are part of a larger sociotechnical system. Without a map of this landscape, it's difficult for them to understand the true impact of their architectural decisions on the overall system." This was a core point I dug into during my session at ‪@ndcconferences.com‬ Oslo yesterday, where ... 1/7
May 22, 2025 at 11:19 AM
May 22, 2025 at 8:35 AM
@icooper.bsky.social many people say they do domain-driven design, but only few do responsibility driven design. And there is a disconnect there because the design style of DDD follows RDD by @rebeccawb.bsky.social
May 22, 2025 at 8:33 AM
Something special is happening in two weeks at @dddeu.bsky.social‬. We're running a hands-on session where we'll tackle one problem using four distinct collaborative modelling tools: Domain Storytelling, EventStorming, Wardley Mapping, and Domain Message Flow Modelling.
May 20, 2025 at 6:50 AM
So, last Friday, we wrapped up our 2-day journey into Strategic Domain-Driven Design and Team Topologies. The final day was all about connecting our designs with the sociotechnical systems they inhabit, picking up from where we left off.

We began by employing 1/9
May 19, 2025 at 8:24 AM
Two weeks ago, Evelyn and I delivered a 2-day training on how to facilitate domain modelling or collaborative modelling decisions, grounded in our book. The journey continued this week with Strategic Domain-Driven Design and Team Topologies, and how to become an enabling architect. 1/6
May 16, 2025 at 6:50 AM
I just finished another 2-day Collaborative Software Design training with @evelynvankelle.bsky.social. It always gets me thinking. We push hard for teams to be autonomous, and that also means they design with their stakeholders, not just for them. It makes sense; they know the problems best.

But ..
May 2, 2025 at 10:59 AM
The future requires engineers who excel at understanding and design, leveraging AI as a powerful assistant, not a replacement. Check-out the book I co-authored with @gienverschatse.com and @evelynvankelle.bsky.social collaborative-software-design.com
April 9, 2025 at 2:04 PM
Moving to 'self-organized, stream-aligned teams' with Team Topologies, but then refusing to let those teams pick their own opportunities? Instead, just handing them solutions from product or designers, or messing with the team structures yourself?
April 2, 2025 at 6:13 AM
Today, I'm starting another round of Domain-Driven Design training with software teams. When designing how information flows through our systems, collaborative modelling is key. User experience influences software architecture, while technical decisions—
March 31, 2025 at 7:30 AM
Wannabe? Maybe just a little bit! My Spice Girls shirt yesterday at @fastflowconf.bsky.social might have hinted at the spirit of our closing keynote with the brilliant @evelynvankelle.bsky.social : "Autonomy, is that what we really want? Really Really want!"
March 28, 2025 at 8:23 AM
Doing another Foundational Domain-Driven Design for Software Teams training this week. I've probably run this thing around 50 times over the last six years, always trying to improve it. But honestly, I'm still amazed every time by the creative ideas people come up with. 1/4
March 18, 2025 at 12:46 PM
Day two of @evelynvankelle.bsky.social and my deep dive into Domain-Driven Design, Collaborative Software Design, and Software Architecture. We've been putting EventStorming to work, really honing in on user needs and how they shape our design and inform software models. 1/2
March 11, 2025 at 9:03 AM
Fast Flow conf in the Netherlands? Three weeks! Really looking forward to closing it out with Evelyn, showing off the latest take on our Autonomy talk. We've done this thing a lot over the past four years, and it's always evolving. New stuff we've figured out, new stories.. you know how it goes.1/3
March 6, 2025 at 11:45 AM
If you discuss how the software should work, you're designing it. Whether you write 'requirements', only use the software, or just chat about what you need doesn't matter. And if you don't realize you're designing, you'll end up with a mess that does not help yourself or the company.
March 5, 2025 at 9:50 AM
Autonomous teams" sound great, but they need to understand their impact on the bigger picture. Otherwise, you've got a bunch of teams going their own way – and, as Fleetwood Mac might say, you can go your own way, you can call it another lonely day!

1/5
February 27, 2025 at 12:45 PM
Want to dive deeper? Check out the book on our website: https://buff.ly/3CpzrAp
February 14, 2025 at 7:13 AM