10 ms·
Ask for no, don't ask for yes (2022)
- gred 2y agoBefore reading the article, I parsed the title as "ask for permission only if you want a 'no', otherwise don't ask for permission and just do it".
- mglvsky 2y agoI initially parsed as text variant of this video: https://youtu.be/-vZXgApsPCQ https://youtu.be/-vZXgApsPCQ
- OutOfHere 2y agoWhy bother. If the company doesn't want to respond in the affirmative to a valuable idea that has been communicated clearly, let it torpedo itself and dig its grave. Whatever the answer, the outcome will be righteous. In the bigger scheme of things, it is better to evolve companies that answer optimally. There is no need to ever bend over backwards to save a company that is not your own.
- _boffin_ 2y agoUnless you have a limited pool of opportunities. If so, educate and demonstrate value. Maybe even if pool isn’t super limited.
- NegativeK 2y agoOr, if your job is decent, don't let perfect be the enemy of good. (Also, not every decision that you need to communicate up to your manager is going to have a significant impact on your company. Sorry?)
- readthenotes1 2y agoYou just may, at some point, find yourself in a situation where your goal is not to "evolve a company", but instead to work with the people at hand to get something done. In that case, remembering that "it's easier to get forgiveness than ask for permission" is a valuable tool to have in your repertoire.
- hackerknew 2y agoSometimes the ask is something that you want to improve your own experience at the company. Let's say the ask involves improving the quality of the code that you work on every day. You know your boss will not say "yes" because refactoring does not have an apparent value. But you are confident that if you can some time to work exclusively on some refactor, it will be a benefit not only to the company, but to your future self. I think the advice in the article is a solid way to go about asking for that.
- OutOfHere 2y agoI would rather just work at a place where my hands weren't so tied. The actions you noted only come in the way of it.
- mazambazz 2y agoI hardly think wanting to be more productive/efficient on your own behalf is "bending over backwards" to save a company. It could be a project with a deadline, and you want to knock some things out earlier so that there is less crunch time needed in a few weeks. Maybe you want to get some of your work done early so you can take it easier in near future where you anticipate yourself being preoccupied with other responsibilities. Or, hear me out. You feel secure in your job position, and simply take pride in your work. You will be there working anyways. I would rather get stuff done and feel productive at work than to have meaningless down time twiddling my thumbs, waiting for a response.
- OutOfHere 2y agoI would rather just work at a place where my hands weren't so tied. The actions you noted only come in the way of it.
- brookst 2y agoIt’s quite a luxury to work in a company where every interaction is perfectly empowered. Many of us have jobs that are on the whole very good, but where inter-departmentmental or inter-personal challenges come up from time to time. I’m definitely not one who’s willing to quit in search of the elusive perfect company in that case.
- OutOfHere 2y agoStartups often offer it, and it doesn't have to be so early stage that one has to work more hours either. Once a company gets older, it adds layers of damaging bureaucracy that comes in the way of innovation.
- brookst 2y agoI’ve worked at several startups and I’m not at all sure the typical employee is more empowered. Yes, large companies have bureaucracy, but startups often have micromanaging founders who haven’t learned stuff like delegation.
- zulban 2y agoYour career isn't going to go very far if you have no strategies to overcome roadblocks and deadweight employees in a large org. "Let it torpedo itself" and then what? Find a new job any time you encounter stupid obstacles? That's a new job every 4 months.
- xyzzy9563 2y agoIt is an irrelevant optimization unless you own a lot of equity in the company.
- dsjoerg 2y agoNo, it also helps you progress in your career faster, boosting your own ability to get things done and hence your bargaining position.
- readthenotes1 2y agoThis is a variation of a sales tactic which says to not give people the option to say no but instead only give them affirmative options. E.g., Not "When can we talk about this deeper?" But "Would Tuesday at 1 or Wednesday at 3 be better for a follow-up?"
- OutOfHere 2y agoThat's a high-pressure sales tactic, and the obvious answer to such a question is "Let me get back to you." If I am forced to schedule, I will schedule and then cancel.
- danielheath 2y agoI don’t do sales, but I use this all the time with friends - not to force a particular schedule, but to remove ambiguity about my availability. Folks are generally happy to suggest another time if they aren’t available. If I put “let’s catch up” out there with no information about when I am available, I’m giving the other person the mental labour of initiating the scheduling process.
- bee_rider 2y agoI often say something along the lines of “I suggest X day, but I picked it completely at random just to get the ball rolling, so feel free to overrule.” I do find that people tend to just sort of be overwhelmed by the options when scheduling stuff, so it is easier to just suggest something. But, I hope/think putting all my cards on the table and explicitly pointing out how arbitrary it is makes it seem less presumptuous.
- kianN 2y agoI think it’s less about putting pressure on a prospect as it is making the follow up meeting as easy as possible to schedule. To many people, me included, it does come off a bit abrasive, but it does reduce the number of decision to make into a yes or no.
- dec0dedab0de 2y ago
- aqueueaqueue 2y agoI do this. I got too impatient asking for yes so I ask for no with deadline. Unless it's very risky, then you do a DACI or call a meeting etc. Try to make most of your operations 2 way doors with safety fallbacks. If you have good tests, you'll be able to get away with more.
- AdieuToLogic 2y agoA related technique is: It is easier to ask for forgiveness than permission.
- glitchc 2y agoI think this kind of approach, and I've used it in the past, only works in American companies or bosses who are familiar with the American way of business. It can backfire badly if the boss doesn't like it. During a performance review, the boss inevitably labels you as insubordinate and all of the evidence needed was handed to them on a platter. Sometimes asking for permission really is the best way, even in the US. Doubly so where resources are concerned.
- ulfw 2y agoThis will not work in non-American companies where a boss might actually have a life and not work weekends, or heaven forbids have days/week(s) off.
- Jolter 2y agoThis would have worked fine in a Scandinavian company where managers are expected to delegate (some/most) technical responsibility. If boss was off, and couldn’t react in time, their eventual reaction would depend entirely on the outcome. If you were successful, they’ll appreciate that you didn’t hold up the decision by asking them.
- chgs 2y agoWorks fine in my British company that is almost as old as America, it’s called “out of office”. If they aren’t in the decisions are delegated to someone else.
- coffeemug 2y agoI don't think I've ever worked for a boss who would have disliked this approach, and I had many (good and bad). Assuming of course what you're doing isn't idiotic. All of them were steeped in American culture, though.
- foobarian 2y agoHonestly it's not my boss I worry about, more like a sibling team or service client that would have a stake in the decision but is known to drag their feet.
- locusofself 2y agoI like this approach to communication, except the the "deadline" part. I'd prefer my reports just let me know if they are working on something which I may want to veto (because I may have more context as to why it's a waste of time or not a priority). Giving a "deadline" to your manager is strange, and almost like a weird, annoying threat. I also would like to think I would give people on my team enough autonomy to make their own decisions about something as trivial as a github action.
- afarviral 2y agoI really like the idea of seeking a no (e.g. let me know if I shouldn't go ahead) but as soon as I add something like, "I will do this on this date, unless I hear otherwise", is a little aggressive feeling. It might be easy enough to simply mention the time the work will take place, but leave it unspoken that they could decide it's best to not proceed, "I should get it done around this time". Then again, it's been a goal of mine forever to be assertive. Cowing only takes you so far.
- post-it 2y agoIt's just a matter of phrasing. "Hi, I wanted to give you a heads up that XYZ needs doing, and I'll be doing it on Wednesday. Let me know if that doesn't work."
- wavemode 2y agoAgreed, stating a deadline on something that is still just an idea, is weird and aggressive. Usually, a deadline is used to communicate "I have already decided I'm doing this, and received approval/consensus to do it, so now I'm informing you of the fact that I'm doing it."
- seansmccullough 2y agoA lot of times you have to set a “deadline” when interacting with other teams/orgs, or they will just never get back to you.
- 2y ago
- ChrisMarshallNY 2y agoI pretty much work this way. In my experience, they completely ignore what I’m doing (“yeah…whatevs”), then pitch a fit, when they see the result. I get a lot of whining about how come I don’t have clairvoyance, and didn’t interpret their ignoring me, as a “no.” Annoying AF, but I still do it, as I can point to my statement of intent, and tell them that they had their chance. Often, I don’t just ask for a “no.” I also ask for specific input and feedback (which I also don’t get). That gives me more ammo, when they get butthurt. The trick is to not do something that will really upset them. That takes experience and empathy.
- maeil 2y ago403s here, guess they're geoblocking entire continents.
- emmelaich 2y agoOr just do it, in testing. If it's reviewed by colleagues and looks good then ask for no.
- jrexilius 2y agoThis is a great way to frame it with the caveat that you've done a fair bit of homework to support your assertion. And the other thing I would add is context-aware time padding. The "deadline" should be adjusted to respect the bosses schedule AND the potential impact. i.e. if it could hit production, give them more time. If it can't easily be rolled back, give them more time, etc. But in general, if you are an adult, competent at your job, taking initiative, and have spent a bit of time thinking through the second and possibly third order effects, this is great.
- tdiff 2y agoProbably most of so called software engineers consider themselves "competent". "Adults" are well aware of it, and apply to themselves, hence collect others opinion.
- ryandrake 2y agoThis is a critical skill in big companies where everyone is swamped and busy and things get lost. I do this all the time when I’m dealing with people who don’t answer their email, or who tend to stall and delay approvals, or people who are just very busy. I’ll Email and describe the problem and then say the magic phrase “If I don’t hear back from you in [N] days, I am going to do XYZ on [DAY N].” This way I’m not asking for approval and then helplessly waiting and pinging. I’m putting them on notice. XYZ is going to happen unless you get off your butt and stop me. Occasionally someone will come back weeks later, angry that I did XYZ without telling them, and I always have a paper trail showing that they were the ones who dropped the ball.
- sieabahlpark 2y agoWorks great until you break the law by accident if you're in a regulated industry. Sometimes it isn't as easy to do that.
- gukov 2y agoYeah, opting in by default like that can backfire when something gets done and the boss gets in trouble.
- kmoser 2y agoThese days I almost take it for granted that somebody isn't going to read my email, or won't read it thoroughly, or will read it but will fail to acknowledge it. One can use this to their advantage if they want to skirt a hard "no" but as you said, it may backfire. And the "boss" may have a point: relying on them to read, understand, and acknowledge your email, especially when it's important, is somewhat disingenuous. At the very least one has an obligation to confirm that the recipient actually read and understood what was sent, before taking the default action.
- tempestn 2y agoOne thing I've eventually managed to learn after failing at it many, many times is that in the vast majority of cases an email can only say one thing; if you try to ask multiple questions, or give multiple pieces of information, best case people will actually read one of them. Worst case it'll overwhelm and they'll ignore the whole thing. It's obviously different if you know the recipient and that they're able to handle more, but my default assumption is that people will read the first 1-3 sentences of an email, so I do my best to keep it to that, and if I have more to say I'll make a note to myself for once they reply.
- JackFr 2y agoThis is a recipe for disaster the first time you break something. Getting a yes or a no indicates that your boss is aware of it. When you’re in the hot seat, and someone asks “Who approved this?”, the truthful answer is that no one approved it.
- ludston 2y agoIt really depends on the culture of your organisation and how effective management is. If there is nobody that can act like this at your org it shows that your leadership team suffers from failure to delegate.
- lelanthran 2y ago> It really depends on the culture of your organisation and how effective management is. If there is nobody that can act like this at your org it shows that your leadership team suffers from failure to delegate. I think it's more than just that - upthread I posted that I used this technique for over a decade against a difficult party. This approach is, briefly, for CYA: It's for when you are in the following situation: You have to do something and will be punished if you don't, but a stakeholder is being difficult and/or hostile. They can delay you or outright sabotage you just by silence and/or bike-shedding.
- Imustaskforhelp 2y agoThanks. Made things a lot more clearer. It seemed that my natural response reading the article was to use such approach everytime no matter what & some people in the comments also said that they use this approach everytime.
- prh8 2y agoThis is such a helpful way of viewing it. I have a principal at work that will comment on things to delay or slow down, and then never revisit after their comments are addressed.
- sdwr 2y ago
- finnigja 2y agoAnother take on this I like is "radiating intent". Broadcast what you want to do, when you plan to do it, and give stakeholders space to explicitly object, rather than explicitly chasing consensus / alignment / approval. Works in some scenarios, and generally requires baseline trust to have been earned. https://medium.com/@ElizAyer/dont-ask-forgiveness-radiate-intent-d36fd22393a3 https://medium.com/@ElizAyer/dont-ask-forgiveness-radiate-in...
- kashyapc 2y agoThanks, this is an interesting take. The 4 reasons for "radiating intent" make sense. It works in moderately high-trust organisations. I also appreciate the author (Eliz Ayer) adding the below nuance: "In all fairness, you might get less done by radiating intent. It does give obstructive or meddling folks a way into your thing. Also, advice like this is very situation- and organization-dependent and won’t be appropriate all the time."
- tempestn 2y agoYou can even do this kind of thing without going as far as stating that you'll take action unless overridden. It can be as simple as rephrasing a question from a "yes" to a "no", like "Does this work for you?" -> "Do you have any objections?" Even when the request is logically equivalent, people often find it easier to say "no" than "yes".
- allset_ 2y agoYou can also phrase it a little more gently. "I plan to start on this on X date, let me know if you have any concerns." And send a reminder so that you're giving them multiple chances to respond.
- reader9274 2y agoAh yes, do what all these slimy companies do to get you to accept their new terms: "These terms take effect on this date unless you send us certified mail to opt out". Works every time
- 42772827 2y agoI call this “creating sane defaults.” That is, rather than going to people and asking that they make decisions about every detail, pick a set of sane defaults that demonstrate your knowledge of the situation and just tell them you’re going to run with it. This will build trust with people, and they’ll be more likely to give you attention when you really need it — because they’ll know you’re not wasting their time.
- wes-k 2y agoI like the framing of "defaults" too. Gives space for suggestion and change.
- toomanyrichies 2y agoI've used this technique ever since I read DHH's article about the book "Turn The Ship Around" [1]. The book's author, a Naval officer, had a policy of "Don't come to me for permission, come to me with intent." Hearing that phrase changed my professional life for the better in so many ways. Admittedly I haven't included a deadline nearly as often, but I've found a huge difference between saying "Can I do XYZ?" to my team lead (or even worse, "What should I do?"), vs. "Unless you object, I plan to do XYZ." The latter is frankly much more empowering as an employee, and it doesn't hurt that it sounds so much more senior. If I come with intent, I have to be prepared to defend that intent, which gives me more ownership in my role on a team. 1. https://signalvnoise.com/svn3/you-dont-have-my-permission/ https://signalvnoise.com/svn3/you-dont-have-my-permission/
- w10-1 2y agoIt's fair to bias for action in this way. But offering a negative option to object could be more likely to induce mistake and undue reliance. (Remember: negative options are illegal per FTC.) But the real question is not the form of the ask but what information to include. You have to tell deciders what they need to know to decide. Don't queue them up for a research project or to go survey stakeholders on your behalf. Deciders need at least to know the range of consequences and likelihoods, and when and how there will be new information or opportunities for monitoring/managing. Usually that means you also propose their management plan. e.g., "I'm updating dependencies on Sunday. If it fails we'll roll-back, which is ~2 minutes of downtime (within this quarter's SLA). If it works, offshore will need to refresh their devenv, but we can reduce the security notice Monday. I'll preflight Saturday if you want to confirm with me Sunday beforehand, and I'll cc you on offshore/security go-ahead's."
- robertclaus 2y agoI personally try to nudge even my junior team members towards this. I would never admonish them for taking this type of initiative working with me. I WOULD however have some difficult conversations if they thought this meant they could cut corners on communicating with stakeholders or execute on something without appropriate planning or review. There's a big difference between showing initiative and ignoring process that exists for good reason.
- _kb 2y agoIf you extrapolate this to larger / more bureaucratic organisations this is a change advisory board. You advise that change X will happen to system Y at time Z along with details of prep work, risks, and conditions for back-out. This gives a window for questions or concerns to be raised. In lieu of a nope, it then proceeds.
- 4dregress 2y agoI believe the phrase is “Ask forgiveness not permission”.
- 4gotunameagain 2y agoIn this case it is different, you are implicitly asking for permission on a timeout clause.
- seanwilson 2y agoPart of this "I'm going to do this unless you let me know otherwise" trick is not phrasing it like a question to reduce communication overhead. That way the receiver doesn't have to write a reply and you don't get another email to read (and for anyone CCed). Saying that, I like emoji reaction features like on GitHub and Google Docs where you can just give a thumbs up to acknowledge you read and agreed to something. Seems really unpopular with some on HN for some reason, but emoji reactions are a useful lightweight way to communicate that you're on the same page, rather than making someone go through the motions of sending a "Okay, makes sense!" comment for every little thing. A bit like an upvote.
- Imustaskforhelp 2y agoI totally agree with this comment. I think this is a sort of art in communication which I have just discovered. Though in emails I am not sure if there is an option just for thumbs up , but I do wish so. I am going to start to learn this art , like this is such a good way of working but it also has to be a little subtle , not rude and may or may not work , IDK just my two cents.
- DeathArrow 2y ago>Hey, boss, I am going to install action X, which should solve the XYZ problems we’ve been having. Will take care of this on Monday unless I hear differently from you. Great Pete, that means you've finished all the work from the current sprint and from the next and you've searched the backlog and didn't find anything to work on. Otherwise you wouldn't have wasted time on this. Since you have this free time, I have a task for you.
- megadata 2y agoHey, boss, I am going to hand in my notice now, which should solve the boss problem we’ve been having. Won't be here this on Monday unless I hear differently from you.
- deleted 2y ago[deleted]
- bingemaker 2y agoThis is the famous pattern that we see in building interfaces. "Tell, don't ask".
- HeatrayEnjoyer 2y ago[flagged]
- conductr 2y agoI call this “Don’t Ask, Tell” and it has so many uses inside but also outside work. It really is just a basic communication skill to hone. It leads to concise and decisive outcomes. I actually have this conversation a lot with my wife. She’s more of an asker. A recent example from earlier this evening. We had arrangements set to meet a group for dinner. Her style is to send a text to the group, 8 people, saying “what time is everyone arriving?” Which is so open ended it would initiate a flurry of comms. But, we knew we would be there an hour early because of where/when we were dropping our kid off for the evening. So I just said TELL them when will be there and TELL them we’ll be at the bar if anyone wants to have a drink beforehand. So much more straight forward, everyone showed up early and it was perfect with minimal comms required. Sure it was a lucky accident that everyone had care for their kids lined up to and was able to make it but the point is It took no time and actually didn’t even require any response at all in the case someone was not monitoring their messages. It’s somewhat related to the idea of “ask for forgiveness, not permission” which I’m a huge fan of in all kinds of ways. Sure it can be riskier but I’m a rebel at my core so it comes with the territory. But this has its place too, group collaborations like GitHub repos is probably not a good place to yolo big changes that effect other people.
- kjrfghslkdjfl 2y ago> But, we knew we would be there an hour early because of where/when we were dropping our kid off for the evening. So I just said TELL them when will be there and TELL them we’ll be at the bar if anyone wants to have a drink beforehand. I do this too. And it's not just better communication, it's better life. This way I'm not dependent on other people to have fun. I'm not waiting on coordination in order to start doing the thing I want. I'm doing the thing I want, and letting others know that they can join.
- conductr 2y agolol. Same. And from same example of this dinner night I described started with my wife sharing 3 restaurant options with the group and a few texts flying around that I 1) didn’t get ahead of and 2) was late to the convo on but even by the time I got onto it all the messages were “they all look great” “oh I just can’t choose” “you choose we can’t!” and I just get to it and see this has been going on/off 6 hours with no decision and say “X would be my pick” and every quickly agrees to it. Idk if it’s a men vs women thing or me specifically, but I just like to have a bias for action and make quick decisions with efficiency in communication. I think saying that briefly online in a comment probably makes sound like a bossy jerk but there’s a lot of nuance and skill to hone with this style of communication that is more difficult to elaborate on here, but the key is doing it without rubbing people the wrong way.
- vmurthy 2y agoI like the general idea. I read the book “Start with no” a long time ago and the lessons stuck. The first principle here is that people have an innate need for autonomy and giving them the option to say no gives them peace of mind. Highly recommended. https://www.goodreads.com/book/show/689417 https://www.goodreads.com/book/show/689417
- deleted 2y ago[deleted]
- worik 2y agoI'd fire him > .”Hey, boss, I am going to install action X, which should solve the XYZ problems we’ve been having. Will take care of this on Monday unless I hear differently from you.” No thank you. I'm the boss. Don't push me around
- mooreds 2y agoAuthor here. Ah, this is interesting feedback. I think that there's some nuance to this approach that I didn't capture in the post. You have to have some level of trust between yourself and your boss, which you've earned over time by being right and/or fixing mistakes you've made if you were wrong. The idea isn't to push the boss around; it's to make the boss' job easier by making default decisions for them, but letting them weigh in.
- worik 2y ago> You have to have some level of trust between yourself and your boss Yes. What you are suggesting is corrosive to trust though. Frank discussion is good. Stating what you need and what you expect. Game playing is no good and I would probably not fire you for it, I was being hyperbolic, but the point I am making is do not play games. At work, or anywhere. Relationships thrive on honesty.
- xerox13ster 2y agoYes you’re the boss and no one can take that away from you. You must have worked very hard to get there if you’re blocking your team from taking initiative and making independent contributions to the organization. Based on this attitude I’d assume you suffer from an extreme inability to delegate and are going to be stuck in whatever direct supervisor position you’re in for the remainder of your career. If I showed initiative like this and your response was “I’m the boss. Don’t push me around.” I’d quit on the spot and I sincerely hope you only have lackeys too dumb to understand how detrimental this egoist attitude to your own authority is to productivity and creating organizational value.
- worik 2y ago
- kstenerud 2y agoYup, this is the meatspace equivalent of "opt out" vs "opt in", and works for pretty much the same reasons.
- weitzj 2y agoI think this person has also interesting content regarding No and Yes https://youtube.com/shorts/DjuC8xauWWk?si=VkGFbgbqyzKqPjLD https://youtube.com/shorts/DjuC8xauWWk?si=VkGFbgbqyzKqPjLD
- weitzj 2y agoAnother interesting one https://youtube.com/shorts/tWthV06ZIDo?si=JdKPvykIuv5q7RGY https://youtube.com/shorts/tWthV06ZIDo?si=JdKPvykIuv5q7RGY
- thornycrackers 2y agoChris Voss, former FBI Hostage Negotiator and author of Never Split The Difference. Has lots of great tips.
- hamandcheese 2y agoI like the perspective, but then the concrete example given (adding a new GitHub action) is such a trivial 2-way door that I am worried for the author. There are better companies out there!
- notpushkin 2y agoWith great power comes great responsibility. People will think you went behind their backs, even though on paper you did everything correctly. If you abuse this trick, you’ll quickly lose people’s trust. Use it carefully, always give a reason, and set reasonable deadlines.
- Feathercrown 2y agoThis is an excellent tool for the toolbox. My company has work from home days but the managers technically have to approve schedule changes/exceptions. Since they almost always approve it, we usually just say "I'll be working from home Tuesday if that's okay" and unless they object, you're good.
- Pamar 2y agoIn my current job ... I write design documents that must be approved (in writing) by Key Users in two different companies. Followed by test cases signature and then by user acceptance test documents. This style could never work for me: "I'll push it to production on Day X, exactly as described here - unless you object" is not really applicable for me.
- Imustaskforhelp 2y agoYes I really like such approach. But it feels a little confrontational. Maybe I haven't read all the comments but I would love to if somebody could give me certain examples where it doesn't sound confrontational and maybe as confrontational as asking for a yes. I really like the approach but I think I would be looked as if rude , like look at that guy , he thinks he can do whatever he wants if I say nothing , Let me use politics to put him down unnecessarily. Again , I really like this approach and am just asking for better / more examples. Something which I can apply practically.
- lionkor 2y ago"Hi, I want to switch our logging solution in our client from Console.WriteLine to NLog, because it's been bothering our tech support that we don't have log levels for errors. I've made an issue here: ... . I have some time end of next week due to XYZ, so unless you object, I'll do that on Friday and put it up for review." And then bother them until you get some reaction that they have read it.
- jsmeaton 2y agoI often give similar advice to colleagues that ask me for pointers on getting their recommendations approved. "Make it as easy as possible for them to say yes" Don't dump 14 paragraphs in front of someone expecting them to get onto the same level that you've been after many hours of studying a problem. If you're confident in your approach (and you should be, if you want an easy yes!), then be succinct, briefly describe the problem and why your solution is correct. Optionally link to a document that has more information if a reader wants to go deeper. Make sure you've already gained "approval" from your other team mates or product owners. "We're going to solve X by doing Y. Team are all onboard. Proposal document is at [link] if you want the detail. Going to begin on Tuesday unless there's any more feedback we need to address." Managers etc don't have time to get into the detail of every little thing, and appreciate when you've done the work, including gaining support from the wider team, so if they need to approve, they can just approve.
- whoknowsidont 2y ago>Managers etc don't have time to get into the detail of every little thing, and appreciate when you've done the work, including gaining support from the wider team, so if they need to approve, they can just approve. This is how popularity contests start lol. Managers that work this way are ineffective / pointless.
- nlitened 2y agoA manager that organized their team so that each team member makes concrete thought-out proposals with all details covered, so that it's their only job left is to give approvals and do nothing else? I'd say that's a brilliant manager
- andrei_says_ 2y agoI agree and that’s how I often get things greenlit. Pro tip: have a quick conversation with a manager and have them make a decision on a $noncriticaldetail before the announcement.
- darkest_ruby 2y agoThis is basically asking for forgiveness instead of asking for permission
- puapuapuq 2y agoHow to phrase it if you need code review from other team and deploy code into their code base?
- bob1029 2y ago> Again, pursue this approach for problems you feel are in the scope of your role If something is actually in scope of your role, you shouldn't be bothering your manager about it. Wait for them to come to you and then provide an update about your progress or new ideas/concerns. Every time you send an unsolicited email to your boss it costs time and money. Doesn't matter how it's worded. It's gonna consume some energy.
- A_No_Name_Mouse 2y agoThis works great from a leadership perspective as well. If anyone is interested, I can recommend the book Turn the Ship Around! by David Marquet about this very subject.
- lrvick 2y agoI have done this my whole career some companies see it as being over eager, or even insubordinate. Do it anyway, because the companies worth working for will support you self assigning work that needs done, and hire other people capable of doing the same. Hire people who can self manage instead of hiring managers.
- dweekly 2y agoI've found "I presented this project to partners in Risk, Cyber, Compliance, and Legal and received no objection." is quite effective. People in a large company want to know you're working with the right set of people and that nobody is going to be surprised. At some point if a large enough set of people have seen a project and are aware without objection, folks don't want to try to "push back the tide" and a thing will achieve momentum of its own. "Gosh if Wendy and Bob and Jill are all okay with this...ehh sure."
- zb 2y agoI’m reminded of an infamous occasion when this technique was used: https://en.m.wikipedia.org/wiki/Cable_243#Preparation https://en.m.wikipedia.org/wiki/Cable_243#Preparation
- epolanski 2y agoI like to appeal to person interest more. I'm gonna do X, that should remove some of the arguments in our *insert meeting/discussion" (removes problems from that stakeholder) and speed up this so we're never the blocker when other teams are involved (puts your stakeholder like a pm ahead of his peers and in the corporate rat race). The more you know the stakeholder (a colleague, a manager, an owner) the more you understand his goals and his pains the more surgical you can be. E.g. "I am going to rewrite this in typescript because typed languages are nicer to use" => "I am going to rewrite this in typescript as it will provide a better experience and make hiring easier" (might be important if youre looking for extensive Magento experience in the middle of countryside Germany to drop it and PHP). "I will only provide feedback under the form on mobile because that's the only screen where they won't see it without scrolling" => "I will only provide feedback under the form on mobile so we don't confuse users on desktop and lose sales". Again, it is very important to understand what drives the particular stakeholder and try to sell general ideas under the light of how it benefits him. Your website lacks accessibility? Don't appeal to ethics of disabled people. Explain it's your managers head on the line if someone complains due to the EU accessibility act and there's legal responsibilities.
- keyle 2y ago27 years professionally and I naturally do this. ... However I suffix it with "if that's okay" or "unless there is something more pressing".
- jonplackett 2y agoI think all this arguing over the phrasing is kinda missing the point. It comes down to whether you expect this person really will have objections. If you are going to do something you believe they won’t approve of, even the most polite wording will not stop it being a dick move and confrontational. Likewise if it’s something you’re pretty sure they won’t object to, you can probably be quite abrupt and it’ll be fine.
- mcv 2y agoThis is good advice that I've seen applied effectively many times, with one big difference: don't ask your boss, ask your team. Especially when it involves Github actions that will effect the way the team works. Chances are it impacts developers more than your boss, and they're likely to know more about it. Depending on circumstances also include your boss of course, or maybe they're already part of the team. But it can't hurt to cast a wider net asking for objections.
- grahamm 2y agoTo me this is a key change in a direct reports development. When they first start they need to be told what tasks to do; then they develop to asking for permission to do tasks that find or know need to be done; and finally they are telling me they are doing a task so I know we are going in the right direction. These changes give much better autonomy within the team and I am know longer the blocker to progress. It also means I can get on and do more interesting tasks myself while working with the junior members of the team.
- mooreds 2y agoI want to work for you!
- EtCepeyd 2y ago> finally they are telling me they are doing a task so I know we are going in the right direction Yes, but. :) Assume a high-profile open source project where your direct report is a maintainer. The higher-profile the project is, the more political it becomes, of course. Your report will not need your (= the manager's) input on technical decisions; instead, they will inform you (in the optimal case) of where things have been heading. However, if that maintainer also participates in community governance -- which is quite likely --, they won't be able to avoid decisions that are more political than technical in nature. And whatever they decide there may easily reflect on their employer or client, one way or another. That kind of stuff is something that they should consult you on, regardless of their technical seniority.
- geomcentral 2y agoHow does this work in a Scrum context? I want to get stuff done but I need to raise a ticket, have the priority agreed, and get it planned into a sprint. Then after these layers of 'asking for yes' I am allowed to work on something without scrutiny. Let's say I wasn't subject to this process, my pull request would still need someone to approve it. Is there a way I can adopt the approach of 'asking for no' with these constraints? Or does it only apply in high autonomy workplaces?
- mooreds 2y agoI don't see how this works in the context of scrum as I've seen it done, except in the weak case of you getting to raise the ticket of whatever topic you'd like. I guess you could ask for no around specific implementation details too? So if you are working on ticket XYZ that could be solved in N ways, you could pick one that might be a bit out of the norm (but still solves the problem) and 'ask for no'.
- mozzieman 2y agoIt is all about backing up this question with confidence before asking it. Not about trust you earn over time but trust each time you ask it. I require teams to do their own security reviews, that includes requirement gathering before shipping anything. If i get a "Anyone have any objections / concerns question" I usually know directly if they just bullshitting and only done the minimal viable to get something out and want to be able to say "but i asked" or if they done their due dilligence.If the person only says short what they will do and just broadcast it. "Throws it over the fence". Imho is just bullshit. The people that are good have backed it up with explanations, proper knowledge about different areas what they are doing, presenting their thoughts and make sure stakeholders are informed in person or by good documentation and overall just come across like they know stuff. Then it is okey / good to ask like this to find out if you missed anything.
- wodenokoto 2y agoIn student council in high school we implemented a similar approach. Any vote was a vote to deny, not approve because basically nobody bothered voting, so that was the way to make things happen.
- demarq 2y agoI wish I’d found this article earlier. My biggest frustration at work was literally this. Having to propose ideas a million times before any one of them saw the light of day.
- OhMeadhbh 2y agoWhile I appreciate the OP's position, I suggest the preference of forgiveness over permission is highly contextual. If you're working on a social networking web site, certainly, move fast and break things. But if you're working on a nuclear launch control system, you probably want to model a "don't launch until authorized" control system instead of a "launch unless told not to" system. That being said... I've used this technique in larger collaborative projects: "If we don't come to agreement by <date>, I'm going with the default choice that may not be optimal for everyone. (i.e.- don't waste time suggesting your alternatives.)" In my younger days I thought you needed to have a horrible default, but that only works a few times before your collaborators think they're just better off without you.
- mooreds 2y agoI'm the author. Thanks for your feedback. Lots of nuance here! I agree that different kinds of orgs and projects and decision scopes all play a role. As does trust between you and your manager, knowledge of what requires feedback, what doesn't, and what is risky enough to require an affirmative response. But having a bias towards action has been really important for my career. That doesn't mean I haven't flamed out at times, but when I found the right environment with the right level of trust, this technique was super helpful to me.
- ysavir 2y agoThis seems like the sort of communication style that would immediately have me label someone as a liability. It presents the communication as if it's saving someone time. In practice, it's a communication style that tells the manager that they need to always keep on top of whatever the employee is doing or else that employee might be taking unwanted action(s). The article treats it as a notification, but even with the best intentions and the best understandings, notifications have a habit of getting lost in a noise of signals. A lack of response does not indicate consent. It could, but it could also very well indicate that the message hasn't been received. It might be fine if the problem was something the employee and manager previously talked about and this is simply moving forward with a solution, but it's a terrible way to introduce a problem that the other party hasn't even considered. It's a selfish take, and the antithesis of teamwork. Feels like the sort of thing someone might have seen one of the mythical 10x, Rockstar engineers do. The sort of engineer that's always on top of their game, churning out feature after feature, knows what to do, and has enough respect from and mutual understanding with management that they're given the leeway to self-manage. And the someone, seeing this, decided that the same can apply to themselves, without understanding why that rockstar engineer gets that treatment, or how to go about earning it for themselves in the firstplace.
- bentt 2y agoAs with everything it's about the relationship. If you do this 3 times in a row and receive "stop, please don't" then obviously you're off in some regard. If you do it 3 times in a row and get praise, then keep going. The liability person is someone that is told no, then figures out how to do most of it anyway. Then looks for a yes. Then the next task same thing. No responsiveness to feedback. So, it's really not about the method described as much as the working relationship. It seems like a fine thing to try in a high-trust environment where people are busy.
- mooreds 2y agoThat's a great point. There needs to be trust between the person doing this and the boss. That trust is earned. You also need to pick the right scope of problems--not too big. If you are one month into a new job and use this technique, but the problem you are trying to solve is deep rooted and you don't understand it, you'll burn effort and credibility. It also makes sense to respond to feedback from your manager, as you suggest above. Some managers may hate this (see other comments, including one that would fire anyone using this technique). In fact, you could even explicitly ask how a manager wants to weigh in on decisions that you feel are in your purview but that they might have feedback on. (Drawing out a manager's readme, as it were.)
- mft_ 2y agoA technique I use regularly (mostly for decision-making in meetings) and successfully is the five finger approach. Essentially, people have to hold up a number of fingers showing how strongly they feel about the decision that is proposed. If they strongly oppose it they can do, but they have to offer an alternate proposal at the same time. What works very well about this is that it moves people away from “do I support this, and is this the perfect proposal?” to “do I hate this enough to block it?” As such, I think it’s similar to the article’s approach – the default decision (in the absence of strong disagreement) becomes a yes.
- s3p 2y agoThis is such an interesting strategy, thanks for sharing. We typically get bogged down in meetings by people dropping constant nuances and edge cases and overly complicating things when a new proposal is presented. I might see if we can adopt a similar approach.
- coding123 2y ago[dead]
- EtCepeyd 2y agoNice; instead of burdening your boss with a decision, now you're burdening them with a ultimatum, with a deadline. I guess, as a manager, I wouldn't love anything more than a report saddling me with an arbitrary deadline, one I'd have to schedule along with the rest. One of my managers used to tell me this, instead: ask for forgiveness, not permission. That one seems way saner to me.
- mooreds 2y ago> One of my managers used to tell me this, instead: ask for forgiveness, not permission. That one seems way saner to me. So you are suggesting making the change without consultation and then waiting for it to be discovered? I guess that makes sense for certain kinds of situations, but the ones I can imagine don't sound very pleasant. Maybe I'm missing something. What is an example of a situation where you'd take this approach?
- imajoredinecon 2y agoIt’s really about (a) the wording (b) the level of risk. For something that isn’t risky, I trust my reports to make reasonable decisions and wouldn’t benefit from the “I’m going to do this tomorrow unless you say no” approach. Instead, they can just tell me they’re doing it (or let me know after the fact, or add/FYI me on the code review, or not even mention it, depending on what it is). For a decision that is more important/higher risk, they should get affirmative agreement rather than just hoping that I see the ultimatum and silently approve. That’s why I’m with the GP that the ultimatum-with-deadline doesn’t seem like the best choice in any situation.
- mooreds 2y agoThanks for the feedback. I guess I'd put the 'ultimatum-with-deadline' in between the two risk profiles you outline--something just on the edge of risk. > Just hoping that I see the ultimatum and silently approve. I never would have thought of this as an ultimatum--to me it's more like a 'default decision' that makes my manager's life easier while still looping them in and giving them control should they choose to exercise it. But now I can definitely see how it might be seen as one, depending on the type of decision and the relationship between employee and manager. I should probably update the post to say that you need a degree of trust and alignment for this technique to work; you shouldn't roll this out on the first day.
- lokimedes 2y agoNATO runs on this principle, “silent procedure”.
- mooreds 2y agoTIL: https://simple.wikipedia.org/wiki/Silence_procedure https://simple.wikipedia.org/wiki/Silence_procedure
- EtCepeyd 2y agoYes, but NATO members are not bound by contracts that classify them into superiors and subordinates. Whereas at work, you'll have some form of contract in which you agree to taking -- and usually: soliciting -- direction from your superior or client. Silence procedure works between equals, where each party is required, from the get-go, to (a) announce their intent to the shared message bus, (b) diligently listen to the shared message bus, and take action whenever necessary. The communication pattern between manager and report is totally different; the parties are not equals there.
- rererereferred 2y agoThe same is for requests/procedures in my government. Unless they respond within a predetermined time, the request is considered granted.
- k__ 2y agoSeems like a reasonable middle ground between asking for permission and asking for forgiveness.
- tofflos 2y agoJust do the thing. I'll have your back if it goes wrong. Sincerely Your non-toxic boss.
- jcutrell 2y agoI'll add to the conversation another interesting technique from Chris Voss, which is to use no-oriented questions. People like to say no. (I'm not sure what this cognitive bias is, but anecdotally I agree.) So, if you can frame your requests in a way that "no is permission", it will often get a red light a bit easier. Example: replace "Is this a good idea?" with "is this a bad idea?" Now, of course "not a bad idea" is not the same thing as "good idea", but it's a lot more likely. Even reading that, I imagine most people would respond more intuitively, because it helps us avoid a commitment we don't necessarily want to adopt.
- docmars 2y agoThis is roughly how I've operated for the past 5 years in my career and it's only benefited everyone. Sure, I get pushback sometimes when a stakeholder feels strongly about taking a different approach or maybe waiting to find out whether certain features or scope are needed, but most of the time, like this blog mentions, people will develop respect for you that you can make confident decisions in the work you're doing, and that you've spent the right time understanding how to solve a certain problem without needing to disrupt their flow.
- deadbabe 2y agoThis is such bad advice all around. Everyone already knows the “ask for forgiveness, not permission” trick. The problem is if you don’t get forgiven, you are absolutely fucked and the other side is perfectly justified in raking you over the coals. If you had permission, you’d be excused. Imagine your boss reads your email and knows what you want to do is a bad idea. So they ignore you. You do it. It fucks shit up, now your boss has your ass. You can’t assume they saw your message, they never said yes or no. Don’t do this. Get a yes.
- righthand 2y agoHumanoid task runners are learning to log the scheduling of their tasks! Panic?
- skeeter2020 2y agoLots of good conversation here; I'd argue this isn't a better approach, but different and in many circumstances one of the few ways to get anything done. I put it in the "ask for forgiveness" bucket, but done responsibly. Sometimes it's actually the nicest thing to do, because busy people who don't care enough to step up get to avoid (yet another) distraction. It helps calibrate how much someone really cares, as it takes some energy to provide input vs. just objecting out of principle or as a default position.
- kmstout 2y agoYears of listening to C-SPAN have taught me the value of declaring what I intend to do and then proceeding "without objection." [1] (I'm still waiting to "yield myself such time as I may consume.") --- [1] https://en.wikipedia.org/wiki/Unanimous_consent https://en.wikipedia.org/wiki/Unanimous_consent
- toss1 2y agoThe version I've found most useful is "UOD", as in "Unless Otherwise Directed..." As in "Unless Otherwise Directed, I'll be updating the Foo project next week to include the Bar modules..." or "UOD, I'll call Alice tomorrow to update her on Bob's plans..." Works well, concise, shows you are on it and proactive, and works both as a proper status/planning update and/or an opportunity for the person to weigh in to change course... (and documents the chain of events).
- cynicalsecurity 2y ago> Now, let’s take the alternative approach.”Hey, boss, I am going to install action X, which should solve the XYZ problems we’ve been having. Will take care of this on Monday unless I hear differently from you.” That's how people get fired.
- dctoedt 2y agoAs pointed out by @thevarmint, UNODIR is a longstanding military abbreviation for "unless otherwise directed." And that'd be a useful code to include in the subject line of the email as an attention-getter and summary, e.g.: ========= To: Boss From: Me Subj: UNODIR 2/23/25: Upgrading production database ======= And the body of the email could provide more background.
- deleted 2y ago[deleted]
- neilv 2y agoSometimes I do something like: "Small heads up: I plan to do [thing] at [time/day], unless I hear any objections before then. [optional following paragraph(s), with link to the issue-tracking task, and/or inline rationale/detail]" This is for things that probably don't need to be discussed, with people with whom you have a good working relationship, but for which a low-friction opportunity for correcting my mistaken assumption is good. If you do it for something that you should've realized probably needs to be discussed, or that you should've realized probably needs an affirmative approval, then bypassing that was a mistake of yours, and damages trust. If you do it when there's some kind of trust problem, then it's dripping with subtext. Like you might be looking to bypass them with weak paper trail, or maybe you're being passive-aggressive in the way you nominally keep them in the loop. Until you fix the trust problem, err on the side of avoiding new misunderstandings.
- lifestyleguru 2y ago> Ask for no, don’t ask for yes That's not what she said, and now he's in trouble.
- chfritz 2y agoThis is the difference between I(nform) and C(onsult) in RACI matrixes, a great framework to keep in mind as you think about team communications. https://en.wikipedia.org/wiki/Responsibility_assignment_matrix https://en.wikipedia.org/wiki/Responsibility_assignment_matr...
- GarnetFloride 2y agoI have noticed that very few people in a big corp have the authority to say yes, but lots of people have the authority to say no, and love to exercise that power.