Observe Before You Interpret

In a professional conversation, you rarely receive raw data for long. You see a colleague look down, hear a pause, and your mind rapidly supplies an explanation: they dislike the proposal, they are hiding something, or they have stopped listening. That mental shortcut can be useful as a hypothesis, but it becomes risky when you mistake the hypothesis for an observation. In this lesson, you will practise treating behaviour like a field researcher: record what happened first, then develop several possible explanations.

You are observing a procurement meeting between a Belgian manufacturing company and a German software supplier. The supplier presents a revised annual support fee after the buyer requested additional implementation coverage. During the first ten minutes, the procurement director sits upright, keeps her notebook open, asks short factual questions, and frequently looks between the supplier and her finance colleague. When the revised fee appears on screen, she stops writing, presses her lips together briefly, leans back, and asks, “Is that the best commercial position you can offer?” The finance colleague turns his laptop slightly toward himself and begins typing while the legal adviser asks for the termination language.

A careless summary might call the buyer resistant, the finance colleague disengaged, and the legal adviser hostile. A disciplined summary would preserve the sequence: the fee was displayed; the director stopped writing and leaned back; her wording shifted to a question about commercial flexibility; the finance colleague changed his laptop orientation and typed; the legal adviser introduced termination language. Several explanations remain possible: the price may exceed an internal threshold, the team may be checking approval requirements, or the group may simply be moving to its standard contract review. The next professional move is to clarify the decision process rather than declare what anyone “really thinks.” See how this principle plays out in practice: Body Language in Negotiations: Reading the Table in B2B Deals.

Use language that a camera, audio recording, or neutral colleague could verify. Prefer “looked down at the contract for two seconds” over “lost confidence,” and “waited before answering” over “was evasive.” Include the speaker’s exact words when possible, because wording and timing can change the meaning of a physical cue. Also record what you did not observe: for example, “No raised voice, interruption, or attempt to end the meeting was observed during this sequence.”

Suppose the procurement director leans back immediately after the fee is shown. One hypothesis is that the price has created discomfort; another is that she is leaning back to see the slide more clearly; a third is that she is making space to consult her colleagues. These hypotheses lead to different actions, which is why premature certainty is costly. A neutral question such as “Which part of the revised proposal would you like us to unpack first?” tests the situation without forcing the other person to defend an accusation.

After the interaction, you may form a provisional hypothesis, but label it as provisional and show the evidence beneath it. For example: “The fee appears to have become a point requiring internal review because the director stopped writing, leaned back, and asked about commercial flexibility immediately after it was shown.” This is stronger than “The director rejected the fee,” because it describes the observable cluster and limits the claim to what the evidence supports. A good hypothesis also identifies what would change your mind, such as the director later approving the fee after confirming implementation coverage.