ZelnickSignal hub
UTC --:--

Field manual / 2 MIN PROTOCOL

Time and attention protocol

A recovered productivity note rebuilt around finite attention, deliberate refusal, and work that can actually end.

ACTIVE SIGNALRECOVERED SOURCE / CURRENT PROTOCOL

FM.03REVISED 2026-07-25

Curated from two recovered productivity and personal fragments.

Time management is often described as arranging hours. The scarcer resource is attention: the ability to remain with one worthwhile thing long enough to change it.

Name the signal

Choose one outcome that would make the session count. Write it in language that can become true: the deployment is verified, the essay has a complete first draft, or the failure has a reproducible cause.

A list of ten unrelated intentions is not a plan. It is an archive of future guilt.

Give it a boundary

Reserve a block of time and decide what ending means before beginning. A 25-minute interval can help when starting is the problem; a longer block is better when the work needs depth. The timer is not a judge. It is a shoreline.

Remove notifications, close unrelated surfaces, and keep a small capture area for thoughts that belong later. Distraction is easier to release when it knows it will not be forgotten.

Distinguish priority from volume

Ask:

  • What changes something important?
  • What prevents future damage or confusion?
  • What only feels urgent because it is visible?
  • What should be deleted, delegated, or allowed to remain unfinished?

Do the consequential work while attention is intact. Group mechanical tasks into a shallower channel.

Refusal is part of the system

The recovered note said to learn when to say no—and to allow yourself to say yes. Both matter. Refusal protects the work already chosen; consent keeps the system from becoming a fortress built around productivity.

Going with the flow can become a quiet way of letting other people schedule your life. A useful plan should still leave enough unclaimed space to recognise your own decisions.

Close the loop

At the end of a block, record what changed, what remains, and the smallest next action. Then stop. Rest is not the absence of the protocol; it is how the protocol remains possible tomorrow.

attentionpracticeboundaries