WAH MEK / LEARN / QUESTIONS
Common execution questions
Start with familiar execution problems and connect the observable pattern to competing mechanisms rather than forcing a label.
PROBLEM LANGUAGE
Start with what keeps happening.
Questions such as “Why can’t I start?”, “Why do I keep stopping?”, “Why can’t I finish?”, and “Why is it hard to restart after an interruption?” describe observable problems. WAH MEK uses those descriptions as an entry point for separating possible mechanisms.
START WITH A QUESTION
Why can’t I start even when I know what to do?
Separate an initiation problem from unclear next actions, over-preparation, and context conditions that can produce the same surface pattern.
Separate the starting problem → CONTINUITYWhy do I keep stopping once I start?
Separate ordinary continuity loss from friction-triggered stopping, failed re-entry after interruption, and context conditions that destabilize execution.
Separate the stopping problem → CLOSUREWhy can’t I finish?
Separate a true closure problem from missing completion proof, continuity loss before the finish line, and uncertainty about what “done” requires.
Separate the finishing problem → RECOVERYWhy is it hard to restart after an interruption?
Separate a true recovery problem from unclear re-entry steps, unstable continuity, and changed conditions that can make returning to the work fail.
Separate the restart problem → BROAD PATTERNProcrastination vs. execution breakdown
See why visible delay does not identify a single cause, and how WAH MEK separates the mechanism before testing a correction.
Separate delay from mechanism →CONTINUE