Why your risk framework isn't changing anything
Most operational risk frameworks are built around risk categories and taxonomies. They produce registers, heat maps, and quarterly reports. They satisfy regulators and fill board packs. And they have almost no impact on how the business actually manages risk day to day.
The problem isn't the thinking — it's the starting point. When you begin with abstract risk categories, you end up with abstract risk assessments. When you begin with the actual processes your teams run, you end up with risk management that's embedded in how the work gets done.
This is the core of what we call outcome-focused risk management. Instead of asking "what are the risks in this business unit?", we ask "what are the processes that deliver outcomes, and where can they break?" The difference sounds subtle. In practice, it transforms how teams engage with risk.
A process-first approach means risk assessments reflect operational reality rather than organisational structure. It means controls are designed for the actual failure points, not the theoretical ones. And it means the people who run the processes are the ones who understand and own the risks — because the framework speaks their language.
We've seen this approach compress what typically takes six months of traditional risk assessment into ten-week agile sprints, with usable outputs delivered every fortnight. More importantly, the teams involved don't just tolerate the risk work — they find it genuinely useful.
If your risk framework disappeared tomorrow and nobody noticed, it's time to think differently about where risk management starts.
Read more