In an SME management committee, the decision to use AI is rarely put in writing. Six months later, nobody knows who approved which use, on what data, or what was ruled out and why. When a client asks the question in its supplier questionnaire, the answer rests on somebody's memory.
That is what the protocol addresses: one morning, seven roles around the table, a real subject from the business, a deliverable produced in session and an arbitration log that stays with you. Here, more broadly, is how I work when I arrive at your site.
I start by looking at the installation, not the binder. I talk to the people who hold the job, not only to those who hold the file. By the end of this phase, we agree on the real problem — which is not always the one announced at the outset.
Not everything can be tackled at once, and an SME cannot fund everything in the same year. I prioritise according to what genuinely exposes you: formal notice, production shutdown, loss of a key customer. The rest waits, and that is stated in writing.
You receive a document your teams can use without me: named actions, identified owners, dated deadlines, estimated workloads. Not a summary presentation, not an assessment that merely describes what you already knew.
The aim of every assignment is that you can do without it afterwards. I train the person who will take the subject over internally. A consultant you can no longer do without has done a poor job.
Food processing, ICPE sites, metalworking, automotive subcontracting: the constraints of a classified site, the weight of a customer audit, the grammar of a HACCP plan or the heaviness of a process FMEA are realities I have already worked in.
Thirty years in foundry, metalworking, subcontracting for light and heavy vehicles, ICPE sites, QHSE and Six Sigma taught me one simple rule: a method is only worth the context you place it in. That is why I never arrive with a preset template to fill in.
For companies that want to structure AI use as a team rather than post by post, I run the M.A.U.F.R.A.S.® method and the Cockpit CadrIA protocol, created by Stéphane Maufras, for which Viactis is the regional partner for south-west France. Each of the seven roles in the session is held by a different person: the AI pilot does not decide, and the decision-maker does not write.
It is a tool, not my offering. If the subject interests you, we discuss it during the first call —documentation of the method.