Frequently asked questions about thinking, epistemology, and cognitive tools. 1214 answers
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.
The most common failure is applying a single quality standard to all output types — treating every deliverable as if it requires the same level of polish, rigor, and review. This produces two simultaneous problems: critical outputs are under-polished because you ran out of energy over-polishing.
Define what good enough looks like for each output type.
A pre-delivery checklist catches errors before outputs reach their audience.
A pre-delivery checklist catches errors before outputs reach their audience.
A pre-delivery checklist catches errors before outputs reach their audience.
A pre-delivery checklist catches errors before outputs reach their audience.
A pre-delivery checklist catches errors before outputs reach their audience.
A pre-delivery checklist catches errors before outputs reach their audience.
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.
The most common failure is building a checklist so long it becomes its own project. A forty-item checklist is not a quality gate — it is a bureaucratic obstacle that you will skip the moment you are under time pressure. Effective checklists are short enough to use every single time, which means.
A pre-delivery checklist catches errors before outputs reach their audience.
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.
The most common failure is a stealth merger — you tell yourself you are doing a creation pass, but you cannot resist rereading the last paragraph and tweaking a sentence before moving forward. Each tweak pulls you out of generative mode and into evaluative mode, and the switching cost accumulates.
Separate creation from editing — trying to do both simultaneously slows both.
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.
The most common failure is over-engineering templates — building elaborate multi-page structures with detailed instructions for every section, creating a template so rigid that filling it out feels like compliance paperwork rather than accelerated creation. The second failure is hoarding templates.
Templates for common output types let you start producing immediately.
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.
Treating MVO as permission to ship sloppy, thoughtless work. The minimum viable output is not the minimum possible effort — it is the minimum complete version that delivers real value. Stripping an output below the viability threshold produces something that wastes the recipient's time and damages.
Deliver the simplest version that provides value then iterate if needed.
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.
Interpreting this lesson as permission to ship garbage at high velocity. Frequency without a minimum quality threshold produces noise, erodes trust, and trains your audience to ignore you. The point is not maximum frequency — it is consistent frequency above the MVO threshold established in L-0867.
Consistent output at regular intervals builds trust and momentum.