Principles
2,201 principles · page 12 of 46
Record attention allocation in real time using both…
Record attention allocation in real time using both automated tracking and manual categorization to overcome retrospective estimation bias.
Question the assumptions underlying goals at quarterly…
Question the assumptions underlying goals at quarterly intervals, not just whether you are achieving them, because executing a strategy based on falsified assumptions produces tactical success masking strategic drift.
Rotate reflection questions periodically when answers become
Rotate reflection questions periodically when answers become predictable, because stale questions optimize brain's search path and prevent discovery of novel insights.
Use AI to generate follow-up questions and identify…
Use AI to generate follow-up questions and identify unexamined assumptions in completed reflections rather than to draft reflections, because the insight comes from your mind doing generative work, not from receiving polished analysis.
Conduct pattern analysis by reading multiple review periods…
Conduct pattern analysis by reading multiple review periods in a single session rather than individually, because working memory's 3-5 item limit prevents simultaneous access to temporally separated experiences during daily reflection.
Wait at least 24 hours between experiencing a failure…
Wait at least 24 hours between experiencing a failure and reviewing it formally, because perceived psychological threat is highest immediately after negative events and this heightened threat systematically reduces the honesty of self-assessment.
When analyzing successes, classify each contributing factor…
When analyzing successes, classify each contributing factor as replicable (within your control) versus contingent (dependent on external circumstances), then extract operational principles only from the replicable factors to avoid attributing controllable outcomes to luck.
Treat energy depletion patterns as leading indicators…
Treat energy depletion patterns as leading indicators of burnout rather than productivity decline, because emotional exhaustion precedes output degradation and is only visible through energy/emotion tracking, not task completion metrics.
Design review environments to ensure privacy from external…
Design review environments to ensure privacy from external observers, because the knowledge that others might see your reflections activates social self-presentation concerns that systematically distort the honesty of self-assessment toward socially desirable narratives.
Match vulnerable reflections to appropriate containers…
Match vulnerable reflections to appropriate containers — share with trusted partners who have psychological safety, relevant context, no competing interests, and proven trustworthiness.
Treat avoidance in reflection as diagnostic data pointing…
Treat avoidance in reflection as diagnostic data pointing toward the topics most important to your development, not as personal failure to overcome.
Categorize tracked activities by cognitive demand type…
Categorize tracked activities by cognitive demand type rather than clock time or task label to reveal attention allocation patterns invisible to narrative memory.
Make undiscussable topics discussable by naming…
Make undiscussable topics discussable by naming the avoidance explicitly before attempting to engage with the avoided content.
Shift focus from event reflection to system reflection…
Shift focus from event reflection to system reflection when reviews become repetitive — when current questions produce no new insight, question the level of analysis rather than abandoning the practice.
Focus quarterly reviews on systems and assumptions rather…
Focus quarterly reviews on systems and assumptions rather than actions — examine the mental models, beliefs, and structural patterns that generate behavior, not just the behavior itself.
Design tool stack architecture with explicit data flows…
Design tool stack architecture with explicit data flows, defined boundaries, and clear integration points rather than accumulating tools as isolated utilities.
Choose tools whose interface complexity matches…
Choose tools whose interface complexity matches the complexity of your need—tools that are too simple force workarounds while tools that are too complex impose unnecessary cognitive overhead.
Designate exactly one authoritative write location for each…
Designate exactly one authoritative write location for each information type to prevent sync drift and the cognitive overhead of reconciling contradictory copies.
Evaluate tools primarily on whether they reliably perform…
Evaluate tools primarily on whether they reliably perform your specific job-to-be-done, not on feature count or theoretical capabilities you may never use.
Choose tools that store data in open formats (Markdown, CSV…
Choose tools that store data in open formats (Markdown, CSV, JSON) rather than proprietary formats to preserve data portability and reduce migration risk.
Select tools based on how well they integrate…
Select tools based on how well they integrate with your existing stack rather than evaluating each tool in isolation, because integration quality determines system-level effectiveness more than individual tool quality.
Push past initial tool competence into proficiency…
Push past initial tool competence into proficiency by deliberately practicing capabilities that would expand your effectiveness rather than repeatedly using only the subset you already know.
Train attentional control through repeated…
Train attentional control through repeated detection-and-return cycles rather than attempting to prevent mind-wandering entirely.
Maintain exportable backups of your data in portable formats
Maintain exportable backups of your data in portable formats independent of whether you plan to migrate, to reduce future switching costs.
Evaluate tool interoperability as a primary selection…
Evaluate tool interoperability as a primary selection criterion rather than feature richness alone, as disconnected best-in-class tools require you to be the integration layer.
Consolidate functions into existing tools at 80%…
Consolidate functions into existing tools at 80% effectiveness rather than adding specialized tools at 100% effectiveness when the switching cost exceeds the capability gap.
Set defined trial periods with explicit success criteria…
Set defined trial periods with explicit success criteria for new tools, including a scheduled exit date, to prevent permanent accumulation of trial tools.
Build custom tools when frequency is high, requirements…
Build custom tools when frequency is high, requirements are highly specific to your workflow, and available skill permits maintenance you will not resent.
Buy commercial tools when requirements are standard across…
Buy commercial tools when requirements are standard across thousands of users, even if they serve your needs imperfectly, unless the imperfection creates friction in high-frequency workflows.
Treat the act of building a tool as a form…
Treat the act of building a tool as a form of externalization that reveals implicit steps in your workflow, making the tool itself secondary to the understanding gained.
Document tool configurations immediately upon creation…
Document tool configurations immediately upon creation with both the specific setting and the reasoning behind it, as a single artifact, to prevent drift between implementation and explanation.
Store configuration documentation as version-controlled…
Store configuration documentation as version-controlled files that serve as both the implementation and the documentation, making drift structurally impossible.
Build cognitive infrastructure on local-first tools where…
Build cognitive infrastructure on local-first tools where the canonical data copy exists on your device and network connectivity is optional for core functionality.
Design daily schedules around your finite deep work capacity
Design daily schedules around your finite deep work capacity rather than attempting to maximize total work hours or distribute effort uniformly across the day.
Design AI-augmented workflows with graceful degradation…
Design AI-augmented workflows with graceful degradation where AI accelerates but is not required, allowing core work to continue offline at reduced speed rather than stopping entirely.
Implement automated backup systems that run independently…
Implement automated backup systems that run independently of human memory and intention, removing yourself from the critical path of data protection.
Run tool evaluations with bounded scope and parallel…
Run tool evaluations with bounded scope and parallel baseline to create controlled comparisons rather than full-stack migrations.
Audit your entire tool stack quarterly to identify…
Audit your entire tool stack quarterly to identify redundancy, unused subscriptions, and unmaintained dependencies before they compound into cognitive overhead.
Review actual output produced before reviewing tool usage…
Review actual output produced before reviewing tool usage to maintain tools-in-service-of-goals rather than goals-in-service-of-tools orientation.
Establish single sources of truth for each data type…
Establish single sources of truth for each data type to prevent information duplication and the entropy of maintaining multiple conflicting versions.
Maintain offline capability for critical workflows to ensure
Maintain offline capability for critical workflows to ensure cognitive infrastructure remains functional when network connectivity fails.
Treat cognitive infrastructure as a coupled system where…
Treat cognitive infrastructure as a coupled system where capability emerges from the quality of integration between brain, tools, and methods rather than from any component in isolation.
Position tools and resources based on usage frequency rather
Position tools and resources based on usage frequency rather than categorical logic, placing high-frequency items within arm's reach to minimize retrieval friction and preserve flow states.
Create distinguishable contextual markers (orientation…
Create distinguishable contextual markers (orientation, lighting, objects, time blocks) to enable functional separation within a single physical space when dedicated rooms are unavailable.
Use concrete sensory descriptions instead of evaluative…
Use concrete sensory descriptions instead of evaluative labels to prevent defensive reactions and enable collaborative problem-solving.
Question each workspace object with 'did I use this for my…
Question each workspace object with 'did I use this for my current function in my last three work sessions?' rather than 'could this be useful?' to overcome endowment effect.
Create three workspace zones—active, near, and archive…
Create three workspace zones—active, near, and archive—with objects moving between them based solely on usage frequency relative to current function.
Match your lighting to circadian phase—bright, blue-rich…
Match your lighting to circadian phase—bright, blue-rich light during analytical work hours, warm, dim light in evening to protect sleep quality.