The constraint nobody names.

In every programme there is a constraint that everyone feels and nobody says aloud. It might be a relationship, a decision pending at the top, or a scope assumption that has never been tested. Naming it is the move.

The unnamed constraint has a particular signature. The programme feels stuck in a way that does not correspond to any of the problems being actively managed. Risks are being mitigated. Issues are being resolved. Progress is being reported. And yet the thing does not move.

The reason is that the actual binding constraint is not in the risk register. It is not in the programme plan. It is in a conversation that has not happened, or a decision that has not been made, or an assumption that everyone is holding privately and nobody has put in a room.

Finding it requires a different kind of question. Not what is the status of X but what is the thing we are not talking about that is making all of this harder than it should be? Asked genuinely, in a room where it is safe to answer, it almost always produces something.

The reason it goes unnamed is usually one of three things. The constraint implicates someone with power, and naming it feels like a career risk. The constraint requires a decision that nobody wants to own. Or the constraint is an assumption so foundational that questioning it feels disloyal to the programme's premise.

All three are real. None of them make the constraint go away. They only delay the cost of it, with interest.

The move is to name it. Not recklessly: timing, framing, and the right room all matter. But name it. A constraint named is a constraint that can be moved. An unnamed constraint runs the programme from underneath, invisible and compounding.

What is the thing your programme is not talking about?