concept business domain in category software development

This is an excerpt from Manning's book Writing Great Specifications: Using Specification by Example and Gherkin.
Some answers come from the business domain and others from the technology domain (see figure 1.5). Usually, the business domain provides the who and the why, and the technology domain provides good what and how answers.
Document the business domain for people who are unfamiliar with it
Just like students, people on teams and in organizations aren’t uniform. For example, let’s consider a junior-level engineer, straight out of college, who joined the team a few months ago; an analyst who’s fairly senior but as a new hire hasn’t yet fully grasped the business domain; a mid-level designer; and a senior tester who has been around forever and knows the ins and outs of the system. They all have different work experiences and skills. How can you write documentation for all of them?