What Did We Agree To? • The distance between a good meeting and a shared commitment

You leave a meeting thinking everyone agreed on a decision. A week later, someone acts in a way you did not expect. When you ask about it, they point to the same conversation, but remember it differently.

Neither of you thought there was anything left to clarify.

“Make this account a priority” might sound clear during the meeting. The person in charge of delivery thinks it means they can move people off other tasks. Someone else assumes current commitments stay the same and the new work will fit in. The confusion shows up when both need the same person on Thursday.

By that point, everyone has made plans based on what they thought was agreed.

Could everyone involved independently describe the same decision and what it means for their work?

Ask what changes

It’s easier to agree to a decision before anyone has to say what they will stop doing to make it happen.

When you call something a priority, it leaves the details unclear. If everyone is already busy, someone has to decide what gets delayed. If you do not talk about it, each person might make that choice on their own.

MIT Sloan’s Strategic Agility Project examines how common understanding helps translate strategy into everyday work. For an owner, a useful application is to ask people what a decision changes in their part of the business while there is still time to compare answers.

You might find out that a deadline depends on help no one has asked for, or that two people expect different work to come first. It is much easier to sort this out during the meeting than after everyone has made commitments.

Check who else is involved

The person accepting responsibility may need support from someone outside the room. Assigning an owner does not establish that the help is available.

Ask whose time or approval the work depends on. If that person has not been asked yet, decide who will talk to them and when. Do not assume they are involved until they have had a chance to consider the request.

This matters particularly when you are moving resources between teams. The person losing support needs to know what they can now reasonably be expected to deliver.

Before the meeting ends

Use the final few minutes to record:

  • The decision: What has been decided, including what will take precedence if work conflicts?
  • The owner: Who is responsible for the next step, and by when?
  • The dependencies: Whose support is needed, and have they agreed?
  • The open questions: What is still unclear, and could it affect delivery?

Ask the people responsible to describe what they will do next. You will learn more from their answers than from asking whether everyone is clear.

Send the notes to everyone affected, including those who were not at the meeting. If something changes later, update the people who are counting on it.

A short clarification can feel unnecessary when a meeting has gone well. It is worth making time for it before everyone begins work on their own version of the decision.

Source:

https://mitsloan.mit.edu/ideas-made-to-matter/a-guide-to-mit-sloan-management-reviews-strategic-agility-project

Leave a Reply

This site is not part of the Google or Facebook websites or Google Inc. or Facebook Inc. Additionally, this site is NOT endorsed by Google or Facebook in any way.
Google and Facebook are trademarks of their respective companies.