Profile avatar
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
441 posts 1,041 followers 621 following
Regular Contributor
Active Commenter

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/

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

I’m seeing it more and more clearly: the way we teach computer science and programming is actually counterproductive to creating the adaptive software that most organizations need to thrive. With the rise of AI, it's becoming undeniable that we're focusing our efforts on the wrong skills. - 1/10

Spend 2-days with @gienverschatse.com last week facilitating domain modelling!

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

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

@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

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.

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

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