Event Storming through the eyes of a non-technical domain expert
A Q&A with business domain experts who took part in an actual Event Storming session: whether they found it useful and what they learned from it
A while ago, we launched a Domain Driven Design initiative at our company. Its aim is to share our knowledge of and experience with DDD, along with the many complementary tools and techniques we routinely apply on clients’ projects.
After searching for a problem and a domain that would work well as a showcase, we chose one of the processes our administration department handles every day – managing resources/equipment within our company. It looked moderately complex (neither too simple nor too complicated, so that readers could follow it), which made it a good fit for the task.
We began by reaching out to our colleagues from the administration department and letting them know what we had in mind. Once they agreed to join, we scheduled the first Event Storming workshop session to get the project going.
After wrapping up our workshops, which spanned three sessions, we asked our domain experts how they felt about the sessions and what impressions they took away – feedback that was especially valuable since both of them were new to the Event Storming technique and the practices surrounding it.
Below is a Q&A with two colleagues who work in our administration dept and kindly agreed to act as our domain experts for this project
Having completed your very first Event Storming session, how do you feel about the process and its goals (both the expected and the achieved ones)?
Expert A:
It was a genuinely interesting and refreshing experience. Work in the administration department tends to be fairly repetitive, so this was an opportunity to try something new, outside our area of expertise. Even though I roughly knew what to expect beforehand, I did not anticipate that we would go into such detail on the process we chose to model. I had no idea that something that looked obvious and trivial to us in administration could turn out to be so complex. The session also helped us spot gaps and missing pieces in our current process.
Expert B:
For me it was an entirely new experience, since it was the first Event Storming session I had ever taken part in. I was convinced the process we picked was so trivial and straightforward that a single session would be enough. I could not have been more wrong – the process proved so complex that it took several more sessions to work through and explore it.
What did you know before the session? Did you need to prepare for it in any way?
Expert A:
I knew very little about Event Storming workshops. I had read a handful of high-level articles online, but I was not really sure what to expect. My only preparation was brushing up on my domain vocabulary in English, because in our daily work we use our native language – that was all.
Expert B:
The colleagues who started and led the workshops kindly sent us a few links to articles explaining the basic “why and how” of Event Storming, and that was it. Apart from that, I knew nothing before the session.
What did you think of how the session was structured and facilitated? Were you comfortable during it?
Expert B:
I felt at ease throughout all the sessions thanks to the safe and professional environment we built together. Any question could be asked and got an answer, and any idea could be put forward and taken into consideration.
The introduction the facilitator gave at the start was extremely valuable, because it laid out clearly what we would be doing step by step, what would come next, and so on. He was driving and updating our Miro board, so it always reflected our current state of knowledge.
The regular mood checks were spot on: they let us monitor how attentive we were, and whenever focus began to slip, a short break was called so we could catch our breath and concentrate again.
Expert A:
My impression is that every session was well structured and organized. We moved smoothly from one stage of the workshop to the next, and everything was run in a way that made it easy to understand where we were and what was coming next. I was slightly concerned that the session might feel formal, but that concern proved completely unfounded – the workshops ran smoothly in a friendly atmosphere. Still, the sessions were tiring, since getting the best results demanded a lot of focus and engagement.
One small thing I found especially helpful was the practice of regularly checking how all the participants were feeling during the session. It might seem like a minor detail, but it proved really valuable and meant we took breaks exactly when we needed them.
What pleasantly surprised you about the session?
Expert A:
Definitely the fact that the sessions turned out to be really engaging. I was convinced it would be just another dull workshop – after all, it was about our own work, so what could be exciting about that?
Expert B:
Long, tiring and fairly demanding as they were, the sessions were truly engaging and interesting. I was happily surprised that our colleagues from engineering showed real interest in the process and genuinely wanted to learn and fully understand it.
What were your key takeaways from the session?
Expert A:
Although we believed we knew the process well, we managed to find some gaps in it that had never caused trouble before but could easily surface in real life. It also revealed that some areas had never been spelled out explicitly, and at times we depended on tribal knowledge that was not documented anywhere.
Expert B:
A side effect of the workshops was the discovery that our processes might be lacking some steps or flows and needed a careful review to make them more complete.
What drawbacks or negative findings did you notice regarding the product/business process and the session in general?
Expert A:
Nothing comes to mind as far as the workshops themselves go. A note to self: get proper equipment for online workshops like these. During such engaging sessions, the last thing you need is your laptop and conferencing software lagging so badly that you can no longer follow the board and keep dropping out.
Expert B:
I did not notice any drawbacks, nor did I come across anything negative during the session.
Has the session changed the way you see the business process you discussed?
Expert A:
As I mentioned earlier, I did not expect the process we were working on to be so complex, with so many intricate points and quirks.
Expert B:
Having analyzed our process, I wish it had at least some automation, because the session revealed that it is more complex than we thought and could benefit a great deal from cutting down on manual work.
How do you view such close collaboration between stakeholders and IT when building software products? Do you think sessions like this are worthwhile?
Expert A:
Workshops like these are enormously valuable when building IT systems for any sort of complicated business problem. To the people who carry out these processes every day, they may look simple and trivial, because they know them inside out and are accustomed to them, but a closer analysis shows that outsiders find them harder to grasp and that they are not so easy to model.
In my view, when such sessions are run well, they give a much better chance of building the right product than a mere list of “product requirements” written down in a document.
Expert B:
Running sessions like these is very valuable. The main goal is for engineers to discover and understand what users need, so that later they can build the right thing – one that serves precisely the purpose of solving the problem it is meant to solve. There will be no bells and whistles that customers pay for (or at least have to wait for due to development time) and then never use. Everyone wins.
Wrapping up
In the Q&A above, our two colleagues offered invaluable insights into what Event Storming can do and shared how they experienced the workshops as non-technical first-timers. Their path through the sessions as domain experts uncovered subtleties and complexities hidden in processes that seemed simple, highlighting the importance of deeper analysis and understanding before plunging into coding. Looking at the benefits they describe, it is evident that such workshops provide a way to build software solutions that fit business needs well.