Article

Does a project really fail because of its methodology?

When a project starts to drift, we often look for the cause in the tools.

The methodology was wrong.

The schedule was too optimistic.

Roles were not clear enough.

Tracking was not rigorous enough.

We need another checkpoint.

A better tool.

A stronger governance model.

All of that may be true.

But sometimes we repair the mechanics while the real problem sits somewhere else.

In the relationships.
In the decisions.
In what nobody wants to say.
In what everyone knows… but nobody puts on the table.

A methodology cannot decide for us

We can have an excellent schedule and avoid a difficult decision.

We can have a perfect risk register and never discuss the risk that actually worries the team.

We can hold weekly meetings and never address the question blocking the project.

We can even be highly disciplined in the wrong direction.

A project may show every sign of being well managed.

Updated dashboards.

Indicators.

Minutes.

Assigned actions.

And still gradually lose contact with reality.

Because methodology organizes the work.

It does not guarantee that we are looking at the right thing.

The problem is not always in the plan

Sometimes the problem is in a sentence nobody wants to say.

“This deadline is no longer realistic.”

“We do not have the resources.”

“The two teams are not truly aligned.”

“Nobody wants to make this decision.”

“This project may no longer make the same sense it did at the start.”

A good method does not replace a good question

Henry Mintzberg has often challenged the idea that strategy can be fully contained in formal plans.

The same idea matters in projects.

A plan is a representation.

Not reality.

So we need to ask more than:

“Are we on schedule?”

We also need to ask:

“Does what we are doing still make sense?”

“What has changed since we made this decision?”

“What problem are we actually trying to solve?”

“What conversation are we still avoiding?”

We amzakal…

We return to the field.

We look beyond dashboards, tools and methods.

And before asking how to make the project move faster,

we check once more whether we are moving in the right direction.