Browse the library — page 4

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

1154 entries · Page 4 of 12

• Fan possible causes out before narrowing themprotocol
• Find the assumption value where the choice flipsheuristic
• Find the bottleneck from waiting, not busynessquestion
• Find the breaking point before production finds it for youprotocol
• Find the failure without creating a second incidentcollection
• Find the fault without making the incident harder to understandcollection
• Find the first boundary where the record becomes wrongtemplate
• Find the missing stakeholder before late reviewchecklist
• Find the user problem before building more machinerycollection
• Fix thermal discomfort before searching for a cognitive hackprotocol
• Flatten nested interruptions when you canheuristic
• Flip the frame, keep the factsheuristic
• Follow an accepted job to its actual completion statechecklist
• Follow labels with observable detailprotocol
• Follow the cause chain until you reach a changeable contradictionprotocol
• Follow the why-chain until the cause becomes changeableprotocol
• Follow up on whether the problem changed, not whether the meeting happenedprotocol
• Force combinations across dimensions to surface new optionsprotocol
• Framing effectconcept
• Functional fixednessconcept
• Generate human options before asking AI for ideasprotocol
• Generate in writing before the group starts talkingprotocol
• Generate more distinct options before choosing onecollection
• Generate once before opening the visual examplesprotocol
• Get a changing skin mark assessed instead of repeatedly asking an appprotocol
• Get the perspective before you trust the guesscollection
• Get their perspective before trusting your imagined versionprotocol
• Give a KPI a decisiontemplate
• Give a long AI task a durable feature ledgerprotocol
• Give a promising new connection a second interactionprotocol
• Give a retryable mutation one stable operation IDpattern
• Give agent memory a write-manage-read policyprotocol
• Give AI the right context, memory and reusable skillscollection
• Give batchable communication check windowsprotocol
• Give changing knowledge an explicit stateprotocol
• Give computer-use tasks a start state and success checkprotocol
• Give decision rights, not just tasksprinciple
• Give each language its own evidence trailprotocol
• Give each requirement one behavior to proveheuristic
• Give each speaker information the other needsprotocol
• Give every postmortem action a verifiable finishchecklist
• Give feedback at the smallest actionable unitprotocol
• Give freed capacity a named destinationprotocol
• Give important external memory a fallback pathchecklist
• Give omitted, null and blank different test caseschecklist
• Give one person the incident commandprotocol
• Give parallel agents independent tests and merge boundariesprotocol
• Give postponed intentions a trigger before they fadeprotocol
• Give production changes one operational laneprinciple
• Give queued work an expiry conditionprotocol
• Give secondary skills a maintenance floorheuristic
• Give selected memory items a spoken traceheuristic
• Give shared capacity a noisy-neighbor ruleprotocol
• Give structure early when the method is still invisibletemplate
• Give technical terms one local definitionprinciple
• Give the agent only the tools this job needschecklist
• Give the canary a fair comparison and a real stopping rulechecklist
• Give the colour a second way to speakchecklist
• Give the favored judgment a real devil's advocateprotocol
• Give the lesson a verifiable finishtemplate
• Give the phone a power path that does not depend on the wall outletchecklist
• Give the second check evidence the first answer did not createprotocol
• Give the user a goal and keep your instructions out of the resultprotocol
• Give verification an independent evidence pathprinciple
• Give workflow changes their own approval gateprotocol
• Grade the final state and the agent trajectory separatelyprotocol
• Graph the behavior before explaining the causeprotocol
• Hand off the contingency with the taskprotocol
• Hand off the uncertainty, not just the statuschecklist
• Handle a work conflict as a problem to resolve, not a verdict to wincollection
• Hear the contrast across different voicesprotocol
• Help work finish instead of merely keeping it busycollection
• Hide condition labels from the person judging the outcomeprotocol
• Hide first scores until everyone has oneprinciple
• Hide volatile decisions behind stable interfacesprotocol
• Huddle when reality invalidates the planprotocol
• Identify uncertainties that can reverse the strategyquestion
• Import identifiers as text before a spreadsheet can reinterpret themprotocol
• Improve one controllable part of the jobcollection
• Improve one controllable part of the jobprotocol
• Improve the alternative before bargaining harderheuristic
• Improve the job by redesigning one resource at a timecollection
• Improve the search before you increase the quotacollection
• Improve the search before you increase the quotaprotocol
• Include the people whose access needs your tests missprotocol
• Increase challenge and resources togetherprinciple
• Increase scrutiny when AI feels effortlessly rightheuristic
• Increase task value before increasing pressureprotocol
• Incubate after a real attempt, not instead of oneprotocol
• Interleave confusable cases, not unrelated workstreamsprinciple
• Interleave only where choosing mattersheuristic
• Interleave when the learner must discriminate, not by defaultheuristic
• Interrupt for reflection only when the drift is worth the interruptionprotocol
• Inventory resources already present before adding a new onechecklist
• Invite bad news before status polishprotocol
• Invite one deliberately different discipline into ideationheuristic
• Is a Medium article enough?longread
• Is It Worth Upgrading Your Device?longread
• Isolate concurrency for the slow dependencyprotocol
• Iterate citation chaining only when it keeps adding valueprotocol

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