Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Pair every important outcome with 1-2 leading indicators…
For each important outcome you care about, identify one lagging indicator (the outcome) and pair it with 1-2 leading indicators (upstream behaviors that predict it), tracking both to validate the predictive relationship.
Execute cuts during the audit session itself — deferral…
Execute all identified cuts during the audit session itself rather than creating a deferral list, as audit outputs are decisions implemented immediately not intentions documented for later.
Use a 3-step context switch
When switching between cognitive contexts, implement a three-step loading protocol: (1) close the current context by writing a one-sentence summary and noting open loops (30 seconds), (2) create a transition gap of deliberate non-engagement (60 seconds), (3) load the new context by reviewing relevant notes and orienting before producing (60 seconds).
Spend 60-90 seconds orienting before producing…
During context loading for complex cognitive work (coding, writing, design), spend the first 60-90 seconds orienting through review of previous state before attempting to produce output, as the cognitive system requires initialization time before it can operate at full capacity in that domain.
Bright cool light for analytical work, dim warm light…
Configure workspace lighting to match cognitive mode—bright, cool-temperature light (5,000-6,500K) for analytical work requiring convergent thinking; dim, warm light (2,700-3,000K) for creative work requiring divergent thinking.
When multiple contexts compete, designate one as primary…
When multiple contexts are active simultaneously, identify which one is primary for the current work period and explicitly park all others with specific time and place commitments.
When a commitment will be missed, renegotiate proactively…
When a commitment cannot be met, communicate the fact proactively before the deadline and renegotiate terms explicitly, as silent dropping versus explicit renegotiation distinguishes reliable commitment systems from internal intention failures.
Write blockers as 'I cannot [action] because [obstacle]'…
Write blockers in the form 'I cannot [specific action] because [specific obstacle]' immediately upon noticing friction to convert ill-structured problems into solvable ones.
Split compound blockers into separate obstacles…
Decompose compound blockers into separate obstacles with independent owners and solutions before attempting resolution, because monolithic blockers resist action through perceived complexity.
Weekly
Audit thinking environments weekly by comparing actual conditions against documented specifications to detect entropy, because environmental decay through accumulated objects, browser tabs, and permission drift is constant and unnoticed without structured review.
Define each priority level with a one-sentence operational…
Write a one-sentence decision rule for each priority type that defines membership criteria operationally before applying the types to any backlog.
If more than 20% of items are top priority…
Ensure that highest-priority items constitute less than 20% of total backlog; if more items are marked critical, recalibrate threshold definitions to restore differentiation.
Every priority system needs an explicit 'not now' tier…
Include an explicit 'not now' or lowest-tier priority type to prevent deferred items from inflating middle categories and to create visible records of deliberate exclusion.
Priority labels without response protocols are decoration…
Attach specific response protocols (timing, resources, escalation) to each priority type rather than treating them as descriptive labels, making priority actionable.
When performance is stable with no bottleneck, stop…
When measurement data shows stable satisfactory performance with no identifiable bottleneck, redirect optimization effort to a different system rather than continuing to optimize the current one.
Calculate optimization breakeven time — if payback exceeds…
When evaluating whether to optimize an existing system, calculate breakeven time by dividing optimization effort by weekly time savings—if payback exceeds the system's expected remaining lifespan, redirect effort to the actual constraint instead.
Categorize weekly decisions as routine or novel — build…
Audit your work week by categorizing each decision as 'routine' (similar decision made before, could use framework) or 'novel' (requires fresh thinking), then for the five highest-frequency routine decisions, draft simple frameworks (default answer, two-option heuristic, or pre-commitment rule) and implement all five within one week.
Multiply direct correction time by 3x for true cost…
Track the full cost of recurring corrections by multiplying direct time by three to account for context-switching, opportunity cost, and verification overhead, revealing the true resource drain that justifies prevention investment.
When correction exceeds 20% of weekly capacity, shift…
When error correction consumes more than 20% of weekly capacity in a domain, shift resources from faster correction to upstream prevention mechanisms that reduce error generation rate.
Cap coordination at 15-25% of total hours — new…
Set an explicit coordination budget as a percentage of total available hours (15-25% for most knowledge work), and require any new coordination mechanism to fit within that budget or displace an existing one.
Classify every task as ONLY ME, COULD DELEGATE, or SHOULD…
Calculate your attention allocation by categorizing each task as ONLY ME (requires unique judgment), COULD DELEGATE (someone/something else can do it at 80%+ quality), or SHOULD NOT EXIST (adds no value), then delegate or eliminate everything outside ONLY ME to reclaim attention for highest-value work.
ONLY ME time below 50% of working hours signals…
When your ONLY ME time falls below 50% of working hours, you have a delegation deficit requiring immediate correction, because spending the majority of your highest-value resource on work that doesn't require it violates the constraint optimization principle.