Most of the damage done to a project comes from its own side.
Not from the vendor who underbid, and not from the supplier who missed a date. Those are ordinary problems, and there are ordinary ways to handle them.
The expensive damage comes from a department head who agrees a change directly with a developer because it seemed small. From a sponsor who promises the business a date that was never in the plan. From a committee member who approves a deliverable without reading it, because nobody else around the table looked worried. From an architect who settles a scope question in a corridor and tells no one.
Not one of those people is obstructing anything. Every one of them is trying to help.
Confusion in the Field
In the field, friendly fire is almost never about hostility. It is about people holding different pictures of the same situation.
The plan changed, and one unit was not told. Two groups were on different channels. A position was reported against the wrong reference. Nobody in that sequence wanted the outcome, and the outcome happened anyway.
The fix is not braver soldiers or better equipment. It is the same briefing, the same map, and the same signals, issued to everybody in the area, including the people who will never fire a shot.
That last part is the whole point, and it is the part organizations skip.
The One Person Who Gets Trained
Companies do buy methodologies. They pay for the licenses, the templates, the tooling, and the course.
And the course is attended by project managers.
That is the implementation. That is all of it.
The people with by far the greatest influence over whether a project succeeds attend nothing. The sponsor, the budget holder, the Steering Committee members, the department heads whose staff sit in the team. They are informed by email that the company now works according to PRINCE2, or a scaled Agile framework, or an internal method with a name and a logo, and that is where their involvement with it ends.
So the method now lives in one head in the room.
When the project manager says a change has to be assessed and priced before anyone starts building it, that sounds like process for its own sake. To everybody else at the table, it is exactly that, because nobody ever explained what it is for or what it prevents. They are not being obstructive when they push past it. They are doing what seems obviously sensible, which is getting on with the work.
And the project manager slowly becomes the person who says no.
What Half a Day Would Fix
The remedy is not a bigger training budget, and the Steering Committee does not need the five-day course.
It needs about half a day, covering four things.
What the committee actually decides, and what it only advises on. Those are different, and most committees have never been told which is which.
What tolerance means, and the point at which a decision stops belonging to the project manager and arrives at the committee. A board that does not know its own tolerances cannot tell the difference between being informed and being asked.
What happens to a change between being requested and being approved, and why that order is not bureaucracy. Assessed, priced, decided, then built. Any other sequence means the organization is paying for something it never agreed to buy.
And what it means to accept a known defect into production. Who decides, what the workaround is, and who explains it to the user who finds it on a Monday morning.
None of that requires a binder. It requires somebody senior enough to insist that the people making the decisions understand the system they are making them inside.
What is Actually Being Asked
Look at what gets asked of a project manager in an organization that has trained nobody else.
Lead a team that has never been trained in the company’s own method.
Report to a board that is not fluent in it.
Inside an organization that has not mastered it either.
Then carry the accountability for the outcome.
That is not a difficult assignment. It is an impossible one, and it is usually described as a good opportunity to step up.
Nobody sets out to hit their own side.
It happens when half the people in the area are working from a briefing the other half never received.
The project manager is not the one holding the map. The project manager is the one standing out in the open, waving.