When Work Gets Stuck

Confusion often begins before the work itself.

When people are not clear about what they are trying to achieve, even a fairly straightforward problem can become difficult.

Take a project review where the customer wants a committed launch date.

Sales wants to protect the relationship. Product wants to preserve what was promised. Engineering wants more time to reduce risk.

Everyone is being reasonable.

And yet the discussion can go around in circles for an hour because each person is solving a slightly different problem.

Sales has a simple ask. Keep to the client commitment.

The engineering team is asking, what can we safely deliver?

And the product team is asking, how much of the original promise can we preserve?

The problem is not necessarily the launch date.

The problem is that no one has agreed on what the discussion is actually trying to achieve.

Suppose the purpose is made explicit:

We need to give the customer a commitment we can actually keep.

Now the conversation changes.

Sales can explain what the customer really needs. Engineering can say what is realistically possible. Product can decide what scope may need to change.

The same team. The same constraints. But now they are solving the same problem.

I have seen this often enough to believe that when a discussion keeps going in circles, it is worth stopping and asking one question before adding more analysis:

What exactly are we trying to achieve here?

Sometimes the problem is not that the answer is difficult.

It is that everyone is answering a different question.