Principles
2,201 principles · page 38 of 46
Use pre-mortem analysis on schemas by imagining…
Use pre-mortem analysis on schemas by imagining they have already failed and working backward to identify plausible failure paths, which increases ability to detect weaknesses by approximately 30%.
Red-team your own schemas by building the strongest possible
Red-team your own schemas by building the strongest possible evidence-based case against them, which either confirms their resilience or reveals upgrade paths before reality forces the update.
Monitor leading indicators of schema drift rather…
Monitor leading indicators of schema drift rather than waiting for catastrophic prediction failures, using statistical shifts in your input environment and changes in decision confidence patterns.
Subject-object shifts—where what was previously invisible…
Subject-object shifts—where what was previously invisible and controlling becomes something you can observe and manage—constitute the mechanism of developmental stage transitions.
Measure the quality of any personal development practice…
Measure the quality of any personal development practice by whether it changed a schema structure or merely added information to an existing one, as only structural change constitutes genuine growth.
Record the source provenance of each schema during inventory
Record the source provenance of each schema during inventory to identify unexamined inherited schemas, as schemas with no traceable origin are most likely outdated.
Allocate cognitive improvement effort to meta-schemas rather
Allocate cognitive improvement effort to meta-schemas rather than individual schemas to achieve multiplicative returns through compound propagation across all schemas governed by the upgraded meta-schema.
Make your schema-formation process explicit and examinable…
Make your schema-formation process explicit and examinable to convert accidental cognitive development into deliberate development.
Stress-test adopted frameworks against your specific context
Stress-test adopted frameworks against your specific context before trusting them, as theoretical coherence does not guarantee contextual validity.
Check schemas against test data they were not built…
Check schemas against test data they were not built from rather than only the training data they were derived from to distinguish genuine patterns from memorized examples.
Prefer simpler schemas when accuracy and scope…
Prefer simpler schemas when accuracy and scope are equivalent, as unnecessary complexity creates untrackable failure modes and cognitive load.
Define observable conditions that would prove each schema…
Define observable conditions that would prove each schema wrong to distinguish genuine models from unfalsifiable belief systems.
Build a living registry of your schemas with metadata about…
Build a living registry of your schemas with metadata about source, confidence, last-tested date, and status rather than treating beliefs as a static snapshot.
Use the downward arrow technique to surface invisible…
Use the downward arrow technique to surface invisible foundational schemas by repeatedly asking what a surface belief would mean about deeper identity-level assumptions.
Inventory actual operating schemas revealed through behavior
Inventory actual operating schemas revealed through behavior rather than aspirational schemas that reflect desired self-image.
Map dependencies between schemas to understand cascading…
Map dependencies between schemas to understand cascading effects when foundational beliefs change rather than treating each belief as independent.
Identify foundational schemas that support many dependent…
Identify foundational schemas that support many dependent beliefs and subject them to the most frequent verification, as their failure produces the widest cascades.
When a foundational schema fails, trace the cascade…
When a foundational schema fails, trace the cascade to its source and restructure deliberately rather than compensating by shoring up dependent beliefs independently.
Document schema dependency graphs in external form rather…
Document schema dependency graphs in external form rather than relying on intuitive connectedness, as the structure exceeds working memory capacity.
Build explicit conflict-resolution protocols…
Build explicit conflict-resolution protocols for contradictory schemas rather than collapsing conflicts prematurely to reduce discomfort.
Match schema selection to error cost structure
apply thorough multi-perspective analysis when errors are irreversible and expensive, fast heuristics when errors are reversible and cheap.
Weight schema selection by domain-specific track record
prioritize schemas that have produced accurate predictions in structurally similar problems over schemas that feel familiar or recent.
Match schemas to domain structure
apply analytical schemas to domains with clear causal chains, interpretive schemas to domains with reflexive actors, and generative schemas to domains with unconstrained solution spaces.
Select schemas with feedback loop speed matching…
Select schemas with feedback loop speed matching your learning timeline: prioritize short-loop schemas when you need rapid iteration, long-loop schemas when you can wait for delayed outcomes.
Create explicit records of schema-application-outcome…
Create explicit records of schema-application-outcome triples to train your schema selection mechanism through feedback rather than relying on memory-based pattern recognition.
Design learning activities to produce confusion…
Design learning activities to produce confusion and cognitive disequilibrium at the edge of current understanding, since that tension drives schema accommodation and genuine conceptual change.
Implement continuous small schema updates based on new…
Implement continuous small schema updates based on new evidence rather than waiting for crisis-driven wholesale revision, since incremental adjustment compounds into fundamental transformation with lower emotional cost per update.
When learning effort fails repeatedly, question your schema…
When learning effort fails repeatedly, question your schema about how learning works rather than concluding you lack capability, since mismatched learning strategies produce failure independent of ability.
Match change methods to change type
use linear approaches for clear low-resistance changes, stage-based for motivation challenges, systems approaches for feedback-loop contexts, and adaptive approaches when the problem requires self-transformation.
Identify and intervene on stabilizing feedback loops rather…
Identify and intervene on stabilizing feedback loops rather than overwhelming them through brute force, since sustainable change requires restructuring the corrective mechanisms themselves.
Direct change effort toward what you control (judgments…
Direct change effort toward what you control (judgments, intentions, responses) rather than what you cannot (others' behavior, external events), since attempting to change the uncontrollable is both ineffective and the primary source of unnecessary suffering.
Distinguish technical problems (known solutions exist)…
Distinguish technical problems (known solutions exist) from adaptive problems (people must change themselves) and give the adaptive work back to the people involved rather than providing technical solutions to adaptive challenges.
Treat every experience as training data for continuous…
Treat every experience as training data for continuous schema calibration, weighting surprising observations more heavily than confirmations, rather than freezing your models and deploying them indefinitely.
Model other people's reasoning as operating from different…
Model other people's reasoning as operating from different premises shaped by their experiences and schemas rather than dismissing contradictory conclusions as character flaws, since engagement with reasoning structures enables actual persuasion while character attribution blocks it.
Recognize that your expectations about others alter…
Recognize that your expectations about others alter your behavior toward them in ways that change their behavior, creating self-fulfilling prophecies where the confirming evidence reflects your schema's influence rather than their inherent nature.
Design systems based on Theory Y assumptions (people seek…
Design systems based on Theory Y assumptions (people seek meaningful work and responsibility) rather than Theory X (people need coercion) when you want engagement and self-direction, since the organizational structure creates the behavior that appears to validate the theory.
Update self-schemas through generating new behavioral…
Update self-schemas through generating new behavioral evidence rather than through positive affirmation, as schemas revise based on observational data not verbal assertion.
Audit your self-schemas in three layers—surface statements…
Audit your self-schemas in three layers—surface statements, narrative structure, and meta-schemas about change capacity—as each layer constrains the ones above it.
When planning task duration, deliberately switch…
When planning task duration, deliberately switch from inside-view scenario construction to outside-view base-rate consultation to override the planning fallacy embedded in future-oriented schemas.
Structure risk exposure with asymmetric payoffs—bounded…
Structure risk exposure with asymmetric payoffs—bounded downside with unbounded upside—rather than minimizing risk as a scalar quantity, as risk shape matters more than risk magnitude.
Separate decision quality from outcome quality…
Separate decision quality from outcome quality in post-decision analysis, as conflating the two (resulting) causes your risk schema to update on noise rather than signal and converges on superstition rather than calibration.
When encountering a new schema, evaluate it laterally…
When encountering a new schema, evaluate it laterally by investigating the source's track record and independent assessments rather than vertically by analyzing only the schema's internal coherence.
Calibrate trust to the specific conditions of each…
Calibrate trust to the specific conditions of each claim—domain match, evidence transparency, incentive structure, and peer consensus—rather than adopting blanket heuristics of trusting or distrusting expertise.
Navigate vertically through abstraction layers by asking…
Navigate vertically through abstraction layers by asking 'why' to move up (toward theory) and 'how' to move down (toward procedure), using gaps in either direction to diagnose missing cognitive infrastructure.
Build meta-schemas with base cases that terminate recursion…
Build meta-schemas with base cases that terminate recursion through action rather than allowing infinite analytical descent.
Use external observations of behavior rather…
Use external observations of behavior rather than introspection to validate self-models, treating discrepancies between internal narrative and external evidence as diagnostic of metacognitive blind spots.
Conduct metacognitive analysis retrospectively rather…
Conduct metacognitive analysis retrospectively rather than in real-time to avoid resource competition between the cognitive process being examined and the examination itself.
Build environmental structures and external protocols…
Build environmental structures and external protocols to compensate for introspective blind spots rather than attempting to eliminate blind spots through increased introspective effort.