Ask for no, don't ask for yes (2022)
mooreds.com
Ask for no, don't ask for yes (2022)
1–10 of 96 posts
Re: Ask for no, don't ask for yes (2022)
#2There'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"
Re: Ask for no, don't ask for yes (2022)
#3Re: Ask for no, don't ask for yes (2022)
#4This 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"
Re: Ask for no, don't ask for yes (2022)
#5This 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"
Re: Ask for no, don't ask for yes (2022)
#6This 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"
My default is to trust engineers based on my experience with and expectations for them. If they want input—anything from a deep review to a gut check—I'm happy to help. If you're looking for a gut check, this is a fine way to do it. It communicates your level of confidence, which is an important data point for me.
If someone is adding a GH action, do we need a prototype? Maybe! But also maybe not. Bias towards action. Not YOLOing, not hacked together crap, not vibe code merged without review. But I've found that great engineers are often more hamstrung by permission checks than the issues they're meant to prevent.
Re: Ask for no, don't ask for yes (2022)
#7Re: Ask for no, don't ask for yes (2022)
#8This 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"
Not really. The advice is prefixed with this context.
> When you have something you want to do and that you feel is in scope for your position, but you want a bit of reassurance or to let the boss know what you are up to
Basically it's saying if it's your job to make this decision, but it's something where the boss needs to know (or you need them to know because you need a small amount of reassurance), then asking for "yes" fails to communicate your understanding in that regard.
Asking for "yes" says it's the boss's job to make this decision - but we're talking about decisions where you believe it's your job make it.