Stop asking your manager for yes; announce it and let them say no
Instead of "Can we install action X?", you send: "I'll install it Monday unless you tell me otherwise." The boss keeps the veto. You keep the momentum.
The reframe is tiny: never request approval for work already in your lane. State the action, attach a deadline, and the silence becomes a yes.
It transfers the cognitive load. Saying no takes one click; saying yes makes the manager co-own a decision they would rather not study.
But the same sentence reads as initiative or as a hostage note, depending entirely on whether the thing you announced was a prototype or a push to prod.
A sentence that flips who has to act
Dan Moore's argument is narrow on purpose. For work that already sits inside your responsibility, stop reaching out to your boss for a yes. Instead, announce the action with a deadline: "I will do X by [date] unless I hear otherwise." The veto survives intact, but the default flips. Silence now means approval.
The mechanism is cognitive load. Actively saying yes forces a manager to study your plan and put their name on it; saying no is a single objection they can raise only if something is actually wrong. Moore's own example swaps "Can we install action X?" for "I'll install it Monday unless told otherwise." He fences it carefully: in-scope work only, mostly tested at small companies under 200 people, and never for decisions that genuinely need collaborative input.
The thread's first move was to question the blast radius. The tactic's safety, one reader argued, lives entirely in the stakes you attach it to:
"This is great advice to become a pain in the ass that managers know they need to keep on a short leash. There's a big difference between 'I'm going to put this into prod on tuesday unless you tell me otherwise' vs 'I'm going to put a prototype together for review on Tuesday unless you tell me this is a waste of time'" — a reader drawing the prod-vs-prototype line
Push it to the extreme and the deadline-veto curdles into a threat. Michael Geary offered the reductio:
"Hello $BOSS! I have a code change that is so vital to the survival of our company that … If you fail to respond by Monday, I will push it to production." — a reductio ad absurdum
A third reader supplied the part Moore left implicit, and in doing so re-derived the in-scope caveat from first principles:
"if you tell somebody you're going to do something, you're not asking them to take responsibility. you're telling them that you're taking responsibility" — naming the unstated mechanism
That is why the trick only works where you already own the outcome. And it has found a second life: one developer reported moving the rule straight into his agent config to stop an LLM from over-asking.
"tell don't ask. … it's now in my AGENTS.md: … do the thing that you think makes sense and then write down what you did and why." — a developer who put it in his AGENTS.md
The reason it persists is the same in both cases. Responsibility, not permission, is what the sentence actually moves. State an action you own and you have already absorbed the risk; ask for a yes and you hand a slice of that risk to someone who would rather not hold it. Get the scope wrong, as the thread kept warning, and the deadline reads as a demand instead of a courtesy.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
The creator of Lodash needed five years to come back to it
Lodash ships to something like 100 million npm installs a day. The person who built it lost his mother, went through a divorce, and disappeared for half a decade.