6.2Recurring problems (playbook)
The essentials in 30 seconds
- Reflex: one symptom = likely causes = an action sequence — diagnosing before fixing.
- Root: a returning block almost always comes from the same fundamentals (priorities, focus, system, energy).
- Order: starting with the table most frequent cause, then verifying on your week before applying the rest.
Anis thread — 1 year on: the playbook posted near the calendar
One year on, Anis keeps this playbook near his calendar. Verdict: three lines served him most — emails checked continuously fragmenting everything, the to-do swelling without ever shrinking, and meetings devouring his mornings. For each, he ended up fixing the root (dedicated slots, limited prioritized list, questioned meetings) instead of repeating the incident.
Observed symptom, verified causes, actions in order: the reflex holds in three beats.
One reflex per symptom
Most time-management difficulties return for classic reasons. Linking each symptom to its likely causes and an action sequence saves precious time.
| Symptom | Likely causes | Actions |
|---|---|---|
| Feeling of running without ever progressing | no clear priorities, day dictated by urgency and requests | clarify 1-3 objectives, sort with Eisenhower, plan 2-3 priorities/day with margin (L0.4, L1.1, L2.1) |
| Important tasks never get done | important non-urgent sacrificed to urgent, no reserved slot | block slots (time-blocking), set aside deep work, protect these slots (L2.2, L5.1) |
| Fragmented focus all day | permanent notifications, continuous emails, multitasking | Focus mode, handling emails in batches, one thing at a time (L0.2, L4.3, L5.2) |
| The to-do list demotivates and swells | catch-all list, vague or too big tasks, not prioritized | concrete actions (verb), break down, limit the day list, prioritize (L1.3) |
| Saying yes to everything and overloaded | fear of disappointing, reflex “yes”, ignored opportunity cost | pause, refuse/renegotiate with tact (“yes, if we shift X”) (L1.4) |
| Tasks spread indefinitely | Parkinson's law, fuzzy deadlines, over-perfection | short firm deadline, time-boxing, aiming for “good enough” (L2.4) |
| Everything kept in mind, mental load and stress | nothing captured in a reliable system | capturing systematically (GTD), clarifying next action, reviewing (L3.1, L3.5) |
| Meetings devour days | useless meetings, too long, poorly prepared | questioning their necessity, objective + agenda + timing + actions (L5.3) |
| Exhaustion, fatigue not passing | over-optimization, no breaks or disconnection, neglected sleep | aligning tasks with your peaks, true breaks, disconnection, watching signals (L5.5) |
Ready-to-say script — naming the symptom before fixing (1 min)
“My symptom: [running without progressing / important never done / fragmented focus]. My hypothesis #1: [playbook most frequent cause]. I verify on my week then apply the sequence. I review in two weeks.”
Copy-paste template — express diagnosis card
OBSERVED SYMPTOM (facts and week concerned): ...
Since when / frequency: ...
LIKELY CAUSES (playbook 6.2): ...
Verification (calendar, 3-day log, day list): ...
ACTIONS (in order): 1) ... 2) ... 3) ...
TARGETED FUNDAMENTAL (priorities, focus, system, energy): ...
REVIEW in 2 weeks: improved? stable? worse?Small business / small budget
No formal table: one symptom, one cause verified on the week, one noted fix.
Algeria SME
Integrating activity peaks and real requests (phone, WhatsApp) into causes before concluding a willpower issue.
Remote / hybrid
Adding digital requests to likely causes: remote, each open channel looks like one more interruption.
Intercultural
Checking local availability expectations before acting: a polite “no” is not phrased the same everywhere.
48h challenge — apply tomorrow
Spot 1 current symptom in your week, fill the express diagnosis card and test the 1st action.
- I can link a symptom to its likely causes.
- I filled (or scheduled) an express diagnosis card.
- I know the referral to the level to dig into for my case.
Anis checks his emails and phone continuously and can no longer focus. Which reflex applies the playbook?
The same returning block is not ten incidents: it is a missing reflex to fix at the root (clarifying priorities, protecting focus, capturing in a system, preserving energy).