She copies the name. That’s step one. From an email thread that is already 48 messages deep, full of attachments and conflicting notes. Then she opens the web-based screening tool-the one we paid $878 thousand for-and pastes the name. The tool screams ‘match.’ She hits the screenshot button. Opens Word. Pastes the image. Saves the document as a PDF. Uploads the PDF to the shared drive where the naming convention is cryptic and relies on a key the intern wrote down on a Post-it note back in 2018. Finally, she opens the Master Excel sheet (the one that slows the network down whenever anyone touches it) and updates cell J28.

I’m still limping slightly, which probably colors this whole reflection. I hit the corner of a coffee table this morning-an object designed to hold things, yet perfectly positioned to cause maximum, clumsy pain. That coffee table is exactly what our compliance ecosystem has become. It’s meant to support us, but its sharp, disconnected edges just cause bruises.

The Anatomy of Fragmentation

We built a Frankenstein’s Monster. Not one huge, terrifying system, but a creature stitched together from dozens of perfectly functional, small parts. We bought the screening tool because it had the best watch lists. We bought the workflow tracker because the spreadsheet was getting too unwieldy. We bought the document vault because of the new data retention policy. Every single purchase was justifiable on its own merit. Every tool solved one specific, tactical problem.

The real cost isn’t the subscription fees. It’s the data friction. Look at that single name the analyst just processed. That name existed, sequentially, in an email client, a web browser, a proprietary SaaS database, a local desktop application, a PDF file, a shared network drive, and a cloud-based Excel sheet. None of these systems natively talk to each other. We rely on the squishy, fallible organic matter between the keyboard and the chair-the analyst-to be the API connector.

The person whose job it is to ensure structural integrity is forced to manually build the bridge every 8 minutes. And every time data is copied, pasted, and re-uploaded, we introduce a risk factor: the transposition error, the forgotten step, the accidental upload to the 2018 folder instead of the 2028 folder.

The Hostile Environment: Escape Room Design Meets Compliance

This is where the world starts to resemble a poorly designed escape room. I was talking to Hayden A. about this recently. Hayden designs high-end, extremely complex escape rooms for corporate clients. His genius isn’t in creating hard puzzles; it’s in forcing the players to use disconnected pieces of information from different physical locations to unlock a single, central mechanism.

“

If the connections are completely arbitrary-like, using the color of a book on shelf A to decode a word in room B that unlocks a box in room C-the players don’t feel clever. They just feel angry. They give up because the system is hostile, not challenging.

Our compliance system is hostile. It actively discourages the user from completing the task efficiently by making the connections arbitrary and the data flow painful. We’ve become trapped inside a system we designed ourselves, forever seeking the decryption key that lies in a folder someone named “Archive_Final_v3.8.”

We chase the promise of ‘best-in-breed,’ forgetting that disparate breeds often fight fiercely when forced into the same kennel. We end up with systems that are individually exquisite but collectively dysfunctional-a set of Formula 1 tires bolted onto an off-road chassis, held together by duct tape and an analyst’s determination.

The Nervous System: From Friction to Flow

We need to stop thinking about compliance technology as a collection of specialized components and start viewing it as a continuous, unified nervous system. The data screening, the risk scoring, the document management, the approval workflow-these are not separate jobs. They are phases of a single, non-negotiable process. The moment that single name leaves the screening phase, its context, score, and associated documents should travel with it, automatically, without the need for human middleware.

The Personal Cost of Redundancy

Look, I have strong opinions on this because I have been part of the problem. Early in my career, running Risk Ops for a mid-sized financial entity, I approved the purchase of three separate due diligence trackers within 18 months. Why? Because the first one was great for supplier onboarding but terrible for transactional monitoring. The second was brilliant for sanctions screening but couldn’t handle complex beneficial ownership structures. The third promised to fix the others but was, predictably, just another silo with a better UI.

We kept layering complexity on complexity. We had three different databases holding versions of the same entity data, which meant three separate maintenance schedules, three training protocols, and, crucially, three different answers to the question: “Is this entity approved?”

Redundancy, in this context, is not robustness; it is brittle paralysis. We end up storing the same identity documentation three times: once in the initial KYC tool, once in the document vault, and once attached to the email chain confirming approval. It’s like carrying three wallets, each containing a different, slightly outdated driver’s license, just in case one is rejected. This triplicate storage exponentially increases data risk, bloats storage costs by 28%, and makes audit trails into nightmarish archaeological digs.

The same essential information-the risk profile-is being replicated, re-validated, and re-contextualized across these systems. The spreadsheet says ‘Low Risk.’ The screening tool returns ‘Potential Match (False Positive Acknowledged).’ The workflow tracker sits stagnant waiting for manual input, showing ‘Pending Approval.’ The single truth dissolves into 8 fragmented opinions.

The Clockwork Lesson: Alignment Over Parts

That reminds me of a brief, ridiculous detour I took a few years back. I got obsessed with early 20th-century clockwork mechanisms. The truly impressive ones weren’t the clocks with complex faces, but the ones with the most elegantly simple internal gears-where every piece had a clear, defined, single purpose, and they all meshed perfectly. Our modern digital compliance systems are the opposite. They are a jumble of competing gears, often spinning the same axle, occasionally colliding, and frequently stripping their teeth because the alignment is wrong.

That coffee table I stubbed my toe on? It taught me something about poor design. It wasn’t built for movement or flow; it was built for static storage, and when introduced into a dynamic environment (a person moving quickly), it became a hazard. Our legacy compliance architecture-built for static data storage and manual review-fails catastrophically when introduced to the dynamic reality of global commerce and instantaneous risk changes.

We must eliminate the manual touch points that serve only to translate information between incompatible dialects. Every single mouse click dedicated to transferring data-rather than analyzing risk-is a tax we impose on our organization for poor architectural choices made back when point solutions seemed like a smart, affordable choice. That tax adds up to significant inefficiency, maybe $108 thousand in wasted labor every year, depending on the scale.

Hayden A., the escape room designer, would never create a puzzle where the player had to physically move a clue from Room 1 to Room 8 and then back to Room 4 before they could use it. That’s bad design. It’s friction for friction’s sake. Yet, this is the environment we force our most critical oversight teams to navigate every day.

We spent years accumulating tools, each one promising efficiency, resulting in a terrifying machine whose primary output is complexity. We optimized the teeth of the gear but forgot to align the drive shaft.

We have the technology to build seamless, intelligent, unified systems. We simply lack the conviction to dismantle the scattered, patchwork monster we’ve already paid for and learned to fear.

So, the question remains, not for the analyst painstakingly copying a name into the 28th system of the day, but for the leadership: How much more friction-how many more costly, unnecessary steps-will we tolerate before we admit that accumulating solutions has become the single biggest obstacle to achieving actual, effective compliance?