Toll Free:
877.456.EFSI (3374)
I still remember the conversation like it was yesterday.
We were handling complex OTC interest rate swaps—high-stakes, high-maintenance, and loaded with risk—and I was walking my boss through how intensive the reconciliation process had become.
It wasn’t a complaint. Just the reality of supporting that kind of transaction: verifying details, confirming with counterparties, checking and double-checking every number.
He let me finish, then asked, “What if we didn’t reconcile them at all?”
At first, I thought he was kidding. But he wasn’t.
He was challenging the assumption behind the work. Asking if our time and attention were going to the right place. That question changed the way I approached operations for the rest of my career.
Because the truth is, good ops leaders follow the checklist. Great ones ask if the checklist still makes sense.
Static Systems Fail in a Dynamic Business
If there’s one thing managing operations teaches you, it’s that change doesn’t announce itself. It just happens.
A firm starts trading in new markets—Korea, Australia, Brazil.
At first glance, it all seems similar enough. The assets may look familiar, but beneath the surface, everything shifts: settlement cycles, time zones, compliance standards, regional idiosyncrasies.
And the systems? They don’t raise a hand. They just keep running—quietly unaware they were never designed for this new reality.
That’s the nature of financial operations.
What worked last quarter may already be falling short this quarter. And if your processes don’t evolve alongside the business, failure won’t show up as a headline. It’ll sneak in as a subtle miss—until it snowballs into something worse.
This is what makes “If it ain’t broke, don’t fix it” so dangerous in ops. Because things rarely break all at once. They erode—slowly, silently.
Spreadsheets Are Comfortable—But They Can’t Keep Up
There’s a reason so many firms still rely on spreadsheets.
They’re familiar, flexible, and probably a step up from whatever came before. They give teams a sense of control—you can build a tab for anything, copy over last quarter’s process, and make changes quickly.
But that comfort can be deceptive.
Over time, that same flexibility creates blind spots.
Versions drift. Tasks change hands without documentation. Updates live in email threads, or don’t live anywhere at all.
And when something slips—a missed deadline, a reporting error, a dropped compliance task—there’s no audit trail, no ownership, and no clarity on what went wrong.
The problem isn’t that teams aren’t working hard. It’s that the system wasn’t built for visibility, accountability, or scale.
Financial operations today move too fast, and carry too much complexity, for spreadsheets to keep up. Dependencies, regulatory timelines, and ad hoc exceptions all introduce risk—and spreadsheets don’t catch what they can’t see.
And it’s not just about avoiding the big blowups. It’s the small, repeated misses that erode trust: the review that runs a day late, the NAV that’s off by just enough to raise eyebrows, the task that was assumed done because no one followed up. Each one introduces friction. Together, they undermine confidence.
True operational control means knowing what’s done, what’s stuck, and what’s at risk—without guesswork.
That’s a level of oversight spreadsheets were never built to provide.
Kaizen: Making Curiosity Concrete
In operations, it’s easy to confuse consistency with control. If reports are going out, deadlines are being met, and no one’s raising alarms, it’s tempting to believe everything is fine.
But I’ve learned that calm often masks slow-moving problems.
That’s why I talk about curiosity—not as a soft concept, but as a core leadership trait.
Being curious means asking: What are we doing out of habit? What no longer makes sense? What changed that our systems didn’t catch?
For me, that philosophy took shape through a concept called Kaizen—a Japanese term for continuous improvement.
I was introduced to it by a former colleague who had worked in Japan and brought it back to our team. The idea isn’t to blow everything up, but to build a habit of making small, thoughtful improvements over time.
In ops, that means tightening handoffs, systematizing close calls, and refining workflows based on what actually happens—not what we hope happens.
The firms that embrace this mindset don’t just reduce mistakes. They build cultures of operational resilience. They stay nimble, improve faster, and empower their teams to shape how the business runs.
Building Systems That Learn
At the hedge funds where I ran operations, we had a rule: every near miss was a learning opportunity. If something almost went wrong, we talked about it. What failed? What didn’t catch it? What needed to change?
That approach made us sharper. We didn’t eliminate all risk—but we caught problems earlier, responded faster, and improved with each cycle.
Most ops tools are built to track work. But tracking alone isn’t enough. You need a system that helps you spot trouble early, investigate why it happened, and then lock in the fix so it doesn’t happen again.
That’s what spreadsheets—and even most stitched-together systems—don’t offer. They’re passive. They record what happened. But they don’t help you learn from it.
In operations, the best procedures aren’t handed down. They’re earned. Built from experience. Refined through iteration.
And they only stick if your system helps you build on them.
Because in operations, the most valuable processes aren’t the ones that were handed down—they’re the ones you build through experience.
Final Thought: Stay Curious
If everything looks calm right now, I hope it is. But in ops, quiet can be misleading.
Ask your team what still feels fragile. Ask yourself what’s changed in your business—and whether your systems are keeping pace.
Build the habit of continuous improvement into the culture.
Because the biggest risks in operations aren’t always what you can see. They’re what’s quietly eroding behind the scenes.
And the best ops leaders aren’t the ones who wait for the fire.
They’re the ones who spot the smoke early, ask better questions, and build systems that get stronger over time.
**********
Frank Caccio is the founder of OpsCheck.com, a platform purpose-built for financial firms to gain the visibility and oversight needed to prevent operational errors. Connect with him on LinkedIn here.