“If you model only one thing in Agile, model the domain.”

— Scaled Agile Framework’s article, “Advanced Topic — Domain Modeling”, March 2, 2023

I create Domain Models to give teams a big-picture view of a service at the start of a design or development project.

A domain model outlines the scope and key parts—people, processes, technologies, and workflows—so everyone has a shared understanding before diving into the details of building a service blueprint.

Creating a Domain Model early helps to:

•Clarify the boundaries and structure of the service ecosystem

•Create a common language for business and technical teams

•Frame solutions around desired outcomes or “Jobs to be Done”

•Identify technology / platform interdependencies early on

I vary the detail of the domain model to meet the collaborating teams where they are in their understanding of the environment.

I created this large-format (3 ft x 12 ft) domain model to help cross-functional teams plan the integration of 90+ systems into an enterprise CRM. While a solution vision already existed, teams needed a clear view of the supporting capabilities and systems.

The diagram mapped customer-to-backstage architecture layers (top-down) and business process flows (left-right), highlighting key integration points across technical components.

Outcomes: Provided a shared “big picture” that enabled business and IT teams to align on scope, prioritize efforts, and identify opportunities to leverage data and technology for new capabilities.