Define what finished looks like for each step

Decide in advance what a completed step looks like, because a step is either done correctly or not done at all.

Pourquoi ça marche

The 2007 introduction says tasks are quantal (all or nothing): they are either completed correctly or not completed at all, with no intermediate state. The model uses this to treat stages as hard and distinct. This page applies it as a self-check: a yes-or-no completion question for each step removes the fuzzy middle where you can keep telling yourself you are nearly there.

Comment faire

  1. For each sub-step, write one question that has a yes or no answer, such as “is the figure checked against the source?”
  2. Do the step, then answer that question only.
  3. If the answer is no, the step is not complete, whatever progress you feel.
  4. Keep the list visible so the next session starts from what is actually done.

Données probantes

The quantal character of tasks is a stated assumption of the 2007 introduction, used there to justify discrete stages. Using it as a self-check is this page’s application. (mechanistic)

The model assumes quantal tasks as a basis for scoring. Many real goals are not quantal, and forcing a yes or no on them can distort the work.

Sources

Erreur fréquente

Counting a step as nearly done because most of its effort is spent, and skipping the check that would show what is still missing.

Pratiquez cela avec IX Coach

Commencer avec IX Coach

Plus de pratiques pour The Model of Hierarchical Complexity, Explained

Concepts associés