Frequently asked questions about thinking, epistemology, and cognitive tools. 604 answers
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.
Take your most recent completed output and build a distribution map: list every person or group who should see it, the channel that reaches them, and the format each channel requires — then execute the distribution within 24 hours.
Take the most substantial output you produced in the past thirty days. Identify five different formats it could be adapted into — a shorter written piece, a visual summary, a presentation, a social post, a conversation script — and produce at least two of them within sixty minutes, noting where.
Build a personal output scorecard by listing every output you produced in the last 30 days, scoring each on reach, resonance, and downstream action, then ranking output types by total value to identify where your production effort should concentrate.
Schedule your first output review for this week — gather measurement data from your last 10 outputs, answer all four review questions in writing, and commit to one specific production change based on what you find.
Map your next collaborative output using a RACI matrix: identify one Responsible person, one Accountable person, specific Consulted parties, and who gets Informed — then run the collaboration with explicit handoff points and a brief retrospective afterward.
Audit your last twenty completed outputs and build the first version of your personal output archive with consistent metadata and a findable structure.
Catalog every piece of output you have published or shipped in the past twelve months, count the total, identify the one piece that generated the most unexpected consequence, and write a one-paragraph analysis of why that particular piece — and not the one you expected — was the one that compounded.
Build your Personal Output System Architecture document — the synthesis artifact for Phase 44. This is your production engine made explicit. (1) Draw or describe your complete output system using the five subsystems from this capstone: Value Definition (what you produce and why), Production.
Identify one significant project, decision, or experience from the past month that you completed but never deliberately reflected on. Set a timer for twenty minutes and write answers to these five questions: (1) What was I trying to accomplish, and did I accomplish it? (2) What assumptions did I.
Tonight, before you go to bed, spend exactly five minutes with a blank page — paper or digital. Write the date, then answer three questions: What happened today that I want to remember? What did I learn that I did not know yesterday? What would I do differently if I could replay one moment? Do not.
Block 45 minutes this weekend for your first weekly review. Gather all daily review notes, calendar entries, and task completions from the past seven days. Answer three questions in writing: (1) What patterns appear across multiple days? (2) What did I commit to that I did not do, and why? (3).