What is a real person trying to finish?
Describe the task in plain language, from its trigger to the moment the result is accepted.
Route 07 / prepare the first conversation
Bring the operation, not a polished pitch.
A useful project brief can fit in one email. Answer what you know, label assumptions and leave questions open. Do not send passwords, private keys, payment-card data, regulated records or sensitive personal information in the first message.
Continuity brief
Eight questions worth answering.
Copy these prompts into an email or your own document. The aim is not to produce a specification. It is to expose the people, dependencies and failure points that determine whether a technical engagement is feasible.
What breaks or creates uncertainty today?
Name delays, repeated entry, missed approvals, fragile tools, unclear status, lost records or manual reconciliation.
Who uses and owns the process?
List the working roles, decision-maker, technical account owners and person authorised to accept a release.
How is the operation connected to Lebanon?
Identify the users, locations, entities, vendors, customers, data or transactions that create the Lebanon context.
Which languages and devices matter?
State whether Arabic, French or English is required, who reviews it and which real devices or connections are representative.
What information and money move through it?
Describe categories—not sensitive records—and identify analytics, AI, payment, email, hosting or other vendors already involved.
What must happen when the main path fails?
Explain the acceptable manual fallback, retry, escalation, reconciliation or recovery route.
What would make a first release successful?
Choose a small measurable result and a time window that proves the operation improved without hiding new risk.
Safe first contact
Share enough to scope, not enough to expose.
An initial conversation should establish fit and the next discovery step. Protected access and sensitive information wait for an approved method and an actual need.
- Do sendA plain-language problem, public links, screenshots with private information removed, rough scale, constraints and desired outcome.
- Do not sendPasswords, private keys, payment-card information, identity documents, health records, full customer exports or confidential legal material.
- Label assumptionsSeparate facts you verified from beliefs that still need a user, provider, authority or qualified professional to confirm.
- Name urgency honestlyIf a live operation is failing, explain the impact and any current workaround. Urgency does not remove the need for safe access and rollback.