Frequently asked questions about thinking, epistemology, and cognitive tools. 200 answers
Choose something you would normally read passively — an article, a book chapter, a podcast transcript. Read or listen to it in segments of roughly 500 words or 3 minutes. After each segment, close the source and write one to three sentences capturing the core idea in your own words. Do not copy.
Create your first five Zettelkasten notes — not as a test drive, but as the beginning of a real system you will continue building. Step 1: Choose one source you have read recently — a book, an article, a podcast, a lecture — that contained ideas you found genuinely valuable. Step 2: Identify three.
Build your first 10 spaced repetition cards using Anki (free, cross-platform) or any spaced repetition tool you prefer. Step 1: Choose a topic you have recently learned and genuinely want to retain — a mental model, a technical concept, a professional framework, a set of principles from this.
Open your primary note-taking or knowledge management system. Select twenty recent items — notes, bookmarks, saved articles, clipped references — captured in the last three months. For each item, assign it to one of four expiration categories: (1) Expires within one week — time-bound to a specific.
Conduct a search-versus-sort experiment on your own system. Step 1: Choose your primary note-taking or document storage tool — whatever system holds the largest volume of your information. Step 2: Identify ten items you have filed in the past six months. Pick a mix: some you file frequently, some.
Choose five notes from your existing collection — articles you saved, book highlights, meeting notes, anything. For each one, apply the first two layers of progressive summarization. Layer 1: Read through and bold the passages that contain the core ideas — aim for no more than 10 to 20 percent of.
Perform a deliberate synthesis session using material you have already processed. Step 1: Open your note system — Zettelkasten, digital notes, highlights, whatever you have — and select five to seven notes from at least three different source domains. Do not pick notes that are obviously related..
Design and document your personal information sharing protocol. Step 1: List the five people or groups you most frequently share information with — your team, your manager, a friend, a community, a partner. For each, write down their typical context when receiving information from you: How much.
Perform an information bankruptcy right now — or, if you are not currently overwhelmed, design your bankruptcy protocol so it is ready when you need it. Step 1: Inventory your backlogs. List every information queue you maintain — email inbox, read-it-later app, note capture inbox, RSS reader,.
Design your daily processing habit using the four-element template. First, choose your anchor: an existing daily behavior that already happens reliably (morning coffee, arriving at your desk, lunch break ending). Second, define the minimal version: the smallest processing action that counts (open.
Run a tool-versus-habit audit on your own information processing practice. Step 1: List every information management tool you have used in the past two years. Include note-taking apps, read-it-later services, task managers, bookmarking tools, and any other system where you stored information with.
Build your Personal Information Pipeline Architecture document — the synthesis artifact for Phase 43. This is not a tool recommendation or an app configuration. It is a meta-document that describes how your entire information system works. (1) Draw or describe your five-stage pipeline: What are.
List every tangible output you produced in the past seven days — documents written, decisions made and communicated, emails that moved projects forward, code shipped, presentations delivered, feedback given. Count them. Now list every hour you spent consuming information, attending meetings, or.
Conduct a personal output audit over the past two weeks. Step 1: Open your calendar, your email sent folder, your messaging app, your document editor, and any project management tools you use. Scan the past fourteen days and list every tangible thing you produced — every document, every message.
Build a quality standards matrix for your five most frequent output types. Step 1: Return to the output type inventory you created in L-0862. Select the five types you produce most frequently — these might be emails, meeting notes, documents, code, presentations, or social posts. Step 2: For each.
Build a pre-delivery output checklist for your most frequent output type. List the five to seven errors you have actually made in past deliverables, convert each into a yes/no checkpoint, order them from most catastrophic to least, and test the checklist on your next three outputs — refining after.
Choose a piece of output you need to produce this week — a memo, an email, a report section, a blog post, anything that requires more than a paragraph. Produce it in two strictly separated passes. Pass one: set a timer for the length of writing you would normally spend, cut it in half, and write.
Identify the three output types you produce most frequently — emails, memos, status reports, code reviews, project plans, whatever recurs at least weekly. For each one, create a template by extracting the common structure from your last three good examples of that output. Write the template as.
Pick one output you are currently procrastinating on or overbuilding. Write down the full version you have been imagining. Now strip it to its core: what is the absolute minimum deliverable that would provide value to its recipient? Define that minimum version in one sentence. Build it today, ship.
Choose one output type you produce regularly (or want to). Define a frequency — daily, twice weekly, or weekly — and commit to that cadence for the next fourteen days. Track every output on a visible calendar. At the end of fourteen days, count your total outputs, note which days you almost broke.
Identify one output you are currently holding back because it feels unfinished. Set a timer for 30 minutes, bring it to the minimum standard from L-0867, and ship it to at least one real recipient today. Record the feedback you receive over the next 48 hours. Compare the feedback to what you.
Identify one output type you produce regularly — lessons, emails, social posts, reports, meeting agendas, code reviews, anything that recurs. This week, instead of producing each instance individually as it comes due, batch three or more instances into a single focused session. Before the session,.
Map your last five completed outputs to a four-stage pipeline: Draft, Review, Polish, Deliver. For each output, estimate how much time you spent in each stage and how many times you regressed from a later stage back to an earlier one (e.g., going from Polish back to Draft). If you find more than.
Pick one important output you produced in the last month. Reconstruct its version history — how many distinct drafts or revisions existed? Can you access earlier versions? If not, establish a versioning protocol for that output type today: name the convention, choose the storage location, and save.