Hidden assumptions
Everyone assumes something different, and nobody says it out loud.
2 days · 4 hours each Remote Up to 10 participants
Event Storming for Teams
Find the gaps before your teams write code.
For teams and organisations that want business and tech to build the right thing, together. Two blocks of about 4 hours on a shared online board, on a real process from your own domain.
What goes wrong before the first line of code
Each of these can turn into rework, delays or the wrong product later in the SDLC.
Unclear requirements
Stories say what to build, not why or for whom.
Shallow tasks
Tickets lack the context developers need to make good decisions.
Different views of the process
Business, product and tech each picture a different flow.
Undocumented processes
Knowledge lives in people's heads, not in shared artefacts.
Solution before problem
Teams jump into the solution space before the problem is understood.
What Event Storming helps with
Most delivery problems start before the code. Event Storming helps bring them to the surface early.
Questions come up early
Open questions show up before development, not during it.
Shared understanding
Business and tech look at the same process on one board.
Common language
Teams start using the business's names, in meetings and in code.
Better architecture input
Process boundaries can become a base for modules and team ownership.
From past sessions
“We discovered that we didn't need to build half of the system, because the device already covered it.”
“Our organisation started working differently. People began thinking about the product and asking why, and how it really works in the organisation.”
How the training works
01
Discovery call
Free · 30 min
We agree on goals and pick a real process from your domain.
02
Training
2 days · 4 hours each · remote
Hands-on training in Big Picture and Process Level, practised on your own domain.
03
Support after the training
5 hours · valid for 2 months
Use it for reviewing your next session, refining the board, turning hot spots into backlog items or Q&A.
The training
A standard plan, tailored to your needs during the discovery call.
Day 1 about 4 hours
-
45 min · Preparing a session
The genesis of a technique, choosing the use case and organising the workshop.
-
3 h · Big Picture on your domain
Chaotic exploration, building the timeline, marking hot spots and pivotal events.
Day 2 about 4 hours
-
2 h · Process Level on one flow
Commands, policies, actors and read models for one chosen process.
-
45 min · Facilitation
How to run the next session yourselves and ask the right questions.
-
30 min · Wrap-up
Questions and open discussion.
What your team walks away with
- ✓ Practice with Big Picture and Process Level on your own domain.
- ✓ A prioritised list of hot spots.
- ✓ Hot spots turned into backlog items.
- ✓ Board export, templates, a facilitator cheat sheet and 5 hours of support.
- ✓ A team that knows how to run the next session.
Who it's for
People who will run or take part in sessions: tech leads, architects, product owners, analysts and developers, plus at least one domain expert.
Remote, up to 10 participants. More participants or an extra block change the scope, so we settle that on the discovery call.
Want this for your team?
Book a free 30 minute call. Tell me about the process you want to map and we will plan the training around it.
Get in Touch