Definitionv1
Error pattern: a recurring sequence of similar mistakes that
Error pattern: a recurring sequence of similar mistakes that emerges when multiple instances of the same type of error are analyzed together, revealing structural weaknesses in systems rather than individual character flaws
Why This Is a Definition
This definition establishes the precise semantic boundary of 'error pattern' by identifying its key characteristics: recurrence, similarity across instances, analytical process of grouping, and diagnostic function pointing to system weaknesses rather than personal failures. It distinguishes error patterns from individual errors and explains their diagnostic value.
Source Lessons
Connections
Defines (46)
AxiomAutomatic Fusion of Observation and InterpretationAxiomPerceptual Plasticity Through TrainingAxiomSystematic Overconfidence TaxonomyAxiomEmotion as Systematic Cognitive ModulatorAxiomMeaning as Receiver ConstructionAxiomCultural Transmission Through Shared IntentionalityAxiomBrain as Hierarchical Prediction MachineAxiomLooping Effects of Human ClassificationAxiomAutomatic Pattern PerceptionAxiomPeople interpret failure as either evidence about theirAxiomCatastrophic failures in complex systems rarely result fromAxiomProcess variation consists of two fundamentally differentAxiomWhen estimating future task duration, people naturally adoptAxiomReference class forecasting (using base rates from similarAxiomHumans exhibit automation complacency — reducing monitoringAxiomDefault options determine behavior more reliably thanPrincipleApply the same tags to notes from different domains whenPrincipleProcess inbox items in two distinct passes—first clarifyingPrincipleInstrument systems with the minimum number of metrics thatPrincipleWhen designing cognitive agents, examine the full patternPrincipleBuild cognitive agents with multiple independent triggerPrincipleIdentify and eliminate shared dependencies across multiplePrincipleBlock your measured peak attention hours on your calendar asPrincipleUse the 'five whys' technique on any significant energyPrincipleBuild energy systems through sequential single-componentPrincipleWhen initial hypotheses form during debugging or incidentPrincipleDesign social chain links to specify your own behaviorPrincipleConduct functional analysis before attempting extinction byPrincipleDistinguish between hypothesis failure (wrong theory),PrincipleMaintain a separate backlog for experimental ideas distinctPrincipleIdentify and reduce context dependencies in important habitsPrincipleAct on courageous decisions while fear's activation energyPrincipleWhen holding more power in a relationship (formal authority,PrincipleTest causal hypotheses about personal patterns throughPrinciplePeriodically surface process schemas by extracting embeddedPrincipleDefine explicit escalation criteria specifying whenPrincipleLeverage tacit team knowledge about individual strengths,PrincipleUse satisficing decision rules (define 'good enough'PrincipleAggregate predictions by confidence level and compare statedPrincipleBefore applying expertise developed in one domain to aPrincipleDesign physical and digital workspaces to afford only thePrincipleDocument not only what tools you use but the completePrincipleNavigate vertically through abstraction layers by askingPrincipleApplying a single decision process across structurallyPrincipleTreat major changes in goals, team composition, or systemPrincipleImplement each identified root cause as an encoded