Use whenever you record a claim — attach its verbatim source (the quote, who, when, what kind) so a finding can always be traced back.
Use before you write a line of demand copy or plan a launch — when the value seems "nice to have," when adoption is flat despite good messaging, or when nobody can answer "why…
Use when there's more worth building than time to build it, or two good options compete — make the tradeoff explicit, pick one, and say what you're NOT doing and why.
Use at the ship gate for any release — enforce one sanctioned scripted door to prod, a rollback you have actually tested, no leaked secrets, no regressed control, and the…
Use to maintain the living body of knowledge — one findable source of truth, deduplicated, tagged to a stable schema, with each belief carrying its evidence, confidence, and any…
Use when the system must change safely over time, when an invariant needs protecting, for "should we rewrite this?", or for a behavior-preserving refactor — protect the…
Use when writing a spec for a feature or a one-way-door decision — a Working-Backwards PRD whose whole top half is WHY before any WHAT.
Use when laying out any screen or composing a set of elements — make the eye go where it should. Establish visual hierarchy (one focal point, deliberate scan path), group with…
Use when handed a real deck, one-pager, or pitch to assess end to end — the orchestration that turns the seven reads into the ordered deliverable.
Use when proposing the approach for an initiative, or when tempted to add structure "for future scale" — design the idiomatic, simplest thing that solves the real problem and…
Use when structuring content, navigation, or labels — when users can't find things, the nav is growing organically, a new section needs a home, or you're naming/grouping concepts.
Use when a call is hard-to-change or a one-way door (persistence, boundaries, public interfaces, the build/deploy path, a dependency) — record an ADR; immutable once accepted,…
Use when rolling out any risky change to many users/hosts — stage it (canary → progressive → full) behind health gates and flags so a bad change is caught at 1% and auto-aborted,…
Use to keep research a habit, not a phase — small weekly touchpoints with real users, structured as an opportunity-solution tree, with every belief paired to the cheapest test…
Use when a security incident is suspected or active (breach, leaked secret, active exploit, suspicious activity) — run the NIST lifecycle: contain, eradicate the root cause,…
Use before committing to build anything non-trivial — name the one assumption that, if wrong, kills the idea, and design the cheapest test that could falsify it, run BEFORE the…
Use before recording any new person/entity/insight/belief — search what already exists and converge new signal onto it; coin a new node only when nothing fits.
Use when you'd otherwise pitch features or send a comparison sheet — lead with a true, non-obvious insight that reframes the buyer's own problem and points to your strength…
Use before a launch/traffic spike (marketing push, Black Friday, a new large customer) or when asked "can we handle the load / will this scale" — model the expected and worst-case…
Use for any consequential design or technology choice — surface ≥2 viable options, score them against the ranked drivers, name the sensitivity and trade-off points, and recommend…
Use whenever designing any surface or component — design the full set of states, not just the happy path.
Use to close the audit — render an honest ship / don't-ship verdict with the blocker list, what you tested and didn't, the residual risk, and the routing of every finding to the…
Use when defining what "success" means for a feature/initiative, when picking a metric, or when a number looks suspiciously good — choose a North Star + guardrails, reject vanity,…
Use whenever a change is heading to production or you're asked "is this ready to ship / is it live / is it healthy" — adopt the you-build-it-you-run-it posture and verify by…
Use when writing code that touches I/O, state, concurrency, or external systems — design for failure: validate inputs, fail fast, be idempotent and concurrency-safe, and make it…
Use when reliability/recoverability is being assumed rather than proven — deliberately inject the failure (dependency down, AZ/region loss, restore from backup, failover, on-call…
Use when advancing a deal toward commitment — build a Mutual Action Plan working backward from go-live (including legal/procurement), drive each step, and ASK for the commitment…
Use before you test anything — build your own model of "correct" from the brief, spec, and user journeys so you have a basis to call something a bug, and state which expectation…
Use when the message is aimed at "everyone," when one product serves multiple distinct buyers, or when you need to pick the beachhead segment to lead with.
Use when someone demands "100% uptime," when arbitrating ship-speed vs stability, or when defining how reliable a service must be — set an SLI/SLO and an error budget so…
Use when assessing founder conviction and "why you / why this" — separate a genuine haunting from FOMO.
Use when recording or ranking any finding — read each source for what it IS and weight it by strength of evidence (behavioral > attitudinal, observed > reported, first-party >…
Use when the pipeline is thin or you need to open NEW conversations — proactively build a target list, sequence multi-touch outreach (call/email/social), open a cold conversation,…
Use when more than one entry surface exists or is proposed (CLI, API, MCP, UI, webhook, cron) — make every surface route to one shared core code path, and run a DRY pass for the…
Use when performance matters, something is slow, or a job is failing/timing out — measure before optimizing, profile to find the real bottleneck, parallelize independent work and…
Use when summarizing whether the bet clears the bar — explicitly tally how many unique insights it carries across tech, market, and GTM. One isn't enough; name which ones and why.
Use before drawing any screen — when asked to "design a page/feature/screen," map the user's task end to end (entry, happy path, branches, every empty/loading/error/edge state,…
Use pre-build, for a new idea, or at n=1 — is there a real market and will anyone pay? Run Mom-Test conversations on real prospects, hunt commitment + advancement, say "no one…
Use when recommending controls or evaluating whether a system is secure by construction — apply the classic security principles (least privilege, fail-safe defaults, complete…
Use when scoping what to test on a non-trivial build — model coverage across the product's real dimensions (Structure, Function, Data, Integrations, Platform, Operations, Time) so…
Use when copy across surfaces is inconsistent or ad-hoc, when you need a reusable messaging framework the whole team can derive from (homepage, deck, ads, onboarding all ladder to…
Use when ops work is manual, repetitive, and scaling with growth (manual deploys, hand-run migrations, copy-paste fixes, ticket-driven provisioning) — identify the toil and…
Use on a discovery or first real sales call — diagnose the buyer's problem with SPIN + Gap Selling (current → future → quantify the gap) before pitching anything; problem → impact…
Use when a vulnerability is reported from OUTSIDE the team (a security researcher, a user, a bug bounty, an embargoed upstream CVE) — triage it without shooting the messenger,…
Use when the feature is AI/LLM-powered (generation, summarization, classification, agents, RAG) — its acceptance is an EVAL, not "it runs." Define the dataset, graders,…
Use to scan everything an outsider can read — README, marketing copy, docs, public config, AND error messages, stack traces, debug pages, response headers, and logs — for leaked…
Use for build-vs-buy, adopting a new framework/database/language, or "should we use X" — apply the innovation-token test; default to the well-understood; a stack only the AI…
Use when designing the ergonomics of a terminal / CLI / builder tool — command and flag design, sensible defaults, inferring arguments instead of demanding flags,…
Use whenever you write or review external copy in someone's voice (the founder/brand), and as a gate on every claim.
Use whenever a rewrite, redesign, or refactor would remove, replace, or overwrite copy or visuals that are already in place — a tuned headline, a converting landing page, a hero,…
Use before or while designing when you need to understand users — their goals, context, mental models, and real behavior.
Use when defining modules, services, interfaces, or data ownership — or when "let's go microservices" comes up — design for cohesion/coupling and Conway's Law; refuse the…
Use for any change before calling it done — prove it with the right tests (unit base + an integration test that hits the real surface and asserts persisted state), then do an…
Use when assessing demand — trust what customers DID over what they say. Triangulate demand from the displaced status quo and the losses, never the TAM slide.
Use when gathering directly from people — talk about their life and specific past behavior, not your idea; get past Q&A into story; embrace silence.
Use when reviewing a change, feature, or design for security — walk Shostack's four questions and STRIDE across every trust boundary of THIS stack, not a generic checklist.
Use when there's a technical or scientific claim under the pitch — push on the mechanism in proportion to how load-bearing it is.
Use when starting an initiative or when the request names a vague quality ("make it scalable / fast / secure / robust") with no bar — derive and RANK the architecture…
Use when documenting how to deploy, operate, or recover a service, or after learning something a release/incident taught you — write a runbook so good a competent stranger could…
Use when a new dependency is added, a CVE is reported, or the build/CI pipeline is reviewed — assess reachability not just presence, pin and lock deps, and treat the…