The conversation most construction project teams never have.

March 25, 2026

Why communication, not complexity, is the real cause of rework, delays and project friction

It starts small. A main contractor receiving notice of a design change two weeks after it was initially communicated. A subcontractor who stops raising concerns because the last time they did, nothing happened. A project meeting where the real conversation takes place in the corridor, not around the table.

No one sets out to create these dynamics. They emerge naturally when a group of organisations, each with their own priorities, pressures and ways of working are assembled into a project team and expected to perform as one. The assumption is that a contract and a PC deadline will be enough to align them. Usually, they aren't.

The result is a fault line that runs beneath most major construction projects. It's rarely visible on the programme. It doesn't show up in the risk register. But when the pressure increases as it always appears, it's where things break.

In complex projects, technical capability is rarely the constraint. Culture is.

What the Data Actually Shows

Construction has a rework problem, and most of the industry knows it.

What's less commonly acknowledged is where that rework comes from. Global research suggests that approximately 52% of rework on construction projects is caused by poor communication or incorrect information, not technical error. The average cost of rework sits at around 10% of total project value.

Add to that the finding that roughly 35% of project time is spent on non-optimal activities, resolving disputes, searching for information, unpicking misalignments and a pattern emerges. A substantial portion of what makes construction projects expensive and difficult to deliver isn't complexity of the build. It's the friction created when people aren't communicating, aligned or working effectively together.

The uncomfortable implication is that a great deal of what gets written off as 'the nature of construction projects' is, in fact, preventable.

Why Project Teams Struggle to Communicate

It's worth being specific about why communication breaks down on construction projects, because 'poor communication' as a diagnosis is almost useless. It describes the symptom, not the cause.

Construction project teams are unusual in their composition. They typically bring together people from different organisations, different disciplines and different company cultures, each of whom interpret risk, information and pressure in different ways. A commercial manager and a design lead looking at the same situation will often draw entirely different conclusions about what it means and what needs to happen next. Neither is wrong. They're just working from different perspectives, shaped by their training, their role and what their organisation is incentivising them to prioritise.

When those differences aren't surfaced and understood early, they become sources of friction later. Assumptions go unchecked. Decisions get made on incomplete information because people didn't know what others needed to know. Issues sit unraised because the environment doesn't feel safe enough to raise them and on construction projects, where hierarchy is often pronounced and pressure is high, psychological safety is frequently in short supply.

There's also the structural reality that most project teams never actually design how they will work together. They agree what they will deliver. They set out the technical standards and contractual obligations. But how they will share information, how they will handle disagreement, how they will make decisions when things get complicated, these are almost never discussed explicitly at the start. They're assumed. And assumptions, under pressure, tend to fail.

Most project teams never design how they will work together. They agree what they will deliver, but not how.

What Effective Project Teams Do Differently

The project teams that consistently perform well under pressure tend to have a few things in common and none of them are technical.

  • They establish a shared understanding of culture early, before the pressure is on. Rather than assuming that a shared contract creates a shared team, they take time at the outset to build a common language around how the project will actually run: what the overall goal/objective of the team is, how decisions get made, how information flows, and how different roles and disciplines interpret risk and pressure differently. This alignment at the start is what makes the team more resilient when complexity increases later.

  • They create clear communication standards collectively. The most effective project teams don't just agree what they will deliver, they agree how they will work together. They define, as a group, how they will share information, challenge each other, raise concerns and resolve disagreement. Because those standards are built collectively, they carry real weight when things get tense. A framework imposed from outside rarely holds under pressure; one the team has shaped together usually does.

  • They build psychological safety deliberately, not accidentally. On construction projects, where hierarchy is often pronounced and the consequences of raising a problem can feel significant, people frequently stay quiet when they should speak up. The teams that perform consistently well are those where challenge is expected and issues are raised early, not because people are fearless, but because the environment has been deliberately designed to make it safe to do so. That requires consistent behaviour from leaders and clear norms around how feedback and challenge are handled.

  • They embed these behaviours over time, not in a single session. Changing how people communicate and collaborate isn't achieved in a one-day workshop. The project teams that sustain strong performance do so because the behavioural foundations they build early are reinforced throughout the project, through regular reflection, real scenario practice, and a shared commitment to calling out when the standards slip.

A Question Worth Sitting With

Think about your current project, or the last significant one you were involved in. How much of the friction, the delays, the disputes, the rework, the conversations that happened too late was genuinely technical in nature? And how much of it was rooted in misalignment, assumption, or communication that didn't happen when it should have?

Most people who ask themselves that question honestly come up with a similar answer.

The good news is that these are solvable problems. The teams and organisations that invest in building strong behavioural foundations at the start of a project consistently find it pays back significantly as the project progresses.

“Project Playbook provides a powerful space for project teams to reflect on behaviours, communication and leadership within live project environments. The sessions are engaging, practical and immediately applicable back on projects. It is an excellent programme for strengthening collaboration, trust and overall team performance.”   Project Playbook participant

At The Condor Collective, we work with project teams to build exactly these foundations, through Project Playbook, a practical culture workshop programme designed specifically for construction projects where collaboration, pressure and pace are constantly in play. If this has prompted some useful thinking about your own project, we'd be glad to talk.

How is your organisation approaching team culture at the start of a project? We'd love to hear what's working, and what isn't.