Group weekly tasks under parent objectives, allocate best hours to goal-one tasks — unconnected tasks go last or get eliminated

Why This Is a Rule

Tasks inherit their parent objective's priority — trace each task to 'which ranked objective does this advance?' before scheduling assigns inherited priority to tasks. This rule converts those priorities into a weekly schedule by matching task priority to time quality. The principle: your best cognitive hours should go to your best objectives' tasks, and your lowest-quality hours should go to your lowest objectives' tasks (or orphans).

The grouping step is the key organizational move: instead of a flat to-do list sorted by deadline, you organize tasks under their parent objectives. This makes the objective-task relationship visible in the schedule itself: "Goal 1 tasks: strategy draft, customer interviews, prototype review. Goal 2 tasks: hiring pipeline, team training." Each group gets allocated a time quality tier based on its parent objective's rank.

Unconnected tasks — those that can't trace to any ranked objective — receive the "last or eliminated" treatment. "Last" means they get whatever time remains after all objective-aligned tasks are scheduled. "Eliminated" means the task doesn't survive the scheduling process — if it serves no objective and there's no remaining capacity, it doesn't happen. This is the practical implementation of Classify every task as ONLY ME, COULD DELEGATE, or SHOULD NOT EXIST — then eliminate or delegate everything outside ONLY ME's SHOULD NOT EXIST category.

When This Fires

• During weekly planning sessions
• When the to-do list is long and undifferentiated — grouping reveals what actually matters
• When important work consistently loses to busy-work in the weekly schedule
• Complements Tasks inherit their parent objective's priority — trace each task to 'which ranked objective does this advance?' before scheduling (task-level priority inheritance) with the weekly time-allocation implementation

Common Failure Mode

Flat-list scheduling: sorting all tasks by deadline regardless of parent objective. The resulting week serves many low-priority objectives while high-priority objectives get fragmented scraps of time. Grouped scheduling ensures the highest-priority objective's tasks get the best and most time, not just whatever is left.

The Protocol

(1) List all tasks for the week. (2) Group under parent objectives: which objective does each task serve? Create clusters. (3) Identify orphans: tasks that don't fit under any objective. Question each: eliminate if possible, schedule last if necessary. (4) Allocate time tiers: Goal 1 tasks → peak hours (mornings, high-energy blocks). Goal 2 tasks → next-best hours (late morning, early afternoon). Goal 3+ tasks → remaining capacity (post-lunch, end of day). Orphans → whatever's left, if anything. (5) Block the calendar following this allocation. Goal 1 tasks occupy the best time slots before anything else is scheduled.