Open loops kill desk focus. A half-done page, a parked plugin fix, a lead enrichment switch you “might try later.” None of them need a daily ping. They need a date.

If the work is not finishable this week, do not leave it as a vague chat promise. Park it with a revisit that will actually fire.

The tip

Every unfinished item gets one of three homes:

  1. Done this week (scheduled work with a clear finish line)
  2. Parked with a date (a reminder or calendar block that names what to decide)
  3. Dropped on purpose (written as killed, so it stops floating)

“We’ll get to it” is not a home. It is how polish and half-ideas steal outreach time for weeks.

How to park cleanly

  • Write the outcome in one sentence (what “done” means)
  • Name the blocker in plain words (plugin 500, credit burn, waiting on a form test)
  • Set a revisit date inside weekday hours
  • Say what the wake should ask: resume, revise, or kill

The revisit is a decision, not a status dump. When it fires, you choose. You do not re-discover the whole thread from memory.

What not to do

  • Leave the item only in chat history
  • Keep poking at it in odd minutes with no finish line
  • Set a reminder with no ask (“check Customizer”)
  • Park five things for the same morning

One parked item per wake is plenty. Batching five “maybe later” tasks into one morning creates the same second inbox you already cleaned up elsewhere.

Paste-ready rule

Park-with-a-date rule:
1) Unfinished work is Done this week, Parked with a date, or Dropped on purpose.
2) A park note must include: outcome, blocker, revisit date, and the decision ask (resume / revise / kill).
3) Prefer a weekday daytime reminder over "someday."
4) The wake asks for a decision. It does not restate the whole history.
5) If you will not decide by that date, drop it on purpose instead of sliding the date forever.

This keeps the desk pointed at finishable work and customer outreach, and keeps half-built ideas from pretending they are still on the critical path.

Park It With a Date