After a talk at @jdriven by @tomhier on #EventModeling I'm inspired to explore this method once more. It's a more compelling approach to #DDD than #Eventstorming, even though it shares some fundamental bits. #jdriven

This week, we open sourced our #EventStorming case. Celebrating #DDDEurope, which I’m currently visiting. We have learnt a lot from the community and want to give something back.
https://www.qwan.eu/2025/06/02/ddd-case.html
#dddeu

I've been facilitating the #EventStorming sessions for years now, and something keeps catching my attention.

While teams naturally focus on mapping out those orange event sticky notes (the backbone of any EventStorming session), they often underestimate the power of two critical elements: Hot Spots and Notes.

What I value most about Hot Spots and Notes isn't just how they improve workshops - it's how they change team culture around uncertainty.

In technical discussions, we often feel pressure to know everything immediately.

Hot Spots create permission to say, "I don't know yet" while still making progress. They transform uncertainties from conversation-killers into clearly defined next steps.

I've seen teams evolve from hiding what they don't know to actively hunting for uncertainties as valuable information. Questions become assets rather than liabilities.

If you're incorporating EventStorming into your toolkit, don't underestimate these powerful elements. They might not get as much attention as domain events, but in my experience, they often separate a productive modelling session from a frustrating stalemate.

Read more in the latest #ArchitectureWeekly: https://www.architecture-weekly.com/p/the-underestimated-power-of-hot-spots

What happens if you mix #EventStorming with a Low Code Platform? Christof Heinzel & Alexander Miertsch will take you on a visual modelling journey based on a real use case from a client's project. https://youtu.be/gozEINlnsMg

In #EventStorming Workshops kommen schnell viele Domain Events zusammen – und genau das macht es oft schwer, den Blick fürs Wesentliche zu behalten.


Michael Plöd zeigt in seinem Blogpost, wie sich mithilfe 9 einfacher Heuristiken Pivotal Events erkennen lassen: Ereignisse, die zum Beispiel nachgelagerte Aktivitäten auslösen, Zustände verändern oder wichtige Geschäftsentscheidungen markieren.

🔗 Link zum Blogpost in den Kommentaren. 👇

«CoMo soll das Fachwissen aus den Köpfen der Fachleute in die Köpfe von Entwicklerinnen, Testerinnen, Product Ownern, Produktmanagern und Business-Analysten transportieren»

Collaborative Modeling: Software-Architektur mit den Stakeholdern gestalten | Developer https://www.heise.de/hintergrund/Collaborative-Modeling-Software-Architektur-mit-den-Stakeholdern-gestalten-10371860.html
#CollaborativeModeling #StakeholderEngagement #DomainDrivenDesign #RequirementsEngineering #CoMo #EventStorming #DomainStorytelling #ExampleMapping #UserStoryMapping #Teamwork #ProjectManagement #Projektmanagement

The Application Service is your transactional boundary. It defines the atomic scope of a use case, ensuring all related changes happen together, or not at all.

#DDD #EventStorming #EventDriven

Read more at: https://joebew42.github.io/2025/04/06/growing-systems-towards-ddd-event-sourcing-and-event-driven-architecture/

@marick not me, but thanks to your wikipedia link and @k9ox 's link to #elixir / #erlang behaviours, maybe several things are is starting to fall into place.
FYI I remember @marcevers being keen on DCI, but it didn't speak to me at the time. I now see links with the kind of designs that flow from #EventStorming . And somehow behaviours in #elixir make sense. I was programming a distributed system in #PhoenixLiveView without noticing (until the book pointed it out, that is :-) ) .

New post this week on #eventStormingJournal "Remote Event Storming Made Easy: a Step-by-Step Success Guide" https://www.eventstormingjournal.com/remote%20facilitation/remote-event-storming-made-easy-a-step-by-step-success-guide/ #remote #EventStorming #workshop #facilitation #ddd #domainDrivenDesign

New post today on #eventStormingJournal Remote Event Storming: Your Step-by-Step Preparation Guide https://www.eventstormingjournal.com/remote%20facilitation/remote-event-storming-your-step-by-step-preparation-guide/ #eventStorming #remote #workshop #facilitation

On the way home from a great #EventStorming workshop with Alberto Brandolini (@ziobrando). Learning the method, getting valuable tips about the technique, meeting amazing people is one thing... But when a workshop is this engaging, one's motivation for using the learnings in practice skyrockets.
#ddd

Next Tuesday, March 11, starting at 18:00 we’re holding the #Meetup "Optimizing for Flow & Evolutionary Design" at N26's office.

Check out more information and confirm your attendance at:
https://www.meetup.com/dddbcn/events/306576690/

#DDD #DDDesign #DomainDrivenDesign #DDDBCN #EventStorming #BoundedContext #Subdomain #CollaborativeModeling #CollaborativeModelling #DomainModeling #DomainModelling #DomainDiscovery #XP #ExtremeProgramming #Agile #TeamTopologies #DevOps

2 Meet-Up tips for this week.
The first one is tonight in Berlin. The inventor of #EventStorming is in the house:
Collaborative Modeling Meetup with special guest Alberto Brandolini! Again!

https://www.meetup.com/domain-driven-design-berlin/events/305955494/

And the 2nd one is online on Thursday. A meet-up where we talk about all things #agile / #scrum was organized by Tobias Mayer. Usually, we go very deep and philosophical here. Great likeminded souls:
https://www.meetup.com/de-DE/agile-conversations/events/304075962/

From #EventStorming to tactical #DDDesign in 16 minutes. #EventSourcing is up next.

https://mastodon.social/@VaughnVernon/114074508138424853

How can you effectively facilitate domain modelling decisions? This new book, co-authored by our senior consultant Gien Verschatse, explores techniques and practices you can use to deliver higher-quality software. https://buff.ly/4icNAQS #dddesign #domainmodelling #eventstorming

My sketch note of Alberto Brandolini's talk "Modelling up!"

https://buff.ly/436zUmh

The talk was a bit chaotic (at least for me), which is never good for a sketch note 😅

#SketchNote #EventStorming

New post on #eventStormingJournal today! "#Remote #EventStorming Simplified: 7 Essential Practices" #workshop #facilitation https://www.eventstormingjournal.com/remote%20facilitation/remote-event-storming-simplified-7-essential-practices/

I have the strong opinion that when working with #EventStorming, if you aren't always keeping technology at least in the back of your mind, you won't recognize unreasonable discussions that are impractical or impossible to implement in solutions. There must be a balance between abstract system process thinking and technology. Otherwise, you'll easily slip into esoteric navel gazing.

Segona part de la serie💡 Anatomia d’un refactoring

Avui parlem de:

✅ L’ús d’EventStorming per alinear l’equip i entendre el domini.
✅ Combinació de DDD estratègic i DDD tàctic per dissenyar solucions sòlides.
✅ Les fases d’un equip segons el model de Tuckman.
✅ La importància de la documentació viva amb el framework Diátaxis.

🔗 Català: https://didacrios.cat/comprendre-domini-construir-equip-bases-canvi-2/
🔗 Versió en anglès a https://dev.to/didacrios/understanding-the-domain-and-building-the-team-the-foundations-of-change-ii-4442

#DDD #EventStorming #Refactoring #SoftwareDevelopment

@kenny_baas @ahl @diana @selketjah
so true! Everyone who tried collaborative modeling should know better. But still, in so many companies I worked all these things where done by a single person, working with „requirements“. Which books are you referring to? I might them to my article about #eventstorming