6.2Recurring issues (playbook)
The essentials in 30 seconds
- Reflex: one symptom = likely causes = an action sequence — diagnose before fixing.
- Root: a block that keeps returning almost always comes from the system (line, calendar, proof), not algorithm luck.
- Order: start with the table's most frequent cause, then check on numbers before applying the rest.
Nour thread — 1 year later: the playbook pinned above the calendar
One year later, Nour keeps this playbook near her publishing calendar. Verdict: three lines served her most — reach collapsing under pure promo, ads burning budget with no Pixel, and the 20-page reporting nobody read. For each, she ended up fixing the root (40/40/20 mix, 5 € × 3 × 7-day test, 1 page with decision) instead of repeating the incident.
Observed symptom, verified causes, ordered actions: the reflex holds in three steps.
One reflex per symptom
Most social media blocks are old classics. Linking each symptom to its likely causes and to an action sequence saves precious time.
| Symptom | Likely causes | Actions |
|---|---|---|
| Collapsing reach | promo only, no hook, zero interaction | 40/40/20 mix + 3-s hook + replies <2 h |
| Stagnating followers | no reason to follow or stay | series + value carousels + daily stories |
| Empty/toxic comments | no moderation, missing charter | displayed charter + graduated response + human replies |
| Hacked or orphaned account | no 2FA, single admin gone | 2FA + 2 admins + generic email + vault |
| Ad burning budget | no Pixel, blind boost, leaky page | tested Pixel + 5 €×3×7-day test + <3-s page |
| Rising bad buzz | silence or 3 contradictory voices | unit + facts + single voice + public review |
| Exhausted team | day-to-day, doing everything | calendar + batch + recycling + written scope |
| Ignored reporting | 20 pages of raw data | 1 page + indicators + cause + decision |
| Reported stolen visual | Google Images, faces without consent | remove + licensed libraries + written permissions |
Ready-to-say script — naming the symptom before fixing (1 min)
“My symptom: [collapsing reach / ad burning / reported visual]. My #1 hypothesis: [playbook's most frequent cause]. I check on numbers then apply the sequence. I review in two weeks.”
Copy-paste template — express diagnosis sheet
OBSERVED symptom (numbers and facts): ...
Since when / frequency: ...
LIKELY causes (playbook 6.2): ...
Check (native exports, calendar, rights): ...
ACTIONS (in order): 1) ... 2) ... 3) ...
Targeted SYSTEM (line, calendar, proof): ...
REVIEW in 2 weeks: improved? stable? worse?Small business / tight budget
No formal table: one symptom, one cause verified on numbers, one dated fix.
SME Algeria
Build activity peaks and short means into causes before concluding an algorithm problem; check real connection times.
Remote / hybrid
Add the validation loop to likely causes: at distance, an unreviewed post looks like a fuzzy line.
Intercultural
Check local codes before acting: a tone seen as neutral here may read as aggressive elsewhere.
48h challenge — apply tomorrow
Spot 1 current symptom on your accounts, fill in the express diagnosis sheet and test the 1st action.
- I can link a symptom to its likely causes.
- I filled in (or planned) an express diagnosis sheet.
- I know the referral to the level to dig into for my case.
Nour's account sees reach collapse after weeks of pure promo. Which reflex does the playbook apply?
One same hassle returning endlessly is not ten incidents: it is a system to fix (line, calendar, proof).