The Checklist That Ate The World: Why Context Destroys Compliance

The Checklist That Ate The World: Why Context Destroys Compliance

An insider’s perspective on how rigid frameworks stifle innovation and why understanding local realities is the only true measure of success.

The shoe hit the carpet with a dull thud, and the spider-a leggy thing that had been mocking me from the corner of my desk for 14 minutes-was finally gone. I sat back, the adrenaline of the kill fading into the familiar, low-grade headache caused by my monitor’s blue light. On the screen, a 54-page PDF sat open like a digital tombstone. It was a due diligence checklist from a Tier-1 financial institution, sent to me by a project manager who sounded like he was on the verge of a breakdown. Jax K.L., that’s me, usually spends my days analyzing traffic patterns-predicting where the flow of people and machines will bottleneck-but lately, I’ve found myself analyzing the traffic jams of capital. And let me tell you, the gridlock caused by 474 redundant compliance questions is far more destructive than a four-car pileup on the M1.

🌍

ESG Impact Report

Non-fixed logistics assets, Kenya

🐎

Carbon Footprint Analysis

The Donkey

❗

Critical Deficiency

Flagged by Clarence, London

I was looking at question 124. It asked for a ‘comprehensive ESG impact report for non-fixed logistics assets’ in a region of Kenya where ‘logistics’ often means a guy with a donkey who knows which roads aren’t washed out by the rain. The analyst on the other end of the thread, a 24-year-old in a glass tower in London named Clarence, had flagged this as a ‘critical deficiency.’ Clarence wanted a carbon footprint analysis for the donkey. I wish I was joking. But in the world of institutional due diligence, the donkey must be quantified, or the $10,004,004 project dies in the cradle. This is the delusion we live in: the belief that a standardized template is a substitute for actual industry knowledge.

Standardization vs. Context: The Unseen War

Standardization is the enemy of context. We’ve built a system where the most innovative, context-specific solutions are systematically rejected because they don’t fit into a pre-formatted cell in an Excel sheet. I’ve seen projects that could literally transform the economic landscape of entire sub-regions get discarded because the local partners didn’t have a 44-page ‘Internal Diversity and Inclusion Policy’ written in perfect corporate-speak. They were too busy actually building the infrastructure to hire a consultant to write a manual about how they hire people. It’s a paradox of the modern age: we claim to want to fund ’emerging markets,’ yet we demand they behave exactly like the London Stock Exchange before we give them a dime.

The Demand

‘Perfect’ Corporate-Speak

44-Page Policy

VS

The Reality

Building Infrastructure

Actual Work

The Performance of Due Diligence

It’s a performance. That’s the thing people don’t want to admit. Most due diligence isn’t about risk mitigation; it’s about blame mitigation. If I’m an analyst and I follow the checklist, and the project fails, I’m safe. I can point to the 504 pages of documentation and say, ‘Look, I checked all the boxes.’ But if I use my brain, look at the actual traffic patterns of the local economy, and recommend a project that doesn’t fit the mold-and it fails-my career is over. So, we choose the safety of the checklist over the potential of the project. We choose the optics of legality over the reality of business. It’s a cowardly way to move money, and it’s why so much ‘impact investing’ never actually makes an impact.

504

Pages Checked

(Blame Mitigation)

0

Projects Failed

(Analyst Safe)

The Crane & The Greyscale Analyst

I remember talking to a veteran project manager who had spent 34 years on the ground in East Africa. He was sighing so loudly over Zoom that I thought his microphone was clipping. He spent 144 minutes explaining to a junior analyst why a Western metric for ‘just-in-time delivery’ was a physical impossibility in a port where the crane breaks down every second Tuesday. The analyst just kept citing ‘Section 8.4 of the Risk Assessment Framework.’ It was like watching a man try to explain the concept of color to someone who was determined to only see in greyscale. The irony is that the veteran PM knew exactly how to navigate the delays; he had built a buffer into the supply chain that was ingenious and resilient. But because it didn’t look like the ‘standard’ model, the analyst saw it as a risk rather than a solution.

34 Years Experience

Ground-level knowledge, real-world buffers

Framework cites

Section 8.4 of the Risk Assessment Framework

Killing Miracles with Jargon

This rigid adherence to templates creates a filter that only lets through the most boring, least innovative, and often most ‘corporate’ projects. The real disruptors, the ones who are actually solving problems in messy, un-templated ways, are left out in the cold. We are essentially saying that if you can’t describe your miracle in the specific jargon of a Manhattan boardroom, your miracle doesn’t count. I’ve killed spiders with more grace than these institutions kill viable projects. When the 44th revision of a debt-to-equity ratio doesn’t reflect the reality of a frontier market, you stop looking at the spreadsheets and start looking for a partner who understands the ground.

