Rules
1,053 rules · page 20 of 22
Lay out multiple notes in parallel visual access…
Lay out multiple notes simultaneously in parallel visual access rather than reading them sequentially, because synthesis requires holding multiple ideas in working memory or visual space at the same time.
Look for structural parallels across inputs during…
During synthesis, look for structural parallels and shared dynamics across inputs rather than topical overlaps, because topical overlaps produce aggregation while structural parallels produce synthesis.
Test synthesis
Test synthesis output by asking whether it makes a claim that could not be found in any individual source - if it could be produced by listing inputs, you have aggregated rather than synthesized.
Inability to explain simply = incomplete processing…
When you cannot explain a concept in simple terms to someone with zero shared context, treat this as diagnostic evidence that your processing is incomplete rather than a labeling problem.
Declare information bankruptcy when backlog exceeds daily…
When information backlog in any queue exceeds your daily processing rate by more than 10%, declare that queue a bankruptcy candidate requiring immediate archive-and-reset rather than incremental catch-up.
Start processing habits tiny
Start new information processing habits with a minimal version (processing 5 items, 2-3 minutes) for five consecutive days before expanding to full sessions, because initiation barriers determine habit formation more than execution quality.
Four nested processing cadences
Operate information processing on four nested cadences: daily triage (20-30 min), weekly review (catch drift), monthly audit (source quality), and quarterly purge (accumulated sediment).
Pick a tool with 5 minimum requirements, select the first…
Choose one information processing tool by defining 5 minimum requirements, selecting the first that meets them, and committing for 90 days before re-evaluation, rather than maximizing across all available options.
Track daily completion (yes/no) not tool configuration…
Track daily whether you completed your information processing session (yes/no) rather than optimizing configuration, because consistent execution of a mediocre tool outperforms sporadic use of a perfect one.
Measure pipeline health by processing days in the last 30…
Measure information pipeline health by counting processing days in the last 30 (target: 28+), not by note count, graph density, or tool sophistication, because daily execution is the only variable that compounds.
When pipeline maintenance costs more than the pipeline…
When information pipeline maintenance consumes more cognitive resources than the pipeline saves, the system economics have inverted and simplification is required, not optimization.
Annotate each output type with its half-life…
Annotate each output type in your taxonomy with its approximate half-life (hours, weeks, months, years) to calibrate appropriate investment in durability, structure, and polish.
Define both good-enough criteria and over-investment…
For each output type, define both 'good enough' criteria and explicit over-investment thresholds to prevent perfectionism from consuming effort that belongs to higher-stakes work.
Mandatory quality pause between "I think this is done"…
Position quality verification between 'I think this is done' and delivery as a mandatory pause point with an explicit checklist, not as optional review when time permits.
Limit checklists to 5-9 items targeting frequent +…
Limit output checklists to five-to-nine items targeting errors that are both frequent and consequential, ordering from most catastrophic to least to enable partial execution under time pressure.
Build checklists from documented error history…
Build checklists from your documented error history rather than hypothetical failures, promoting an error to checklist status only after it has occurred in actual deliverables.
Embed checklists at the point of delivery — integrate…
Embed checklists at the physical or digital location where delivery occurs, making them harder to skip than to use by integrating them into templates, pull request forms, or pre-send screens.
Separate creation and editing into different calendar…
Schedule creation and editing as two separate calendar blocks with a minimum gap of thirty minutes (preferably overnight) to allow defamiliarization and enable fresh-eyes error detection.
Three sequential editing passes for high-polish outputs
For outputs requiring high polish, structure editing as three sequential passes—structural edit (organization), line edit (sentence clarity), copy edit (mechanics)—to prevent simultaneous optimization across incompatible dimensions.
Default pass policies by output type
Build default two-pass policies by output type—emails under five sentences single-pass, documents over one page mandatory two-pass, strategic outputs three-pass with overnight incubation—to prevent case-by-case deliberation.
Prioritize long half-life + high reach outputs over short…
Route attention and effort disproportionately to outputs with long half-lives (months-to-years) and high audience reach over outputs with short half-lives (hours-to-days) and narrow reach when both compete for finite production time.
Name the specific output before consuming information…
Before consuming any information during learning sessions, define the specific output that consumption will feed into—if no output can be named, the learning session does not belong on the calendar.
Design near-complete templates for recurring outputs…
For recurring operational outputs (status reports, bug reports, meeting minutes), design templates with nearly complete structure including section headings, formatting, and boilerplate text, requiring only variable content insertion.
Extract templates from your 3 best past examples…
Extract templates from your three best past examples of an output type by identifying common structure across those instances, rather than designing templates from theory.
Define minimum viable output
Define the minimum viable output by identifying the recipient, the action they should take, and the minimum content needed to enable that action—then produce only to that threshold before shipping.
Pre-produce 3-5 buffer outputs before launching any public…
Before launching a public output cadence, pre-produce three to five buffer outputs to absorb inevitable disruptions without breaking the chain.
Complete all preparation before the production session…
Complete all batch preparation (gather materials, load contexts, prepare templates) before the production session begins, so that session time is pure execution without information-gathering pauses.
Sequence batches
Within a batch session, start with the easiest or most familiar output to build momentum, tackle demanding outputs at peak cognitive capacity, and save formulaic outputs for the end when pattern-matching remains strong but creative energy wanes.
Define the distribution plan before starting production…
Before beginning any significant output, define its distribution plan by identifying specific audiences, channels, formats, and timing rather than treating distribution as a post-production task.
Move outputs forward through pipeline stages…
Move outputs sequentially through pipeline stages (Draft → Review → Polish → Deliver) without skipping stages or oscillating backward except through explicit, documented regression decisions.
Check 3-5 yes/no gate criteria at each pipeline stage…
At each pipeline stage transition, check explicit gate criteria (3-5 yes/no questions) before advancing the output, and if any answer is no, keep the output in its current stage until deficiencies are addressed.
One cognitive mode per stage
During draft stage, generate content and follow templates without editing or polishing; during review stage, evaluate structure without wordsmithing; during polish stage, refine language without restructuring—never mix activities from different stages in a single work session.
Work the most downstream pipeline stage first — Deliver…
Before every work session, consult your pipeline board and work on the most downstream stage that contains items (Deliver before Polish, Polish before Review, Review before Draft) to pull from bottlenecks rather than accumulating work-in-progress.
Set WIP limits per pipeline stage (solo
Set work-in-progress limits for each pipeline stage (typical solo creator: Draft—3, Review—2, Polish—2) and do not start new items in a stage until existing items advance, to prevent attention fragmentation and increase throughput.
Scale versioning to stakes
For high-stakes outputs with long lifecycles, implement full versioning with named versions, changelogs, and archived copies; for medium-stakes outputs, use lightweight date-stamped versioning; for low-stakes outputs, skip active versioning entirely to match overhead to value.
Snapshot the current state before each pipeline stage…
Before an output advances from one pipeline stage to the next (draft to review, review to polish), snapshot the current state as a version to create recoverable checkpoints throughout the production process.
Push distribution for known audiences + time-sensitive…
Use push distribution (direct delivery to inbox/channel) for known audiences with time-sensitive needs, and pull distribution (searchable repositories) for unknown future audiences seeking information over time—deploy both for significant outputs, not one or the other.
Four audience-mapping questions before finalizing any output
For every output, answer four audience-mapping questions before finalizing: (1) Who specifically needs this? (2) What do they need from it? (3) Where do they consume information? (4) When do they need it?—then format and time distribution accordingly.
Rewrite for each format — don't copy-paste across mediums…
When translating an output to a new format, rewrite the content in the language, tone, structure, and emphasis that format demands—do not copy verbatim across formats, because each medium requires different cognitive packaging to serve its audience effectively.
Cascade derivative formats over days/weeks after…
Cascade derivative format releases over days or weeks after the pillar ships (rather than publishing all simultaneously) to extend the life of the original research, prevent audience fatigue, and create multiple touchpoints across time.
Track four output dimensions
Build a personal output scorecard tracking four dimensions (reach, resonance, downstream action, personal growth) rather than any single metric, reviewing monthly to identify which output types score highest on the dimension that matters most to your goals.
Define your personal value metric before measuring…
Before measuring anything, define your personal value metric (what 'value' means for your specific outputs) as the lagging indicator that ultimately matters, then select leading indicators that predict it—never measure without first answering 'value for what purpose.'
When viral outputs produce zero action and quiet outputs…
When a heavily-viewed output generates zero downstream action while a quiet output generates high-value outcomes, increase production of the quiet output's type—optimize for measured impact, not vanity metrics, even when impact metrics are smaller and less emotionally satisfying.
Stop causal reasoning at process/structure level…
In post-action reviews of outputs, terminate causal reasoning at the process and structure level, never at the personal adequacy or character level, to extract systematic improvements rather than identity-based judgments.
Four-question output review
During output reviews, answer exactly four questions in sequence: (1) What did I produce and what results did it generate? (2) What patterns exist across successful vs unsuccessful outputs? (3) What assumption should I question? (4) What one specific thing will I change next cycle?
Integrate the committed action from your review…
Close every output review by integrating the committed action from question 4 directly into your next production cycle's plan before ending the session, ensuring review insights become operational changes rather than intellectual observations.
Five metadata fields for every archived output
Store every archived output with exactly five metadata fields: descriptive title containing search keywords, completion date, output type from your controlled vocabulary, project/context, and 2-5 searchable tags, establishing this as the minimum metadata standard before any file enters the archive.
Two-minute archiving ritual after every delivery
Implement a two-minute archiving workflow triggered by 'I shipped an output,' consisting of filing the output in your single archive location with required metadata, treating archiving as the closing ritual of every delivery rather than a deferred task.