Each Meeting Alone Drives Nothing

You have Copilot. You have protocols. You might write your own notes afterwards.

Good. None of it drives an outcome.

Not because the format is wrong. Copilot is not the problem. The protocol is not the problem. The handwritten notes are not the problem. They are all equally good — and equally insufficient on their own.

The problem is that each meeting is treated as complete in itself. Documented. Archived. Done.

It Is Not One or the Other

There is a false dichotomy in how we talk about meeting documentation. Copilot versus protocol. AI-generated versus human. Automated versus considered.

It doesn't matter. That is the wrong question.

The right question is: does it connect to everything else, or does it sit in isolation?

A summary sitting in isolation drives nothing. A summary that forms part of an accumulated structure — together with standup notes, phone calls, project meetings, all the other occasions you have met the same contact — begins to point toward something. It contributes to a foundation that can actually be used to drive toward an outcome.

It is not one or the other. It is both, together, over time.

What Gets Built When Everything Connects

A contact you work with appears in more contexts than a single meeting. Standups. Project meetings with four others. A phone call from the car. Three sentences in a Teams call that was really about something else.

Each occasion gives a fragment. The fragments alone are not enough.

None of these is sufficient alone. Together, the content within them forms a structure that AI can actually use — to prepare, to identify patterns, to answer the question of what you are actually trying to achieve with this contact.

It is the structure of everything, taken together, that drives toward an outcome.

The Thresholds Are Real

The structure is not equally valuable at all volumes. There are thresholds.

At the 20-plus threshold, something changes. You no longer need to formulate a well-written question. You can ask AI loosely: "What are we actually trying to achieve here, and what is stopping us?" The structure carries the answer. The prompt is barely needed.

My Own Numbers

Since 2022 I have been collecting systematically — summaries, voice notes, transcripts, preparations — from all formats, about every contact. The growth looks like this:

In Q1 2025 I had almost no preparation files. In Q1 2026 I had 39. Not because I became better at preparation — but because the structure had become rich enough for preparation to actually lead somewhere.

The framework I use to capture everything — transcripts, preparations, standups, daily dashboards, analytics — is an open framework, free to use: core-claude-skills. Not a finished system, but a starting layer for anyone who wants to build the same kind of structure.

I am not unique. I am structured. That is the difference.

Not a New Format — a Decision

The solution is not a new tool. Not better Copilot settings or stricter protocol requirements.

It is a decision about how you organise what you are already producing. Every summary, protocol and note that concerns the same contact ends up in one place. Not sorted by meeting. Sorted by contact, by what you are trying to achieve.

Loose summaries drive nothing. The structure of all meetings together can drive everything.

How many loose summaries do you have from your most important contacts over the past year?

How many of them connect?

See also: Your Meeting Summary Is Worthless (series 4) — the problem of the isolated document; Three Channels, One Place (series 5) — the infrastructure for capturing everything in one pipeline; Everything I Say Becomes Text (series 2) — the mechanism; Messy and Crisp (series 14) — how accumulated material leads to precise understanding.

The framework behind the numbers: core-claude-skills — open framework, free to use.