Strategy 2019
Bounded Context Canvas
A Business-Model-Canvas-style one-pager for one software service's purpose, roles, and contracts.
What it is
Eight cells: name, purpose, strategic classification, domain roles, inbound communication, outbound communication, ubiquitous language, and the business decisions the context owns. One canvas covers exactly one bounded context — pin several side by side to see a whole system's contracts.
Reach for it when
- A monolith being split into services with no agreement yet on where the boundaries fall
- A new engineer trying to understand what one unfamiliar service actually owns
- An EventStorming session that produced sticky notes but no lasting documentation
Running it
- Pick one bounded context already identified from an EventStorming session or an architecture diagram — one canvas, one context.
- Fill Name and Purpose together first, then work outward to inbound and outbound communication, since naming contracts forces scope decisions.
- Capture ubiquitous-language terms as they surface naturally in discussion, flagging any that mean something different in a neighboring context.
- Run it with the owning team of 2-6 in 60-90 minutes, plus a representative from each adjacent context if you can get one.
Watch out: Purpose gets written as a technical description of what the service does instead of the business capability it exists for, and the inbound/outbound boxes get filled with ‘talks to the API’ instead of naming the actual contract.
Add unlimited notes to any activity
Comments & Discussion
Add a Comment
Recent Comments (3)
This workshop was incredibly effective for our remote team! We adapted it slightly for a virtual setting and it worked wonderfully. The key was breaking into smaller breakout rooms.
Great resource! One tip: prepare all materials the day before to avoid any last-minute rushes.
Used this for our quarterly planning session. The structured approach really helped us stay on track!