Meeting notes nobody reads versus a decision log people search

Meeting notes record what was said. A decision log records what was settled, by whom, and until when. Only the second is ever searched.

The pricing decision nobody could find

In March the team changed the order of two plans on the pricing page. In June a designer reversed it. Nobody could say why it had been set that way.

The notes existed. Forty sets of them, in a folder named by date, each written by whoever happened to be taking them. None had a title anyone could guess.

Four people searched for twenty minutes each and found nothing. The change went in. The original reasoning was lost, which is the normal outcome.

What the notes actually recorded

The entry for that meeting read that the team discussed pricing page hierarchy. It added that they agreed to revisit after the quarter. That is all.

That sentence summarises a conversation rather than recording an outcome. It contains no decision, no owner, and no date. Nothing in it can be acted on.

It is also, by any word count, a reasonable note. The failure is structural rather than careless. The writer did the job the template asked for.

Why attendance shapes the notes

Notes are written for people who were in the room. They lean on shared memory to fill every gap. The reader is assumed, never served.

Phrases like the usual approach or as discussed only work for someone who was present. That excludes everyone hired later, which is most future readers.

That is why notes read well in the week they are written. They read badly a year afterwards, when the room has emptied.

A decision has a date and an owner

A decision entry needs four things. What was decided, who decided it, when, and what would make it be revisited. The last item is the one teams skip.

Skipping it is how a decision becomes permanent by accident. Without a review trigger, an old choice looks like a law. Nobody dares to test it.

A trigger can be a date, a metric, or a named event. Anything works, as long as it arrives without anyone remembering. That is the whole point.

The log entry for the pricing call

The replacement entry ran to three lines. The cheaper plan went second because the trial converts better when the price appears after use. That was the reasoning.

It named the head of growth as the decider and dated it the twelfth of March. It set a review for the end of the quarter. Three fields, twelve words.

Three lines replaced a paragraph of narrative. They answered every question the June designer actually had. She found the entry in one search.

What the log left out on purpose

The log does not record who argued or how long it took. It does not record which option came second. Those belong in notes, if anywhere.

Keeping the log thin is what makes it maintainable. A log that preserves the discussion turns back into notes within a month. Then nobody writes either.

The test is simple. If an entry cannot change a future action, it does not belong in the log. Most of what a meeting produces fails that test.

Search is the only test that matters

Nobody reads a decision log from the top. They arrive with a question and one search box, usually about a feature or a price. The log is a lookup table.

Entries therefore need the words a future reader would type, not the words the meeting used. Hierarchy was the meeting’s word. Order was the searcher’s.

The March entry said hierarchy. The June designer searched pricing page order and found nothing. The wording was fixed that afternoon, and the entry was rewritten.

Two artefacts, two different jobs

Notes serve the people in the room, which makes them a working document with a short life. The log serves everyone else, indefinitely. They are not versions of each other.

A team needs both, but only one deserves a permanent home and a maintenance habit. That one is the log, because it is read years later.

Most teams keep the notes and skip the log. That is exactly backwards in cost per future reader. It is also the easier habit to defend.

The meeting where nothing was decided

After two months of logging, the team noticed something. Most meetings produced no entries at all. The weekly product call had produced two in nine weeks.

That was not a failure of the log. It was evidence that the recurring meeting had become a status exchange with a calendar invitation. Nobody had said so out loud.

They cut it to twenty minutes. They kept the log for the monthly planning call, where real trade-offs were made. Attendance at the weekly call fell by half.

How the log changed the meeting

Knowing that an entry would be written changed how people spoke. Vague agreement stopped surviving the last five minutes. Someone always asked for the wording.

The chair began ending each item with two questions. Who owns it, and when will we look at it again. Both questions took about fifteen seconds.

That removed a class of ambiguity that used to surface three weeks later. It also made the meetings shorter, which nobody had predicted. The chair noticed within a month.

The cost of maintaining both

The log costs about ten minutes per meeting. It is written by the chair rather than a volunteer, which is why it survives. Volunteers stop volunteering.

Notes still get written, but nobody edits them for posterity. Nobody is asked to tidy the folder either. The folder is now a scratchpad.

Total writing time went down. The notes stopped trying to be a record, and the log stopped trying to be a transcript. Both got cheaper.

What new joiners asked for

The first person hired after the change asked for the log in her first week. A colleague had mentioned it in passing. Nobody had pointed her at it.

She read eleven entries in half an hour. She stopped asking why the product was built the way it was. That question had been asked monthly for a year.

The log had become onboarding material without anyone deciding it should be. That is usually the sign that a document is doing real work. Nobody maintains it for that reason.

If your last five meetings produced no entry that could change a future action, what were they actually for, and who decided that?