TOPICS & READING PATHS
Start with the task in front of you.
Each path connects a practical procedure to the evidence behind it. Read in order or go straight to the handoff you need to fix.
Research & notes
Keep the source attached
A useful answer needs a question, a source and a way for the next reader to check both. Start with evidence gathering; move to extraction and a portable citation library.
3 guides · 12 archive recordsWriting & documents
From draft to a document someone can use
A polished sentence can still change the facts. Build a reusable brief, inspect the revision, then make the finished file navigable for its reader.
3 guides · 16 archive recordsMeetings & email
Close the loop on shared work
The job is not finished when the recap is generated. Reconcile commitments, protect the send boundary and turn the working record into an update somebody can act on.
3 guides · 16 archive recordsAutomation & agents
Make the failure path part of the workflow
An automation needs more than a happy-path demonstration. Give each event an identity, contain retries, make approval meaningful and test changes before widening the scope.
4 guides · 12 archive recordsCoding & data
Check the result, not just the explanation
Fluent output is not a reconciliation. Trace totals to rows, inspect the query that produced the answer and keep generated code changes small enough to review.
3 guides · 16 archive recordsSetup & friction
Count the work around the tool
Permission checks, maintenance and exit costs belong in the decision. Use a narrow access test, cost the recurring work and rehearse a replacement before depending on a vendor.
3 guides · 12 archive recordsEvidence
Make a modest claim you can defend
A vendor announcement, a workplace survey and a task experiment answer different questions. Use the studies for context, then evaluate one bounded workflow with a visible quality bar.
1 guides · 16 archive records