Domain expert
The person who knows how the business really works, such as a receptionist, an accountant or a doctor, and whose knowledge the software model has to capture.
In DDD the domain expert is a design partner, not a source of requirements handed over once. Developers learn the ubiquitous language from them, test the model against real cases with them, and come back when the code finds an edge case nobody described. Often the expert is not the manager who signs off the project but the person who does the work every day.
Event storming and a discovery phase are the usual ways to get experts and developers in one room. With coding agents, the same knowledge goes into specs and examples the agent reads, so an expert’s hour is worth even more.
Related terms
- Ubiquitous language: One shared vocabulary for a domain, used the same way by experts, developers and the code itself.
- Event storming: A workshop where business and technical people map a process as a timeline of events on sticky notes to find rules, gaps and boundaries.
- DDD (domain-driven design): Designing software around the business’s own language and rules, with the code split where that language changes meaning.
- Paid discovery (phase 0, inception): A short, separately priced project before the build: workshops, a technical feasibility check and a scoped plan with a quote you can take to any vendor.
