"I have scheduled beginning $X on $Date. Documentation:... Please remit any feedback, please and thank you"
And in the second example, unrelated to the first scenario: "I had planned to begin $X on $Date, but priorities have shifted and $X is being tabled for now. Documentation:... Please remote any feedback, please and thank you."
Don't lie or whatever, or do. I don't, but none of this feels manipulative, you're just managing your time and workload.
I may have missed some nuance.
Planning to move forward with X on $Date. Docs are here, but if you object, I totally understand and will respectfully accept your decision... though I'd hate for this to be one of those decisions that comes back to haunt you.
I think this is guaranteed to set fire to any goodwill you have in your organisation
It's still needlessly confrontational. Why are you accusing someone of failing to understand the importance of something?
Ask yourself this: do you need someone else's input? If you do not need it, you do not need to ask questions. If you feel the need to request input then in the very least you need to reach out to them in a way you value their input.
This can work for or against you. If your goal is movement, then waiting at every step for a pedantic discussion with back and forth can kill entropy.
It's not. The key difference is that you're needlessly throwing blanket accusations towards other stakeholders. Is there a way to ask for forgiveness without throwing people under the bus?
Sounds even more confrontational.
> I'm going to proceed with XYZ in N days. If any of you fucking idiots have a problem with that, then scrawl it down in crayon and flush it down the jacks, which is where you'll end up if you dare question my decisions in future.
Though I’d tone down the swearing
In that case, the most likely mismatch between the language you provided and the responses you're getting is your use of the word "considering".
If you're using it to describe the state of mind you'll be in after you fail to receive a reply, that was a mistake. It is a common connective in English that explains the reason for something:
https://www.merriam-webster.com/dictionary/considering
https://en.wiktionary.org/wiki/considering#Preposition (the preposition)
What this means is that the sentence "I will go ahead with changing X, considering you don't think it's important" is equivalent to "I've noticed that you don't think X is important, so I'm not looking for your input on my proposed change".
Learning a language well is a double-edged sword - if you look like you know what you're saying, and you make a mistake, people will assume you meant what you said. You can get away with really outrageous things if you come off as someone who can barely talk. But long after that point, there will still always be things that you never quite learned.
Maybe they were sick for a couple days. Or were recently on vacation (and you haven't been notified yet). Or dealing with some higher priority emergency. Or just genuinely missed the email for some reason (accidentally sent to spam folder?)
Also even if it is true that the recipient thinks it is unimportant, it doesn't follow that the thing should be done. If somebody sends me an email asking me whether they should swallow bubblegum (or something on that level of trivial stupidity), I'd think they shouldn't -- but probably wouldn't bother to respond, or at least I wouldn't write a lengthy email explaining why not.
I'm not even joking, these days I often scroll through social media with a mild kind of twisted amusement watching people do and believe in stupid things -- while I can reply to each of them explaining why they're wrong, it's a well-known fallacy due to xkcd386. Coworkers are admittedly "closer" and thus I probably should warn them about potential hazards, but if it's a large org and I was just among a long list of cc-ed people... I might decide not to bother.
Every time you send a message like this it's a chance to convert someone to your cause. Don't waste it!
In such case why not just ask: 'Since [reason x] I propose to do y. Please let me know if I should proceed.
If they don't find it important enough to answer, you can just follow your own good judgement, backed with a papertrail.
Still personally I find all above tactics a bit pedantic and not enough to the point... often I just communicate what I am doing and what my next intended steps are, in standups and followup meetings. Or in-between, I just send mails with stakeholders in copy. I will hear it soon enough if someone does not find it a good idea or has a better idea.
- If I don’t hear back from you in [N] days, I am not going to do XYZ, considering you don't deem it to be important.
>this cargo cult behavior of citing Amazon's leadership principles
Technical principles too: microservices. Firm size follow a Zipf distribution, thus in most case the decision was made it wasn't necessary and actually slowed down development.