Tasks inherit their parent objective's priority — trace each task to 'which ranked objective does this advance?' before scheduling
For each task on your to-do list, trace it upward by asking 'Which of my ranked objectives does this directly advance?' and assign it the inherited priority of that objective, not its standalone urgency.
Why This Is a Rule
Tasks have two types of priority: standalone urgency (how time-sensitive the task feels) and inherited priority (which objective the task serves). These rarely align. Filing expenses feels urgent (deadline approaching) but serves a low-priority objective (administrative compliance). Drafting the product strategy feels non-urgent (no deadline) but serves your highest-ranked objective (product launch). Without priority inheritance, urgency wins by default — and your highest-priority objectives get only the leftover time after all urgent-but-low-objective tasks are completed.
Priority inheritance overrides this: each task's priority is determined by the ranked objective it serves, not by its standalone urgency. An expense filing serving objective #5 gets objective-5 priority regardless of its deadline urgency. A strategy draft serving objective #1 gets objective-1 priority regardless of its lack of urgency. The inheritance ensures that your best time goes to tasks serving your best objectives (Draw the line after item 3 — peak attention hours go above the line, everything below gets leftovers or explicit deferral).
Tasks that can't trace to any ranked objective are orphans — they don't inherit any priority because they serve no objective. Orphans should be questioned: why does this task exist if it doesn't advance any objective? (Classify every task as ONLY ME, COULD DELEGATE, or SHOULD NOT EXIST — then eliminate or delegate everything outside ONLY ME SHOULD NOT EXIST category).
When This Fires
- When prioritizing a to-do list for the day or week
- When urgency is dominating your task selection despite having clear objective rankings
- When important tasks keep losing to urgent ones — the inheritance is missing
- Complements Draw the line after item 3 — peak attention hours go above the line, everything below gets leftovers or explicit deferral (top-3 peak allocation) with the task-level assignment mechanism
Common Failure Mode
Urgency-based prioritization: sorting tasks by deadline rather than by parent objective. This produces days where every task is "done" but no important objective advanced — because all the completed tasks served low-ranked objectives that happened to have deadlines.
The Protocol
(1) Start with your ranked objectives (Break 'everything is priority 1' paralysis with pairwise comparison: 'if I could only accomplish one in 90 days, which?'-686). (2) For each task on your list, ask: "Which of my ranked objectives does this directly advance?" (3) Assign the task the priority of its parent objective: tasks serving objective #1 get priority 1. Tasks serving objective #3 get priority 3. (4) Tasks that don't serve any ranked objective → classify as orphan. Either find the objective connection or mark for elimination. (5) Schedule and execute tasks by inherited priority, not standalone urgency. Objective-1 tasks get peak hours (Draw the line after item 3 — peak attention hours go above the line, everything below gets leftovers or explicit deferral). Objective-3 tasks get leftover capacity. Urgent orphans get scheduled around objective-aligned work, not before it.