Context
Explain the current situation and what triggered the request.

PRIVATE CHANNEL
Direct contact with Alexis Roux ZG: a situation to clarify, a project to build or a specialist to find.
Operational briefOperational brief
Tell Alexis the context, what you want to achieve and your deadline. He can then explain his understanding, scope of involvement and any complementary skills required.
MESSAGE / DIRECT CHANNEL
Share the essentials. No confidential document or sensitive access is needed at this stage. Fields marked with an asterisk are required.
Answer the points relevant to your project. Other points can remain open questions.
02 / Intervention areas
Explain the current situation and what triggered the request.
Describe the decision, outcome or risk reduction you need.
State what may be shared, with whom and under which constraints.
Provide the useful date, imposed stages and actual urgency level.
State who decides, who executes and who should receive conclusions.
Define what must be true, visible or possible when the assignment ends.
Mention deadlines, jurisdictions, imposed systems, dependencies and red lines shaping the response.
State whether the decision needs a rapid note, documented audit, experiment or durable system.
Sensitive relationships, names and assignments are not exposed to impress. An initial exchange requires no secret and no inventory of contacts.
03 / FIELD NOTES
The first exchange qualifies the stakes; it is not designed to collect unnecessary sensitive information.
Rapid audit, second opinion, risk mapping or clarification before a decision.
Web architecture, editorial system, private agent, monitoring or visibility observatory.
Weak results, technical debt, semantic confusion, dependency or failing governance.
Team coordination, arbitration, quality control and executive reporting.
Build a verifiable baseline to compare the situation before and after intervention.
Formalise rules, tools, documentation and controls required for continuity.
04 / OUTPUTS
A few structured lines enable a faster response without exposing information that need not yet circulate.
What exists, what works and what no longer works.
The event, decision or risk behind the request.
The concrete outcome sought, not only the proposed means.
Deadlines, jurisdictions, imposed tools, data and access levels.
Decision-makers, relevant teams and report recipients.
The first date requiring a decision or action.
Decisions already made, previous attempts and the main available lessons.
What may be shared now, later under agreement, or never outside the internal perimeter.
05 / Method
An initial response states the understanding, any questions and the next useful step.
06 / FAQ
Clear answers on scope, limits, methods and engagement conditions.
Email is suitable for initial context. No sensitive document is required in the first message.
Depending on availability and subject. Declared urgency is not automatically real priority.
Yes, from France, with remote and international assignments.
No. A factual summary is sufficient; scoping may itself be part of the assignment.
Yes, when proportionate to the scope and reviewed before sensitive information is exchanged.
Yes. An independent diagnosis may be delivered without an obligation to award deployment.
Illegal, disproportionate, deceptive requests or those intended to harm people are not accepted.
No password, trade secret, unnecessary personal data or sensitive document. A suitable channel can be agreed after qualification.
After the initial reading and any scoping questions. It states objectives, exclusions, deliverables, validation and schedule.
Yes. Qualification or a focused audit can secure the decision before a broader commitment.
Yes. The first message should remain factual and minimal. A suitable channel and confidentiality level are agreed before any sensitive exchange.
08 / CONTACT
State the context and objective. You will receive a clear initial reading.
DEEPER READING / PRACTICE
A request often comes with a solution already imagined: re-design, AI agent or content campaign. First, describing the difficulty you have encountered allows you to check if this solution really meets the problem.
Updated on .
Indicate who is concerned, what has changed, the decision to be made and the relevant deadline. A public example, an URL and a trail description are often enough to start the qualification.
Too large demand makes priorities difficult to set up. Confidential documents and access IDs are not required to explain the initial context.
A short definition of need can be made up of four paragraphs: situation, objective, restrictions and expected outcome. Adding the attempts already done prevents the recovery of tracks that have been removed.