Browse the library — page 6
An alphabetical directory of published knowledge, collections and longreads. Every page works without JavaScript.
1154 entries · Page 6 of 12
- Make AI work improve from failures instead of accumulating ritualscollection
- Make AI-assisted work earn your trustcollection
- Make assumptions visible before asking for commitmentchecklist
- Make avoided information actionablecollection
- Make causal diagrams traceable to evidencechecklist
- Make coding agents work in inspectable incrementscollection
- Make dependencies directional where possibleprinciple
- Make difficulty earn its keepheuristic
- Make disagreement between you and AI a review triggerprotocol
- Make disagreement sound open to correction without hiding your pointprotocol
- Make enlarged text fit the task, not just the screenprotocol
- Make every mock assessment rewrite the planprotocol
- Make every selected record end in an explicit status buckettemplate
- Make expertise visible so leadership can movechecklist
- Make feedback earn a second attemptprotocol
- Make feedback end in another attemptprinciple
- Make follow-through easier without a discipline contestcollection
- Make household administration survive the day something stops workingcollection
- Make interruption policy stricter as cognitive load risesprinciple
- Make meetings answer a goal instead of merely occupying a slotcollection
- Make non-essential interaction motion optionalprotocol
- Make one human own the agent-generated changeprotocol
- Make peer review a criteria-based learning taskprotocol
- Make practice harder only when the difficulty teaches the right thingcollection
- Make practice reveal learning, not just activitycollection
- Make queue overtaking an explicit exceptionchecklist
- Make the agent loop finish, recover and stay inspectablecollection
- Make the early checkpoint return useful feedbackprotocol
- Make the environment carry more of the focus loadcollection
- Make the error show the next repairprotocol
- Make the first judgment before the group talksprotocol
- Make the first version simple enough to repeat before making it impressiveprotocol
- Make the gesture carry the relationshipheuristic
- Make the numbers answer the right questioncollection
- Make the receiver reconstruct the messageprotocol
- Make the receiver synthesize the handoffprotocol
- Make the reminder arrive while action is still possibleprotocol
- Make the reminder name both when and whatprotocol
- Make the repeatable behavior pleasant enough to keep choosingprotocol
- Make the rollout stop itself on a known bad signalprotocol
- Make the safe routine action the defaultheuristic
- Make the subject line carry state and asktemplate
- Make the task usable across different ways of accessing itcollection
- Make the write conditional on the version you reviewedprotocol
- Make unavoidable device use bounded, then visibly returnprotocol
- Make vocabulary retrievable, durable and usablecollection
- Make your skills portable before you need to movecollection
- Map relationships when isolated facts are not enoughprotocol
- Map relationships when the structure is the lessoncollection
- Map the balancing loop behind a limitprotocol
- Map the decision, not just the stakeholdersprotocol
- Map the reinforcing loop behind growthprotocol
- Map the task to the current AI frontierheuristic
- Map which component performs which function on whatprotocol
- Mark the example features you must not inheritprotocol
- Match autonomy to capability and riskheuristic
- Match detail depth to the receiver's decisionprinciple
- Match learning support to what the learner already knowsprotocol
- Match practice to the response the assessment demandsprinciple
- Match the identifier together with its issuing namespacetemplate
- Match the liquid medicine, its instructions and its measuring devicechecklist
- Match the reset to depletion, not a magic timerprinciple
- Measure adoption, not just whether AI was consultedprinciple
- Measure agreement on the criteria, not only the verdictprotocol
- Measure AI speed and quality as separate outcomeschecklist
- Measure appropriate reliance as two errors, not one trust scoreprotocol
- Measure arrival rate, work in progress, and cycle time togetherchecklist
- Measure attention and well-being, not only screen-time minutestemplate
- Measure dominance by protected quality attempts, not hoursprinciple
- Measure habit strength by reduced deliberation, not just streak lengthquestion
- Measure the active tool set, not the catalog sizeprinciple
- Measure workload before blaming attentionprotocol
- Merge duplicates when you encounter them, not in a heroic cleanup monthprotocol
- Mine postmortems for repeated failure patternsprotocol
- Mine traces for failure categories before changing promptsprotocol
- Minimize the number of teams that must change togetherheuristic
- Mitigate first when the incident is still hurtingprinciple
- Mix practice when the real task is choosing the methodcollection
- Mix practice when the real task is choosing the methodprotocol
- Mix problems so the method is no longer announcedprotocol
- Model the decision before buying more certaintycollection
- Monitor the agent after deploymentprotocol
- Monitor the whole agent trajectory, not only individual allowed actionsprotocol
- Move a looping disagreement from text to speechcollection
- Move a looping disagreement out of chatprotocol
- Move feedback close enough to the event to keep the evidenceprotocol
- Move from a B2 plateau toward C1 performancecollection
- Move from the concrete case to the ruleprotocol
- Move from the event down the systems icebergprotocol
- Move intentional internet use to a less portable device during the trialprotocol
- Move poison work out of the main queueprotocol
- Move quality checks upstream of the bottleneckheuristic
- Move the problem boundary outward when the local frame is stuckheuristic
- Multiply successive percentage changesprotocol
- Name files for identity and state, not for your desktop historyprotocol
- Name one dominant development edgeprotocol
- Name the decision rule when debate loopsprotocol
- Name the exchange before making a conditional concessionpattern
- Name the noise before choosing the fixconcept
- Name the smallest change worth acting ontemplate
Inspect the public connection graph. Connections explain how pages and sources relate; they are not quality scores.