Personal prioritization is choosing what work deserves your best energy instead of reacting to every request equally. Several lightweight routines encode this. The 1-3-5 rule commits each day to one big task, three medium tasks, and five small tasks. The ABCDE method labels tasks from A (must-do, serious consequences) through E (eliminate), and the rule is that all A's get done before any B's. Eat the Frog is the Mark Twain-inspired rule of tackling the hardest or most-procrastinated task first thing in the morning — protecting peak cognitive hours for the work that matters most.
Capacity metaphors shape thinking. The Pareto Principle, the 80/20 rule, suggests that roughly 80% of outcomes come from 20% of inputs, so focus goes to the high-leverage 20%. The Pickle Jar Theory loads the largest rocks first — your real priorities — and lets smaller commitments and busywork fill around them rather than displacing them. The boulders, rocks, pebbles, and sand framework makes the same point with more granularity. The Ivy Lee method ends each day by writing the six most important tasks for tomorrow, in order, and working them sequentially until done.
Several time-management systems embed prioritization explicitly. The Bullet Journal's migration habit periodically reviews unfinished tasks and decides to move, schedule, or drop them — built-in prioritization hygiene. The two-minute rule, from Getting Things Done, says that if a task takes under two minutes, do it now rather than scheduling it. GTD's prioritization layer uses context, time available, energy, and priority in that order to pick the next action. A two boxes approach keeps one box for committed work and another for stretch, protecting commitments while leaving room for opportunistic wins. The two-pizza team rule from Amazon bounds priority scope to a domain small enough that two pizzas feed everyone, recognizing that small teams need stricter prioritization than large ones because less slack means each "yes" excludes more.
The honest tests of personal prioritization are uncomfortable. The calendar test compares stated priorities against what is actually scheduled. The money test asks whether the team would pay real budget to have something done first. The manager-vs-maker schedule distinction, from Paul Graham, reminds us that makers need long uninterrupted blocks; prioritization decisions should protect those blocks from being fragmented by meetings. Decision fatigue degrades late-day decisions, so big priority choices belong in the morning. An interrupt budget defines the team's tolerance for unplanned work this period; once exhausted, new asks defer. The two-week rule: if a priority item hasn't moved in two weeks, escalate or kill it — zombie commitments quietly drain attention. A no list raises the cost of new asks creeping in unchecked, and negotiated deferral — agreeing the request is valid but committing to a later, named date — preserves trust without overcommitting capacity. The "say yes to the person, no to the task" technique honors the relationship while still declining the work. Finally, the meta-question for any system: "Are we working on the most important things — and how would we know if we weren't?"