Know what done looks like

Work without a definition of done becomes busywork, and busywork is how a week ends with finished tasks and no result anyone can defend. Every task on the plan carries a measurement contract: what will be measured, from which source, over which window. Reading it before you execute is what makes the Measure step possible. It tells you which number will judge the work and when that answer is due, so you are not assembling a story later from whatever figures happen to look good.

Before you begin any task, especially the first time you run a weekly plan. Also when a task feels vague: the card tells you whether that's a real gap.

• You have picked the week's move (see Start with this week's move).
• You know which integrations are connected (for example GA4 or Meta), because they decide what can be measured automatically.

1. 1Open the task card and read "Why this matters", then expand "How we'll know it worked". That panel is the task's structured contract, with chips for the target, metric, source, and window.
2. 2Read the sentence above the chips, which ends with "A good signal is" and the expected result. That is the number that would tell you the task did its job.
3. 3Decide now what you will do if the signal stalls, so you know when to hold and when to adjust.
4. 4Check the due date, if one is set ("Set due date" adds one). If the work can't realistically land inside the window, say so now. A plan that ignores capacity fails silently.
5. 5If the "UPCOMING SEASONAL OPPORTUNITIES" section appears, scan it. If a seasonal moment lines up with the task (a holiday, a local event), attach the work to it; if not, move on.
6. 6If the card carries no metric, source, or window, name that plainly: success is not defined for this task. Either define it or treat the task as completion-only proof.

The measurement contract (target, metric, source, window) and the expected good signal. On a completion-only task you see no result affordance; that is the design, not a missing feature.