The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Schedule important-but-not-urgent tasks (Q2) on your calendar with specific day and hour blocks before touching urgent tasks, because scheduling converts intention into commitment while deferral guarantees displacement.
When a category contains more than 7-9 items all claiming equal priority, force binary pairwise comparisons asking 'if I could only accomplish one in the next 90 days, which one?' to produce ordinal ranking.
After producing a ranked priority list, draw a line after the third item and allocate your peak attention hours only to items above that line, treating everything below as receiving leftover capacity or explicit deferral.
Each morning before opening email or responding to requests, ask 'What is the ONE thing I can do today such that by doing it everything else becomes easier or unnecessary?' and write the answer before starting work.
Apply the ONE thing question at nested time horizons (daily, weekly, quarterly) and verify that answers align such that daily ONE things serve weekly ONE things which serve quarterly objectives.
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.
Schedule your week by grouping tasks under their parent objectives, then allocating best hours to goal-one tasks, next-best hours to goal-two tasks, with unconnected tasks either scheduled last or eliminated.
Schedule recurring reassessment checkpoints (weekly/monthly/quarterly) calibrated to domain volatility rather than relying on spontaneous awareness to detect when priorities need updating.
When environmental conditions shift (personnel changes, market movements, health events, new opportunities), pause execution and run the zero-based question on each current priority before resuming work.
Define event-based reassessment triggers in advance by listing specific conditions that would invalidate each priority, then treat trigger activation as mandatory pause points rather than optional considerations.
Maintain a priority stack of three to five items maximum, working exclusively on the top item until it completes or genuinely blocks, then rotating to the next unblocked item rather than distributing attention across the full list.
Cross-reference your priority stack weekly against your commitment budget to verify that every stack item corresponds to a budgeted commitment and every budgeted commitment has appropriate stack representation.
When declining requests, state three components explicitly: what you're declining, why (the priority being protected), and an alternative when appropriate—never just 'I'm busy.'
Conduct quarterly priority debt audits by dating each important-but-not-urgent priority's first identification, estimating original versus current cost to address, and scheduling the highest-interest-rate debts first.
When priority conflicts arise with stakeholders, present the tradeoff as a forced binary choice with visible costs for each option rather than silently absorbing both demands or refusing without explanation.
Distinguish strategic deferral (conscious choice with communicated tradeoffs) from silent deferral (automatic absorption without negotiation) by asking whether you chose to defer or failed to negotiate—only the former preserves sovereignty.
At the start of each week, write your top priorities on a blank page without consulting last week's list, then compare only after fresh selection is complete to detect drift.
When someone makes a request that would conflict with your top priority, name that priority explicitly and ask whether the request can wait or go to someone else with available bandwidth.
Log how you spent your waking hours in thirty-minute blocks for one week, then categorize every block by domain and calculate the percentage of discretionary time each priority actually received.
Each week, verify that your calendar gives each priority a time block proportional to its rank—if your top priority receives less time than your third priority, you have structural misalignment requiring correction.
When analyzing which activities consumed the most time this week, tag each with its trap mechanism—perfectionism, people-pleasing, novelty-seeking, busyness signaling, or sunk cost anchoring—to identify your dominant distortion pattern.
When your active priority count exceeds five, apply the triage question: if you could only advance two priorities this week, which two would create the most downstream relief or unlock the most progress?
For each priority you defer during simplification, assign one of three explicit dispositions: defer to a named date, delegate to a named person, or declare pause with stakeholder notification.
Treat simplification to one or two priorities as an emergency protocol to execute during overwhelm, not as a permanent lifestyle—scale back up to your full three-to-five item stack once capacity recovers.