EventStorming tools, what is in my flight case!

08 May, 2019

Whenever I give or facilitate an EventStorming training or workshop people always ask me, what is inside your suitcase? What are the essential items I need to do a successful EventStorming? Most importantly what do I need to buy! So in this post, I will give you the EventStorming tools that are in my flight case and where you can buy it!

First of all, for an EventStorming, you can pick any colour you like. I would advise you to stay consistent with doing EventStorming for yourself, the teams and the company. Besides that always use a legend. For myself, I still use the standard colour because that usually is also what people recognise. The following is the picture that explains almost everything, and the colour you generally use in all the types of EventStorming.

Now to save some cost, you can also buy these as a big package. Be aware that you will use more orange than the rest, and this package does not match entirely with the neons. SO you will either end up with a lot more blue, green and pink than with the orange. Or you need to buy orange neons to fill up and then it can happen that the orange colours won’t match. 


The bigger 3×5 inches are hard to find in a separate package, 3m recently changed their offers. So I would go with the following, also greener box, that has all three colours you need; Aggregate or Consistent Business Rule (Yellow), Policy or Eventual Consistent Business Rule (Purple), system (pink):

The only thing we lack now is the small post-it for actors, the little yellow. We have a lot of options too but. Now I also use the small post-its for other concepts like value streaming and arrows voting. Because I use multiple colours I always buy:

If you like more squared post-it, try these:

Extended items

As you might have seen from the picture above, I have more eventstorming tools in my flight case. I give not only EventStorming training but also Example Mapping, Impact Mapping, Domain Story Telling, User Story Mapping, Heuristics Mapping; basically, I mix and match whenever I feel it is needed. For that I have more in the suitcase, here is a list of what I have.

Also, this post is published on my personal blog site.

A lot of knowledge is lost when designing and building software — lost because of hand-overs in a telephone game, confusing communication by not having a shared language, discussing complexity without visualisation and by not leveraging the full potential and wisdom of the diversity of the people. That lost knowledge while creating software impacts the sustainability, quality and value of the software product. Kenny Baas-Schwegler is a strategic software delivery consultant and software architect with a focus on socio-technical systems. He blends IT approaches like Domain-Driven Design and Continuous Delivery and facilitates change with Deep Democracy by using visual and collaborative modelling practices like Eventstorming, Wardley mapping, context mapping and many more. Kenny empowers and collaboratively enables organisations, teams and groups of people in designing, architecting and building sustainable quality software products. One of Kenny's core principles is sharing knowledge. He does that by writing a blog on his website and helping curate the Leanpub book visual collaboration tool. Besides writing, he also shares experience in the Domain-Driven Design community as an organiser of Virtual Domain-Driven Design ( and Domain Driven Design Nederland. He enjoys being a public speaker by giving talks and hands-on workshops at conferences and meetups.
1 Comment
Newest Most Voted
Inline Feedbacks
View all comments

[…] Also, this post is published on the Xebia blog site. […]

Explore related posts