🗺️ Modelling with events

Many design mistakes start before the code, when the team doesn’t yet understand the process it’s building. Modelling with events means describing a process as a sequence of facts, like “reservation confirmed” or “payment failed”, and talking it through with the people who know the business. You’ll learn how to run such sessions so they bring out rules and open questions instead of getting stuck.

The first article is a talk on modelling mistakes to avoid. The second shows how to combine EventStorming, a workshop that maps a process on sticky notes, with other techniques. The next two are about running a session: marking disagreements and unknowns instead of arguing them out, and letting people think alone before the group discussion so the loudest voice doesn’t decide. The last one turns a list of requirements into code.

Read them in order.