Skip to content

Latest commit

 

History

History
38 lines (27 loc) · 1.53 KB

prioritization.md

File metadata and controls

38 lines (27 loc) · 1.53 KB

Prioritization rubric

How the scanner orders open loops, most-urgent-first. The board renders this order directly, and the "Right now" hero is simply the top item.

Tweak this file to change what "urgent" means to you.

The tiers

Urgent — act within 24–48h or something breaks.

  • Hard deadlines (applications, payments, renewals).
  • Time-sensitive prep (an interview tomorrow, a meeting in an hour).
  • Anything with a cost for waiting (a trial about to renew, a slot about to fill).

High — act this week.

  • Active projects with momentum: keep them moving while they're warm.
  • Commitments to other people (replies owed, follow-ups promised).
  • waiting items whose nudge date arrived.

Normal — real, but no clock.

  • Ongoing projects, drafts in progress, plans forming.
  • The bulk of a healthy board lives here.

Low — the backlog.

  • Nice-to-haves, someday/maybe, research rabbit holes.
  • Never deleted, never nagged about. Visible at the bottom so they stop occupying headspace.

Tie-breakers (same tier)

  1. Earlier due date first.
  2. External commitment beats self-commitment (someone waiting on you outranks you waiting on you).
  3. Smaller next action first — a 5-minute win beats a 5-hour project when energy is scarce.

Anti-rules

  • Don't inflate: when everything is urgent, nothing is. Most items are normal; that's fine.
  • Don't age items up automatically. An old normal item is still normal unless a deadline appeared.
  • The user's explicit priority beats the rubric. If they said "this can wait," it waits.