Cold Open — The Hook
There is a debt sitting on your organization's balance sheet that no accountant will ever find. It doesn't show up on the P&L. There's no line item for it. But you pay interest on it every single day — and I can prove it to you in the next fifteen minutes.
I call it cognitive debt. And I believe it is quietly killing more organizations than bad strategy, bad markets, or bad hires combined. If it's not killing yours, it's the single thing standing between you and your next stage of growth.
Now, before we go further — I'm not a neurologist. I'm not a psychologist. But here's the thing: I don't know how to do a valve adjustment on my Honda Pilot either, and I drive it every day. You don't need a medical degree to understand the basics of the machine you operate every waking hour. And the biggest blind spot I see in leaders — after four decades of building companies, software teams, and sales organizations — is that they never think about the brain. Not their own. Not the brains of the people they lead. And you cannot lead what you don't understand.
So let me take you into a conference room.
Part One — What I See in the Room
As a consultant, my work usually starts the same way: I sit in a meeting. Conference room, Zoom, doesn't matter. Engineers, marketing, sales, the leadership team. Someone's running it, someone's taking notes, there's an agenda. What did we get done? Are we on track? Completely ordinary. Nobody in that room thinks anything is wrong.
That's exactly the problem. They've stopped seeing it. I haven't. And there are four things I notice every single time.
The first thing: most people are not present. Physically, they're in the room. Mentally, they're somewhere else. One person is on their phone. One is finishing a conversation from an hour ago. One is answering a question from the previous meeting — this is the first time these two people have connected all day, so the last meeting is invading this one. The brains are halfway in attendance. Before a single agenda item comes up, this meeting is already failing — because six people arrived at six different starting lines, and nobody noticed.
The second thing: the information is being captured everywhere and nowhere. One person types notes into a laptop. One writes in a notebook. One writes nothing and is betting everything on memory. There's a spreadsheet on the screen that says a project is "on task" — but the room quietly knows it's a five out of ten. Ownership is assigned to a team, not a person. And I'll tell you right now: a team owning a task is nobody owning a task, wearing a group costume.
There is no central area of truth. Which means by Friday, this one meeting will exist in six slightly different versions — and every one of those notebook people will sit at their desk tonight like an archaeologist, trying to reconstruct what actually happened from their own handwriting.
The third thing: everything is 80% done. Progress seems to be happening, but nothing crosses the finish line — because there is no definition of done. Now, my software background is showing here, because engineers solved this. In software, a feature isn't done when the code is written. It's done when it's tested, reviewed, documented, and deployed. There's a checklist. Outside of software? "Done" is a feeling. And here's the cruel part: that last 20% is where all the ambiguity comes due at once. The unrecorded decision. The assumed ownership. The scope nobody agreed to. Things aren't 80% done. They're 100% done — to a definition nobody ever wrote down.
And the same blockers keep coming back. As Yogi Berra put it — it's déjà vu all over again. Same obstacle, same conversation, next month. Listen: a blocker you've hit twice isn't an obstacle anymore. It's a feature of your system that nobody has named.
The fourth thing is what's happening in my head while all of this unfolds. I'm watching the person whose presence appears to raise the room's stress — the one who walks in and people brace. And I'm watching the person who walks in and shoulders drop, and people actually think out loud. Two people, same title maybe, opposite effects on the room. In ten minutes I can get a rough sense of an organization's cognitive climate by watching how people respond to one another.
I notice someone asking a clarifying question about a task that was supposed to happen last week — and the answer takes thirty seconds. That question sat unanswered for seven days. The clarity was free. The delay cost a week.
And then I do the quick math. Eight people in the room, call it a hundred dollars an hour each. That's an $800 meeting — wholesale. But retail? Loaded cost, opportunity cost, all the work those eight people are not doing right now? That meeting cost $2,400. And we got five hours of collective work out of a meeting that needed to produce ten.
Was it worth it? Nobody's asking. Because nobody can see it.
Part Two — I've Seen This Pattern Before
Now here's why I recognized what I was looking at, when the people living inside it couldn't.
Years ago I put together a startup in the fintech space. As we grew, the database underneath us turned into a spaghetti mess — so many tables wired into each other that nobody could touch one thing without breaking three others. My team was living in panic mode: fixing bugs, keeping the system alive, spending more time deciphering the past than building the future. Eventually I brought in a new team and we rebuilt it from scratch.
Software engineers have a name for what I was paying off. They call it technical debt — a term coined by a programmer named Ward Cunningham back in the early nineties. And the genius of the term is the financial metaphor. Debt isn't bad. Businesses borrow every day to build factories and fund growth. Debt becomes dangerous only when it's invisible — when the interest compounds faster than the repayment and nobody is tracking the balance. Every shortcut my developers took — duplicate the code, skip the documentation, patch it and move on — was a rational decision that borrowed complexity from the future. And the future always collects.
Here's the part most people miss: that debt existed for decades before the term did. Engineers felt the drag every day, but "the code is getting messy" sounds like a craftsman's complaint, not a business problem. They couldn't get budget for it. Then Cunningham gave it a name executives could reason about — debt, interest, repayment — and suddenly the invisible frustration became a manageable liability. Naming it was the first repayment.
So I paid off my technical debt. Then I moved from the startup world into the enterprise world — a thirty-five-million-dollar software budget, hundreds of engineers across multiple countries, outside consulting firms, the works. And I watched the same disease reappear in a second host.
The spaghetti wasn't in the database anymore. It was in the tools. We had teams that lived on Microsoft Teams and hated Slack. We had teams that lived on Slack and hated Teams. We had Jira, Confluence, Wrike, Zoom, email chains, Salesforce notes — and here's the punchline: everything gravitated back to a spreadsheet. Thirty-five million dollars of systems, and the actual database of record for that organization was Excel. Nobody decided that. It just accreted — one reasonable decision at a time, exactly like the spaghetti tables.
I was watching technical debt happen to people.
Part Three — The Day My Own Brain Defaulted
But I didn't fully get it until it happened to me.
Understand my situation at the time. I'm on Zoom and Teams calls from seven in the morning until nine at night. I'm hopping on planes, working with software teams in different countries. And I'll be honest with you — I've always had a big engine. High capacity. I could hold a lot in my head, and I was proud of that.
One day I hop into the next meeting ready to wing it — because winging it had always worked. Except my mind was still running the list from the previous meeting, and I'm sitting there trying to remember what this meeting is even for. And it showed. I was embarrassing the person who had set up the meeting — in front of his people. He ended it, sent everyone out, and laid into me. And here's what I want you to notice about what happened next, because this is the whole lesson in one moment:
I felt flooded with stress. My memory faltered. I got tongue-tied. The high-capacity engine I'd relied on my whole career seemed to go offline in the exact moment I needed it most.
It scared me. It scared me enough that I talked to my doctor about it. I told him I was worried about my brain.
He laughed.
Now, my doctor is not an ordinary man. Before medical school, he did the mathematics on the heat shielding for the space shuttle re-entry. PhD in thermodynamics. A literal genius. And he tells me this story. He says: "Jim, I was the best man at my brother's wedding. And I have no recollection of it. None. I know I was there because I'm in the pictures."
The wedding fell in the middle of his residency — in one of the worst crime areas in America, in the early eighties. Gunshot victims coming into the ER, life-and-death decisions all day, understaffed, under-budgeted. Sustained stress, around the clock, for years. He explained that high stress can interfere with access to memory; that experience did not imply a lack of intelligence, character, or commitment.
Sit with that. A brain that could do the math to bring a space shuttle safely through re-entry did not retain his own brother's wedding. Research suggests that sustained stress may impair how memories are encoded or retrieved. The point is not a diagnosis. It is that cognitive capacity can change with conditions.
And driving home, it clicked into the thing David Allen had been saying for twenty years in Getting Things Done: the mind is for having ideas, not holding them. The brain is a brilliant processor and an unreliable storage device — and under stress, it isn't even a reliable processor.
Now run that back through the conference room. Meetings conducted under sustained stress — deadline pressure, interpersonal tension, people juggling three projects in their heads — may make it harder for participants to encode and retrieve what was decided. Yet we run our companies as if hundreds of stressed human brains can serve as the database for thousands of commitments spread across a dozen disconnected systems.
That's when the two wires touched. The spaghetti database. The thirty-five-million-dollar tool sprawl. The six versions of Friday's meeting. My own brain going offline. It was all the same thing.
Cognitive debt: the accumulated gap between what your organization collectively knows, and what any of your people can actually access, trust, and act on.
The decisions made verbally and remembered differently. The ownership that was implied but never explicit. The context locked in one inbox, one notebook, one head. And the trust — because when people don't understand how each other think, every handoff leaks, and even well-preserved information gets misread. Your company hasn't gotten less intelligent. Its intelligence has become fragmented — and reconstruction is the most expensive line item you've never seen.
Part Four — Why AI Makes This Urgent
Now, here's why I'm making this video now, and why this can't wait.
My first instinct, after that conversation with my doctor, was: how can AI solve this for me? Finally — a technology that could actually be the trusted external system David Allen described, at organizational scale. A memory that doesn't flood with cortisol. A record that doesn't fragment into six versions.
And that instinct was half right. Here's the half that keeps me up at night.
AI is an amplifier. It makes your organization more of what it already is. Hand it to a company with clear decisions, explicit ownership, and durable context, and it compounds that clarity into extraordinary leverage. Hand it to an organization already drowning in cognitive debt, and it amplifies the debt — more documents nobody reads, more summaries of meetings nobody aligned on, more versions of reality generated faster than anyone can reconcile them.
Think about what AI actually changes. Output becomes abundant. The cost of producing a report, a plan, an analysis is collapsing toward zero. You know what does not become abundant? Shared understanding. Knowing which report reflects the actual decision. Which plan is current. Which owner is real. When production is cheap, coordination becomes the constraint. Your bottleneck was never how fast your people could work. It was how clearly your people could think together.
Same amplifier. Two completely different outcomes. And the fork in that road is whether you've paid down your cognitive debt — before you pour AI on top of it.
Part Five — The First Repayment
So what do you do about it?
Remember the technical debt lesson: engineers couldn't fix the problem until they could name it. The name came first. Then the budget, the attention, the discipline. Naming it was the first repayment.
That's where you are, right now, with cognitive debt. The drag is real, the symptoms are everywhere, and it's being mistaken daily for a communication problem, a tooling problem, a talent problem, or a "we just need better meetings" problem. You keep treating symptoms because nobody has named the pattern. Well — now you have the name.
And once you have it, the path gets surprisingly tractable. Decisions that are durable — written, findable, one version. Ownership that is explicit — a name, not a team. Context that outlives the meeting — organizational memory that doesn't live in anyone's skull. And trust — the relational infrastructure that keeps clarity from leaking out of every handoff. And underneath all four: leaders who understand that stress can affect memory, fragmented attention can affect thinking, and a steady presence can help people think together.
You don't need to be a neurologist. You need to know how to drive.
Close
So here's what I want you to do this week. Sit in one meeting — one — and don't run it. Just watch it. Count the brains that are halfway in attendance. Count the capture systems. Ask who owns each thing that got decided — a name, not a team. Then do the math on what that hour cost, wholesale and retail.
You'll see it. And once you see it, you can't unsee it — and once you can name it, you can fix it.
If you recognized your own organization anywhere in this video — the meetings, the drift, the six versions of Friday — take the assessment or read more about Jim's background. That conversation is where repayment begins.
I'm Jim Koetting. Your organization isn't broken. It's in debt. Let's pay it down.