From Coordination to Cohesion
What the Best Project Teams Understand That Average Ones Don’t
There is a version of project management that is essentially sophisticated administration.
Agendas are set. Minutes are circulated. Actions are tracked. Programmes are updated. Information flows from one party to the next in the right order and at the right time. Risks are logged. Issues are escalated through the appropriate channels. Meetings are chaired with efficiency and concluded with a list of next steps that everyone photographs on their phones and subsequently ignores.
This version of project management is not without value. Its absence produces chaos. But it is not, by itself, what produces outstanding outcomes.
The projects that genuinely perform - that deliver not just on time and on budget but with a quality and coherence that reflects the original ambition - are almost never the result of better administration. They are the result of something harder to define and considerably harder to manufacture.
A team that has moved beyond coordination into genuine cohesion.
A team where trust has replaced process as the primary operating mechanism. Where challenge is welcomed rather than managed. Where the shared commitment to the outcome is stronger than any individual’s attachment to their position within the hierarchy. Where the difficult conversation happens in the meeting rather than in the corridor afterwards.
Understanding the difference between these two states - and knowing how to move from one to the other - is one of the most important and least discussed disciplines in the delivery of complex projects.
The Coordination Trap
Coordination is seductive because it is measurable.
You can count the meetings held, the actions closed, the reports issued, the programme milestones achieved. You can demonstrate activity. You can show a client a RAG status dashboard and point to the green cells as evidence of progress. You can fill an inbox and empty it and fill it again and feel, at the end of each day, that something has been accomplished.
The problem is that coordination measures process, not performance. It tells you what has happened, not whether what has happened matters. It creates the appearance of control without necessarily creating control itself.
In project environments, the coordination trap manifests in a specific and recognisable pattern. Teams spend significant energy managing the flow of information - who needs to know what, by when, in what format - without investing equivalent energy in the quality of decisions that information is supposed to enable. Meetings are held to update rather than to resolve. Reports are produced to demonstrate activity rather than to drive action. The governance framework becomes the purpose rather than the mechanism.
The result is a team that is busy but not cohesive. A team that communicates frequently but not well. A team that is aligned around the process of the project without being aligned around the intent of the project.
Research into project failure consistently identifies communication breakdown and decision latency - not technical complexity or resource constraints - as the primary drivers of cost overrun and programme delay. Not because teams are communicating too little, but because the communication that is happening is not producing the clarity and commitment that good decisions require.
Coordination, in other words, can become a substitute for the harder work of building the kind of team that actually delivers.
“Coordination measures process, not performance. It tells you what has happened - not whether what has happened matters.”
What Cohesion Actually Means
Cohesion is a word that is used loosely in management literature and even more loosely in project environments. It is often conflated with harmony - with teams that get along, that enjoy each other’s company, that have strong social bonds and well-attended team lunches.
This conflation is not merely imprecise. It is actively misleading.
Cohesion, properly understood, is not about warmth. It is about alignment. A cohesive team is one in which every member has a shared and deeply internalised understanding of what the team is trying to achieve - and is willing to subordinate individual preferences, comfort, and sometimes contractual position to that shared objective.
The distinction is important because it changes what we look for in high-performing teams. A warm, collegial team may be pleasant to work with but produce mediocre outcomes. A cohesive team may be intensely challenging - full of disagreement, debate, and discomfort - while producing exceptional ones.
Organisational psychologist Amy Edmondson makes a related distinction between ‘teamwork’ and ‘teaming.’ Teamwork describes what happens when a relatively stable group of people with established relationships work together toward a shared goal. Teaming describes what happens when people who may not know each other, operating under time pressure and uncertainty, must rapidly form effective collaborative relationships around a complex problem.
The workplace project is almost always a teaming challenge rather than a teamwork challenge. Architects, project managers, cost consultants, contractors, client stakeholders and specialist advisors are assembled - often for the first time - around a project that will last months or years, under conditions of significant complexity and pressure. The relationships that will determine whether that project succeeds must be built rapidly, deliberately, and under fire.
This is not achieved through coordination. It is achieved through cohesion - and cohesion must be actively created, not passively hoped for.
The Architecture of a Cohesive Team
If cohesion must be built rather than assumed, the question becomes: how?
The answer is not a single intervention but a set of conditions - an architecture - that must be designed into the project environment from the outset. This architecture has four components, each of which is necessary and none of which is sufficient alone.
Shared purpose beyond the specification.
Every project has a specification - a brief, a set of employer’s requirements, a programme, a cost plan. These documents describe what is to be delivered. They do not describe why it matters. Cohesive teams have a deeper shared understanding of the purpose that sits behind the specification - what the project is trying to achieve for the organisation, for the people who will occupy the space, for the community it will serve. This shared purpose provides the reference point against which decisions can be tested when the specification runs out of answers, which it inevitably does.
Psychological safety at team level.
Amy Edmondson’s research demonstrates that psychological safety is not a personality trait - it is a team-level phenomenon. Some teams have it. Others do not. And the difference is created not by the personalities of team members but by the behaviours of team leaders. Leaders who model curiosity rather than certainty, who acknowledge what they do not know, who respond to challenge with engagement rather than defensiveness - these are the leaders who create conditions in which others feel safe to speak. In a project environment, this safety is the precondition for the honest communication that high performance requires.
Clarity of accountability without rigidity of role.
Cohesive teams are characterised by what might be called accountability fluidity - a willingness to take responsibility beyond the boundaries of their formal role when the project requires it. This is not the same as role confusion, which undermines performance. It is a higher-order form of commitment: a recognition that the shared outcome matters more than contractual scope, and that problems which fall between roles are everyone’s problem until they are resolved.
Structured trust-building, not accidental rapport.
Trust in project teams is often treated as something that develops naturally over time - the byproduct of working together, sharing pressure, and navigating difficulty. This is partly true. But in complex projects operating under time pressure, waiting for trust to develop organically is a luxury that most programmes cannot afford. The most effective project environments invest deliberately in trust-building - through structured early-stage conversations that surface different perspectives on risk and priority, through shared experiences that reveal how team members behave under pressure, and through explicit agreements about how the team will operate when things go wrong.
The Decision as the Diagnostic
One of the most reliable indicators of a team’s position on the spectrum from coordination to cohesion is the quality of its decision-making - and specifically, what happens to decisions under pressure.
In coordinated teams, decisions are made through process. The right information is gathered, the appropriate stakeholders are consulted, the decision is escalated to the correct level, and approval is obtained through the established channel. This works well when the environment is stable and the questions are clear. It works poorly when time is short, when the information is incomplete, and when the question requires judgement rather than calculation.
In cohesive teams, decisions are made through trust. Team members trust each other’s judgement sufficiently to act on incomplete information. They trust that their own judgement will be respected sufficiently to share it honestly. They trust the shared purpose sufficiently to make decisions that may not perfectly serve their individual interests.
The distinction shows up most clearly in the moments that determine project outcomes: the value engineering conversation, the programme compression decision, the contractor negotiation, the design review where the brief and the budget are in tension.
In a coordinated team, these moments are managed. Information is presented. Options are outlined. The decision is deferred to the appropriate authority. The meeting concludes without resolution.
In a cohesive team, these moments are navigated. The honest assessment of the situation is shared, even when it is uncomfortable. The trade-offs are named, not obscured. The decision is made by the people in the room who are best placed to make it, with the confidence that comes from shared understanding and mutual trust. The meeting concludes with a decision that everyone owns.
The difference in project outcomes between these two scenarios is not marginal. It is the difference between a project that drifts and one that drives.
Moving From Coordination to Cohesion: The Practical Steps
The transition from a coordinated team to a cohesive one is not an event. It is a process - one that begins before the project brief is issued and continues through to practical completion.
Start with the team, not the programme.
The first conversations on any complex project should not be about programme or procurement. They should be about the people: who is on the team, what perspectives they bring, what their experience of similar projects has taught them about where things go wrong, and how they prefer to work. These conversations create the shared context that cohesion requires. They also surface, early, the differences in perspective and approach that will either produce productive challenge or, if unaddressed, become sources of friction later.
Define what success looks like beyond the metrics.
Every project team knows what the KPIs are. Very few project teams have had an explicit conversation about what a genuinely successful project would feel like - what it would mean for the client organisation, for the people who will work in the space, for the professional reputations of everyone involved. This conversation, held early and returned to periodically throughout the project, creates the shared purpose that distinguishes cohesion from coordination.
Create the conditions for honest communication.
This requires deliberate design. Regular forums in which team members can raise concerns without risk. A project manager who models directness - who shares difficult information clearly, who invites challenge, who responds to bad news with problem-solving rather than blame. Reporting frameworks that distinguish between what is known and what is assumed, between what is on track and what is at risk. None of this happens by accident.
Manage the transitions.
In most projects, the periods of greatest relational risk are the transitions between phases - from strategy to design, from design to procurement, from procurement to construction. At each transition, new parties join the team, existing relationships are tested by changed circumstances, and the cohesion built in earlier phases must be actively renewed. The project manager who treats each transition as a relational challenge as much as a technical one maintains cohesion through to completion.
Protect the culture under pressure.
Every project faces moments of pressure - cost challenges, programme setbacks, design difficulties, contractor conflicts. These moments are tests of cohesion. In a coordinated team, pressure typically produces fragmentation: parties retreat to their contractual positions, communication becomes guarded, and the shared commitment to the project’s success is subordinated to the protection of individual interests. In a cohesive team, pressure produces the opposite response: greater collaboration, more honest communication, faster decision-making.
“In a coordinated team, pressure produces fragmentation. In a cohesive team, it produces the opposite - greater collaboration, more honest communication, faster decisions.”
The Honest Acknowledgment
It would be misleading to suggest that building cohesive project teams is straightforward. It is not.
The commercial structures of the construction and fit-out industry do not naturally produce cohesion. Contracts allocate risk and responsibility in ways that incentivise parties to protect their own positions. Procurement processes select on price in ways that can create adversarial dynamics from the outset. Programme pressures reduce the time available for the relationship-building that cohesion requires.
These are real constraints. They cannot be wished away by invoking the language of collaboration.
What can be done - and what distinguishes the most effective project environments - is to work within these constraints with clear-eyed awareness of the relational dynamics they create, and to invest deliberately in counteracting the forces that pull toward fragmentation.
The project manager who understands commercial structures deeply enough to work within them without being captured by them. The client who invests in the early-stage relationship-building that accelerates trust. The professional team that maintains a shared commitment to the project’s success even when individual interests might point in different directions.
This is not idealism. It is pragmatism - grounded in the straightforward observation that cohesive teams consistently produce better outcomes than coordinated ones, and that the investment required to build cohesion is almost always smaller than the cost of the problems that fragmentation produces.
What This Means for How You Build Your Team
The move from coordination to cohesion begins with a single shift in perspective.
Stop thinking about the project team as a collection of appointments. Start thinking about it as an environment - one that you are responsible for designing and maintaining, from the first conversation to the last.
That means asking different questions at the point of appointment. Not just who has the relevant technical experience, but who brings the collaborative capability. Who has demonstrated, in previous projects, the willingness to operate beyond their contractual boundary when the project requires it. Who communicates honestly under pressure. Who challenges constructively rather than defensively.
It means investing in the early stages of the project in ways that most programmes currently do not. Time spent establishing shared purpose, building mutual understanding, and creating the conditions for honest communication is not time spent away from the project. It is time spent creating the conditions in which the project can perform.
And it means staying close to the relational health of the team throughout delivery - not just the programme, not just the cost report, but the quality of the conversations, the honesty of the communication, the degree to which the team is navigating difficulty together rather than managing it in parallel.
The building you end up with is the physical expression of the team that created it. Not just their technical expertise - their trust, their cohesion, their shared commitment to something genuinely worth producing.
That is the difference between coordination and cohesion.
And it is, ultimately, the difference between a project that completes and one that succeeds.
goo collective is a senior-led project management and cost consultancy working at the intersection of commercial expertise and human performance. We believe that the quality of the team is the quality of the project - and we build accordingly.