Risk Matters
I started my “professional” career in a financial services firm that focused on risk.
Risk mitigation was a 24-hour 7-day-a-week job for everyone there. It didn’t need someone shouting it, the idea was in every decision we made.
It saved a lot of energy.
As I moved into the product space in tech, I noticed that rigor was missing.
When teams talk about innovation, they often hold different ideas of how much risk they each can take.
I saw teams often started projects without clearly defining what risk meant. This absence of discussion meant that teams left a lot of possibility on the table. With individuals assigning themselves as “risk mavericks” or “risk mitigators” different camps would develop. Then, based on that identity, teams would waste time and resources fighting proxy wars around the idea of risk without explicitly calling it out.
It’s frustrating, and it can clear itself up by thinking about the following prompt:
How might we understand our tolerance for risk and define it before we begin work?
Make sure you revisit it on a regular basis. Projects are complex and will slip away if you start to assume rather than verify.
