The project where everyone had a different memory of what was agreed

The kickoff went well by every surface measure. The client was engaged, the conversation moved quickly, people nodded at the right moments. You left with energy and a sense of shared direction. No one flagged a concern. No one asked for clarification. The room had the particular warmth of a group that believed it was aligned. Then the first round of work landed and something cracked open. The client referenced a scope you did not recognize. A stakeholder mentioned a constraint that had never appeared in your notes. Someone else insisted a decision had already been made in that first meeting, a decision you had no memory of anyone making. The project had not changed. The understanding of it had simply never been the same for everyone in the room.

A brief is never a complete record of a project. It is a partial transcript of what someone was able to articulate at the moment they wrote it. Everything that felt too obvious to write down, every context the client assumed you already carried, every implication that seemed to follow naturally from what was said out loud, none of that makes it onto the page. Those gaps do not stay empty. They fill immediately with assumption and each person in the conversation fills them differently based on their own experience, their own priorities, their own version of what the project is fundamentally for. By the time the kickoff ends, every person who attended has walked away with a slightly different brief. The document everyone agreed to sign is not the brief they are actually working from. The real brief is the one living in each person's head, unwritten, unverified, already diverging.

What makes conflicting recollections so difficult to untangle is that no one is lying. Each person genuinely remembers the meeting the way they remember it. Memory does not record conversations the way a camera does. It records what felt significant, what confirmed existing expectations, what aligned with the outcome each person was already hoping for. A client who came into the kickoff wanting one thing will remember the conversation as having endorsed that thing, even if it was never explicitly said. A designer who made a quiet assumption about scope will remember the meeting as having established that scope, because the assumption felt settled before anyone spoke. The recollections are honest. They are just not the same.

The practical response is not to write longer briefs, though specificity helps. It is to treat the brief as a starting point for confirmation rather than a finished record of what was decided. After a kickoff, the most useful thing you can send is not a thank you note. It is a plain summary of what you understood to be true: the scope, the constraints, the decisions that were made, the questions that were left open. Not as a formality but as a genuine test of whether the room left with the same project. The responses to that summary will tell you more about the real state of alignment than anything that happened during the meeting itself. Silence is not confirmation. It is just silence.