Building a High-Performing Project Team
Ask a project manager to name the most challenging part of their work and the majority will not say scope management or risk management. They will say people. Building a team that functions well under pressure, that communicates openly, that resolves its conflicts productively and delivers consistently — that is the hard part. And yet it is the part that receives the least structured attention. Most project management methodologies have detailed frameworks for scheduling, budgeting, and risk management. They have almost nothing on how to actually build a high-performing team.
What Makes Project Teams Different
A project team is not a permanent team that happens to be working on a project. It is a fundamentally different organisational form. Project teams are temporary — they are assembled for a defined purpose and disbanded when that purpose is achieved. They are cross-functional — members come from different disciplines, departments, and sometimes organisations, bringing different vocabularies, priorities, and professional cultures. They are often strangers — people who have not worked together before and must develop enough mutual understanding to collaborate effectively, quickly.
And they are under time pressure from the start. Unlike a permanent team that can afford to develop relationships gradually over months and years, a project team must be functional — sometimes fully functional — from very early in the project. The timeline does not pause while the team builds trust.
Tuckman's Model: Accelerating Through the Stages
The most widely referenced model of team development is Bruce Tuckman's four-stage framework: Forming, Storming, Norming, and Performing. Every team moves through these stages; the project manager's job is to understand where the team is and to accelerate progress through the earlier, less productive stages.
Forming. The team comes together. Members are polite, cautious, and uncertain about their roles and the norms of the group. There is little conflict because there is little engagement. The PM's role is to provide structure, clarity about roles and objectives, and an early opportunity for connection.
Storming. As the team gets to work, differences emerge. Members disagree about approaches, priorities, and working styles. Interpersonal tensions surface. This stage is uncomfortable but necessary — it is where the team works out how it will actually function. The PM's role is to facilitate, not suppress, the storming process, keeping conflict in the task domain and preventing it from becoming personal.
Norming. The team establishes shared ways of working. Roles become clearer, communication improves, and trust begins to develop. The PM's role is to reinforce the norms that are working and address any that are not.
Performing. The team is operating at high effectiveness. Members understand each other's strengths, communicate directly, and self-manage much of their coordination. The PM's role shifts toward removing obstacles and managing outward — protecting the team from interference and securing the resources it needs.
The Team Charter
One of the most effective tools for accelerating team development is the team charter — a document the team creates together at the outset that makes explicit the norms it will operate by. A team charter is not a project charter: it is not about scope or objectives. It is about how the team will work together.
A well-constructed team charter covers communication norms (how and when the team communicates, which channels for which purposes), decision-making (who decides what, when the team decides together vs. when an individual decides), working hours and availability expectations, and how the team will handle conflict and raise concerns. The act of creating the charter is as valuable as the document itself: it forces an early conversation about expectations that most teams never have.
The Kick-off Event
A project kick-off event that builds connection and shared purpose is worth far more than the time it takes. This is not a status meeting: it is a structured experience that gives team members a chance to understand each other as people, not just as role-holders, and to develop a shared understanding of what the project is trying to achieve and why it matters.
For co-located teams, the kick-off can include social time, a shared meal, and activities that build informal connection. For distributed teams, the investment in an in-person kick-off — even if it requires travel — typically pays for itself in reduced friction throughout the project. Teams that have met face-to-face communicate better remotely than teams that have not.
Psychological Safety and the PM's Role
The single factor most strongly associated with team performance, according to Google's Project Aristotle research, is psychological safety: the belief that team members can speak up, raise concerns, admit mistakes, and challenge assumptions without fear of embarrassment or punishment. Psychological safety is not comfort — it is not the absence of challenge. It is the presence of trust.
The project manager creates psychological safety through behaviour, not declaration. A PM who responds to bad news by shooting the messenger destroys safety. A PM who responds by asking "what do we need to understand this better?" and "what options do we have?" builds it. The team observes how the PM responds to vulnerability and calibrates its own willingness to be vulnerable accordingly.
The Distributed Team Challenge
Remote and hybrid project teams face specific challenges: fewer informal interactions that build relationship, higher risk of miscommunication in asynchronous channels, and greater difficulty in reading team health. The tools for addressing these challenges — regular one-to-ones between the PM and each team member, explicit check-ins on team health, deliberate over-communication of context and decisions, rotating facilitation to include all voices — are not particularly complex. What they require is consistency and intentionality. Distributed team health does not self-manage.
XNM Consulting builds high-performing project and programme delivery capabilities for complex organisations. Learn more on our Program and Project Delivery page.