a builder's codex
codex · patterns · Diagnose before executing — refuse the playbook ask

Diagnose before executing — refuse the playbook ask

Convergence

Four operators converge on the same anti-pattern fix: when an executive asks for a deliverable ("write me a launch plan," "make the funnel convert"), the high-leverage move is to refuse the playbook ask and run a diagnosis first. Understand-work, DATE, divergent PR-FAQs, going-to-bedrock — same shape, four vocabularies.

Operators

Variation

Implication

For any cross-functional deliverable ask, return with a diagnosis artifact before the deliverable. Standard pattern: "here's what I think the actual problem is, here's the evidence, here are 3 divergent paths." Refuse to produce the single-path artifact until the diagnosis is shared.

Sources

Open the interactive view →