Leading successful teams

Projects are delivered by temporary teams. People come together from different departments and organizations, often part time, often with other priorities, and are expected to perform quickly. PRINCE2 7 recognizes that leading such teams is different from managing a permanent department. Project managers and team managers usually have limited formal authority over team members, whose line managers remain elsewhere. They must lead through clarity, collaboration and trust. This lesson looks at how the PRINCE2 structures of plans, work packages, team structures and reporting support team leadership. Leadership styles, motivation theory, coaching and conflict are covered in depth in PMP-120; here we apply them through a PRINCE2 lens.

What is different about project teams

A permanent team has a shared history, stable membership and a clear hierarchy. A project team has none of these at the start. Members may never have worked together, may belong to different organizations with different cultures and may be allocated for only part of their time. The team will disband when the project ends, so long-term career incentives often sit outside it. These features make it harder to build commitment, but they also create opportunities: people who choose to join a project may be motivated by the work itself, by learning and by the chance to make a visible difference.

Leading without formal authority

In most projects the project manager does not write team members' performance reviews, set their pay or decide their careers. Team managers from supplier organizations answer to their own company. Even within one organization, specialists often report to functional managers. This means that leadership must rely on other sources of influence: expertise, clarity of purpose, fairness, the quality of relationships and the ability to remove obstacles. PRINCE2's structures help, because they make expectations explicit and agreed rather than imposed.

A work package is a good example. It is not an order handed down; it is an agreement between the project manager and a team manager about what will be produced, to what quality, within what tolerances, by when and how progress will be reported. The team manager can negotiate it before accepting it. That negotiation is itself an act of leadership: it respects the team manager's expertise, surfaces risks early and builds commitment to a plan the team helped shape.

The trust and delegation relationship

Lesson 1 introduced the link between trust and delegation. Within the team, the same relationship applies. A project manager who trusts a team manager can set wider work package tolerances and lighter reporting. A new or struggling team may need tighter tolerances and more frequent checkpoints at first. The aim is to widen delegation as trust grows, because over-control wastes senior time and demotivates capable people.

Psychological safety

Psychological safety is the shared belief that it is safe to speak up, ask questions, admit mistakes and raise concerns without being embarrassed or punished. Research on teams in many industries has found it to be one of the strongest predictors of team learning and performance. In PRINCE2 terms, psychological safety is what makes the controls work. Team members report forecast breaches early, raise risks honestly, contribute to lessons and challenge poor plans. Without it, checkpoint reports become exercises in looking good.

Leaders build psychological safety through everyday behavior: thanking people for raising problems, admitting their own mistakes, asking for input before giving their own view, responding to bad news calmly and focusing on fixing problems rather than allocating blame. They lose it quickly through public criticism, defensiveness or punishing the messenger.

Ways of working

Because project teams combine people from different backgrounds, it helps to agree ways of working explicitly at the start of each stage or when new members join. Ways of working cover how the team will communicate, make decisions, handle disagreement, use tools, hold meetings, share information and support each other. In agile teams this is often called a team charter or working agreement; PMP-120 covers team charters in detail. In PRINCE2 the agreements can be recorded in the project initiation documentation, the team plan or a short appendix to the work package.

Part-time allocation and focus

Many project team members are allocated for a percentage of their time. Allocations look tidy in a resource plan but are hard to protect in practice. Switching between several projects and operational duties carries a cost: time lost reorienting, meetings multiplied and attention divided. Leaders should treat allocations as agreements with line managers, monitor them and raise concerns early when actual availability falls short.

Teams across organizations and cultures

When teams include people from several organizations, sectors or countries, differences in culture can affect how people communicate, make decisions, treat deadlines and express disagreement. In some cultures direct disagreement with a manager is normal; in others it is avoided. Some organizations expect decisions to be made by consensus; others expect a leader to decide. None of these is wrong, but mismatched expectations cause misunderstanding. The remedy is to discuss differences openly, agree explicit ways of working and check understanding rather than assuming silence means agreement.

Distributed and hybrid teams add another layer. PMP-120 covers time zones and virtual tools in detail. From a PRINCE2 perspective, the key points are that checkpoint and highlight reporting can carry more of the coordination load, that ways of working must be written down rather than absorbed informally, and that deliberate social contact helps build the trust on which delegation depends.

Team performance and PRINCE2 reporting

PRINCE2's reporting structure gives leaders regular evidence about team performance. Checkpoint reports from team managers show progress against work packages, products completed, quality results and issues. Over several reporting periods, patterns emerge. A team that consistently completes work packages within tolerance and passes quality reviews first time is healthy. A team whose estimates repeatedly slip, whose products fail reviews or whose issues pile up may have a capability, capacity or morale problem worth exploring.

Indicators should prompt conversations, not judgments. A low first-time pass rate might reflect a new team member, ambiguous quality criteria written by someone else or a genuine performance problem. The leader's job is to find out which.