Sign in

Kenny (Baas) Schwegler

@kenny.weave-it.org
1.2K followers 631 following 919 posts

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

PostsRepliesMedia
Kenny (Baas) Schwegler @kenny.weave-it.org · 05/10/2026
How do you keep a culture of team autonomy while scaling, without losing coherence? That's what we've been working on at DHL eCommerce Benelux for the past years. This Wednesday Marc Rooding and I tell the story at Digital Architecture Design Day >>>
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 30/08/2026
@nick-tune.me I know you like Ananas aka Pineapple on pizza. But have you tried this dutch person's recipe of Banana and pineapple pasta with Curryy Pineapple sauce?
120
Kenny (Baas) Schwegler @kenny.weave-it.org · 31/07/2026
Subdomain, bounded context, service. Three boundaries, drawn by different people, for different reasons. The pain is rarely picking the wrong one. It is picking one and assuming the other two came for free.
240
Kenny (Baas) Schwegler @kenny.weave-it.org · 08/06/2026
That tension is also why I was grateful to be pulled onto a panel by Fancy Karolina Tóth on mental health with @marianhartman.bsky.social and @jpelrine.bsky.social, talking about how collaborative software design, sociotechnical systems and decision-making affect how we actually feel at work. >>>
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 08/06/2026
We asked the audience in one of our talks how much their organisation prioritises coaching, training and mentoring. 27 people answered. The average was 3.8 out of 10. Small sample, probably biased by the room. But it matches what I keep seeing elsewhere. >>>
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 08/06/2026
Almost no one is checking the outcomes: what that output actually does, how it changes the team socially, and whether anyone is still teaching people and hardening their engineering disciplines. >>>
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 08/06/2026
And the place we keep landing is the same one too: we should be focusing on understanding our customers and our domain. The deep work. The things domain-driven design has been pointing at for over 25 years. >>>
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 08/06/2026
Last week I was invited to Craft Conf to give two talks with Evelyn van Kelle. Fourteen years ago the conversation was about lines of code and SonarQube KPIs. This time it was token maxing and doing half the work with AI. Same song, different instruments. >>>
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 19/05/2026
At @dddeu.bsky.social this year, Krisztina Hirth, @maxsc.bsky.social, @hschwentner.bsky.social and I are running a hands-on session where groups each tackle distributed systems integration using a different collaborative modelling approach >>>
111
Kenny (Baas) Schwegler @kenny.weave-it.org · 21/04/2026
I recently asked a room of practitioners: "How much are you involved in architectural decision making?" The average was 7 out of 10. Sounds good right? Then I asked the same group: "What is software architecture?" >>>
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 17/04/2026
The biggest blocker to teams making intentional software architecture decisions isn't technical complexity. It's not knowing whether they're allowed to decide. Last week at AI Native Amsterdam I talked about facilitating software architecture while AI agents write the code. >>>
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 24/03/2026
The speed at which AI agents write code is no longer the bottleneck. Whether we understand what that code is actually doing, that's where it gets interesting. On 7 April I'll be speaking at the AI Native Netherlands meetup at the Miro offices in Amsterdam. >>>
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 16/03/2026
Everyone is talking about how AI will change the way we build software. Almost nobody is talking about what was already broken before it arrived. >>>
111
Kenny (Baas) Schwegler @kenny.weave-it.org · 09/03/2026
As per usual practice, we are finalising our slides on the train, one day before @amaconf.bsky.social kicks off in Berlin. The talk is about debiasing your software design decisions and the structured interventions you can take to counter them. ...
161
Kenny (Baas) Schwegler @kenny.weave-it.org · 06/03/2026
Here's something worth sitting with: a product owner deciding "the user should never have to re-enter this information" is making an architecture decision. A domain expert saying "that data doesn't belong here" is making an architecture decision. They just don't always call it that. ...
210
Kenny (Baas) Schwegler @kenny.weave-it.org · 05/03/2026
First day of another DDD foundation workshop, and we hit the wall that almost every team hits: naming. Not "what should we call this?" — that's the surface question. The deeper one is: how much does a name already decide for you? ...
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 03/03/2026
Came across this take recently: "How long until the DDD community realises AI/LLM assisted programming is still DDD, but you no longer need to do the actual implementation, just document & validate it?" We already do. The bounded context pattern is still very much valid. ...
131
Kenny (Baas) Schwegler @kenny.weave-it.org · 02/03/2026
After 2 years consulting DHL eCommerce BeNeLux, I've decided to join them as software architecture enabler. The reason? I'm simply not done yet. And I wonder if I ever will be. ...
2140
Kenny (Baas) Schwegler @kenny.weave-it.org · 26/02/2026
We started day 2 of the Tactical DDD training this morning, not with coding, but with discovering and formalising acceptance criteria through Example Mapping. These acceptance criteria then become input for domain modelling with responsibility-driven design through CRC-card modelling. ...
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 25/02/2026
I usually kick off my tactical DDD training with this flipchart exercise, because there's a misconception I run into time and again: people confusing monoliths with big balls of mud. ...
141
Kenny (Baas) Schwegler @kenny.weave-it.org · 19/02/2026
@evelynvankelle.bsky.social and I are speaking at @amaconf.bsky.social 2026, and we've been sitting with a question that keeps coming up in our consulting work: when a design choice just feels right, how do you know whether that's genuine insight or a cognitive bias in disguise? ...
251
Kenny (Baas) Schwegler @kenny.weave-it.org · 11/02/2026
A friendly reminder that developers using agentic AI just add an abstraction onto this. At least a developer writing their own code still roughly understands the model they're writing. With Agentic AI, they don't and critically engaging with the model dilutes even more, and the model drifts more
0247
Kenny (Baas) Schwegler @kenny.weave-it.org · 14/01/2026
Many Product Owners view software architecture as a technical concern, something strictly for the developers. Yet, the boundaries of a software system are often defined by business decisions and language, not just code. ...
260
Kenny (Baas) Schwegler @kenny.weave-it.org · 10/12/2025
There is a persistent friction in design sessions where facilitators conflate equal speaking time with equal contribution. The goal of collaborative modelling isn’t to ensure everyone speaks the same amount; it is to ensure that everyone’s knowledge is effectively placed on the table. ...
130
Kenny (Baas) Schwegler @kenny.weave-it.org · 08/12/2025
During a training session with tech leaders today, a familiar friction point regarding architecture decision-making surfaced. Participants consistently observed that architects operating outside the teams are perceived as controlling and micromanaging. This behaviour often stems from a paradox. ...
131
Kenny (Baas) Schwegler @kenny.weave-it.org · 18/11/2025
The name you give a Bounded Context isn't just a label—it's the critical foundation that frames your entire DDD modelling conversation. Day 1 of my Domain-Driven Design training was dedicated to EventStorming and distilling Bounded Contexts using Context Mapping....
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 01/10/2025
010
Kenny (Baas) Schwegler @kenny.weave-it.org · 19/09/2025
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 ->
153
Kenny (Baas) Schwegler @kenny.weave-it.org · 16/09/2025
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 -->
120
Kenny (Baas) Schwegler @kenny.weave-it.org · 09/09/2025
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 -->
130
Kenny (Baas) Schwegler @kenny.weave-it.org · 03/09/2025
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...
275
Kenny (Baas) Schwegler @kenny.weave-it.org · 25/06/2025
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.
184
Kenny (Baas) Schwegler @kenny.weave-it.org · 04/06/2025
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/
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 03/06/2025
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
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 22/05/2025
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
100
Kenny (Baas) Schwegler @kenny.weave-it.org · 22/05/2025
010
Kenny (Baas) Schwegler @kenny.weave-it.org · 22/05/2025
@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
161
Kenny (Baas) Schwegler @kenny.weave-it.org · 20/05/2025
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.
151
Kenny (Baas) Schwegler @kenny.weave-it.org · 19/05/2025
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
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 16/05/2025
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
120
Kenny (Baas) Schwegler @kenny.weave-it.org · 02/05/2025
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 ..
182
Kenny (Baas) Schwegler @kenny.weave-it.org · 09/04/2025
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
010
Kenny (Baas) Schwegler @kenny.weave-it.org · 02/04/2025
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?
141
Kenny (Baas) Schwegler @kenny.weave-it.org · 31/03/2025
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—
180
Kenny (Baas) Schwegler @kenny.weave-it.org · 28/03/2025
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!"
162
Kenny (Baas) Schwegler @kenny.weave-it.org · 18/03/2025
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
140
Kenny (Baas) Schwegler @kenny.weave-it.org · 11/03/2025
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
110
Kenny (Baas) Schwegler @kenny.weave-it.org · 06/03/2025
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
120
Kenny (Baas) Schwegler @kenny.weave-it.org · 05/03/2025
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.
121
Kenny (Baas) Schwegler @kenny.weave-it.org · 27/02/2025
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
131