6.2 · Recurring problems (playbook)

Level 6 · In practice

6.2Recurring problems (playbook)

Goal: have a “symptom → causes → actions” playbook for common usage difficulties.
Estimated time: 12 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • Reflex: one symptom = likely causes = an action sequence — frame, check, protect, keep the human on decisions.
  • Check: allow “I don't know”, require cited sources and check proportionately to the stakes.
  • Protect: classify the data and if in doubt do not paste; get legal and HR approved by a professional.

Amine thread — the playbook taped next to the screen

Amine keeps this playbook next to his screen. Verdict after one year: three lines served him most — generic answers reframed in RCTF, AI inventing references, and doubt before pasting a document. For each, he ended up applying the sequence (frame, require sources, classify the data) instead of managing by feel.

Observed symptom, checked causes, actions in order: the reflex holds in three steps.

One reflex per symptom

Most disappointments with AI recur for classic reasons. Linking each symptom to its likely causes and an action sequence saves precious time — and avoids incidents.

SymptomLikely causesActions
Generic, disappointing answersvague prompt, no role/context/formatapply RCTF, give an example (few-shot), iterate
AI invents facts/referenceshallucination, no web search, risk zoneallow “I don't know”, require cited sources, check proportionately
AI always approves my ideassycophancy, leading questionask for explicit criticism (“attack like a sceptic”), devil's advocate
Doubt: may I paste this document?company data, unapproved toolclassify (public/internal/confidential), anonymise or approved tool; if in doubt, do not paste
Bland, interchangeable marketing contentno lived material, no brand toneinject case/figure/opinion, document the tone, “anyone?” question
Conversation thread going everywheremixed topics, bogged-down threadone topic = one thread; restart from a fresh thread with a consolidated prompt
Copilot wrong about my documentsoutdated document taken as reference, approximate synthesisclick the sources, keep documents up to date (titles, dates), arbitrate
Doubtful legal referencelegal hallucination (the riskiest zone)check against the official source, get a professional to approve
HR/hiring use blockedindividual decision / high riskAI does not decide; human in the loop; approve compliance with the DPO
Common misinterpretation: “The playbook replaces checking.” No. The table gives likely causes, not a verdict: reframe the prompt, require sources, classify the data, then get legal and HR approved by a professional.
Text version of the diagram (SEO / screen readers / translation): Playbook method: 1) Name the observed symptom (bland answer, invention, sycophancy, pasting doubt, bogged-down thread). 2) Keep the table's likely causes without concluding alone. 3) Apply the actions in order (frame in RCTF, require sources, classify the data). 4) Get legal and HR approved by a professional. Lesson: a recurring problem calls for a reflex, not improvisation.

Ready-to-say script — handling a blocker without exposing yourself (30 s)

“My symptom: [generic answer / invention / pasting doubt]. I reframe in RCTF with an example, I require cited sources, I classify the data and if in doubt I do not paste. For legal and HR, I get a professional to approve.”

Copy-paste template — express blocker sheet

OBSERVED SYMPTOM (bland, invention, sycophancy, doubt): ...
Since when / on which file: ...
LIKELY CAUSES (playbook 6.2): ...
REFRAMING (RCTF + example + criticism asked): ...
CHECKING (cited sources, level by stakes): ...
DATA (classification, anonymisation, approved tool): ...
PRO APPROVAL (legal / HR / DPO if concerned): ...
REVIEW: reflex to anchor for next time: ...

Small business / tight budget

No formal table: one symptom, the playbook's likely cause, the action and approval by the contact person.

SME in Algeria

Include local realities: organisation-approved tool, team charter, professional or DPO to consult.

Remote / hybrid

Add the written trace to actions: at a distance, a consolidated fresh thread and dated checking avoid misunderstandings.

Intercultural

Check local practices before acting: official sources and expected approvals vary by country.

Caution: Reminder: fact-checking and data protection vary by organisation and country — classify data, use the approved tool and, for legal, HR or hiring, get approval from a professional or the DPO; this guide gives no legal advice.

48h challenge — apply tomorrow

Spot 1 current symptom (last disappointing answer or pasting doubt), fill in the express blocker sheet and test the 1st action (reframe + check).

Section exit checklist
  • I can link a symptom to its likely causes.
  • I filled in (or planned) an express blocker sheet.
  • I know the pointer to the level to dig into for my case.
Self-rating 1-5: reframing and checking before use?classified data and requested pro approvals?
Check your understanding

Amine hesitates before pasting an internal document into a public tool. Which reflex does the playbook apply?

💡

One problem recurring is not ten incidents: it is a missing reflex to fix at the root (frame the prompt, check the facts, protect the data, keep the human on decisions).