The Cost of Forgetting: What Lost Decisions Do to a Company

Every company measures the cost of meetings. Salaries per hour, times attendees, times duration. There are calculators for it.

Almost no company measures the cost of what happens after the meeting: the decision that was made, agreed on, and then quietly forgotten. That cost is larger, and it compounds.

Where Forgetting Costs Money

A mid-size company runs thousands of meetings a year. Decisions are made in nearly all of them. Then the meeting ends, and the decision's survival depends on someone's notes, someone's memory, or someone's Slack message. Here is where the losses actually land:

Re-litigated decisions. A question that was settled in March gets reopened in June because nobody can point to where it was decided, by whom, or why. The second discussion costs the same hours as the first, and often lands on a different answer, which resets everything downstream. If your leadership team re-decides even two settled questions a month, that is a full working week of senior time per quarter spent producing nothing new.

Handovers that lose the "why." An employee leaves or changes roles. Their documents transfer; their context does not. The successor inherits conclusions without reasoning, and either follows them blindly or redoes the thinking. Studies on institutional knowledge loss put the cost of a departing knowledge worker at a meaningful share of their annual salary, most of it context rather than files.

Repeated discovery. A team spends a week evaluating a vendor, a market, or a technical approach. Eighteen months later, another team does the same evaluation from scratch, because the first one lives in a slide deck nobody can find, if it was written down at all. The company already knew the answer. It just could not retrieve it.

Disputed agreements. "That is not what we agreed", said by a customer, a partner, or another department. Without a record, the dispute is settled by whoever is more senior or more insistent, not by what was actually said. Sometimes that costs goodwill. Sometimes it costs the contract.

Slow onboarding. New hires spend their first months reconstructing context that exists only in colleagues' heads: why the pricing is structured this way, why the product does not do X, what the customer said last quarter. Every question interrupts someone senior. Multiply by every hire.

None of these show up as a line item. All of them show up in the P&L, disguised as "slow execution."

Why Notes Don't Fix It

The standard answer is discipline: take better notes, write summaries, keep the wiki updated. It fails for a predictable reason: note-taking competes with participating. The person writing is only half in the conversation, and the notes capture what they thought mattered in the moment, not what turns out to matter later.

Notes also lack the property that makes records trustworthy: evidence. A bullet point saying "agreed to proceed with option B" cannot answer the follow-up questions: who agreed, with what conditions, what was the objection that almost won. When notes are challenged, they lose, because there is nothing behind them.

What an Auditable Company Record Looks Like

The alternative is to treat conversations the way finance treats transactions: everything recorded, structured, and traceable to the source.

In practice that means every meeting produces, automatically, a record with three layers: a structured summary (themes, decisions, owners, action items); a full transcript with speakers identified; and the original audio, so any disputed point can be checked against what was actually said.

The transcript makes it searchable. The audio makes it auditable. The structure makes it usable: you can ask "what did we decide about pricing in Q2?" and get the decision, the owner, and the moment it was made, instead of scrolling through recordings.

For European companies there is one more requirement the generic tools miss: this only works if the record is accurate in the language the meeting actually happened in. A transcript that mangles Estonian names and rounds Finnish numbers is a liability, not a record. That is why Teneks Meetings was built for Estonian, Finnish, Polish, Baltic, and Nordic languages first.

The Asymmetry Worth Noticing

Here is the strange part: the cost of forgetting is enormous, and the cost of remembering has collapsed. Ten years ago, keeping an auditable record of every meeting meant a human secretary in every room. Today it is software that joins the call.

The companies that notice this asymmetry early get a compounding advantage: every conversation they have makes the company slightly smarter, while their competitors keep paying the forgetting tax and calling it normal.

Your company is not short on knowledge. It is short on memory. See what a real meeting record looks like: send one real meeting and compare it against your notes.