“We are essentially saying that if you can’t describe your miracle in the specific jargon of a Manhattan boardroom, your miracle doesn’t count.”

This is where the methodology of AAY Investments Group S.A. diverges from the herd. They recognize that a Kenyan supply chain cannot be viewed through the same lens as a Swiss manufacturing plant, and that bespoke consultation is the only way to bridge the gap between institutional capital and local reality.

Context is King

The Only Currency That Matters

The Road Not Taken (By The Checklist)

I often think about my work in traffic patterns. You can have the best road design in the world on paper, but if you don’t account for the fact that people will take a shortcut through a park because the main intersection is confusing, your design is a failure. The ‘law’ of the road is nothing compared to the ‘logic’ of the commuter. Financial due diligence is the same. The ‘law’ of the checklist is nothing compared to the ‘logic’ of the local economy. If you ignore the logic to satisfy the checklist, you are building a road that nobody will use, or worse, a road that leads nowhere. We are currently building a global financial system made of roads that lead nowhere, paved with 54-page PDFs.

Confusing Intersection

Design fails logic.

Checklist Logic

Ignores local economy.

Road to Nowhere

Paved with 54-page PDFs.

The Deception of ‘Perfect’

I made a mistake once, about 24 months ago. I was so focused on the data points of a project-the ‘traffic flow’ of the capital-that I ignored the human element. I told a client the project was a ‘go’ because the numbers lined up perfectly. It was the most standardized, ‘perfect’ project I had ever seen. It failed within 84 days. Why? Because the numbers were a fiction created specifically to satisfy the due diligence process. The founders had spent all their energy making the project look good on paper to get the funding, and they had no energy left to actually run the business. They had ‘checked the boxes’ so well that they had hollowed out the actual value of the enterprise. That was a wake-up call for me. Since then, I’ve been more skeptical of ‘perfection’ and more interested in the ‘mess.’

Project Status (84 Days)

FAILURE

Hollowed Out Value

Wasting Brilliant Minds

We need to stop asking the same 47 compliance questions in three different formats. It’s a waste of human potential. I think of the thousands of hours spent by brilliant entrepreneurs answering questions about their ‘5-year projected carbon offset’ when they are still trying to figure out how to keep the lights on during a power grid failure. It’s not that these questions aren’t important in a vacuum; it’s that they are being asked at the wrong time, by the wrong people, for the wrong reasons. They are being asked to satisfy a legal department, not to build a better business.

Thousands of Hours

Spent on Irrelevant Questions

At the wrong time, for the wrong reasons.

The Shoe, The Spider, and The Checklist

If we want to actually move the needle on global development, we have to empower people who have the authority to say ‘This question doesn’t apply here.’ We need analysts who are allowed to be humans rather than glorified OCR scanners. We need a system that prizes the ‘Why’ over the ‘What.’ Jax K.L. doesn’t have all the answers, but I know that if I see one more 54-page checklist, I might just lose my mind. I’d rather go back to killing spiders. At least with the spider, there was a clear problem and a clear solution. With institutional due diligence, there is only a never-ending loop of ‘Please Clarify’ and ‘Refer to Appendix 14.’

The spider’s web was actually quite beautiful, now that I think about it. It was intricate, context-specific, and built perfectly for its environment. Then I came along with my shoe-the blunt instrument of my own annoyance-and destroyed it because it didn’t fit into my idea of where a spider should be. That’s what we’re doing to these projects. We are the shoe. Our checklists are the blunt instruments. We are smashing these delicate, highly-evolved local solutions because they are ‘out of place’ according to our global templates. And the worst part? We think we’re the ones doing the cleaning. We think we’re ‘mitigating risk’ when we’re actually just destroying value.

The Blunt Instrument of Annoyance

Our checklists, smashing delicate local solutions because they’re ‘out of place’.

Looking at the Traffic, Not Just The Map

I’m looking at the smudge on the carpet now. It’s a 14-millimeter stain. It’s a reminder that sometimes, the things we try to ‘fix’ or ‘manage’ are actually things we just don’t understand. The next time a project manager tells me about a 47-point questionnaire, I’m going to tell them about the donkey in Kenya. I’m going to tell them that you can’t quantify the soul of a project with a template, and you can’t find the truth in a spreadsheet that was designed in a different hemisphere. We need to do better. We need to look at the traffic, not just the map. Because the map is often 34 years out of date, but the traffic is happening right now, in real-time, right outside our window.

You may also like...