WAH MEK / LEARN / COMMON QUESTIONS
Why is it hard to restart after an interruption?
An interruption is not automatically the breakdown. WAH MEK looks at what happens after the interruption ends: whether the person can recover the task, regain the next action, and resume execution under workable conditions.
SHORT ANSWER
Difficulty restarting can point to a recovery problem, but not every failed restart is Recovery Breakdown. Re-entry can also fail because the next action is no longer clear, the original work stream was already unstable, or the return context has changed. The useful question is: “What specifically prevents execution from becoming active again?”
01 · PRESENTING PROBLEM
The interruption and the recovery failure are two different events.
A meeting, phone call, child-care demand, commute, sleep period, or unexpected problem can legitimately stop work. That event alone does not establish Recovery Breakdown. The recovery question begins once the interruption has passed and execution could reasonably resume.
What is execution breakdown? →View the 12 Working Diagnoses →
02 · COMPETING EXPLANATIONS
Four WAH MEK mechanisms can make restarting look difficult.
These categories are WAH MEK Working Diagnoses: provisional product-level explanations used to guide a test. They are not medical or mental-health diagnoses and should not be treated as permanent traits.
03 · DIAGNOSTIC SEPARATION
Separate failure to return from failure to know how, sustain the work, or regain the original conditions.
Recovery Breakdown becomes more plausible when the person repeatedly does not resume despite having a usable return point.
Path Uncertainty deserves more weight when re-entry fails because the person must reconstruct what to do next.
Continuity Breakdown may explain more of the pattern than recovery alone.
If execution was already unstable before interruption, see why you keep stopping →
Context Mismatch deserves consideration when the same work resumes reliably in one setting but not another.
WAH MEK should not label unavoidable delay as a recovery failure. The return opportunity, next action, and context all matter.
04 · TARGETED TEST
The first correction should make re-entry observable and test one suspected mechanism.
- Preserve the return pointCapture where execution stopped and what the next executable action should be before the interruption fully displaces it.
- Define the first workable return opportunityIdentify when the interruption has actually ended and resumption is realistically possible.
- Test one recovery aidUse one targeted correction rather than adding a bundle of reminders, timers, planning systems, and environmental changes at once.
- Record Proof of re-entryCapture whether execution actually resumed and what observable action occurred after the return.
- Retest under comparable conditionsUse another interruption/re-entry exposure to see whether the same mechanism and correction pattern repeats.
05 · EVIDENCE BEFORE CERTAINTY
If re-entry improves, that supports the hypothesis. If it does not, reopen the explanation.
A failed correction does not prove the person lacks discipline. It may indicate the suspected mechanism was wrong, the correction did not adequately target it, the exposure was not valid, or the retest was not comparable. WAH MEK is designed to revise the Working Diagnosis when the evidence requires it.
NEXT STEP
Find what is breaking your execution.
WAH MEK separates competing explanations before selecting a targeted correction.
Find What’s Breaking My Execution → Back to Common Questions →