Why Projects Fail. It's Never the Plan. It's the Conversation You Didn't Have.
After 20 years of running programmes, I can tell you something that won't surprise anyone who's been in the trenches: the number one reason projects fail isn't scope, budget, or technology.
It's communication.
Not the "we need better status reports" kind. I mean the real stuff. The conversation someone avoided. The risk no one raised because raising it felt dangerous. The moment a project manager knew something was off but stayed quiet because the room wasn't safe enough to speak up.
We've built an entire industry around Gantt charts, methodologies, and governance frameworks. And none of it matters if people won't tell each other the truth.
Vulnerability Isn't Soft. It's Strategic.
Brené Brown has spent two decades researching vulnerability, courage, and leadership. Her work gets misread constantly, especially in corporate settings. People hear "vulnerability" and think it means sharing your feelings in a standup. It doesn't.
What Brown actually found is that the highest-performing teams are the ones where people feel safe enough to say three things: "I don't know." "I got this wrong." And "I need help."
That's it. That's the competitive advantage.
In her research on armoured versus daring leadership, Brown draws a clear line. Armoured leaders protect themselves. They control information, avoid hard conversations, and perform certainty they don't actually have. Daring leaders do the opposite. They lean into discomfort because they know that's where the real problems get solved.
Now think about your last troubled project. Was there a moment, early on, where someone could have flagged a risk but didn't? Where a vendor smiled through a steering committee while knowing the timeline was shot? Where a sponsor quietly stopped engaging but no one called it out?
That silence is what kills projects. Not the risk itself, but the fact that no one felt safe enough to name it.
Accountability Without Blame
Here's where it gets interesting. Vulnerability alone isn't enough. You can build the safest, most psychologically secure team in the world and still fail spectacularly if no one owns the outcomes.
This is where extreme accountability comes in. The concept is simple: when something goes wrong, the first question isn't "whose fault is it?" It's "what could I have done differently?"
That reframe changes everything. It moves the conversation from defence to learning. From politics to progress.
The best project leaders I've worked with do both simultaneously. They create space for honesty and they hold themselves and their teams to a standard. Vulnerability without accountability is just venting. Accountability without vulnerability becomes a blame culture where people learn to cover themselves rather than solve problems.
The sweet spot is a team where someone can say "I missed this" and the response is "right, how do we fix it?" Not a post-mortem. Not a corrective action register. A genuine, human conversation about what happens next.
The Agency Problem
All of this gets harder, sometimes dramatically harder, when you're working with external agencies and vendors instead of internal teams.
When your delivery partner doesn't sit in your building, doesn't share your culture, and has their own commercial pressures, every communication gap gets amplified. An internal team member might raise a concern in a hallway conversation. An agency resource has no hallway. They have a weekly status call and an incentive to keep things looking green.
I've seen this pattern repeatedly. The agency delivers to the letter of the statement of work while the spirit of the project drifts sideways. Nobody lied. Nobody acted in bad faith. But the distance, both physical and relational, meant the small honest conversations that keep a project healthy simply never happened.
The fix isn't more governance. It's more relationship. Treat your agency partners like team members, not suppliers. Bring them into the hard conversations. Make it safe for them to tell you bad news early. And critically, make it commercially safe too, because no agency will be vulnerable with you if honesty costs them the contract.
The Real Takeaway
Projects don't fail in dramatic fashion. They fail in the quiet moments. The email that wasn't sent. The concern that was softened into meaninglessness. The status report that said "amber" when everyone in the room knew it was red.
If you want your projects to succeed, stop optimising your methodology and start optimising your culture. Build teams where truth travels fast, where accountability is owned rather than assigned, and where the hardest conversations happen first, not last.
That's not a framework. It's a discipline. And it's the one that actually matters.