Automation is reshaping model risk management, but it cannot replace human judgment. As models, regulations, and risks constantly evolve, overreliance on rigid tools can create new vulnerabilities. Effective MRM requires balance - using automation to supp
In the world of model risk management
(MRM), the word "automation" is often spoken with a sense of hope - and
sometimes, misplaced expectation.
At every conference, vendors line up
to present sleek solutions promising to revolutionize how we validate models,
document processes, and manage reporting.
And while I fully appreciate the
technological advances we are witnessing, I also recognize that automation is
not a cure-all. If anything, it introduces a new set of challenges that we, as
risk professionals, must navigate carefully.
One of the realities I have come to
appreciate over years in MRM is that change is constant.
Models evolve, regulations shift,
business priorities realign, and risk landscapes transform in ways we often
cannot predict.
In this environment, the notion that
a single tool - or even a suite of tools - can seamlessly automate large
portions of our responsibilities is optimistic at best.
The more complex and
"fancy" a tool becomes, the more inflexible it risks becoming. And in
a function like MRM, where agility and judgment are critical, that rigidity can
become a liability.
I’ve seen some remarkable technology
showcased - particularly in areas like model monitoring and documentation.
There is clear value in automating
aspects of data handling, standard testing, and tracking model performance over
time. Yet, the heart of MRM is not just about ticking boxes or generating
reports faster.
It’s about understanding risk in a
dynamic environment, where interconnectedness between models - credit risk,
fraud detection, liquidity management - can amplify vulnerabilities in ways
that automation alone cannot anticipate.
One of the biggest misconceptions
about automation in our space is that it can replace human oversight. The
reality is far different. Yes, automation can and should handle repetitive
tasks. But validation is not a static exercise.
Every model we review brings nuances
shaped by current economic conditions, regulatory focus, and emerging risks.
For example, when geopolitical
tensions rise or when markets shift unexpectedly, we cannot simply rerun last
year’s validation script and call it complete. Each situation demands fresh
judgment, contextual awareness, and a risk-based mindset that no algorithm can
replicate.
Documentation is another area where
automation offers promise but comes with caveats.
While tools can streamline the
creation and maintenance of documents, the content itself is subject to
continuous change - driven by evolving methodologies, regulatory
interpretations, and business use cases.
What we document today may be
insufficient tomorrow. Filling today’s gaps through automation only reveals new
gaps as the environment shifts.
It’s an iterative process, and
automation must be seen as a support mechanism, not a solution that eliminates
complexity.
When we speak about investing in
automation, I believe we need to ground those conversations in practicality. I
often joke - but only half-seriously - that if Excel had just a few more
advanced features, it would outperform many of the complex systems being sold
to us.
There’s value in simplicity,
especially when flexibility and adaptability are paramount. Tools should serve
us, not trap us within rigid workflows that become obsolete the moment
priorities change.
Another critical aspect often
overlooked is the role of the first line of defense. MRM does not operate in
isolation.
Any automation tool we implement will
require collaboration and input from business units. If a tool only serves the
second line, its value is inherently limited. This is why I always advocate for
solutions that deliver benefits across the organization.
Tools that enhance efficiency for
both the first line and MRM are far more likely to gain traction, justify
investment, and deliver sustainable value.
The conversation around risk-based
validation frequencies further illustrates the importance of judgment over
automation. High-risk models, by their nature, demand frequent review - not
because a calendar says so, but because the world changes rapidly.