Every organization experiences a crisis at some point. It might be a system outage, a critical product failure or a sudden and dramatic shift in customer expectations. For most, the goal is to survive it and move on. The best leaders, however, use a crisis as a moment to learn, reset priorities and strengthen the foundation for future innovation.

An IT crisis forces clarity, revealing where your systems, processes and culture are strong and where they're weak. When leaders turn that clarity into action, they accelerate ideas and changes that might otherwise take years to unfold. 

When the system breaks

Throughout my career, I have had plenty of those middle-of-the-night, panic-inducing phone calls: Everything's on fire, and we need to fix it! In financial services technology, this can mean a website crashing, payments not processing or entire purchasing systems coming to a halt. Often, it happens during the busiest seasons. 

Related:Before the next VMware: How CIOs prepare for vendor shocks

A failure in the system deeply affects people's livelihoods, from missed paychecks to disrupted access to essential funds. It's our great responsibility to get it right. When we don't, the consequences ripple through families, businesses and communities.

The moments during an incident feel chaotic, but they're also revealing. In pooling my experience, it becomes clear that most crises trace back to human error: manual processes, limited automation or overly complex systems that buckle under pressure. For example, testing practices can lag the pace of technology, and code can go into production without full validation, making teams struggle with broken test environments. They slow progress and increase risk. 

The key is to act fast. Modernize your systems, move from monoliths to microservices, and expand automated testing so teams can release smaller, more reliable pieces of code. Consider pausing "nice-to-have" projects to strengthen your foundation and protect customer experiences.

When an IT crisis exposes a weakness, resist the urge to patch the problem and move on. Do a full root-cause analysis, even if it's uncomfortable. Reprioritize the foundational work that doesn't always make headlines but makes everything else possible. This mindset of never letting a good crisis go to waste turns disruption into an opportunity. It's often the moment that teams learn the most, as well.

Clarity in chaos 

Urgency sharpens focus. In a crisis, decisions are made more quickly because we have no choice. Teams cut through noise and zero in on what matters most.

Related:Priceline CTO prioritizes engineers able to 'hold a room and a roadmap'

I've seen this dynamic firsthand. The urgency of an IT crisis helps accelerate automated testing, something many have discussed for years but don't fully embrace. The need for stability makes the path forward clear. Teams unite, rebuild processes and deliver stronger results. Customer incidents drop. Reliability improves. And we set aside time to focus on innovation rather than remediation. What's more, facing a crisis, improving the system and seeing the results raise team morale like nothing else.

As a leader, take advantage of the opportunity to capture the energy of a crisis. Ask what became possible only because pressure forced it. Then, build structures that keep that momentum going. Identify which priorities moved up the backlog during the crisis and make sure they remain priorities. 

Crises also reveal leaders. People step up, collaborate differently and find creative solutions under pressure. Those moments show you who's ready for more responsibility and who thrives and leads when uncertainty hits.

Building resilience from the rubble 

When the dust settles, the question becomes: now what? The goal isn't recovery, but reinvention of your reaction to a challenge. 

As leaders, we can use those lessons to reshape how our teams operate. Use the opportunity to build a culture of end-to-end ownership, where teams understand how their work connects to the bigger picture. Constantly ask "why" to challenge habits that might have worked in the past, but limit progress today. 

Related:Ask the Experts: How CIOs can identify and overcome cultural barriers to innovation

Build reflection into the process of recovering from a crisis. Hold post-crisis debriefs -- not to assign blame but to turn lessons into playbooks and build an enduring culture of constant improvement. Encourage teams to document what worked under pressure so they can apply it proactively next time. Use recognition to reinforce the behavior you want to see again. 

Transformational change takes time. It means embedding crisis-born agility into everyday behavior. When teams adopt that mindset, they innovate faster, deliver higher-quality work and build deeper trust among themselves. 

Reinvention over recovery

Crises are inevitable. What defines a lasting organization is not only how it responds in the heat of the moment, but also how it learns and adapts afterward.

Great leaders don't just rebuild from crisis. They rethink entire processes. They use disruption as data, urgency as energy and uncertainty as an accelerator of innovation.

When the next IT crisis hits your organization, look for clarity before control. Ask yourself: What is this moment teaching us? What should we never go back to doing? If you treat every disruption as an inflection point, you'll emerge stronger and more inventive every time.

When you never let a good crisis go to waste, you don't just recover -- you reinvent. 

At the end of the day, we must remember our responsibility in financial services is profound. Every system we build, every process we improve, is in service of people's financial security. Getting it right isn't just good business; it's essential to the well-being of our customers and the stability of the broader economy.

About the Author