Sustain Collective Intelligence with Event Storming

Event Storming builds collective intelligence. We can keep it alive if we continue to work closely together and regularly repeat Event Storming.

By Philippe Bourgau, under CC BY-SA 4.0, high resolution image

Don’t use Event Storming to do upfront design!

Event Storming is an iterative process: design, prototype, test, learn, repeat, etc.

It would  be a shame to stop the momentum once the Event Storming is over. As soon as you leave the workshop, start one of the these:

• Build a walking skeleton if you haven’t already
• Spike a burning question
• Build Proofs of Concepts for critical NFRs
• Refactor core concepts
• Add this $$$ feature

And then return to the Event Storming design board with more knowledge. Focus and risk reduction are the keys to a sustainable pace.

💡 Event Storming builds collective intelligence, work as a mob to keep it alive!

I’ve since written about introducing Event Storming and DDD in your organization: Organization refactoring: Event Storming and DDD injection.

Stay up to date with content and upcoming products

I usually write about 15 minutes worth of reading per month. I won't transfer your email. No Spam, unsubscribe whenever you want.

As a gift for subscribing, you'll receive an illustrated mini-ebook "How to start a team coding dojo"!