PMO Flashmob has opened a new series on modern project management, and the first installment makes a claim that project practitioners have heard before: the biggest success factor in project delivery is not the method. It is the leadership and management of people.
That is not a new argument. But it is the one that most transformations quietly forget when the pressure builds.
The short version
- The post opens a PMO Flashmob series on modern project management approaches and techniques.
- It argues that effective leadership of people matters more than choosing the right delivery framework.
- It lists waterfall, Lean, Scrum, Kanban, and agile as common approaches where method selection is important.
- Full content is available through a House of PMO paid membership.
Background: where the method debates go wrong
Project delivery has spent years debating frameworks. Waterfall versus agile. Scrum versus Kanban. The right choice matters. Picking the right approach for the right problem is real work. The mistake is treating method selection as the whole job.
Method advocates and critics both tend to overshoot. The pro-method camp points to well-documented failures of frameworks applied badly. The anti-method camp uses those same failures to argue against formal approaches entirely. Both are arguing about the wrong variable.
Our analysis
The reason the people-first argument keeps needing to be restated is that methods are easier to change than leaders are. A new framework can be rolled out in a quarter. A new leadership behaviour takes a year and sustained coaching. When organizations are in trouble, they reach for the lever that moves fastest.
The trade-off is that "focus on leadership" is easy to say and hard to operationalise. A PMO that takes the argument seriously has to answer three uncomfortable questions: What leadership behaviour are we actually asking for? How will we observe it in practice? What happens when it does not show up? Without answers, the sentiment becomes a poster on the wall.
The PMO's real test is not whether it runs method workshops. It is whether the quarterly review is dominated by framework conversations or by people conversations. The ratio tells you where the real work is happening—or not.
Decision checklist: method vs. Leadership problem
| Question | Points toward method fix | Points toward leadership fix |
|---|---|---|
| Scope | Single project underperforming | Multiple projects struggling simultaneously |
| Pattern | Specific phase or handoff failing | Consistent problems across different contexts |
| Team health | Process confusion | Low engagement, high turnover |
| Sponsor relationship | Misaligned expectations on deliverables | Withdrawn or inconsistent sponsorship |
| Resolution history | New process improves performance | Same problem recurs despite process changes |
If your answers cluster in the right column, a method change will buy time at best.
What to watch next
The next posts in this series will cover specific frameworks and techniques. Watch whether they stay abstract or whether they address the harder question: how do you develop leadership capacity in a PMO that is measured on process compliance, not people outcomes? That tension is where most PMOs get stuck.
Bottom line
Pick the right method. Spend more time on the right leader.
Key takeaways
- Method choice is real work, but people leadership is where project outcomes are actually made or broken.
- The PMO's hardest job is naming leadership gaps without hiding behind framework conversations.
- A method change solves a method problem. A leadership problem requires a leadership response.
Frequently asked questions
What is the post about?
It opens a PMO Flashmob series on modern project management, arguing that effective leadership and management of people is the biggest success factor, outweighing the choice of delivery framework.
Which methods does the post mention?
Waterfall, Lean, Scrum, Kanban, and agile, with a note that the list of approaches is longer.
Is the full article free?
No. Full content sits behind a House of PMO paid membership.
What should a PMO take from this?
Examine whether your default response to project problems is a method change. If it is, you may be treating a leadership symptom with a process prescription. The harder and more valuable work is developing the people leadership capacity across your portfolio.