top of page

When Everyone Agrees on the Problem...But Not on What It Means

Writer: Angus Gregory
Angus Gregory
Aug 12
4 min read

Updated: Oct 19

Black background with white text: "More messaging adds detail. It doesn't add momentum." Curved lines on right. Button: "Why we started building Storylines."


Recognition can create a shared point of attention without creating a shared explanation.

I was recently involved in a cross-functional discussion about why customers were not seeing the value of an offer clearly enough.

The details here are anonymised and combine elements from several recent conversations, but the pattern was consistent.

At first, the meeting felt unusually aligned.

Nobody was arguing that the problem had been exaggerated. People could point to opportunities that had stalled, customers who seemed interested but struggled to explain the value internally, and teams producing different versions of what the offer was really for.

There was a sense of relief in the room. At least we had finally named the problem. Then somebody asked a practical question.

“What are we going to do about it?”

The answers came quickly.

Sales wanted to rewrite the story... Product wanted to revisit the offer and its packaging... Customer Success wanted to improve the path from purchase to adoption... Leadership wanted clearer ownership across the customer journey.

Every response made sense from the position of the person offering it.

But as the actions accumulated, something stopped fitting.

We were still using the same words...

"customers are not seeing the value"

yet we were preparing four different change programmes.

I had assumed that agreement on the problem meant the hardest part of the conversation was over.

Listening to those actions separate made me less certain.

The meeting had agreed on where to look.

It had not yet agreed on what it was looking at.

In the previous two articles, I explored why recognition often comes before understanding, and why recognition is not the same as simplification. This discussion revealed the next complication: several people can recognise the same condition and still be preparing to solve different things.


Agreement can hide the next disagreement

When a group finally says,

“Yes, that is happening here,”

something important has changed.

The condition has become visible enough to discuss. People no longer have to persuade one another that it exists. The conversation can move beyond denial, isolated examples or the assumption that one team is simply overreacting.

That is real progress, but the meeting showed me that progress can be narrower than it first appears.

We had shared a point of concern. We had not yet shared the boundaries of the condition, the evidence behind each explanation or the level at which the problem existed.

Even the phrase

“the same problem”

may have been doing too much work.

We might have been looking at one broad condition from different positions. We might have been describing connected layers. Or the common label might have been covering several related problems that had become entangled over time.

The recognition was genuine, but the understanding was still forming.


The explanation decides what changes

This matters because explanations do not remain abstract for long.

If the problem is messaging, the reasonable response is to sharpen the proposition, rewrite the story or create better sales material.

If the problem is capability or packaging, the response may be to change the offer.

If it is adoption, attention moves toward onboarding, customer education or time to value.

If it is ownership, the organisation may redraw responsibilities or appoint someone to close the gap between teams.

None of those actions is obviously wrong and that is what makes the situation difficult.

An action can be entirely reasonable within one explanation while the explanation itself has not been examined closely enough.

If each team proceeds from its own account of the problem, the organisation can look coordinated while its work begins to separate. Different things are changed. Different outcomes are measured. Different owners are created. Each team can report progress while the original condition remains difficult to explain.

The visible disagreement may therefore arrive late... after the meeting that everyone remembers as aligned.


Difference may contain evidence

My first instinct in conversations like this used to be to find the explanation that would bring everyone back together.

I am now less certain that should always be the first move.

Sometimes one explanation will be better supported than the others. Different views are not automatically equally credible, and evidence still matters.

But the differences may also contain information that the shared problem statement has hidden.

Sales may be describing what customers fail to recognise before purchase.

Product may be describing why the offer is difficult to express consistently.

Customer Success may be describing what happens after the decision has been made.

Leadership may be seeing the absence of a shared account connecting all three.

Those may be competing explanations and they may also be different parts of a larger condition.

The disagreement can therefore be a reason to look more carefully, rather than merely a reason to force consensus quickly.

That does not mean remaining uncertain indefinitely. Organisations eventually have to decide and act.

But moving too quickly from shared recognition to a preferred explanation can close the question before the available perspectives have been understood.

The explanation that wins may simply be the one that is easiest to own, easiest to fund or closest to the authority in the room.


What the meeting had actually achieved

Looking back, I do not think the meeting had failed.

It had achieved something that may not have existed before: a shared point of attention.

The condition had become visible enough for people to examine it together.

Recognition made the next conversation possible, but It did not complete that conversation.

Shared understanding does not require everyone to hold an identical view. Different teams will continue to see different parts of the organisation, and some differences should remain visible.

But it requires more than agreement on a label.

It requires enough shared reality for people to understand what they are acting on, what remains uncertain and why a particular response is reasonable.

So when a meeting reaches the reassuring conclusion that everyone agrees on the problem, I think it is worth staying there a little longer.

Not only to ask whether people agree, but to ask what their agreement is about.

Have we agreed on what is happening?

Have we agreed on why?

Or have we only agreed that something needs explaining?

Comments


bottom of page