Before you optimize the process, ask why it exists
Oct 7, 2026
Before optimizing another handover, ask why it exists. Joint exploration of one business activity, with an Event Model as the shared blueprint everyone can challenge.
Collaboration
Editorial thought-leadership.
Oct 7, 2026
Before optimizing another handover, ask why it exists. Joint exploration of one business activity, with an Event Model as the shared blueprint everyone can challenge.
Collaboration
Sep 25, 2026
If trust in AI output still means a human reads everything an agent produces, the bottleneck has only moved. The blueprint itself must be verifiable.
AI+SDLC
Aug 31, 2026
What gets lost as requirements pass from hand to hand — and how a shared behaviour model rebuilds trust.
CollaborationJun 24, 2026
Automating a muddy delivery process only produces mud faster. Business Solution Design comes first.
AI+SDLCJun 12, 2026
Fragmented understanding is structural, not personal. Make the whole flow visible and the gaps start to close.
CollaborationMay 29, 2026
More prose specification is not the missing input for AI. Explicit behaviour blueprints are.
AI+SDLCApr 23, 2026
In regulated domains, separation of duties belongs in the behaviour model long before it becomes a permission matrix.
L&HApr 17, 2026
A worked example: derive concrete test cases straight from the event diagram instead of from implementation details.
TestingApr 14, 2026
When tests express intent, they stop being an afterthought and become the specification itself.
TestingFeb 12, 2026
Boundaries drawn from decisions rather than data keep enterprise architecture aligned with how the business really works.
L&HFeb 2, 2026
State change, view, automation, translation — four recurring patterns that describe almost any business process.
EventModelingJan 1, 2026
The foundational thesis: teams need a shared blueprint of behaviour before they argue about tools, tickets or frameworks.
EventModeling