Open any functional specification in your estate and read it as a piece of writing rather than a piece of documentation.
It will tell you what the change does. The scope, the objects touched, the fields affected. It is precise, it is complete, and it is almost certainly accurate.
It will not tell you that somebody in the room said this wouldn’t hold up.
That isn’t a flaw in how your specs are written. It’s what a document is. Every artifact your organization keeps was composed after the decision was made, and each one records the outcome as though it were the only option on the table. The alternatives aren’t suppressed. They’re just not what the document is for.
Call it the winner’s account.
What gets deleted
Most objections raised in a design meeting are preference. Two people want to load the dishwasher differently. Either approach works, the dishes come out clean, and the argument is a tax on everybody’s afternoon. Nothing is lost when that objection disappears from the record, because there was nothing in it.
Then there’s the other kind. Occasionally somebody understands a downstream consequence the people deciding genuinely cannot see. Not because those people are careless — because it isn’t visible from where they’re standing. The design assumes master data discipline the organization doesn’t actually have. Or process consistency across sites that was never true.
Those two objections sound exactly the same when they’re raised. Same tone, same confidence, same I’ve seen this before. Which is precisely why the second one gets talked past — at the moment it’s spoken, it’s indistinguishable from the first.
The record deletes them both, equally, without knowing which was which.
And it isn’t the big decisions this happens to. Those have paper — a business case, a steering committee, somebody’s signature. Ask why the company moved a product line to make-to-order and you’ll get an answer, because the whole organization knew why at the time.
It’s the decisions one level down. The rule inside the design. The tolerance. The threshold that’s fifteen and not ten. The scoping call that put something in two plants and not the third. Individually too small to justify a document. Collectively, they determine how the process actually behaves.
Why nobody kept it
The obvious explanation is negligence, and the obvious explanation is wrong.
Think about what keeping it would have required. At the moment an objection is raised, nobody knows which kind it is — that’s the whole problem. So you can’t keep the important ones. You’d have to keep all of them, indexed and searchable, held for a decade against the possibility that one turns out to matter.
The technology was never the obstacle. Search engines have been indexing and ranking unstructured text since the nineties, and doing it well. What you couldn’t do was have one. That capability was the entire product of a company — you used theirs, or you did without.
And indexing a haystack to find a needle you can’t yet describe is not a business case anybody funds. So every organization made the same call: keep the decision, discard the discussion. Every one of them was right to. At those prices, the winner’s account was the rational record.
What changed isn’t the capability. It’s what it costs and how long it takes — and the second one matters more than it sounds.
A capability you can’t reach inside the decision window isn’t a capability you have. An answer that takes eighteen months is not available to a question being settled this week. That’s the sense in which this wasn’t possible: not that the techniques didn’t exist, but that nothing they produced could arrive while it still mattered.
Retrieval over unstructured text, by meaning rather than keyword, has gone from a program budget and a quarter to a rounding error and a few minutes. Which removes the binding constraint — you no longer have to know in advance what’s worth keeping. Every previous attempt at this failed in the same place: somebody had to decide, at the moment of capture, what would matter later. And the objection that matters is precisely the one nobody flagged, because if anyone had known it mattered they’d have acted on it at the time.
The other half arrived without anyone deciding anything. Your meetings are being transcribed. Not because it was planned — because it became free and nobody turned it off. Most organizations now generate more hours of recorded discussion in a month than in the previous decade.
And a transcript has a property nothing else in your estate has. It was produced during the decision rather than after it. What’s in there is the thinking process — how the group weighed it, what got set aside, which option somebody argued for hard and lost. Both kinds of objection are in there, still unsorted, which is exactly right, because nobody could sort them at the time either.
What it’s costing you now
This stopped being a philosophical problem about six months ago.
Point AI at a process and ask where the waste is. It’ll tell you. A mandatory field nobody needs, where everyone types whatever gets them past it. A step that exists twice. A rule that applies to one plant and nowhere else. A tolerance tighter than anything downstream requires.
The analysis is right, and it’s cheap now. That work used to be a consulting engagement. It’s an afternoon.
Then somebody has to decide what to remove, and that’s where it stops.
Because each of those was decided by a person, in a room, for a reason — and four years on, the reason is gone and the rule is still there. What happened in between is the part nobody notices. The rule didn’t fail. It degraded: right most of the time, quietly wrong at the edges, in exactly the circumstances the objection was about. Nobody raised a defect, because nothing was obviously broken. Somebody built a workaround and after a while stopped mentioning it.
Longer still and it isn’t a workaround. It’s just how the process works. There’s nobody to blame, because there’s nothing left to blame.
So you’re holding a list of inefficiencies and you can’t tell which ones are load-bearing. And the two mistakes aren’t the same size. Leaving it costs a little, forever — and that cost was absorbed years ago. Taking it out might cost a lot, on one specific Tuesday, and everyone will know who did it.
Nobody takes that trade without information. So it stays. And so does the next one, and the forty after that.
The finding got cheap. The risk didn’t.
And your content strategy won’t catch it
There’s a version of this that people think they’ve already solved.
It comes up when you stand up a data platform, or scope an AI project, or replace a document system. Somebody has to decide what gets pulled in, indexed, and governed, and what stays where it is, reachable through an API when someone needs it. Important gets materialized. Everything else stays connected.
It’s a sound model, and someone on your team will build that list well. Contracts, specifications, policies, the documentation that took years to assemble. Every one of them produced on purpose, with a title and an owner and a version.
The list will be right, and the thing you actually need won’t be on it.
Because it isn’t content. It’s what people said on the way to producing the content — a passage in the middle of a conversation about something else. It won’t come up in the scoping session. Nobody will argue for excluding it. It isn’t on the list because it was never a candidate.
Your platform will hold everything your organization decided. It just won’t hold why.
The questions nobody asked
Everything above assumes somebody objected. Often nobody did.
The room didn’t have the person who’d seen it go wrong before. Or they were two levels down and not invited. Or they were in a different function and it never occurred to anyone that this touched them. The decision was made carefully, by capable people, and the thing that mattered went unmentioned because nobody in the room knew to mention it.
There’s no erasure there. There was nothing to erase.
Which sounds like the harder problem, and in one meeting it is. Across two hundred, it isn’t — because the same questions turn out to be missing over and over. The one about who reads this downstream. The one about what happens at period close. The one about whether the data will actually arrive that way. They’re not exotic. They’re just not on anybody’s list, because no list exists.
And this is where something genuinely did change, rather than getting cheaper.
Every previous approach required knowing what you were looking for before you started. Define the schema, write the rules, pick the terms to index. The system could only surface what somebody had already thought to specify — which is precisely useless against a blind spot, because a blind spot is by definition the thing nobody specified.
You can’t index an absence. There’s no keyword for nobody asked what happens at period close. Finding it means reading a discussion, knowing what discussions like it usually contain, and noticing what this one is missing. That isn’t retrieval at any price. It’s new.
And it works off the same record. What a room did discuss is what tells you what it didn’t.
Which makes the thing worth building toward something other than an archive. Not a store of what was said — a working set of the questions this organization has learned it needs to ask, assembled from the ones it kept failing to ask.
Your senior people already carry a version of that list. They built it the way everyone builds it: something went wrong, and they never forgot to check again. It took them twenty years, and it leaves when they do.
Where to start
Ask what your transcripts are being used for. If the answer is summaries and action items, you’re extracting the part you already had — somebody was capturing that before, and now it happens by itself. Useful, and not the valuable part.
Then ask your team which workaround they’d most like to be rid of. They’ll have an answer immediately; people carry these. Ask why the underlying rule works that way, and who argued against it at the time.
You probably can’t recover that one. But the rules nobody will be able to explain in 2030 are being decided in your design meetings this quarter, and that part is still in front of you.
The reasoning that would explain the one you’re stuck with happened in a room, four years ago.
Your organization did the thinking once. It just didn’t keep it.