The work before the tool
If the quote, the file or the ticket is not understood, no artificial intelligence will change anything. We start with the flow, the rules, the exceptions.
Approach
Start from the flow that costs, extend only what holds
A priority process, a gesture teams actually do, assistance under control. Only then do we widen. It is slower to tell than a “global transformation”. It is the only way we practise.
Principles
A person at the decision
The assistance prepares; someone approves. Reminders, filings, drafts: nothing sensitive goes out without an agreed review.
Evidence, not a double file
Attendance, signatures, evaluations, invoices: what happened is the source. We do not keep a parallel binder to “look compliant”.
Train the people who do the work
A tool that is not adopted is a cost. Team training is part of the mission, not an option stuck on at the end.
How a mission moves
Listen to the flow
Who does what, with which tools, where it breaks. The Unlock request stays a solicitation until acceptance: nothing is opened to fill a table.
Target a first use
One process, an observable result, a scope narrow enough to hold in the daily work. Extension comes after, if it holds.
Integrate and document
The assistance enters the real environment. The pieces (contracts, agreements, access) follow the same file as the mission.
Hand over, then step back
The teams do the gesture without Unlock in the room. Until that is the case, the mission is not finished.
When the need is training
The approach is the same: start from the work to be practised, not from a catalogue to empty. The public catalogue shows the open programmes. EVA adds none.
A confirmed session produces its agenda, its invitations, its attendance. Certificates, if any, rest on that reality. To enrol people or build a session, request training.
The operational course — from qualification to adoption — is also described, from the deployment angle, on delivery.