2 Days: EventStorming Master Class

GOTO Copenhagen 2026
Monday Sep 28
09:00 –
17:00
Tuesday Sep 29
09:00 –
17:00
11,000.00 DKK
Register for this masterclass

Putting business, software, and user experience experts on the same page!

EventStorming is a family of workshop formats that helps explore, map and design complex business flows, leveraging natural storytelling and an event-driven structure.

The three main formats will let you dive into intricate domains, zooming into details without losing coherence.

  • Big Picture enables highly time-effective, large-scale discovery of complex landscapes. It blends different perspectives into a coherent shape and then uses this background for layered discovery and mapping.
  • Process Modelling leverages a flexible, colourful grammar and a collaborative game approach to engage experts and stakeholders in a robust representation of a business process, suitable for discovery or design.
  • Software Design leverages the same principles to bring collaborative design towards modern event-driven software solutions.

Together, they let you dissect complex domains and design effective solutions, combining different perspectives into a solution with built-in support from the workshop participants.

It’s the developer understanding, not the expert knowledge, that becomes working code.

In an EventStorming workshop, we make everybody’s understanding visible to unlock faster, more meaningful problem resolution.

What you will learn

  • EventStorming notation is designed to be simple. Managing the room is tricky.
  • This Master Class will make you feel the critical moments of a large-scale workshop, and provide actionable tips on the soft skills of facilitation: how to kick off the workshop, how to read the room signals, handle emergent conflicts and address counterproductive behaviour.
  • We will practice the three formats on a realistic problem space. In layers of increased complexity and changing collaboration style along the way.
  • You will learn how to run the standard recipe and how to design, prepare, and fine-tune your workshop to address your specific constraints and needs.

Target audience

  • EventStorming is interdisciplinary and targets collaboration among different roles. Software professionals will learn a more reliable and time-effective way to master domain complexity and detect signals for effective design. UX experts will learn an effective way to include the user perspective in software design. Business experts will have a powerful tool to envision and sharpen key processes and business lines.
  • Together, they will learn how to balance their perspective into a more powerful, coherent view.

Agenda

Day 1 – EventStorming as a discovery tool

  • Quick kick-off: where we are and where we want to go.
  • Real-world Big Picture EventStorming, mastering complexity and unknowns in large-scale modelling.
  • Reading implicit signals, areas of friction, and emergent boundaries.
  • Managing conflicts, highlighting risk, and the problems that are really worth solving
  • Explicit walkthrough: making sure the model matches the conversation.
  • Dive into motivators and opportunities for change.
  • Detecting signals for architectural and organisational design.
  • Actionable insights: how to turn the discoveries into a plan.

Day 2 – EventStorming as a design tool

  • Emerging System Boundaries: from EventStorming to Bounded Contexts
  • Process Modelling EventStorming: a cross-discipline platform for collaborative modelling
  • Leveraging the grammar structure to build robust flow and ask uncomfortable questions.
  • Strategies for the collaborative game. Opening moves, collaboration styles, and understanding when to switch.
  • Making policies explicit. Discovering the hidden truth in business behaviour
  • Design around Value: hidden and explicit motivators.
  • Manage your biases in collaborative design.
  • Software Design EventStorming: discovering key software components
  • Aggregates and transactional consistency: independent moving parts in a complex software system
  • Design around the bottleneck: alternatives to YAGNI.
  • Blending User Experience Design and Service Design into Software Design
  • Transitioning from sticky notes to working code.