A good model tells you what to build; this workshop covers both modeling it and turning it into how. Most teams jump from requirements straight to code, and the architecture ends up being whatever the first few commits made it. Design closes that gap.

At the heart of it is the MOSY Framework, the visual notation that chains one thing to the next: business goals to product functionality, functionality to a conceptual data model and to technical components. It's what keeps new functionality aligned with your current architecture and with the business as the system grows, instead of drifting a little further with every feature. From the model you'll draw architecture diagrams, set boundaries and ownership, and make the service decisions deliberately: how many services, sync or async, events or direct calls, and the trade-offs behind each. The same approach works greenfield or carving a monolith into something that can evolve.

You'll capture the important decisions as ADRs so the architecture stays explained, not tribal knowledge, and you can plug it into an Architecture Community so the team takes part. You leave with a model, an architecture drawn from it, and the decisions recorded: a build-ready plan the Build workshop (and its AI agents) turn into working software.