Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Calculate feature-learning ROI
When a tool's advanced features would save time but require learning investment, calculate break-even: if the feature saves X minutes per use and requires Y hours to master, invest if (frequency × X) > Y within 90 days—shorter payback windows justify learning effort.
For execution (not coordination), choose task tools…
Choose task management tools that support if-then implementation intentions and context tagging over feature-rich project management tools when your primary need is execution not coordination—simpler tools with behavior-triggering structure beat complex tools optimized for planning.
Map tool stack as a graph
Map your tool stack visually with tools as nodes and data transfers as edges, labeling each edge as manual/automated and daily/weekly/monthly—this diagram reveals bottlenecks (high-frequency manual transfers) and redundancies (overlapping functions) that narrative inventory cannot surface.
One-week removal test for tool necessity — if you don't…
Test whether a tool is earning its place in your stack by temporarily removing it for one week—if you don't consciously miss specific capabilities (not just habit), the tool is redundant and should be permanently removed to reduce maintenance surface.
Consolidate overlapping tools by integration quality…
When two tools provide overlapping functionality, consolidate to the tool that integrates better with your stack even if the eliminated tool has superior standalone features—integration quality dominates feature quality in compound workflows.
Run old and new tools in parallel for 2-4 weeks during…
When migrating tools, run both systems in parallel for 2-4 weeks with new data going to the new tool and old data accessed from the old tool, ending only when the parallel period confirms the new tool handles your daily needs.
Test migration before committing
Before migrating any tool, test the destination by importing 20-50 representative items and examining every imported item in detail for formatting survival, metadata preservation, and link integrity.
Migrate active working set (last 90 days) first and verify…
Migrate your active working set (notes/tasks/projects accessed in last 90 days) first and verify every item against the original before migrating archival data.
Set calendar default duration to your actual most-common…
Set your calendar's default meeting duration to match your actual most-common meeting length (e.g., 25 minutes if that's what you schedule 90% of the time) to convert repeated decisions into one-time pre-commitment.
Learn platform-level shortcuts before app-specific ones…
Prioritize learning platform-level shortcuts (Ctrl+C, Ctrl+V, Ctrl+Z, Ctrl+S, Ctrl+Tab, Alt+Tab) before application-specific shortcuts because they transfer across every tool in your stack.
Require a trial period with pre-defined success metrics…
Before adding any new tool to your stack, require it to pass a trial period with pre-defined success metrics and a scheduled exit date, eliminating tools that fail to meet criteria.
3-2-1 backup rule
Apply the 3-2-1 backup rule: maintain at least 3 copies of critical data, on at least 2 different media types, with at least 1 copy stored offsite.
Test backup recovery quarterly
Test one backup quarterly by performing a simulated full restore to verify recoverability before you need it, timing the process and documenting any gaps.
Offline capability audit
Conduct an offline capability audit by disconnecting from internet and testing each critical tool for 10 minutes, grading as fully offline, partially offline, or fully dependent, then identifying local-first alternatives for any fully-dependent critical tool.
Verify data portability before committing
Before committing to a new tool, verify it stores data in exportable open formats by actually performing an export and checking whether another tool can import it without significant loss of structure or metadata.
Practice core cognitive tasks weekly without AI — prevent…
Maintain weekly practice of core cognitive tasks without AI assistance to prevent skill atrophy in capabilities the AI handles routinely, treating this as backup generator testing for cognitive infrastructure.
Define 3 measurable success criteria before any tool…
When evaluating new tools, define three specific measurable criteria before beginning trial and set evaluation period between 14-30 days, as shorter periods miss friction and longer periods activate sunk cost bias.
Run old and new tools in parallel during evaluation…
During tool evaluation periods, maintain parallel operation of existing tools rather than migrating fully, to create controlled comparison between old and new under comparable conditions.
Start weekly reviews…
Begin weekly reviews by stating what your tools helped you produce before reviewing tool configuration or optimization, to anchor tool evaluation in outcomes rather than activity.
Reconfigure bad tool defaults during high-capacity periods…
When tool defaults consistently produce undesired behaviors, reconfigure the default settings during high-capacity periods rather than overriding them repeatedly through willpower during execution.
For critical tools with no export or backup
For critical tools with no export function or backup strategy, either establish automated exports and identify viable alternatives, or consciously accept the single-point-of-failure risk in writing.
Optimize your workspace for your highest-value activity…
When designing workspace environments, accept sub-optimality in lower-value activities to achieve near-optimality in your highest-value activity, treating this tradeoff as a feature rather than a compromise.
Separate functions in shared spaces with orientation, time…
Resolve space-function overlaps through orientation changes (facing different directions), time-based zoning (function varies by time of day), physical markers (specific lamp only on during deep work), or relocation — not through willpower to mentally separate functions sharing the same physical space.
Tally every physical reach and digital tool switch for one…
For one full work session, keep a tally sheet and mark every time you reach for a physical object or switch to a digital tool — do not trust intuition about usage frequency, as it is systematically biased toward what feels important rather than what is actually frequent.