A 30-Second Check to Verify the Task You Chose Actually MattersUpdated a month ago

"Before you strike the match, run a quick verification. It takes 30 seconds. It keeps you from spending 120 minutes on the wrong thing. Do it with the candle unlit, phone already away, workspace quiet.

TWO-QUESTION CHECK

1. If this task is done when the flame dies, what will be different?

2. Would a week from now show that today was the right choice?

Answer both in one or two plain sentences. If you cannot, you chose motion, not progress. If you hesitate on the second, you chose urgency, not importance.

WHAT A CLEAR ANSWER SOUNDS LIKE

Question 1 wants a visible change at the end of the session. Examples:

- Draft: “A complete first draft of the intro section exists in the doc.”

- Code: “Authentication bug reproduces in a failing test and is fixed locally.”

- Research: “Three vetted sources are summarized in notes, with citations.”

- Planning: “Next sprint has a 6-item backlog with owners and dates.”

Vague answers signal motion:

- “I’ll look into it” (what difference will exist?)

- “I’ll get organized” (organized into what output?)

- “I’ll make progress” (progress toward what finished unit?)

THE ONE-WEEK TEST

Question 2 protects you from near-term noise. A week from now:

- Clear yes examples: “Users can sign in without errors,” “Client has a draft to review,” “I have slides ready for rehearsal.”

- Likely no examples: “Inbox at zero for an hour,” “Pixel-perfect spacing on an internal deck,” “Reformatting notes.”

If the future you wouldn’t care, do not light the candle for it.

HOW TO RUN IT IN 30 SECONDS

- Put the phone away. Open your session notebook or a plain sheet.

- Write the task name at the top.

- Answer Q1 in one sentence: the end-state when the flame dies.

- Answer Q2 with Yes/No. If No, choose a different task.

- If Q1 feels fuzzy, sharpen the task into a concrete deliverable and repeat.

WHEN YOU’RE STUCK CHOOSING

- Reduce scope: pick the smallest unit that still changes reality.

- Anchor to handoff: what can you send, ship, test, or publish at session end?

- Name the file now: “proposaldraftv1.docx” often clarifies the work.

- Set boundaries: one section, one module, three sources, five test cases.

COMMIT AND BEGIN

Once the answers are clear, close every unrelated tab and put tempting items on the shelf. State the end-state out loud, once. Strike the match. Work in silence. Stay until the flame dies. No mid-session re-choosing.

AFTER THE FLAME

Stop at the boundary you named. Capture one line: did the check hold? Place the tin on the shelf. If the session drifted, adjust tomorrow’s two-question check. With practice, checking session task is right choice becomes automatic and steadies your 120-minute rhythm."