Everything below was published by this GitHub account. Launch7 indexes it and links to the source; it has not executed, installed or audited any of it, and it is not affiliated with the account.
Categories
Skills
- thinking-effectuation
The market, technology, or problem is novel enough that outcome probabilities are not trustworthy.
- thinking-first-principles
A constraint is treated as fixed ("too expensive," "impossible," "always done this way") without independent support.
- thinking-five-whys-plus
A fault is already localized to a component, path, or subsystem.
- thinking-jobs-to-be-done
Choosing what to build, cut, or prioritize when user need is unclear - Explaining low adoption of a shipped feature - Mapping competition…
- thinking-kepner-tregoe
Core rule: Diagnose deviations by testing causes against both IS and IS-NOT.
- thinking-lindy-effect
For non-perishable ideas, technologies, and practices, expected remaining life scales with current survival age.
- thinking-map-territory
Observed behavior contradicts a doc, test expectation, diagram, comment, dashboard, or prior assumption.
- thinking-margin-of-safety
Capacity, timeouts, pool sizes, queue depths, storage, or SLA numbers under load uncertainty - Timeline or budget commitments where…
- thinking-model-combination
One model already applied (or clearly primary) still leaves a material blind spot that another mechanism covers.
- thinking-model-router
The right thinking skill is unclear and you would otherwise guess or stack tools.
- thinking-ooda
Incident response, outage, or ongoing degradation where state is still moving.
- thinking-opportunity-cost
Allocating scarce time, headcount, budget, or attention across competing options - Feature prioritization, build-vs-buy, tech-debt vs…
- thinking-pre-mortem
Before kickoff, major technical commitment, high-risk sprint work, launch, or release.
- thinking-probabilistic
Core rule: State beliefs as numbers and ranges, not vibes.
- thinking-red-team
Security review of code, authentication, authorization, APIs, data handling, or infrastructure you control and are permitted to probe.
- thinking-reversibility
Uncertain how much analysis a decision deserves (tech, process, product, org) - Tempted to committee a low-blast-radius choice, or to rush…
- thinking-scientific-method
A bug, incident, or anomaly has more than one plausible cause.
- thinking-second-order
Strategic, policy, incentive, or architecture choices with lasting coupling.
- thinking-socratic
Request is underspecified ("make it fast", "add a dashboard", "fix the bug") and a guess would misbuild.
- thinking-steel-manning
About to reject a proposal, design, or alternative approach.
- thinking-systems
Symptom spans services/components; single-stack fixes fail or bounce.
- thinking-theory-of-constraints
Latency or throughput goal where one stage dominates time or rate.
- thinking-thought-experiment
You need behavior under failure, scale, or policy you cannot cheaply trigger or measure (region outage, 100x load, one-way architecture).
- thinking-triz
Architecture, API, or system parameters pull in opposite directions (stable vs evolving, fresh vs cached, strict vs frictionless).
- thinking-via-negativa
Improve by subtraction before addition.