You're Pushing a Project Nobody Actually Wants to Succeed

On paper, everything looks fine.

The project has been approved. The budget exists, or most of it does. The people you need have been assigned, or something close to them has. When you present in meetings, heads nod. When you send updates, the replies are encouraging. When you ask if there are concerns, people say no, or nothing specific, or that they are confident in the team.

And yet the project is not moving. Not in the way it should. Decisions that should take days take weeks. Approvals that were promised do not arrive. Resources that were allocated seem to have been quietly reallocated. The people who nodded in the meeting are not following through on what the nod implied.

You are pushing, and the organisation is not pushing back — it is simply not moving.

What is actually happening

The most common explanation for a stalled project is execution failure — the plan was wrong, the team is underperforming, the resources are insufficient, the timeline was unrealistic. These are real possibilities, and they are worth checking.

But there is another explanation that tends to be less visible and more uncomfortable: the project is stalled not because of execution failure, but because the organisation does not actually want it to succeed.

Not explicitly. Not as a stated position. The approval happened, the budget was allocated, the support was expressed. But underneath the visible endorsement, there is a configuration of interests, relationships, and priorities that is quietly working against forward motion — not through active sabotage, but through the accumulated weight of a hundred small decisions that each seem reasonable in isolation and together amount to the project going nowhere.

This is one of the more disorienting situations in organisational life, because the normal feedback mechanisms don't work. There is no opposition to address. There is no explicit objection to overcome. There is just resistance — diffuse, distributed, and almost impossible to confront directly because it never presents itself as resistance.

Why organisations support things they don't want

To understand why this happens, it helps to understand something about how organisational approval actually works.

In most organisations, approval is not a single, unified act of endorsement. It is a layered process involving multiple people with different interests, different levels of information, and different relationships to the outcome. Some of them genuinely want the project to succeed. Some of them approved it because refusing felt politically costly. Some of them approved it because they didn't fully understand what it would require. Some of them approved it because they assumed someone else would be responsible for making it happen.

The result is a nominal consensus that masks significant underlying divergence. The project has been approved by people who are not aligned — not in opposition, but not genuinely invested either. And in an organisation, uninvested stakeholders are not neutral. They are a form of passive resistance. Every decision that requires their active participation is a decision that will be delayed. Every resource that requires their sign-off is a resource that will arrive late, or not at all.

How to read the signals

There are patterns that tend to distinguish genuine execution problems from structural resistance, and they are worth learning to read.

Genuine execution problems tend to be specific: a particular team member who is underperforming, a specific dependency that hasn't been resolved, a clear resource gap. They present themselves as identifiable problems with identifiable solutions. When you address them, progress happens.

Structural resistance tends to be diffuse: no single point of failure, just a pervasive sense that nothing is quite moving at the pace it should. Solutions to specific problems don't produce progress because the underlying issue is not the specific problem — it is the configuration of the field around the project.

Other signals include: stakeholders who are enthusiastic in meetings but unavailable for actual decisions; timelines that slip in ways that nobody seems responsible for; a sense that the project has become lower priority without anyone having said so; and the particular exhaustion that comes from feeling like you are constantly pushing against a resistance that you cannot quite locate or address.

What you can actually do

The first and most important step is to get honest with yourself about which situation you are in. If the project has genuine structural opposition — if there are people whose interests are threatened by its success, or who have decided it is not worth their investment — then pushing harder is not the solution. It is a way of consuming your energy and credibility on a project that the organisation has already, at some level, decided not to support.

The second step is to surface what is actually happening, as clearly and as non-confrontationally as possible. This usually means having direct conversations with the stakeholders whose engagement has been the weakest — not to accuse them of obstruction, but to understand specifically what is getting in the way of their participation. Sometimes the answer reveals a solvable problem. Sometimes it reveals that the project has been deprioritised in ways that haven't been communicated. Either way, the conversation produces more useful information than the silence it replaces.

The third step, if the structural resistance is real and significant, is to escalate — not as a complaint, but as a request for clarity. If the project has been approved but cannot progress without active stakeholder engagement, then the question of whether that engagement is forthcoming is a legitimate business question that deserves an honest answer from the people who approved the project in the first place.

The harder question

There is, however, a harder question underneath all of this — one that the busyness of pushing tends to obscure.

Is this project worth saving? Not in the abstract — in the context of this organisation, at this time, with this configuration of support. Some projects that are theoretically good are practically impossible in the environment they have been placed in. The ideas are right, but the timing is wrong, or the organisation is not ready, or the people who would need to change to make it work are not going to change.

Knowing when to push harder and when to let go — or to step back and wait for a different configuration of conditions — is one of the harder judgements in professional life. It requires separating your investment in the project from your assessment of its actual prospects. That separation is uncomfortable. But it is more useful than continuing to push against a resistance that is not going to yield.

A different angle on this moment

Here is something that is easy to miss when you are inside the frustration of a stalled project: the resistance itself is information.

It is telling you something about the organisation — about what it actually values, what it is actually ready for, where the real power sits and what it is protecting. That information is not available from the approved project plan. It is only available from the experience of trying to move something through the system and watching where it stops.

That is uncomfortable knowledge to acquire. But it is some of the most accurate knowledge you can have about the organisation you are working in. And accurate knowledge about the field you are operating in — however inconvenient — is always more useful than a version of events that makes the resistance invisible.

MEETONESELF is designed for exactly this kind of moment — when the field around you has become the problem, and you need a clearer view of what it is actually made of before you decide what to do next.