Frequently asked questions about thinking, epistemology, and cognitive tools. 9738 answers
Track which outputs produce the most value to focus your production on high-impact types.
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.
Reviewing outputs without changing anything afterward — treating the review as a reflective ritual that feels productive but produces no behavioral adjustment, turning insight into self-congratulation.
Periodically review your outputs to assess quality trends and identify improvement areas.
Define clearly how collaborative output production works — who does what when.
Define clearly how collaborative output production works — who does what when.
Define clearly how collaborative output production works — who does what when.
Define clearly how collaborative output production works — who does what when.
Define clearly how collaborative output production works — who does what when.
Define clearly how collaborative output production works — who does what when.
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.
Collaborative outputs fail most often from ambiguous ownership — when everyone is vaguely responsible, no one drives the work forward, and the result is a patchwork of conflicting voices that satisfies nobody.
Define clearly how collaborative output production works — who does what when.
Store completed outputs in a findable archive for future reference.
Store completed outputs in a findable archive for future reference.
Store completed outputs in a findable archive for future reference.
Store completed outputs in a findable archive for future reference.
Store completed outputs in a findable archive for future reference.
Store completed outputs in a findable archive for future reference.
Audit your last twenty completed outputs and build the first version of your personal output archive with consistent metadata and a findable structure.
Archiving everything with no metadata — dumping finished work into a folder called "Done" with original file names like "Final_v3_REAL_final.docx" — creating a graveyard instead of an archive.
Store completed outputs in a findable archive for future reference.
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.
Waiting to produce output until you feel ready, which means the compounding clock never starts and you accumulate zero surface area for luck to find you.