Ask for no, don't ask for yes (2022)

Original Article ↗ Hacker News Discussion ↗

Core Idea & Variants

  • Thread centers on reframing approvals from “please say yes” to “I plan to do X unless you object by time Y.”
  • Related concepts mentioned:
    • “Ask forgiveness, not permission.”
    • “Radiate intent” / UNODIR / “silent procedure” (announce actions, invite objections).
    • “Tell, don’t ask” / “creating sane defaults” rather than forcing decisions.
    • Sales/negotiation patterns (offering constrained choices, “no‑oriented” questions).

Perceived Benefits

  • Bias toward action in environments where emails get ignored and approvals stall.
  • Reduces decision fatigue for managers; they react only if they see a problem.
  • Helps mid/senior ICs show initiative, think through tradeoffs, and sound more senior (“I intend to…” vs “What should I do?”).
  • Creates a paper trail showing others were informed and had a chance to object, useful against later blame or foot‑dragging.
  • Fits many “two‑way door” decisions (reversible, low–medium impact) and internal changes that otherwise languish.
  • Can empower teams and reduce micromanagement when there’s existing trust and competence.

Risks, Failures, and Limits

  • Many view the “deadline” framing as confrontational or manipulative—an ultimatum rather than help.
  • If something important breaks, “nobody approved this” can be career‑ending; silence is not reliable consent.
  • Dangerous or illegal in high‑risk/regulated domains or for one‑way‑door changes (safety, compliance, production‑critical).
  • Can be abused as CYA, or as a way to pressure busy stakeholders who simply didn’t see the message.
  • Several managers say they’d see this style (without trust) as a liability or insubordination.

Culture & Context

  • Works best in high‑trust, bias‑for‑action cultures; may backfire in rigid hierarchies or where independent action is seen as insubordinate.
  • Experiences differ by country and company type (startups vs large orgs; US vs Europe/Scandinavia vs others).
  • Recognized parallels to change advisory boards and RACI: shifting from “Consult” to “Inform” for appropriate decisions.

Application & Wording Nuances

  • Safer phrasings suggested:
    • “I’m planning to do X on [date]; please let me know if you have any concerns.”
    • “We’ll proceed with X on [date] unless this conflicts with [constraint].”
  • Emphasis from multiple commenters:
    • Use only within your remit, for reversible/low‑risk items.
    • Do real homework first (alternatives, risks, rollback plan).
    • Often better to seek team consensus, then inform the boss.
    • Tone, trust, and track record are decisive; abuse quickly erodes credibility.