Why does priority inheritance fail?

The most common reason priority inheritance fails: Treating inheritance as a justification for ignoring every task that does not serve your top goal. Priority inheritance is a sorting mechanism, not an elimination mechanism. A task connected to your fifth-ranked goal still matters — it just matters less than a task connected to your first-ranked goal and should be sequenced accordingly. The failure mode is using inheritance as an excuse for permanent neglect: letting relationship maintenance, health routines, or administrative obligations decay because they connect to goals ranked below your primary objective. Inheritance tells you what to do first, not what to never do. Someone who uses it to justify abandoning entire life domains has confused prioritization with tunnel vision — the same trap flagged in the ONE thing question (L-0685).

The fix: Pick five tasks currently on your to-do list — ideally a mix of things that feel urgent and things that feel neglected. For each task, answer one question: 'Which of my top-ranked goals (from L-0684) does this task directly advance?' Draw an arrow from each task to the goal it serves. If a task does not connect to any ranked goal, mark it with a question mark. Now re-sort your five tasks not by their individual urgency or age, but by the rank of the goal they serve. The task connected to your number-one goal goes first, regardless of how small or boring it seems. The task with no goal connection goes last — or gets deleted. Notice how different this ordering feels from the one you started with. The difference between the two orderings is the gap between activity-based prioritization and outcome-based prioritization.

The underlying principle is straightforward: Tasks inherit priority from the goals they serve — connect tasks to objectives.