Offers
Event modeling & adoption sprint
Model the domain together before code exists — and clarify who owns it afterwards.
“We have been discussing requirements for months and nobody shares the same picture.”
- Format
- 2–4 weeks, remote-first with 2 on-site workshop days
- Who it is for
- Initiatives before build start, or projects going in circles
Typical symptoms
- Requirements have been discussed for months without a shared picture emerging.
- Business and engineering use the same words but mean different things.
- Backlog tickets describe solutions instead of flows — the context is missing.
- After every release someone notices a forgotten edge case.
- Nobody can say which increment should ship first, and why.
Outcome
- Event model of the core processes with commands, events and read models
- Slicing into deliverable increments incl. sequence and risks
- Ownership map: who decides, who operates, who explains
- Prioritised decision paper with effort ranges
How we work
01
Preparation (remote)
We review existing documents, processes and systems and clarify which roles absolutely need to be in the workshop.
02
On-site workshop days
Business and engineering model the flow together on a timeline: commands, events, read models — and the spots where it gets fuzzy.
03
Slicing & sequence
The model turns into deliverable increments with sequence, risks and effort ranges — instead of a big-bang plan.
04
Clarify ownership
We record who decides, who operates and who explains. The result is a decision paper you can act on without us.
Frequently asked
- Do we need event sourcing for this?
- No. Event modeling is a modelling method and works fine with classic CRUD architecture. Whether event sourcing fits is a later decision.
- Who should attend?
- Business, engineering and someone allowed to decide. Six to eight people is ideal — more makes the workshop slow.
- What if the outcome is: do not build it?
- Then the sprint paid off most. Stopping an initiative early costs weeks instead of quarters.
- Can you build it afterwards?
- Yes, but you are not tied to us. The decision paper is written so an internal team or another partner can work with it.
Often combined with
Background in the article Event modeling is an adoption tool.