Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Incomplete tasks need longer transition buffers…
After incomplete tasks, insert longer transition buffers than after completed tasks, because unfinished work generates stronger attention residue that degrades subsequent performance.
One 15-minute overflow buffer per 2-3 hours of scheduled…
Schedule one 15-minute unallocated overflow buffer for every 2-3 hours of scheduled activity to absorb inevitable overruns and interruptions without cascading disruption through the rest of your day.
Fill the afternoon trough (typically 1-3 PM) with admin…
Fill the early-to-mid afternoon trough period (typically 1-3 PM for morning types) with administrative work that requires competence but not analytical depth, rather than scheduling demanding cognitive work that will feel disproportionately difficult.
Record estimate before and actual time after every 30+…
Before any task over 30 minutes, write your time estimate; after completion, write actual time—do this for two weeks minimum to generate sufficient data for personal estimation ratio calculation.
Three-point estimation
Generate three estimates (optimistic, realistic, pessimistic) for each significant task and calculate weighted average as (optimistic + 4×realistic + pessimistic)/6 to counteract automatic optimism bias in single-point estimates.
Apply your personal estimation ratio as a multiplier…
Apply your measured personal estimation ratio as a multiplier to all future estimates—if actual/estimated consistently = 1.8, budget tasks at 1.8× your initial estimate to achieve calibrated forecasting.
Estimate four components separately
When estimating tasks, separately account for setup time, core work time, interruption/recovery time, and teardown/transition time—omitting these categories causes systematic 30-60% underestimation of total duration.
Start project estimates with reference class forecasting…
Begin project estimates with reference class forecasting from 3-5 comparable past projects before considering project-specific details, as base rates predict outcomes more accurately than inside-view planning.
5-15 minute pre-mortem before committing to any project…
Before committing to any significant project plan, conduct a 5-15 minute pre-mortem by assuming failure has occurred and listing 3-5 specific failure causes to surface risks that forward-looking analysis systematically misses.
Calibrate your personal do-it-now threshold
Calibrate your personal two-minute threshold by comparing management overhead (processing, organizing, reviewing, re-engaging) against execution time for 10 recent tasks—set threshold where overhead equals execution cost.
Flex your dispatch threshold with context
During meeting-heavy days with fragmented administrative windows, lower your dispatch threshold to ~1 minute; during dedicated administrative blocks, raise it to ~5 minutes to match available processing capacity.
Batch tasks by cognitive context…
When batching similar tasks, group by cognitive context type (communication, financial, scheduling) rather than by chronological arrival order to minimize context-switching overhead.
Four-element meeting gate
Before starting any meeting, verify that four structural elements exist: stated purpose (what decision/problem), timed agenda with allocations, hard stop time, and defined outputs—if any element is missing, either add it or cancel the meeting.
Open meetings with 15-20 minutes of silent reading…
Distribute pre-read documents before meetings and open with 15-20 minutes of silent reading to ensure all participants enter discussion with identical context, eliminating the information-transfer phase that consumes the first half of unprepared meetings.
Cap decision meetings at 6-8 people — communication…
Limit meeting attendance to 6-8 people maximum to prevent communication complexity from scaling combinatorially (n(n-1)/2 conversational pairs) and social cost from suppressing genuine discussion.
Compress meetings into contiguous blocks on designated…
Compress meeting schedules into contiguous blocks on designated days rather than distributing them evenly across the week to preserve multi-hour maker time blocks on remaining days.
Replace status-update meetings with async written updates…
Replace recurring status update meetings with asynchronous written updates unless the meeting serves an additional coordination function beyond information transfer.
Block recovered time for priority work immediately…
Immediately block recovered time on your calendar for specific priority work before recovering it—recovery without preallocation creates a vacuum that entropy fills with new low-value activities within weeks.
Use AI to analyze routine execution logs…
Use AI to analyze routine execution logs across multiple cycles, identifying which deviations correlate with missed executions, to diagnose structural fragility points invisible from inside the experience.
When one routine element fails, execute minimum viable…
When a single element of your routine fails, execute the minimum viable versions of remaining load-bearing elements rather than abandoning the entire routine structure.
Classify routine elements as load-bearing…
Classify each routine element as load-bearing (removing it degrades output or wellbeing) or cosmetic (preferred but not essential) to distinguish what must survive disruption from what can be sacrificed.
Commit 7-8 hours when you have 10 available — leave 2-3…
Plan for seven to eight hours of committed work when you have ten productive hours available, leaving two to three hours as unallocated slack to absorb disruptions without cascade failures.
Audit the past 12 months of calendar data — rate each…
Conduct seasonal time audits by pulling calendar data from the previous twelve months and rating each month as low-demand, baseline, high-demand, or crisis to identify recurring annual patterns.
Make at least one structural adjustment before each…
For each identified high-demand period, make at least one structural adjustment before the period arrives by pushing deadlines, reducing project count, or front-loading preparation during preceding calm periods.