- **Epistemic status:** #seedlings When requesting for a change in a company, write a proposal that details the problem, why we need to change, the solution, how to implement it, how much time and money it will cost. This will save you a lot of time negotiating with your boss while you could deliver the most value. That being said don't rush on all directions starting many initiatives making people confused and having no mass of resources on any initiative. Work out what you can reasonably ask for, develop it well, and once you've got it show the people letting them marvel. Then say, “of course, it would be better if we added…" Pretend it's not important. Sit back and wait for them to start asking you to add the functionality you originally wanted. People find it easier to join an ongoing success. Show them a glimpse of the future, and you'll get them to rally around. --- ## References - “Drunk Post: Things I’ve Learned as a Sr Engineer : ExperiencedDevs.” Accessed February 7, 2022. <https://www.reddit.com/r/ExperiencedDevs/comments/nmodyl/drunk_post_things_ive_learned_as_a_sr_engineer/?utm_source=share&utm_medium=web2x&context=3>. - Thomas, David, and Andrew Hunt. _The Pragmatic Programmer, 20th Anniversary Edition: Journey to Mastery_. Second edition. Boston: Addison-Wesley, 2019. - Watkins, Michael. _The First 90 Days: Critical Success Strategies for New Leaders at All Levels_. Harvard Business School Press, 2003.