Methodology without context is decoration.
Every project manager reaches a point where they realize they know how to apply the framework but don't know how to solve the problem.
For me, that moment came in a meeting where someone was presenting a management case study from an American company as a model for us to adopt. The case was solid: cross-functional teams, well-defined ceremonies, clear delivery metrics. The company had 2,000 people and the budget to keep a fifteen-person PMO just to make sure the process ran. We had three projects running in parallel and one project manager.
Nobody asked whether it made sense.
The real problem with project management best practices is that they become answers before they ever become questions. Someone learns PMBOK, Scrum, SAFe, and starts treating every new project as an exercise in applying what they learned. The company's context goes in as input data and isn't used as a decision criterion.
The result is what I call decorative management: well-documented processes that nobody follows, because they were designed to look mature rather than to work in that environment. A weekly retrospective on a team that has never had the autonomy to change anything. A detailed risk register on a project whose biggest risk is the informal decision the CEO is going to make next Thursday.
What separates a manager who produces results from one who produces reports is the ability to read the environment before deciding which tool to use. Technical mastery doesn't account for the gap.
That requires turning your approach around, which is harder than it sounds. Most certifications and courses start from an implicit premise: there is a right way to do things, and your job is to learn it and apply it. That's comfortable because it shifts responsibility for the decision onto the method. If it went wrong, it was the team that didn't follow the process.
The problem is that the real world doesn't work that way. Every company has its own history of how decisions actually get made, and it differs from what the org chart says: who holds informal power, where agreements are really reached, what the team's natural delivery pace is once you count everything competing for its attention at the same time. A good case study from another company can be a useful reference for understanding what's possible, though it's rarely a map of how to get there.
When I started approaching project management more systematically, I spent time looking for the right method, a set of practices that would work consistently regardless of context. It took me a while to realize I was looking for something that doesn't exist.
What exists instead are principles that work across a wide range of contexts (clear communication, visibility into progress, dependency management) and practices that only work in specific ones. Mistaking one for the other is where most problems begin.
There's a considerable gap between "autonomous teams deliver faster" (a principle observed in a range of contexts) and "let's implement self-managing squads" (a practice that presupposes a very specific set of organizational conditions). Companies that jump that gap invariably adopt the vocabulary without the conditions.
What sets project management that works apart is how honestly the manager reads the context they're operating in, whatever framework was adopted.
That includes things no framework formally captures: the quality of the relationship between the departments that need to collaborate, how ready the team really is to handle autonomy, how well the decision-makers actually know what they want. Ignoring these factors because they don't fit a field in the project template leaves the problem unsolved and pushes it down the road with interest.
Adaptation is the real work, and there's nothing methodologically weak about it.