Ubiquitous language is the shared set of agreed meanings for domain-specific terms used by analysts and stakeholders. It turns vague questions into defined terminology, scope, and reproducible analytical decisions. section 1.2.1
When “yesterday” is not precise
A stakeholder asks how much the business sold yesterday. Clarify whether “yesterday” uses the order date, payment date, or dispute-resolution date, and whether a later return changes what “sold” means. Record the agreed definitions before analyzing the data. section 1.2.1
Build shared terminology through practical decisions:
- Ask stakeholders to define ambiguous entities such as “customer,” including whether the term means a person, an organization, or both. section 3.1.1
- Agree on the scope and meanings needed for the analysis, then document them for transparency and reproducibility. section 1.2.1
- Encode the resulting business entities, concepts, and activities in a data model instead of redefining them for every analysis. section 3.1.1



