I’ve generally struggled with getting buy-in (not as a dev advocate since I just started), but just in general. I always chalked it up to the fact that I’m a minority or I may lack confidence, but after reading your article I feel like I haven't been empathetic, building desired outcomes, or looking for alignment when trying to get buy-in. Some good guidelines for me to use as I gain experience in my role as a dev advocate.
All we can do is prepare as much as possible, but at the end of the day we aren't the decision makers and sometimes we just can't get the buy-in we need. But that also doesn't have to be the end of it. You can try again for the same thing, but doing more upfront work this time. That's where the patience and persistence come into play! Sometimes is a process that could take months to years depending on the scope of the change you're trying to make.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you! Was there anything in particular that stood out to you? Any questions you were left with?
I’ve generally struggled with getting buy-in (not as a dev advocate since I just started), but just in general. I always chalked it up to the fact that I’m a minority or I may lack confidence, but after reading your article I feel like I haven't been empathetic, building desired outcomes, or looking for alignment when trying to get buy-in. Some good guidelines for me to use as I gain experience in my role as a dev advocate.
All we can do is prepare as much as possible, but at the end of the day we aren't the decision makers and sometimes we just can't get the buy-in we need. But that also doesn't have to be the end of it. You can try again for the same thing, but doing more upfront work this time. That's where the patience and persistence come into play! Sometimes is a process that could take months to years depending on the scope of the change you're trying to make.