tjboudreaux

28 skills

thinking-bounded-rationalitytjboudreauxUse when search or investigation could run forever. Set an explicit good-enough threshold first, then stop at the first option that clears it.thinking-circle-of-competencetjboudreauxUse when a specific claim may lack grounding. Check evidence boundary, size wrongness cost, then answer, fetch, or abstain — never confabulate.thinking-cynefintjboudreauxWhen the right response mode is unclear, classify the cause-effect domain first; decompose disorder.thinking-effectuationtjboudreauxUnder genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves.thinking-first-principlestjboudreauxWhen a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.thinking-five-whys-plustjboudreauxWhen a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.thinking-jobs-to-be-donetjboudreauxDeciding what to build or why adoption fails. Recover the progress users hire a solution for under a circumstance, then rank by outcome and competing workarounds.thinking-kepner-tregoetjboudreauxUse when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.thinking-lindy-effecttjboudreauxUse when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.thinking-map-territorytjboudreauxWhen a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.thinking-margin-of-safetytjboudreauxWhen provisioning, setting a limit, or committing an estimate under uncertainty, size a buffer to residual error and the cost of breach—not to the optimistic edge.thinking-model-combinationtjboudreauxWhen one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.thinking-model-routertjboudreauxWhen unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary).thinking-oodatjboudreauxUse under time pressure when the situation is still changing and you must act before certainty — cycle Observe→Orient→Decide→Act on ~70% confidence, then re-observe.thinking-opportunity-costtjboudreauxBefore committing scarce time, people, or money, name the best forgone use of those resources and the value delta of the chosen path versus that alternative.thinking-pre-mortemtjboudreauxBefore committing to a plan or launch, assume it already failed and reason backward through concrete causes — convert failure paths into mitigations, gates, and stop checks.thinking-probabilistictjboudreauxUse when forecasting, estimating, or sizing risk — anchor on base rates, give ranges, update prior→likelihood→posterior on evidence, and factor unmeasured quantities into order-of-magnitude bounds.thinking-red-teamtjboudreauxFor authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible exploit path and verified mitigation.thinking-reversibilitytjboudreauxBefore heavy deliberation, classify the decision as cheap or costly to undo; decide two-way doors fast and stage one-way doors to preserve options.thinking-scientific-methodtjboudreauxWhen a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.thinking-second-ordertjboudreauxWhen a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.thinking-socratictjboudreauxWhen a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.thinking-steel-manningtjboudreauxBefore rejecting a proposal or reflexively agreeing, build the strongest faithful opposing case, state agreement conditions, then update or reaffirm.thinking-systemstjboudreauxWhen behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.thinking-theory-of-constraintstjboudreauxWhen throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.thinking-thought-experimenttjboudreauxWhen a real test is too rare, large, or irreversible, run a controlled counterfactual: isolate one variable, fix conditions, trace the mechanistic chain, and bound what the result implies.thinking-triztjboudreauxWhen two design requirements seem mutually exclusive, name the contradiction, separate conflicting states, then invent a concrete no-compromise resolution.thinking-via-negativatjboudreauxUse when the reflex is to add a feature, layer, or process. Prefer removing harmful or nonessential elements first, with an irreversibility guard before deletion.