21 More Event Storming Tips - part 3 - Anti and Meta Patterns

3 minute read

Even more Event Storming tips! 3 will help you to avoid the mistakes we did. The last 2 are the recipe to learn more tips by yourself!

ℹ️ NOTE: Part of this post has been republished and updated on the Event Storming Journal blog

Drawing of a mistake and a T-shirt pattern with the writing 'More Event Storming Tips' above

This was the last of a 3 posts series compiling Event Storming best practices. The previous post contained tips about facilitation and dealing with existing code. If you haven’t you might also start by the beginning!


As we tried variations around Event Storming, we also learned from our mistakes. Here are a few:

17. Adding special post-its

Before getting Alberto’s advice about logging decisions, we tried to use custom post-its. That did not work well. Event Storming already has a pretty large post-it bestiary, adding more is too much. Plus, it’s almost impossible to find a post-it color that is not already used!

Picture of a guy in front of a wall full of sticky-notes and with a large sticky on his head too! Event Storming already has a complex post-it bestiary, adding a new one is not a good idea.

When we tried this, people ignored these post-its. They made decisions but did not record them.

18. Remote participant

Our company is over 3 main offices: Beirut, Dublin, and Paris. With this constraint, organizing an Event Storming is often a mess. We have to bring some key people from different cities to the same office. Sometimes, we have to delay a workshop for a few weeks because a single person is missing!

I heard good feedback from remote-robots at a conference. We thought we could give it a try for Event Storming. The idea was:

  1. Pair up the remote participant with someone in the room
  2. Let the remote attendee contribute through his robot-avatar

We could not pay for a robot without being sure it would work. We tried to hack one with a moving speaker desk and a laptop… This was a disaster! The only outcome was that the poor remote-guy ended-up with a headache…

Drawing of a dismounted robot. Our tentative to hack-up a robot avatar for a remote participant failed misearbly... We don't have a good recipe for remote participation to Event Storming workshops yet

Up to now, we did not find a satisfying way to run an Event Storming with remote participants.

19. Big Design Up Front

Event Storming is a design activity. Like any design activity, we risk pushing it too far. I wrote that it works best as a tool to do a Rough Design Up Front.

You can always add more refinement to your design. I’m sure you could spend a full week doing detailed Design-Level Event Storming. Though that’s not how it’s meant to be.

You’d have better results by:

  1. Drafting just enough to get started
  2. Building something
  3. Learning from it
  4. Repeating
Drawing of an infographics of the Event Storming loop: Devs meet domain experts -> Grow collective intelligence superpowers -> Make complex decisions in a short time -> Try for real -> Learn -> Devs meet domain experts -> ...
By Philippe Bourgau, under CC BY-SA 4.0, original and high resolution image


Here are 2 extra ‘meta’ best practices about Event Storming.

20. Create an Event Storming community of practice

Spreading Event Storming in a small organization is straightforward:

  1. Get everyone in
  2. Make it a success
  3. You’re done!

It’s a lot more complicated in large organizations. Building a community of practice helped us a lot.

We started ours as I animated a training about Event Storming to other people in the company. We ended this training with time for open discussions. This was the first ‘community’ meetup.

We then created a wiki space and a chat channel. We used them to exchange best practices and experiences around Event Storming. It’s a great way to learn from each other. It’s also very encouraging to hear other’s success stories.

21. Ask Alberto!

You might have noticed that some of these best practices come from Alberto Brandolini. I don’t know Alberto in person, but he’s kind enough to answer my naïve questions on Twitter. So I guess he would answer your questions too!

Run your own!

Event Storming is a magic workshop that unlocks complex decision making in a short time! It can help you with:

Running an Event Storming is rather simple once you get the hang of it. The trick is to get started! Find a forgiving audience, and follow the guide.

I hope these tips will help you along your Event Storming journey. Whenever you discover your own tips or anti-patterns, take a minute or so to share them with a comment!

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"!

Leave a comment