The CTO’s Comprehension Debt
The work doesn’t disappear when you forward the AI’s summary. It moves.
It’s a Wednesday morning and I’m reading a Slack thread. I’ve been brought in fractionally to a startup whose star developer gave two weeks’ notice and disappeared. He held the entire system in his head. The founders, both non-technical, were fine with that arrangement for two years. They aren’t fine with it now. We’ve contracted a dev shop to keep the lights on. The lead engineer there is Priya. She’s trying to get her bearings.
Priya is asking the questions a senior engineer asks when she’s inheriting a system she didn’t build. Not technical questions — those she’ll find in the code. The questions she needs the founders to answer.
What part of the system has been most fragile in the last six months. Which customers are you most worried about losing if we touch the wrong thing. If we’ve got two weeks before the new onboarding flow has to ship, what should we leave completely alone. Of these product specs, which are current and which were aspirational.
These are the questions only the founders can answer. No transcript says this is what matters. That judgment was supposed to live in their heads. It doesn’t. For two years it lived in their star developer’s head. Now he’s gone.
The founders cannot answer. So they reach for the only move available to them. They paste.
A Fathom transcript from a meeting with the old dev, six months ago. A product spec document, eleven pages. A thread of customer feedback. Another Fathom recording, this time of a sales call where architecture came up tangentially. Each one prefaced with some version of “this might help” or “summary from the call attached.”
I watch Priya read each one. I watch the gaps between her messages get longer. Her questions get more specific, then more careful, then quieter.
Then one of the founders pastes what he calls a summary. It’s a Fathom AI recap of a 90-minute conversation. It is two pages long. I unmute the part of myself that’s been observing this for three days and I type: you call that a summary?
The founder is genuinely confused by my pushback. He isn’t trying to hide anything. He isn’t pretending to understand the system. He’s doing the opposite. He’s openly admitting he doesn’t, and hoping that by sending the material through AI first, the smart people downstream will be able to figure it out.
That’s the move I want to name. It’s not deception. It’s a kind of naive hope: if I compress this with a model and forward it to someone smarter than me, comprehension will happen somewhere in the chain.
It won’t. And the founders, exhausted and frightened, are about to learn this the expensive way.
A cousin of technical debt
Technical debt is the shortcut you ship knowing someone will pay interest on it later. The interest comes due in maintenance, rework, on-call pages, the engineer who spends a day decoding a hack before they can change a line.
Comprehension debt works the same way. You forward an artifact you didn’t actually comprehend. A summary. A transcript. A translated spec. A meeting recap. A Linear ticket generated from a Loom.
The artifact looks complete. It’s grammatically clean. It moves through the system like a finished thing. But it isn’t finished. It’s deferred. The work of comprehending it has been pushed downstream onto whoever opens it next, on the hope that they’ll do what you couldn’t.
The founders weren’t being lazy. They were being generous, in a strange way. They were sending Priya everything they had and trusting her to be smart enough to extract signal from it. They didn’t realize that comprehension isn’t a property of the document. It’s a property of a human who has held the document long enough to integrate it. No amount of forwarding produces that.
Why we do this
The human brain is about 2% of your body weight and burns roughly 20% of your daily calories. Thinking is metabolically expensive. The brain is wired to take any cheaper path it can find. This isn’t a flaw. It’s the same logic that makes you sit down when you don’t have to.
AI is the cheapest cognitive shortcut a knowledge worker has ever been handed. Of course we take it. Especially when we’re scared. The founder forwarding the Fathom summary isn’t lazy. He’s a non-technical founder. His company has six months of runway. His entire technical knowledge just walked out the door. And someone handed him a tool that lets him appear to still have access to that knowledge by passing the residue of it through a model.
That’s the part most coverage of AI productivity misses. The dangerous use of AI summarization isn’t by careless people. It’s by frightened people, hoping the model will hold something they couldn’t.
I notice this in myself too. The urge to paste a long thread into Claude and ask “what’s the gist” instead of reading it. The urge to skim, nod, and forward. I’m not trying to deceive anyone. I’m trying to keep moving in a job that has more inbound information than the brain I’m running on can handle. The hope that compression equals comprehension is intoxicating, and it works just long enough to bury the cost.
What comprehension actually is
Comprehension isn’t recall. It isn’t the ability to paraphrase. A high schooler can paraphrase a paragraph they don’t understand. So can Claude.
Comprehension is the act of holding an idea long enough to test it against what you already know, until you could defend it, challenge it, or apply it without the source in front of you. Three things make it real.
Attention
Slowing down enough for the words to actually land. Most “I read it” is “my eyes passed over it.” Real attention is rare and you can feel the difference when someone has it.
Integration
Connecting the new idea to what you already believe, and noticing where it doesn’t fit. This is where the work is. This is the part that costs calories. Until an idea has been integrated, you don’t own it. You’re just storing it.
Stance
Forming a position you’d sign your name to. Agreement, disagreement, doubt, a position. “I think the auth layer is going to break under load by Q3.” Not “the auth layer has scaling considerations.” One is a stance. The other is a sentence that survived a summarization pass.
When the founder pasted the two-page Fathom recap, none of these were present. The information had moved through him without leaving a fingerprint.
The literal transfer
The founder spends two minutes. Skim the Fathom recap, paste it, send. He feels productive. He’s resolving inbound requests.
Priya spends an hour. She reads the two-page summary trying to find the answer to “what should we leave alone.” It isn’t there. The summary is a Fathom AI’s best guess at what mattered in a meeting it didn’t understand the stakes of. She asks a sharper follow-up. Gets another pasted artifact. Finally messages her own engineer to start poking at the code and infer priorities from where the most defensive comments and tests have been written. The judgment she needed from the founders, she’s now reverse-engineering from the codebase. Badly.
Two minutes saved on one side. An hour spent on the other. Plus the wrong priorities she’s about to set, which will surface as a missed deadline in three weeks because the team rebuilt something that didn’t need rebuilding while the actual fragile thing sat there waiting.
Multiply this across a team. Every Linear ticket whose description was AI-summarized from a customer call the PM didn’t watch. Every code review comment that was Claude’s rewording of a thought the reviewer didn’t actually have. Every executive update where someone pasted the engineering dashboard, asked for “key takeaways,” and forwarded those upward with “fyi.”
Most of what’s currently being called AI productivity is comprehension debt. The leader who shipped it has no idea the bill is accruing. The interest is being paid two steps downstream, by people who don’t yet have the vocabulary to push back.
Where AI summarization actually works
AI summarization is genuinely useful for data. Log analysis. Regression triage. Pulling the relevant section out of a 200-page compliance doc. Surfacing the three lines in a Slack thread that contain a decision. If the next step is “trigger an alert” or “look up a record,” summarize away.
It is dangerous for judgment and collaboration. Assigning work. Giving feedback. Aligning a team. Handing off a system. Telling someone what matters. Anything where another human has to act on what you sent, and where your point of view is the value being transmitted, not the information.
The distinction isn’t AI versus no AI. It’s whether the next reader needs the artifact or needs you. Priya didn’t need a summary of the system. She needed someone, anyone, to tell her what mattered and why. When she didn’t get that, she didn’t get nothing. She got something worse than nothing. Confident-sounding paragraphs that pointed in roughly the right direction and obscured the fact that no one upstream knew what they actually wanted.
The other direction
Now look the other way.
You aren’t only the sender of comprehension debt. You’re also the receiver. You sit downstream of the CEO’s Loom that got AI-summarized into a Linear epic. You sit downstream of product’s PRD that was generated from three customer interviews the PM didn’t watch in full. You sit downstream of the board deck whose engineering priorities slide was pasted in from ChatGPT at 11pm the night before the meeting.
The CEO isn’t trying to fool you. The PM isn’t trying to fool you. They’re doing what the founders in my story were doing. Hoping that if they compress the material with a model and pass it to the smart technical person downstream, comprehension will happen somewhere in the chain.
Then you and your team are expected to build against it. You’re the rung where the debt finally has to be paid, because code doesn’t run on summaries. It runs on someone, somewhere, having held the thing long enough for it to integrate.
The harder question isn’t “what am I forwarding that I don’t understand.” It’s what am I building from that nobody upstream understood, and am I going to keep paying that interest in silence?
Three questions before you hit send. And one before you hit accept.
Before forwarding anything you generated or summarized with AI, ask:
Can I say this without the doc in front of me?
What do I actually think about it? One line of stance. Agreement, disagreement, doubt. Something you’d sign your name to.
Who is paying the interest on this?
If the answer to one is no, you don’t send it yet, you read the thing. If the answer to two is “I don’t know,” you don’t send it yet, you form a position. If the answer to three is “someone downstream, and they don’t know it yet,” you stop.
And one for everything that lands in your inbox:
Did anyone upstream actually comprehend this, or am I about to be the rung where the debt comes due?
If the answer is the second one, you don’t build from it. You send it back up. Ask the CEO what they actually think. Ask the PM what the customer actually said. Refuse to be the place where uncomprehended work gets quietly converted into committed code.
The chain
The dev shop is still working with that startup. The founders are slowly learning. Priya is slowly figuring out the priorities the founders couldn’t articulate. The bill is being paid, mostly by her. The founders are starting to see that the bill exists.
I sat with that Slack thread for three days watching two smart, frightened founders forward material they had never comprehended to a team that needed them to actually know what they were handing over. They thought they were being helpful. They were hoping. The hope was generous. It was also a fantasy.
There are three rungs in the comprehension debt economy. The originators who never understood. The forwarders who didn’t read what they passed on. The receivers who build from what they were given. Most CTOs are at least two of those three on any given week.
Audit the last three things you forwarded today. Then audit the last three things you accepted without questioning.
The bill is being paid somewhere. The question is which rung you’re on.