Team Building

Resource technique · See it on the map

Runnable here

Deliberate activities that build how well a team works together, not just its skills.

When to use it

Use it early in a new team's life, when membership changes significantly, or when a team is functioning but not collaborating — people are doing their individual tasks correctly but not catching each other's problems or sharing context, which a status meeting doesn't fix and an off-site sometimes does.

When to avoid it

Don't reach for a team-building activity as a substitute for solving a structural problem: unclear roles, a genuine resource conflict, or a manager who won't release someone's time. An exercise doesn't fix a scheduling conflict, and using it to paper over one just delays the moment the real problem surfaces. And don't treat it as a one-time event — a single off-site early on doesn't sustain a team through a long project without ongoing reinforcement.

Steps

1. Diagnose what's actually missing — trust, shared context, or clarity about roles — since the activity that fixes one doesn't necessarily fix the others.
2. Pick an activity proportional to the problem: a recurring short retrospective for an ongoing coordination issue, a single workshop for a one-time role-clarity gap.
3. Make it genuinely collaborative, not a lecture — team building that's really a status update with snacks doesn't build anything.
4. Reinforce it in the team's regular working pattern afterward; an isolated activity with no follow-through fades within a couple of weeks.

What it produces

• A team with clearer shared understanding of roles and better working trust than before the activity

Common pitfalls

• Running a team-building exercise to avoid having a specific, uncomfortable conversation about a real conflict, which the activity was never going to substitute for.
• Treating team building as a single kickoff event rather than an ongoing practice, so its effect decays well before the project ends.
• Mandating participation in a way that makes the activity itself feel like one more task assigned from above, which undermines the trust it was meant to build.

Worked example

A boutique event-planning company staffs a wedding-season project with two planners who have never worked together. Three weeks in, tasks are getting done but neither planner is flagging the other's risks early. The PM runs a ninety-minute working session where the two of them map out who owns which client touchpoints and where the handoffs are, rather than assigning more individual tasks and hoping coordination improves on its own.

Source

• PMBOK-6 §9.4.2.4

Where it comes from: this technique is named by the PMBOK Guide, 6th edition.