> You can very well state "I'm going to do XYZ because of [REASONS]. I'm going to do XYZ on [DAY N]. If anyone objects or has any reservations, please reach out to me."
Love this phrasing.
As other comments have mentioned, you probably don't want to go into the full depths of reasons in the email. Rather have a high level summary with a link to a long form doc or RFC. And of course, the appropriate level of detail depends on how big and wide reaching the action is.
IME you often get a response that seeks to turn it into s “conversation.” Keeping everything super vague but something that can be pointed to on s paper trail as “I expressed reservations”
Neither approval, nor disapproval just straight up quagmire.
There’s no silver bullet to getting things done successfully in any large organisation of humans.
> Neither approval, nor disapproval just straight up quagmire.
That's ok. Setup a meeting with said stakeholder, clarify your position, ask for input, and in the end ask straight up if they have any objection. Save the meeting minute and send it to everyone who attended the meeting.
They need to put up or shut up. Playing games does not work.
Objection? No. Concerns yes, as have been detailed at length. No good trying to ram it through without doing the work. We can't manage the project for you etc. etc.
There is no silver bullet. You have to treat each one in the way that works for them. Those who do it well, it's a talent.
Or have the compromising photos of the boss and copies of the bank statements so he's scared and backs you publically always and then just roll anyone who isn't effusively enthusiastic. That works too. Wouldn't recommend it.
Love this phrasing.
As other comments have mentioned, you probably don't want to go into the full depths of reasons in the email. Rather have a high level summary with a link to a long form doc or RFC. And of course, the appropriate level of detail depends on how big and wide reaching the action is.