The recap tax
A meeting is booked for half an hour and starts doing its work at about minute nine. The nine minutes before that go on getting five people to the same place: what was decided, what has changed since, why the date moved, who the new person is. Nobody planned those nine minutes. They are on no agenda and never have been.
We have used the phrase recap tax before without ever taking it apart. Here is the version worth arguing about. The cost of re-explaining is not small, it is not spread evenly, and it is not really a time cost at all. It is charged in three places, and none of them appears in anybody's calendar under its own name.
Where the bill actually arrives
The first place is the opening of other meetings. Not a meeting about the project — every meeting that touches the project, each one paying a few minutes to bring whoever is furthest behind up to the line. Twelve meetings a week, a handful of minutes each, and it never shows up as anything because it is always the smallest item in the room.
The second is the interruption. Two minutes at somebody's desk, a message that begins with an apology, a question asked in the corridor because the corridor was where you met. This is the most expensive form the tax takes and the least visible, because the person paying it is not the person who called the meeting.
The third is the document somebody writes to stop the first two happening. That is not a refund. It is a third payment, made by the same person, and it starts going out of date the afternoon it is published.
| Who needs bringing up to date | What they are actually missing | What it costs, and who pays it |
|---|---|---|
| The person who joined in June | Not the facts. The order things happened in, and which of them were arguments | Two hours of the one person who was there for all of it, taken in fifteen-minute pieces |
| The person who has to approve it | Why the obvious cheaper option was turned down in April | A meeting that exists only to hold a decision a second time, with the same people in it |
| The person doing the work | A constraint that was mentioned once, out loud, and written nowhere | A fortnight, found out about at the end of the fortnight |
| The person who was in every meeting | Nothing at all. They are the archive | Their week, in interruptions, which is the most expensive way to buy anybody's attention |
Every retelling is an edit
A recap is not a copy. It is a compression, performed at speed, by somebody who has a view about how it should come out and forty seconds to say it in. Things drop off: the objection that was raised and answered, the option that nearly won, the fact that two people are still unhappy about it. What survives is the conclusion, stated more firmly than it was ever held.
Three hops of that and a team is working from a version nobody in the original room would have signed. The dangerous part is not the drift; it is that a drifted account and an accurate one arrive in exactly the same form — a confident sentence, in a colleague's voice, with no way to tell which one you are hearing.
It gets worse because a decision is rarely one conversation. It is the residue of six: an objection in March, a constraint that came from finance, a customer call that changed what the thing was for, two approaches that were tried and dropped. All of that has to fit into the sentence somebody says in a corridor, and the sentence is the only part that travels.
The tax is regressive
The charge does not land evenly, and it does not land randomly. It lands on whoever holds the most context, because they are the only person who can settle the question, and it reaches them by interruption. The better somebody's grasp of a project, the more of their week goes on reading it back to other people. You are taxing the thing you most wanted more of.
At the other end it is quieter and worse. Somebody new works out within a fortnight that questions cost a colleague something, so they start rationing them. They ask the cheap ones, guess at the expensive ones, and a guess does not announce itself as a guess. You meet one of them six weeks later, in the work, and it looks like carelessness when it was really thrift.
When the question has somewhere else to go
The fix is not a better document. It is that a question about the past stops having to be addressed to a person. Ask Ona reads across the conversations a team has recorded and hangs every claim it makes on the meeting that produced it, so somebody who was not there can read the moment itself instead of taking a colleague's word for what happened in it.
Three things move at once when that is true. Whoever is new stops rationing, because asking is now free for everybody. Whoever was in every meeting stops being the interface to their own memory. And a claim about what was decided becomes checkable, which changes how carefully people make them.
None of that works on meetings nobody kept. The input is ordinary recorded conversation: the planning session, the review, the call where the date moved, each one arriving as a transcript with a proportional summary and the commitments named separately, which is the whole of what Meeting Notes asks of you. Deciding which meetings are worth keeping is the only real setup there is.
Two weeks of counting, then one change
- Note the minute each meeting starts workingTen working days, one number per meeting: the point at which the room stopped catching up and started deciding. You are not measuring anybody's performance. You are finding out the size of a bill nobody has ever seen written down.
- Write down the three questions you answer mostEverybody who holds context has three. Why is it built that way, what did we agree with them in the spring, who owns this now. If you cannot name yours by Wednesday, you are not the person paying this tax and somebody on your team is.
- Record the meetings where those answers get givenNot everything. The conversations where the three questions are actually settled, which is usually a planning session, a review and whichever call the client is on. Four a week is plenty to start with.
- Put the question to the record before you put it to a personMake it the house order, yourself included. If the answer is not there, you have learned something specific: that conversation was never captured, or it never happened out loud at all.
- Cancel one recurring update and see who complainsThe weekly meeting that exists to keep everyone current is the tax institutionalised. Drop it for a month. If nobody notices, you have your answer; if two people do, you have found out exactly who was being served by it, which is worth a month on its own.
A handover is the same bill, paid at once
When somebody leaves, an organisation settles the whole balance in a fortnight. Everything that was only ever in one head has to be moved into other heads, through a series of meetings booked for exactly that, by a person who has already started thinking about somewhere else. What actually transfers is the tidy version, because a tidy version is all that fits. For what a full week of this looks like from the other side of a leadership job, read Ona for business leaders.
I worked out that four hours of my week was answering the same three questions for different people. It was not the four hours that bothered me. It was that every answer was slightly shorter than the last one, and after a while I was not sure which version was true.
Oskar B., Head of Operations, veterinary group
The parts of the bill that stay
A record only holds conversations that were recorded, and a good number of the conversations that most shape a leadership week should not be. The one about a person. The negotiation where somebody is deciding whether to trust you. The call where a colleague tells you something before they have decided what to do about it. Recording changes those, sometimes for the worse, and the right answer in several of them is to leave the room unrecorded and carry it yourself.
A decision that was never said out loud is not in there either. Plenty are made by three people agreeing quietly and everyone else declining to object, and a record of the meeting will show the topic being raised, discussed and moved past. It is not a decision log. It knows what was said, not what carried.
Transfer is also not alignment. Somebody can read the answer, understand it completely and still not be with you, and cutting the recap does nothing about that gap. A team that is well informed and unconvinced is a specific and quite common failure, and it is usually caused by somebody deciding that the informing was the whole job.
And the record is only as complete as what people have chosen to put into it. Nothing you record is visible to anybody else until you share it. Admins are no exception: what a workspace shows them is the set of meetings its members have deliberately shared, and nothing behind that. It is the right default and it has a consequence worth stating plainly: a team memory is an opt-in artefact, and the conversations nobody shares are exactly the ones that will be hardest to ask about later.
Before you cut a meeting
Partly, and the two are not in competition. A written decision record is better than a recording for anything that needs to be found by a stranger in two years.
The trouble is who writes it. Documentation is authored by the person with the most context, which is the same person the interruptions are already aimed at, so it is a fourth payment rather than a refund. Record the conversation and the writing becomes optional rather than load-bearing.
Less than you would think, because the tax is charged on the conversations that were never captured rather than on how they happened.
What matters is that the four or five conversations a project actually turns on get kept in the same place, whichever surface they happened on. A planning session in a room and a review on a call are equally answerable if both were recorded and equally absent if neither was.
Some will, for a fortnight. It settles once the novelty does, and the behaviour it replaces was not attention either — it was people typing while trying to listen.
If it does not settle, that is worth treating as information about the meeting rather than about the recording. A room where nobody needs to follow what is happening did not need all of those people in it.
Hand the next recap to the record
Record the four conversations your project actually turns on this month, and send the next question about them to the record before you send it to a person.