Two people agreed to different things

The quarterly results were dismal. The targets had been missed. Heads were bowed, eyes averted, and a mood of resignation washed over the room.

"Looks like we overestimated market demand." The product team exchanged knowing glances. They had warned about the forecasts months earlier and been dismissed.

This is the most ordinary meeting in business. Everything in it had been tracked. There were project plans, milestones, regular meetings. None of that had caught what was actually happening.

Elena watched the room and saw what was underneath.

The agreement that was never made

She saw first that marketing and development had never actually made a commitment to each other.

Marketing had heard we'll deliver these features. Development had meant we'll try if technically feasible.

Two different things had been agreed to. The gap between them widened with every missed deadline, and by the end it looked like a delivery problem, because that is what it looks like from the outside.

Drawn as a loop this is hard to do by accident. A commitment has somebody who asked, somebody who agreed, and a condition that says what will have been true when it is done. Leave the condition out and you have not made one agreement, you have made two, and nobody finds out until the work is handed over. That is the first way a promise comes apart, and the commonest.

Nobody stands outside their mood

Then she saw the moods.

David had been an engineer at the company for twenty years. He had serious doubts about the product definition and had said none of them. His previous concerns had been dismissed and he had grown hesitant to speak.

His resignation was not a mood he stepped into for the meeting. It was the air he had been breathing for months.

People do not stand outside their moods. They live inside them, and what gets said and heard is shaped by them. Marketing's defensive urgency was the air they breathed too. Everything said in that room was said into it.

So a mood on a map is not a feeling filed beside a task. It is the condition the asking and the agreeing happened under. A request made into resignation is a different request from the same words said into confidence, and it will produce a different yes.

An assessment is somebody's, or it is nothing

The third thing she saw was how the teams assessed each other.

Development saw marketing as unrealistic. Marketing saw development as obstructionist. These judgements were built on past disappointments, they shaped every interaction in the room, and nobody had said one of them out loud.

An assessment is not an assertion. The slab is cured can be checked and is true or false. Tomas is unreliable cannot be checked and is neither. It is grounded or ungrounded, which is a harder test, and most of what gets said about people at work is an ungrounded assessment wearing an assertion's clothes.

The other half of it is whose it is.

A human assessment carries weight because the person making it has something at stake. Their reputation, their relationship, their next conversation with the people it lands on. When an engineer says a system is ready for production, they are putting their name on it. The weight comes from the person, not the words.

Which is why a judgement with nobody behind it is worth so little, and why it is worth insisting on the name before anything else. A wall of criticism with no author is a mood, not a finding.

What a drawing cannot hold

Elena saw two more things, and there is no honest way to draw either.

She saw how each side listened. Development's engineering culture made certain market arguments unhearable to them. Marketing's customer focus shaped which technical explanations they could take in. Communication happens in the listener, and the speaker's real problem is what this listener can hear.

And she saw what was missing in trust. Each team doubted whether the other could do what they promised. Each doubted whether the other meant it. Each had stopped trying to understand what the other cared about. Trust needs all three, and at Synergy all three were thin.

A notation that claimed to hold those would be lying, in the same way a process diagram lies when it draws a decision box over a conversation somebody has to have.

What a map does is smaller and still worth having. It puts two people in the room with names on. It insists that somebody asked, that somebody was free to say no, and that what would count as done was said out loud. It gives the mood and the judgement somewhere to be written down where the other person can read them, which is not the same as resolving either.

Work is not a machine. It is a living system of human interactions, shaped at every turn by the moods, histories, listening and trust of the people in it.

A map is a place to put some of that down where two people can look at the same thing. The rest is still the work.