Modeling Practice ​

There are roles for which the practice of formal modeling is the main one, --- these include ontological, architectural, designer (designer roles), and so on.

But no matter what the main work is associated with, descriptions still have to be made by everyone --- responding to similar requests:

• write instructions for a new employee;
• make a description of the store's operations;
• let's describe our project for an investor;
• write a brief description of the product;

and so on.

At this point, an additional situational layer of roles appears regarding this process of creating a description:

• description customer --- the one who requests the description. They have an understanding (presumably) of why they need the description (what impact and for whom it should be made) and the general context.
• performer/compiler/author --- the one who creates the description, ontology, model. They do not have knowledge of what description is needed, but they have some qualification in how to make descriptions in general; and in a good situation, they can solve the task of the description customer using their skills and involving other stakeholders if necessary.
• addressee --- the one who will read the description and with whom something should ultimately happen. They generally do not yet know that something has been thought about regarding them.

The description customer, performer, and addressee are not necessarily three different people, any two (or even all three) may coincide. But these are always three different roles. Even if you are playing all of them, play them one by one, not simultaneously.