A lot of people use the term “risk adverse” as an excuse to never take any risks, ever, just because it’s disruptive. Let me tell you why being “risk adverse” is actually exposing you to more problems, give you tools, and help you communicate to your stakeholders when it’s time to take a smart risk.
I took a smart risk and ended up being literally clawed in the face by a wolf. I don’t regret taking the risk though, because it resulted in one of the coolest experiences of my life. There’s a bit more to the story than that, but I don’t want to spoil it. The concepts here apply very clearly to IT and to organizations that call themselves “risk adverse”. I’ll walk attendees of this session through measuring risk, identifying worthwhile risks, and communicating with their stakeholders when it’s time to take one.
So many people say things like “well our org is pretty risk adverse so I don’t think I could get my boss on board with that” regarding ideas that are nearly risk free. They just know their bosses shoot down ideas that are disruptive. These folks will stand a much better chance at getting their changes accepted after this session.
Thomas Rayner is a Senior Security Service Engineer at Microsoft with many years of experience in IT. He is a master technologist, specializing in DevOps, systems and process automation, public, private and hybrid cloud, security and .NET coding. Thomas is a former 4x Microsoft MVP, Honorary Scripting Guy, an international speaker, best-selling author, and instructor covering a vast array of IT topics.