Shared vision
Connect daily tasks to product value and a clear project outcome. Purpose guides decentralized decisions.
People deliver projects
Project Team
A high-performing team is a system of complementary skills, clear purpose, shared ownership, effective leadership, and psychological safety. Performance is enabled—not demanded—through environment, structure, feedback, and trust.
PurposeNormsLeadershipConflictGrowth
01 · Foundations
Create the conditions for performance
Roles & boundaries
Clarify accountability, authority, interfaces, and escalation paths without turning collaboration into silos.
Working agreements
Define communication, meeting, decision, review, quality, availability, and conflict norms together.
Psychological safety
Make it safe to ask, disagree, admit uncertainty, report bad news, and learn from mistakes.
Diversity & inclusion
Different expertise and perspectives improve decisions when participation is intentionally enabled.
Trust
Build reliability, competence, care, and integrity through small repeated commitments.
Project manager’s shift: from directing every task to creating clarity, removing impediments, enabling decisions, protecting focus, and developing people.
02 · Team development
Tuckman’s changing needs
Forming
Polite uncertainty. Provide purpose, structure, roles, and introductions.
Storming
Differences surface. Facilitate healthy conflict and reinforce norms.
Norming
Trust and patterns grow. Share ownership and strengthen agreements.
Performing
High autonomy and flow. Delegate, remove constraints, sustain learning.
Adjourning
Closure or transition. Recognize work, transfer knowledge, capture lessons.
Stages are not a one-way ladder. Membership, leadership, urgency, or scope changes can move a team backward. Respond to current behavior, not a label.
03 · Leadership
Adapt style to context
| Style | Useful when | Risk if overused |
|---|---|---|
| Directing | Crisis, low experience, unambiguous compliance | Dependency and low ownership |
| Coaching | Skill or confidence is developing | Manager becomes bottleneck |
| Supporting | Competence exists; confidence/alignment needs help | Insufficient clarity |
| Delegating | High competence and commitment | Abandonment without guardrails |
| Servant leadership | Knowledge work and empowered teams | Mistaken for avoiding hard decisions |
Motivation
Understand individual drivers. Autonomy, mastery, purpose, fairness, recognition, growth, and belonging often matter beyond rewards.
Emotional intelligence
Self-awareness, self-management, social awareness, and relationship management improve judgment under pressure.
Decision modes
Use command, consultation, consensus, or delegation deliberately. State who decides and when.
Recognition
Make it timely, specific, authentic, culturally appropriate, and connected to valued behavior or outcomes.
04 · Productive disagreement
Conflict can create information
Collaborate / solve
Surface facts and interests to seek a win–win solution. Durable, but takes time.
Compromise / reconcile
Each side gives something. Practical under time pressure; may not address root cause.
Smooth / accommodate
Emphasize agreement or yield. Useful when the relationship or issue imbalance warrants it.
Withdraw / avoid
Defer or leave conflict. Useful to cool down or when the issue is trivial; dangerous as a default.
Force / direct
Impose a decision. Appropriate in emergencies or firm constraints; can damage commitment.
Sequence: establish safety → separate people from problem → clarify facts, feelings, positions, and interests → generate options → agree owner/action/date → follow up.
05 · Distributed and hybrid teams
Design for distance
Communication
Default to searchable asynchronous context; reserve meetings for interaction, ambiguity, and decisions.
Time zones
Rotate inconvenience, define overlap hours, and make handoffs explicit.
Visibility
Use shared boards, decision logs, written outcomes, and transparent priorities—not surveillance.
Connection
Create intentional informal contact, inclusive facilitation, and equal access for remote participants.
06 · Measure and learn
Watch outcomes, not busyness
Useful team signals include goal achievement, flow, quality, predictability, rework, impediment age, knowledge concentration, engagement, and stakeholder feedback. Pair numbers with conversation; never rank individuals by simplistic output.
Retrospective
Inspect how the team worked, select a small improvement, assign ownership, and check the result.
Skills map
Expose capability gaps and single points of failure; plan pairing, mentoring, training, or recruitment.
Feedback
Make it specific, behavioral, timely, two-way, and oriented toward a better next action.
07 · Retrieval practice
Check your leadership
A new team openly contests responsibilities and priorities. Which stage and response fit best?
Storming. Facilitate the disagreement, clarify purpose and roles, and reinforce working agreements rather than suppressing conflict.
Which conflict mode usually produces the most durable solution?
Collaborate/problem-solve, because it addresses underlying interests—but it requires enough time and openness.
Does servant leadership mean the leader never directs?
No. It centers team effectiveness and service, but still includes accountability, boundaries, difficult conversations, and decisive action when context requires it.
What should be measured instead of individual busyness?
Team-level outcomes and system health: value, flow, quality, predictability, risk, learning, and stakeholder feedback.