“We Said A, the Email Says B” — What Actually Counts After a Conversation?

After a short hallway conversation. Karim and Jonas verbally agree on option A. Later, Karim sends a message with a new decision.

— Okay, we’ll do A. It’ll be faster that way.
— Okay.

A few hours later, Jonas reads: “Actually, B.” Karim sees a natural update to the agreement. Jonas starts wondering what remains of the shared memory of the first decision.

What really happened

Karim and Jonas agree on option A in the hallway. For Karim, that is sufficient because he treats conversation as a live process: if the situation changes, the decision can simply change too. Jonas also wants a trace that lets people reconstruct what was agreed at a given point in time. When Karim later moves to option B, Jonas is not objecting to the change itself. He is worried about something else: without a record, it could look as though Jonas had chosen A on his own. He therefore starts sending short confirmations. Karim initially hears formality and lack of trust in that behavior. Jonas sees the opposite: the note protects both sides from a later argument about memory.

What the research says

Human memory does not work like a recording. In teams, what matters is therefore not only what each individual remembers but also how the group stores and retrieves knowledge. Research on transactive memory systems shows that teams work better when members know where relevant knowledge resides and can rely on that shared system (Lewis, 2003). That research does not say every decision needs an email. It does help explain why a shared, accessible trace can reduce dependence on one person’s memory. Documentation also carries relational meaning, however: if a team has always relied on verbal agreements, a sudden “confirming this in writing” after conflict may be heard as “I don’t trust you to keep your word.” That second meaning comes from the history of the relationship, not from the text alone.

How to handle it

Agree on the purpose of notes before a conflict appears. A simple “After conversations like this, I’ll post a two-line summary so we all work from the same version” sounds very different from formal documentation introduced only after a dispute. Not everything needs minutes. It is especially useful to record decisions that change scope, timing, responsibility, or project direction. The general rule is: a written trace does not have to replace trust; it can be shared memory, provided people understand why it exists and that it serves everyone equally.

How Empatyzer and Em can help

Empatyzer can show that Karim and Jonas differ not only in communication style but also in what they consider sufficient evidence of a shared agreement. For Karim, conversation is a live process that can naturally evolve. Jonas needs an explicit trace so he can know which decision was valid at a given moment. Before they work together, Em can suggest a simple rule matched to this pair: decisions that change timing, scope, or responsibility end with a two-sentence confirmation in chat. That does not turn work into bureaucracy; it removes later disputes about memory and intention. If the team has the same gap between verbal and written styles, Empatyzer can help establish a shared standard. Micro-lessons reinforce that written confirmation does not have to signal distrust; it can be the team’s shared memory.