Dan Moore urges developers to cultivate a bias for action by framing requests as chances for a no instead of hunting for a yes. He observed that in startups and teams under 200 employees, waiting for explicit approval often freezes momentum. Even a minimal forward step, he says, can dissolve stagnation and keep work flowing.

Moore notes the habit works best where hierarchies are flat and managers are busy. By offering a deadline, the requester signals confidence and forces a quick decision, yet still leaves room for objections. This subtle power shift reduces the back‑and‑forth of email chains and prevents initiatives from disappearing into a crowded inbox.

When Moore proposes adding a new GitHub action to tighten CI quality, he skips the typical “Can we install X?” request. He writes, “I’ll install X on Monday unless you object.” The boss can intervene, but the default is execution. The tight timeframe compels a response, turning a potential bottleneck into a scheduled task.

Moore’s tactic lets engineers act within scope while keeping leadership informed, a practical fit for small companies where speed matters. By treating permission as optional and anchoring it to a near‑term deadline, teams avoid endless deliberation and maintain momentum. The result is faster delivery of tangible improvements without altering formal processes.