The Gap Between Discussed and Resolved

There’s a kind of team friction that doesn’t announce itself.

It shows up later. In meetings. In conversations that keep circling back to something everyone thought was settled. In the quiet frustration of having to re-cover ground that should already be clear.

Most of the time, what’s underneath it is simple: something was discussed, but not actually resolved.

And the gap between those two things is wider than most teams realize.

Here’s what makes this hard to catch in the moment.

When something gets discussed, it often feels complete. The topic came up. People responded. The conversation moved on.

From the outside, and sometimes from the inside—it looks like progress.

But discussed and resolved aren’t the same thing.

Discussed means it came up.

Resolved means people left with the same understanding of what was said, what it meant, and what comes next.

The second part is where the gap opens.

Two people can sit in the same conversation, both engage genuinely, and walk away with entirely different interpretations of what was decided or agreed upon.

Neither is being difficult.

Neither is wrong from where they were sitting.

They just heard it differently, and no one checked.

This happens more than teams want to admit. And it’s rarely because people aren’t paying attention.

Sometimes the topic is heavy enough that it’s easier to let it pass than stay in it long enough to get somewhere real. The busyness of everything else makes moving on feel responsible rather than avoidant. There’s always something else that needs attention.

Sometimes it’s because working through something fully requires more than what’s currently available—more time, energy, or capacity than the moment allows. And rather than naming that gap, the team moves forward and hopes the ambiguity won’t surface later.

It usually does.

When it surfaces, the cost isn’t always dramatic. It’s more like muddiness.

Trying to reconstruct what was actually said.

Piecing together who understood what.

Navigating the quiet frustration of feeling like you’re back at the beginning of something that should already be behind you.

Time gets spent re-clearing ground that should have been solid the first time.

And sometimes, quietly, blame.

Not always spoken. Just present in the room when things didn’t go the way someone expected, and the gap in understanding is why.

A few things worth trying if your team is in this pattern:

Pay attention to how conversations close. Not just whether they end, but how. Did people leave with a shared understanding? Or did the meeting end because time ran out or the discomfort got heavy enough that moving on felt easier?

Check interpretation, not just agreement. Agreement in the room doesn’t mean shared understanding. A simple “what did we just decide, and what does that mean for each of us?” before closing a conversation surfaces more than most teams expect.

Name the gap when capacity is the real issue. If something needs more time or energy than the moment allows, saying that out loud is more useful than forcing closure too quickly.

“We’ve started this, but I don’t think we’ve actually finished it yet” is a complete and honest thing to say.

This week’s reflection:

Think about something your team discussed recently.

If you asked each person what was decided and what it means for their work, would the answers match?

If you’re not sure, that’s worth knowing.

If this is showing up on your team and you’re not sure where to begin, feel free to reach out or book a discovery call.