Browse the library — page 3

An alphabetical directory of published knowledge, collections and longreads. Every page works without JavaScript.

1154 entries · Page 3 of 12

• Cue the part that matters right nowheuristic
• Cycle through OODA when the environment keeps movingprotocol
• Debrief the work, not the personprotocol
• Debug a new role across people, role, and taskcollection
• Debug a new role across people, role, and taskprotocol
• Debug an intermittent failurelongread
• Decide when you're overloadedlongread
• Decide whether the error was a slip or a mistaken planquestion
• Decompose around likely change, not the org chartprinciple
• Decompose the judgment before scoring the wholeprotocol
• Decompose the role into tasks before naming your skillsprotocol
• Deduplicate before spending attention on screeningchecklist
• Define a minimum viable preparation session for disrupted daysprotocol
• Define escalation triggers before autonomy startschecklist
• Define the B2-to-C1 gap from a real sampleprotocol
• Define the behavior before opening the feedback conversationprotocol
• Define the career shock trigger and the first three movesprotocol
• Define the cheaper mode that preserves the core functionprotocol
• Define the estimate object before estimating ittemplate
• Define the forecast event before assigning a probabilitychecklist
• Define the system boundary before optimizingprotocol
• Define update indicators before the situation movestemplate
• Define what meeting success would look likeprotocol
• Delay confidence until after a retrieval attemptprotocol
• Delegate an outcome with boundariesprotocol
• Delegate context, not only instructionsprinciple
• Deliver the small service before automating its machineryprotocol
• Demand far-transfer evidence from brain-training claimschecklist
• Design a fallback at the interfaceprotocol
• Design practice that survives the study sessioncollection
• Design recovery for the error you cannot preventprinciple
• Design routine work so ordinary human slips do less damagecollection
• Design signposts that tell you when the world changedprotocol
• Design the task around cognitive limits instead of fighting themcollection
• Detect configuration drift instead of assuming samenessprotocol
• Detect safety drift before the exception becomes normalcollection
• Detect stagnation separately from completionprotocol
• Diagnose the speaking dimension before fixing the whole performanceconcept
• Discuss the reasons, then re-rate privatelyprotocol
• Distinguish a blocked goal from an obsolete goalquestion
• Distinguish an unfinished task from an unfinished decisionquestion
• Distinguish habitually starting a behavior from expertly performing itquestion
• Distinguish stated position from operating constraintquestion
• Distinguish variation in cases from uncertainty in a meanconcept
• Do not add an alert without an expected responseprotocol
• Do not ask ASR to train every part of speechprinciple
• Do not assume a rubric reduced noise—measure itprinciple
• Do not call a calendar appointment an if-then plan when the action still needs preparationprinciple
• Do not claim a meeting nudge worked from awareness aloneprinciple
• Do not confuse authentic provenance with factual truthprinciple
• Do not confuse choosing a commitment with benefiting from ittemplate
• Do not count a digital-detox plan as behavior changechecklist
• Do not discipline away a system defectprinciple
• Do not expose AI confidence until you have tested its calibrationprotocol
• Do not hide the corrective point inside a praise sandwichprinciple
• Do not infer AI confidence from fluent deliveryprinciple
• Do not make zero filled pauses the speaking goalheuristic
• Do not mistake frequent readings for independent evidencequestion
• Do not move a burning pan or add waterprotocol
• Do not read an odds ratio as a risk ratioconcept
• Do not standardize an AI ritual before testing itprinciple
• Do not track personal data without a question or actionconcept
• Do not transfer ownership until the receiver accepts itprinciple
• Do not treat an insect screen as a fall barrierchecklist
• Draw a connection circle when causes chase each otherprotocol
• Draw decisions, uncertainties and value on one pageprotocol
• Draw the coding agent's execution surface before granting autonomychecklist
• Draw the process while you explain itprotocol
• Dry-run the real-shaped input without the real writeprotocol
• End a focus cycle with a transfer test and a new allocation decisionprotocol
• End an evidence conversation with unknowns, not false closureprotocol
• End debriefs with one changed behaviorprotocol
• End strategy reviews with continue, adapt, or stopprotocol
• Enforce permissions outside the modelprinciple
• Escalate asynchronously with impact, clock and failed pathprotocol
• Escalate concern with a shared signal phrasepattern
• Escalate persistent test anxiety instead of adding more study hoursconcept
• Escalate process risk without attacking motivesprotocol
• Escalate the process when informal repair keeps failingconcept
• Estimate a project timelinelongread
• Estimate active effort and elapsed time separatelyprinciple
• Estimate approvals and integration as deliverablesprinciple
• Estimate before the number arrivesheuristic
• Estimate the delivery system, not only the hands-on workcollection
• Evaluate the same agent task across multiple trialsprotocol
• Evaluate what memory retrieves, not just what it storesprotocol
• Exchange broad credentials for task-scoped accessprotocol
• Explain forecast error by componentprotocol
• Explain the connection, not the sentenceprotocol
• Explain the rule before you reuse the examplecollection
• Explain the rule before you reuse the exampleprotocol
• Explain why the wrong worked example failsprotocol
• Explore a better deal without silently withdrawing the agreed oneprotocol
• Explore careers with a decision questionprotocol
• Expose the default before you accept a consequential choicechecklist
• Externalize volatile task state before it becomes memory workprotocol
• Facilitate multisource feedback before demanding an action planprotocol
• Fade help when performance earns itprotocol
• Fade support when unaided performance becomes reliableprotocol
• Fail work that cannot meet its useful deadlineprinciple

Inspect the public connection graph. Connections explain how pages and sources relate; they are not quality scores.