Every project has two timelines.

The first one lives in the plan. It has milestones, dependencies, resource allocations, and a go-live date that everyone has committed to in the presence of leadership. It is colour-coded, regularly updated, and presented with confidence at every steering committee.

The second one is invisible. It is being negotiated silently, every day, by the culture surrounding the project. It moves at the speed of trust. It stalls at the friction points of unresolved conflict, political caution, and the gap between what people say in a workshop and what they actually do when they return to their desks.

The first timeline is managed with precision. The second one is almost never managed at all.

And yet, in almost every failing project I have witnessed across 20 years of complex programme delivery, it was the second timeline that determined the outcome.

“The project was a symptom. The culture was the condition. And we spent the entire time treating the symptom.”

The Invisible Force Shaping Every Project

Culture is not a soft concept. It is not the values statement on the intranet or the tone of the all-hands presentation. It is the accumulated weight of how decisions actually get made, how conflict actually gets handled, and how safe people actually feel when they need to say something that the room does not want to hear.

When that culture is aligned, transparent, and psychologically safe, the effect on project velocity is extraordinary. Decisions happen faster because people trust the process. Problems surface earlier because raising them feels safer than absorbing them. Teams move with a coherence that no methodology can engineer, because the invisible conditions that enable collaboration have been built into the environment.

When the culture is misaligned, fragmented, or fear-driven, the opposite is true. And the destruction is systematic. It operates in every layer of the project simultaneously, and it is almost impossible to diagnose from a status report.

How Culture Creates the Ebbs and Flows

If you have delivered a complex project, you will recognise the pattern even if you have never named it in cultural terms.

The project starts well. There is energy in the kick-off. Stakeholders attend. Leadership is visible. The novelty of the initiative creates a temporary social cohesion that feels like alignment but is actually closer to politeness. People show up. The culture cooperates, at least on the surface.

Then comes the middle phase. The novelty fades. The real work begins to create friction with existing priorities, existing reporting lines, and the existing distribution of power within the organisation. This is where the culture stops pretending and starts expressing itself.

• The stakeholder who supported the project in principle begins finding reasons why each individual decision needs further review.
• The team that attended every workshop begins quietly reverting to the processes the project was designed to replace.
• The escalation that should have reached the steering committee disappears somewhere in the middle management layer, because the culture has an unspoken norm that problems travel upward only when they are already solved.
• The two departments that were supposed to collaborate begin protecting their own interests, because the project has started to expose a territorial conflict that existed long before any of this began.

None of these dynamics appear on a risk register. They do not generate a red status in the weekly report. They show up instead as decisions that take longer than expected, deliverables that require more rework than they should, and a general sense that the project is moving through something viscous, that progress requires more energy than the plan anticipated.

This is not a project management problem. It is a cultural one. And the distinction matters enormously, because the tools you use to fix a project management problem will not address a cultural one. More governance does not resolve a territorial conflict. More reporting frequency does not create psychological safety. A revised timeline does not fix a leadership vacuum.

“Culture doesn’t self-correct. It calcifies. And it takes your project with it.”

The Myth of Self-Correction

One of the most expensive assumptions in organisational life is that cultural problems, if managed carefully and given enough time, will eventually resolve themselves. That the tension between two departments will settle once both sides see the project delivering results. That the resistant stakeholder will come around once the early wins become visible. That the team will find its rhythm.

I have never seen this happen. Not once, across 20 years and dozens of complex programmes.

What I have seen, repeatedly, is this: cultural dynamics are self-reinforcing. The silo that existed before the project started will be deeper after it ends, unless a leader has actively and deliberately intervened. The resistance that began as scepticism will harden into obstruction unless someone with sufficient authority named it, engaged with it, and changed the conditions around it.

Choosing to wait and see on a cultural problem is not a neutral decision. It is an active choice to allow the problem to compound. And at some point in every project timeline,  often somewhere in that difficult middle phase, a compounding cultural problem crosses a threshold beyond which recovery becomes genuinely unlikely, regardless of what the project plan says.

Why Top Leadership Cannot Afford to Delegate This

This is where the responsibility conversation becomes uncomfortable.

Most senior leaders understand, intellectually, that culture matters. They have read the research. They can quote the statistics. They believe, in principle, that cultural alignment is a prerequisite for successful delivery.

And then they appoint a capable programme manager, approve the governance framework, set the reporting cadence, and quietly exit from the environment that will determine whether the project succeeds.

They remain present for the milestone reviews. They sign off on phase completions. But the cultural conditions that are either enabling or strangling delivery, the political dynamics, the unresolved departmental conflicts, the leadership behaviours creating drag at every level, those remain unaddressed. Because they are harder to put on a slide than a RAG status.

The problem is that no programme manager in the world has the authority to fix what only senior leadership can. A project manager can flag a cultural risk. They cannot resolve a conflict between two executive stakeholders. They can surface a pattern of passive resistance. They cannot change the norm that makes resistance feel safer than engagement. They can manage the process. They cannot change the environment.

“The culture of a project is a direct reflection of the culture of the organisation. And the culture of the organisation is set, every day, by the behaviours of its most senior leaders.”

When leadership is genuinely present in a project, not just at steering committees, but in the informal conversations, the moments of ambiguity, the points where the culture is deciding how to respond to a challenge, the trajectory changes. Not because of any specific intervention, but because the culture takes its signal from what leadership pays attention to, tolerates, and rewards.

When leadership is absent from those moments, the culture fills the vacuum with its own defaults. And the defaults are almost always conservative, territorial, and risk-averse. Exactly the opposite of what a complex change project requires.

What Active Cultural Leadership Looks Like in Practice

This is not an argument for leaders to become project managers. It is an argument for leaders to understand that sponsoring a project and leading its cultural environment are two different responsibilities, and that only one of them can be delegated.

Active cultural leadership in a project context looks like this:

• Naming the cultural dynamics that are creating drag,  not as project risks, but as organisational behaviours that leadership is choosing to address.
• Creating visible and consistent accountability for the behaviours the project requires, not just the deliverables it produces.
• Being present at the moments when the culture is deciding how to respond to difficulty, and modelling the response you need it to make.
• Making it safe for the people closest to the work to surface the real picture, not the managed version of it.
• Understanding that alignment at the top does not automatically produce alignment throughout, and actively working to close that gap.

None of this is comfortable. It requires a kind of candour about the organisation’s own cultural health that many leadership teams find easier to defer than to confront. It requires treating the cultural environment of a project as a leadership responsibility rather than an HR consideration. And it requires accepting that the most powerful variable in project delivery is not the methodology, the technology, or the talent. It is the environment in which all three are being asked to operate.

The Question Worth Asking

The next time a project in your organisation begins to slow, when the milestones start slipping, when the energy in the team shifts, when the steering committee updates start sounding more optimistic than the reality on the ground, resist the instinct to look first at the plan.

Ask instead: what is the culture around this project telling us?

Is it telling you that people feel safe enough to surface the real problems? Or that the real problems are being managed privately, because surfacing them carries too high a risk?

Is it telling you that the organisation is genuinely aligned behind this change? Or that the alignment is a performance, present in the steering committee and absent in the daily decisions of the people who actually have to deliver it?

Is it telling you that the conditions for this project to succeed have been built into the environment? Or that the project has been launched into a culture that was never prepared for what it requires?

The answers will tell you more about where your project is actually heading than any Gantt chart you have ever reviewed. And they will tell you something else, something harder to hear but more important to act on:

“The project is not behind. The culture is. And that is a leadership problem, not a project management one.”

If this resonated, explore more at scottz.com or connect with me on LinkedIn.