THE PROBLEM
Repeated execution failure can look the same while coming from different mechanisms.
Two people can both say, “I keep procrastinating,” while the observable breakdown is different. One may understand the task but fail to initiate it. Another may start reliably and stop when friction appears. Another may work well until an interruption and then fail to return. Another may do most of the work but never close it.
WAH MEK does not treat those patterns as automatically equivalent. Its purpose is to narrow the explanation before prescribing the correction.
HOW IT WORKS
From presenting problem to evidence-based next decision.
- Describe the observable break.WAH MEK begins with what repeatedly happens, not with a personality label.
- Separate competing explanations.The system compares plausible execution mechanisms rather than forcing the first familiar label.
- Select a provisional Working Diagnosis.The current explanation is treated as testable and revisable, not permanent.
- Test one targeted correction.The correction is chosen to act on the suspected mechanism instead of stacking generic advice.
- Record Proof.The user records what was actually done and what observable result existed afterward.
- Retest under comparable conditions.Response across valid exposures helps determine whether to preserve, revise, switch, or reopen the explanation.
THE WORKING DIAGNOSIS LIBRARY
WAH MEK currently separates 12 execution mechanisms.
These are WAH MEK product classifications used to organize execution patterns and test corrections. They are not medical or mental-health diagnoses.
WHAT MAKES IT DIFFERENT
WAH MEK is not designed to be another place to store tasks.
Primarily organize what needs to be done. WAH MEK focuses on why execution of the intended action keeps breaking.
Often gives broadly useful tactics. WAH MEK attempts to match one correction to the current Working Diagnosis.
Can generate explanations and suggestions. WAH MEK uses a bounded diagnostic, correction, Proof, Retest, and decision sequence.
Primarily record repetition. WAH MEK uses observed response as evidence for or against a specific mechanism explanation.
EVIDENCE BEFORE CERTAINTY
A first response is information, not final proof.
WAH MEK is built around the idea that a plausible explanation should survive contact with observed behavior. A correction is therefore not treated as successful merely because it sounds good or because the user intends to perform it.
The system distinguishes the correction that was prescribed, whether the exposure was valid, what was actually done, what observable result occurred, and whether a later Retest was sufficiently comparable. Repeated valid response can increase confidence; non-response, invalid exposure, or conflicting evidence can trigger a different decision.
The purpose is interpretability: change enough to test the suspected mechanism without changing so many things that the result becomes difficult to interpret.
BOUNDARIES
What WAH MEK does not claim.
- WAH MEK does not provide medical or mental-health diagnosis or treatment.
- A WAH MEK Working Diagnosis is a product-level, provisional explanation of an execution pattern.
- The system should preserve uncertainty when the available evidence cannot support a stronger conclusion.
- A correction that works once is not automatically treated as a permanent solution.
- Broader goals provide context, but the system’s immediate job is to test the mechanism believed to be breaking execution.
METHODOLOGY
The system is designed to revise itself when the evidence changes.
WAH MEK separates the presenting problem, Working Diagnosis, correction, Proof, Retest, and decision into distinct stages so that a later outcome can challenge an earlier assumption. The objective is not certainty at the first pass. It is a better-supported next decision.
Explore WAH MEK methodology → Understand execution breakdown →