Organization refactoring: Event Storming and DDD injection - part 1
Injecting DDD or Event Storming in your organization can be tricky. Here are techniques to onboard your domain experts, one step at a time!
A few months ago, I received an email from my friend Bastien asking for help around Event Storming. He had injected some tactical DDD (Domain Driven Design) in his development team:
- They were now using Value Objects
- They had separated the domain from the infra code
- They were already moving on to other DDD patterns
To continue his DDD injection, he needed to onboard domain experts. He also wanted to draw a better context-map of his system. His question was, “How to get domain experts to take part in an Event Storming?”
As we discussed, we found 3 steps I had used to inject DDD and Event Storming at Murex.
1. Practice yourself first
I wrote it before: running an Event-Storming workshop is not rocket science. Still, it requires a bit of practice to get right.
💡 Don’t waste your chances with not enough preparation!
Imagine you persuaded your domain experts to spend 8 hours in an Event-Storming workshop. Now imagine the workshop is a failure because of lousy facilitation. You’ll have no second chance!
Practice short sessions first!
- Read a guide
- Try it with a few colleagues on a sample startup business
- Use it on your development process to find improvements
- You can use it as onboarding for newcomers. Do it within your team, playing roles.
This last trick can raise many questions to ask your domain expert. You could even use the onboarding excuse to lure a domain expert in the workshop!
2. Start with your current tasks
It’s challenging to get domain experts to sign in for a 2 days workshop. It’s a lot easier to have a 15 minutes chat with them!
Next time you have a domain question about your current task, ask the experts! You’ll learn about the domain, and you’ll start to build a relationship with them.
You can even use this technique to inject a bit of Example Mapping! Example mapping is a simple conversation format. Practice it a few time with your teammates, and you’ll be ready to use it with your domain experts.
Example mapping is handy in understanding domain rules. Domain savvy developers become trustworthy in the eyes of the domain experts.
💡 Hijack a conversation with a domain expert into an Example Mapping.
The key is to have these conversations as often as possible. With time, a trustful relationship should settle. That’s the perfect context to shift-up to next gear with Event Storming.
This post was only the first half of the story. The next post contains the third and last step to inject Event Storming. As a bonus, it also provides a few organization hacks to get experts on board.
Leave a comment