The Hidden Performance Variable
Why the Quality of Your Project Team Determines the Quality of Your Workplace
In 2012, Google launched an internal research initiative with a deceptively simple objective: identify what makes a team effective.
The project, known internally as Project Aristotle, drew on years of employee performance data, hundreds of interviews, and the expertise of some of the world's leading organisational psychologists. Its findings surprised almost everyone involved. The highest-performing teams at Google were not distinguished by the seniority of their members. They were not characterised by the sophistication of their processes, the clarity of their objectives, or the complementarity of their skills. What distinguished them - consistently, measurably, across every function and geography studied - was something far more fundamental.
The degree to which every member of the team felt safe to speak, to challenge, to contribute, and to fail without consequence.
Psychological safety, a concept first developed by Harvard Business School professor Amy Edmondson in the late 1990s, turned out to be the single most reliable predictor of team performance across every context Google studied. Not talent. Not process. Not technology. The quality of the human environment in which people did their work.
We have spent decades applying that insight to the delivery of complex workplace projects. The conclusion is the same.
The team is the project. Everything else is context.
Why This Is Not the Conversation Most Clients Are Having
When organisations approach a workplace transformation - whether that is a relocation, a fit-out, a portfolio consolidation, or a flagship headquarters project - the conversations that dominate the early stages are almost always about physical and financial variables.
How much will this cost? How long will it take? What should the space look like? Which buildings should we consider? What procurement route is most appropriate?
These are legitimate and important questions. But they are questions about the project as an object - a thing to be specified, priced and delivered. They are not questions about the project as a human endeavour - a complex, extended collaboration between individuals who may never have worked together before, operating under conditions of time pressure, incomplete information and competing priorities.
The gap between those two framings - project as object and project as endeavour - is where most project failures originate. Not in the design. Not in the procurement. Not in the construction. In the quality of the human system assembled to deliver it.
The research on this is unambiguous. A 2016 study published in the Journal of Management in Engineering found that team dynamics - specifically trust, communication quality and psychological safety - accounted for more variance in project outcomes than any technical or contractual factor. A McKinsey analysis of major capital programmes found that projects with high-functioning leadership teams were significantly more likely to deliver on time and within budget than those with technically superior but relationally dysfunctional ones. The data consistently points in the same direction.
And yet the investment most clients make in thinking carefully about their project team - who is on it, how it is led, what conditions it operates under, and how trust and collaborative capability are built within it - is a fraction of the investment they make in almost every other aspect of the project.
This is the hidden performance variable. And closing the gap around it is one of the highest-value decisions an organisation can make.
What a High-Performing Project Team Actually Looks Like
It is worth being specific about this, because high performance in a project context is frequently misunderstood.
A high-performing project team is not one in which everyone agrees. It is not one in which conflict is absent, in which meetings run smoothly, or in which every decision is made without friction. In fact, the absence of productive conflict is one of the most reliable warning signs that a project team is underperforming - that challenge is being suppressed, that difficult truths are not being surfaced, and that the team is prioritising harmony over honesty.
Patrick Lencioni's model of team dysfunction - developed in his 2002 work The Five Dysfunctions of a Team and subsequently validated across multiple organisational contexts - identifies the absence of trust as the root cause of almost every form of team underperformance. When trust is absent, people do not engage in productive conflict. When productive conflict is absent, people do not commit to decisions. When commitment is absent, accountability breaks down. When accountability breaks down, outcomes suffer.
In a project environment, this cascade is both accelerated and amplified. Projects operate under time pressure. Decisions must be made quickly, often with incomplete information. The cost of unresolved conflict - a design issue that nobody raises, a commercial risk that nobody flags, a programme assumption that nobody challenges - compounds rapidly. A problem surfaced in week two costs a fraction of the same problem discovered in month six.
A high-performing project team has specific, observable characteristics that distinguish it from a merely functional one.
Trust is explicit, not assumed. Members of the team have invested time in understanding each other's motivations, constraints and ways of working. They know who to call when a decision needs to be made quickly, and they are confident that the call will be taken. This does not happen automatically. It requires deliberate investment - in the right conversations, at the right moments, early in the project lifecycle.
Challenge is welcomed, not managed. The best project teams create conditions in which raising a difficult question is understood as a contribution rather than a criticism. The project manager who flags a commercial risk that makes the contractor uncomfortable, the cost consultant who challenges a design assumption that inflates the budget, the client representative who questions a programme that looks optimistic - these are the interventions that protect projects. They happen reliably only when the team culture makes them feel safe.
Accountability is shared, not allocated. In lower-performing teams, accountability is a contractual concept - each party is responsible for their defined scope, and problems that fall between scopes are nobody's problem until they become everybody's crisis. In high-performing teams, accountability extends beyond contractual boundaries. When something goes wrong, the question is not whose fault it is. It is what needs to happen now, and who is best placed to make it happen.
Decision-making is clear and fast. One of the most consistent sources of project delay is not construction or procurement - it is decision latency. Decisions that take three weeks to make because the right people are not in the room, because the governance structure does not support rapid escalation, or because nobody has clear authority to act. High-performing project teams resolve this by establishing decision-making clarity at the outset - who decides what, at what threshold, with what information, and within what timeframe.
Communication is honest, not performative. Project reporting in many organisations has evolved into a form of performance management - RAG statuses that are always green until they are suddenly red, programme updates that smooth over emerging issues, budget reports that absorb contingency without comment. High-performing teams communicate differently. They share bad news early, because early bad news is almost always cheaper than late bad news. They distinguish between what is known, what is assumed, and what is uncertain. They treat the project meeting as a problem-solving environment rather than a status-reporting one.
The Client's Role in Team Performance
There is a tendency, when discussing project team performance, to focus on the delivery side - the project manager, the cost consultant, the contractor, the design team. This is understandable but incomplete.
The client is a member of the project team. In many cases, the client is the most important member of the project team - because the client makes decisions that no other party can make, and because the quality and speed of those decisions determines the momentum of everything else.
A client who is disengaged, slow to decide, or unclear about their own priorities creates conditions that even the highest-performing delivery team cannot fully compensate for. A client who is engaged, decisive, and clear about what they are trying to achieve creates conditions that even a moderately performing delivery team can rise to meet.
This is not a criticism of clients - most of whom are managing workplace transformation programmes alongside significant day-to-day operational responsibilities, without the benefit of having done it before. It is an argument for investing deliberately in the client's ability to perform their role within the project team.
That investment takes several forms. It includes clarity of brief - ensuring that the client's own organisation is aligned around what the project is trying to achieve before the brief is shared with the delivery team. It includes governance design - establishing decision-making structures that allow the client to engage with the project at the right moments, at the right level, without either micromanaging delivery or becoming so distant that critical decisions are delayed. And it includes relationship investment - taking the time to build genuine understanding between the client team and the delivery team, so that when difficult moments arise - and they will - the relationship can absorb them.
Research by the Construction Industry Institute consistently identifies client capability and engagement as among the strongest predictors of project success. Not the sophistication of the procurement route. Not the size of the contingency. The quality of the client's participation in the project as a collaborative endeavour.
Building the Team Before the Project Begins
The most important period for project team performance is not during delivery. It is before delivery begins.
The decisions made in the earliest stages of a project - about who is appointed, in what sequence, under what contractual arrangements, with what governance structure and with what investment in team formation - determine the conditions under which the project will be delivered. Change those conditions later and you are managing consequences. Establish them well at the outset and you are creating momentum.
This has several practical implications.
Appointment decisions are team design decisions. Every consultant or contractor appointment is simultaneously a decision about the composition and dynamics of the project team. Who brings what expertise? Who has worked together before, and with what result? Who brings the collaborative capability - the willingness to challenge, to share accountability, to operate beyond their contractual boundary - that distinguishes a high-performing team from a functional one? These questions are rarely asked in the context of a professional appointment. They should be central to it.
Governance is not administration. The governance structure of a project - how decisions are made, how information flows, how issues are escalated - is the operating system of the team. A poorly designed governance structure creates friction, slows decisions, and suppresses the challenge that high performance requires. A well-designed one does the opposite. Investing in governance design at the outset of a project is one of the highest-return activities available to a client - and one of the most consistently underdone.
Team formation is a legitimate project activity. In the most effective project environments we have worked in, the early stages of a project include deliberate investment in team formation - not as a social activity but as a performance one. Workshops that establish shared understanding of the project's objectives and constraints. Conversations that surface different perspectives on risk and priority. Structured moments that allow team members to understand each other's ways of working before the pressure of delivery makes those conversations harder to have. This investment pays back many times over in the speed and quality of decisions made later in the project.
The project manager's first job is relational. In a technical sense, the project manager's role is to plan, coordinate and control. In a human sense, the project manager's role is to create the conditions in which the team can perform. These two dimensions of the role are not in conflict - but the second is frequently underweighted. The project manager who invests in building trust across the professional team, who creates space for challenge, who models the accountability and transparency they expect from others, and who attends to the relational health of the team as diligently as they attend to the programme - this is the project manager who consistently delivers outstanding outcomes.
What This Means for Your Next Project
If the quality of your project team is the hidden performance variable - and the evidence strongly suggests that it is - then the strategic question is not simply who to appoint, but how to create the conditions under which the people you appoint can perform at their best.
That begins with a shift in how the early stages of a project are understood. The period before design begins and before contractors are engaged is not a preliminary phase. It is the most consequential phase - the moment at which the team is assembled, the governance is designed, the relationships are established, and the conditions for performance are either created or missed.
It continues with a willingness to invest in the human dimensions of the project alongside the technical and commercial ones. Not as a soft supplement to the real work, but as a core determinant of whether the real work succeeds.
And it requires an advisor whose role is not simply to manage the process but to build and lead the team - someone with the credibility, the relationships and the understanding of human performance to create the conditions in which everyone around the table, client and delivery team alike, can do the best work of their professional lives.
The building you end up with reflects the team that created it. Not just their technical expertise. Not just their contractual responsibilities. Their trust, their cohesion, their willingness to challenge each other and to be challenged, their shared commitment to something that is genuinely worth producing.
That is what great looks like.
And it starts - as almost everything in a complex project does - with the decisions made before the project formally begins.
goo collective is a senior-led project management and cost consultancy working at the intersection of commercial expertise and human performance. We believe the quality of the team is the quality of the project - and we build accordingly.