Starting from the expected quote
The manager of a construction company wishes to adapt his quotes to his way of presenting the services. It provides an example of a document which distinguishes the services, the options to be selected, the technical validation, the commercial agreement and the site conditions. This structure specifies what he wants his client to read and validate. The discussion can thus focus on a concrete document, with its information, its hierarchy and its stages of agreement.
Refine the request with the user
Patrice offers an update and mod track to address part of the need. The first proposal calls for further clarification from the manager: the planned presentation is different. The example provided serves to discuss these differences and to better define the desired result. This model clarifies expectations and guides the discussion of the adaptations to be planned.
Reestablishing the creation of specifications
A few months later, a difficulty prevented the creation of estimates in the Dolibarr. Patrice intervenes and asks the user to try again. The officer confirms that the operation is restored. This result concerns the resumption of the creation of the specifications; the layout originally requested remains a separate subject within the scope of this experiment.
The business document as a common thread
This historical monitoring was carried out by Patrice as part of Alltech. It illustrates a useful practice for business development: comparing proposals with examples provided by the company and checking corrections with the person who actually uses the application. This is a basis of the Dtouch approach: understanding the expected document, specifying the needs and supporting the software over time.