📎 Webclip
Remote-optimised Domain Modelling: The Present and Future
The article argues that remote domain modelling should not be a simple lift-and-shift of in-person workshops. It treats remote work as a different setting with its own limits and advantages, and suggests using experiments to discover techniques that fit that setting.
Reading notes#
- Remote teams have been excluded from the strongest collaborative domain modelling practices, but the current shift to remote work makes better techniques necessary.
- Remote modelling should be designed around its own limitations and advantages, not as a temporary substitute for in-person sessions.
- Future changes in communication tools and digital equivalents for physical materials will reshape what domain modelling can look like.
- Tools and user practices co-evolve, so techniques that feel awkward now may become product features later.
- For remote work, the author favors simple experiments first, then gradual evolution toward more complex forms that work.
- Single-threaded storytelling limits the workshop to one conversation and one model update at a time, focused on a specific story or user journey.
- Participants can add questions without speaking, and the group reviews them at iteration boundaries.
- Short iterations and facilitator rotation help keep people engaged and let the group decide whether to continue, zoom in, zoom out, switch stories, or take a break.
- Digital notation can be designed specifically for domain modelling, instead of relying on generic sticky notes.
- Digital tools make lines, arrows, and elapsed time visible, which can reveal loops, hand-offs, gaps, and edge cases.
- Comments and cards can store questions and follow-up actions, and the same data can be viewed in different ways.
- Remote models can have longer lifetime value because more people can access, question, and contribute to them asynchronously.
- Digital models can be copied and repurposed, for example into swimlane narratives or software-architecture views aligned with bounded contexts.
- The author sees potential in APIs and extensibility, but also warns against repeating past mistakes in enterprise modelling.
