Task 3: Support Team Performance
Great project managers don't just assign work and hope for the best — they actively support team performance through appraisal, feedback, and development. Task 3 of the ECO People domain is about the systematic, ongoing process of evaluating how the team is performing, identifying gaps, providing meaningful feedback, and verifying that improvements actually take hold. It bridges leadership (Task 2) with concrete performance management practices.
This study guide covers the three ECO enablers, the performance management cycle, KPI frameworks, feedback methodologies including 360-degree feedback, SMART goal setting, and exactly how these concepts appear on the PMP exam. You'll also learn how performance support differs between predictive and agile environments.
ECO Enablers for Task 3
The PMP Exam Content Outline defines three enablers for supporting team performance. Each builds on the previous one, forming a natural cycle: assess, develop, verify.
- Appraise team member performance against key performance indicators (KPIs). Performance management starts with measurement. You can't improve what you don't track. This enabler requires the PM to establish meaningful metrics, collect performance data, and compare actual performance against expectations. The emphasis is on objective, data-driven appraisal — not gut feelings or personal bias.
- Support and recognize team member growth and development. Appraisal is only the starting point. Once you've identified strengths and gaps, the PM must actively support improvement — through coaching, training, stretch assignments, mentoring, or adjusting the work environment. Recognition of good performance is equally important; it reinforces desired behaviors.
- Determine the appropriate feedback approach, verify performance improvements. Different situations call for different feedback styles. Some team members respond to direct, candid feedback; others need a more nuanced approach. Critically, the PM must follow up to verify that feedback led to actual improvement — the loop isn't closed until improvement is confirmed.
These enablers align with PMBOK 7's Team performance domain (which emphasizes shared ownership, a healthy environment, and continuous growth), the Leadership principle, and the Value principle (because team performance directly impacts value delivery).
The Performance Management Cycle
Supporting team performance is not a once-a-year event. It's a continuous cycle that the project manager facilitates throughout the project lifecycle. Understanding this cycle helps you answer situational exam questions about what the PM should do next.
| Phase | What Happens | PM's Role | Exam Scenario Clues |
|---|---|---|---|
| 1. Plan | Define performance expectations, establish KPIs, set SMART goals, agree on success criteria with each team member | Collaborate with team members to set clear, measurable expectations. Document goals. Align individual goals with project objectives. | "A new team member has joined the project" / "Performance expectations haven't been established" / "The team is unclear about success criteria" |
| 2. Monitor | Track ongoing performance through observation, metrics, stakeholder feedback, and self-assessments | Collect objective data. Avoid relying on a single data point. Watch for trends, not isolated incidents. Maintain a performance log. | "The PM notices a team member missing deadlines" / "A stakeholder raises concerns about quality" / "Velocity has been declining for three sprints" |
| 3. Review & Feedback | Conduct regular performance conversations — both formal (scheduled reviews) and informal (real-time coaching). Provide balanced feedback (strengths + areas for improvement). | Choose the right feedback approach for each individual and situation. Be specific, behavior-focused, and timely. Make it a two-way conversation, not a lecture. | "It's time for a performance review" / "A team member's work quality has declined" / "The PM needs to provide feedback about a recent deliverable" |
| 4. Develop & Support | Provide resources for improvement: training, mentoring, job shadowing, adjusted assignments, additional tools | Remove barriers to improvement. Advocate for the team member's development needs. Follow up on training effectiveness. | "A team member lacks a specific skill" / "The team needs training on the new tool" / "Performance gaps have been identified" |
| 5. Verify & Adjust | Confirm that feedback and development activities produced measurable improvement. Reassess performance. Adjust approach if gaps persist. | Close the loop. If improvement hasn't occurred, investigate why — was the feedback unclear? Was the development inadequate? Is there a deeper issue? | "Six weeks have passed since the performance conversation" / "The PM needs to determine if the improvement plan worked" |
The third enabler explicitly states "verify performance improvements." On the exam, if a scenario describes a PM who has provided feedback or arranged training, and the question asks "what should the PM do next?", the correct answer often involves following up to measure whether the intervention worked. Look for answer choices like "assess whether the team member's performance has improved" or "review recent deliverables against the agreed KPIs." PMI wants project managers who close the loop — not those who provide feedback and walk away.
Key Performance Indicators (KPIs) for Project Teams
The first enabler requires the PM to appraise performance against KPIs. But what KPIs are relevant for project team members? The exam expects you to understand that KPIs should be tailored to the project context and the individual's role. Here are common categories:
| KPI Category | Examples | How Measured | Relevant When… |
|---|---|---|---|
| Delivery / Productivity | Tasks completed on time, story points delivered per sprint, milestone achievement rate, throughput | Project management tools, sprint reports, milestone tracking, burndown/burnup charts | Evaluating whether the team member consistently meets commitments |
| Quality | Defect rate, rework percentage, first-pass acceptance rate, customer-reported issues | Testing reports, peer review feedback, customer satisfaction surveys, defect tracking systems | Assessing the caliber of work output, not just the quantity |
| Collaboration & Communication | Participation in meetings, responsiveness to requests, stakeholder feedback, knowledge-sharing contributions | Peer feedback, 360-degree reviews, meeting attendance records, stakeholder satisfaction surveys | Evaluating soft skills and team contribution beyond individual deliverables |
| Growth & Learning | New skills acquired, certifications earned, mentoring contributions, process improvement suggestions implemented | Training completion records, certification verification, self-assessment, manager observation | Assessing continuous improvement and professional development |
| Reliability & Accountability | Escalation timeliness, issue ownership, follow-through on commitments, proactive risk identification | Issue tracking systems, risk register contributions, retrospective feedback, manager observation | Evaluating dependability and ownership of work |
PMI emphasizes that KPIs should be established collaboratively with the team member at the beginning of the project or assignment, not imposed unilaterally. This aligns with the servant-leadership philosophy and the principle of shared ownership from PMBOK 7.
Feedback Approaches: Matching Method to Situation
The third enabler specifically mentions determining "the appropriate feedback approach." The PMP exam expects you to recognize that feedback is not one-size-fits-all. Here are the primary approaches and when each is correct:
Formal vs. Informal Feedback
- Formal feedback: Scheduled performance reviews, documented appraisals, 360-degree assessments. Appropriate for milestone-based evaluations, annual cycles, or when documentation is needed for HR purposes. On the exam: formal feedback is correct when the scenario mentions organizational HR requirements, scheduled review cycles, or the need for a documented record.
- Informal feedback: Real-time coaching, quick check-ins, praise after a successful deliverable, a brief conversation about a minor issue. Appropriate for daily reinforcement, course corrections, and building trust. On the exam: informal feedback is correct for immediate, day-to-day situations — PMI prefers it for most scenarios because it's timely and builds relationships.
360-Degree Feedback
360-degree feedback gathers performance input from multiple sources: the team member's manager, peers, direct reports (if any), internal and external stakeholders, and a self-assessment. PMI views this as the most comprehensive and least biased feedback approach because it captures multiple perspectives rather than relying on a single evaluator. On the exam:
- 360-degree feedback is the correct answer when the scenario asks for a comprehensive performance assessment, when the PM needs to evaluate soft skills that peers observe, or when reducing bias in performance evaluation is mentioned.
- It is not the correct answer for urgent performance issues that need immediate attention — in those cases, direct, private feedback from the PM is appropriate.
- 360-degree feedback is typically used for developmental purposes, not for disciplinary actions or termination decisions.
The PMP exam frequently tests whether you understand the importance of timely feedback. If a scenario describes a team member who has made a mistake or whose performance has declined, and one of the answer choices is "wait until the next scheduled performance review to address it," that answer is wrong. PMI expects project managers to provide feedback as close to the observed behavior as possible — this makes it more accurate, more actionable, and more likely to result in improvement. Delayed feedback loses impact and can allow small problems to grow into major issues.
SMART Goals for Team Performance
When performance gaps are identified, the PM should work with the team member to establish SMART goals for improvement. SMART is one of the most tested frameworks on the PMP exam, and you must know what each letter represents:
| Element | Meaning | Good Example | Poor Example |
|---|---|---|---|
| S — Specific | The goal targets a concrete, well-defined outcome. Not vague or ambiguous. | "Reduce defect rate in your code modules from 12% to 5%" | "Improve your coding quality" |
| M — Measurable | Progress and completion can be objectively quantified. You'll know when the goal is met. | "Achieve at least 90% on-time delivery of assigned tasks each sprint" | "Be more reliable with deadlines" |
| A — Achievable | The goal is realistic given the team member's current skills, resources, and constraints. It stretches but doesn't break. | "Complete the intermediate Python certification within 8 weeks, with 4 hours of study time per week allocated" | "Become the best developer on the team" |
| R — Relevant | The goal matters to the project, the organization, and the individual's role. It's worth pursuing. | "Learn the new CI/CD pipeline tool to support the upcoming DevOps transition" | "Learn French because it might be useful someday" |
| T — Time-bound | The goal has a clear deadline or timeframe. Open-ended goals invite procrastination. | "Demonstrate the improved skill by the end of Q3 (September 30)" | "Improve over time" |
Supporting Growth and Development
The second enabler requires the PM to actively support team member growth. This goes beyond simply identifying gaps — it means taking concrete action. The PMP exam expects you to understand the range of development options available:
- Formal training: Courses, certifications, workshops. Best for building foundational or technical knowledge. The PM should evaluate whether training is available, budget for it, and verify its effectiveness afterward.
- Mentoring: Pairing a less experienced team member with a more experienced one for guidance, knowledge transfer, and career development. Mentoring is particularly emphasized in the ECO (see Task 13).
- Coaching: The PM provides real-time guidance, asking questions rather than giving answers, helping the team member develop problem-solving skills. Coaching is distinct from mentoring — it's more task-focused and immediate.
- Stretch assignments: Giving the team member a task slightly beyond their current comfort zone to accelerate growth. Must be paired with support to avoid overwhelming them.
- Job shadowing and cross-training: Allowing team members to observe or temporarily work in other roles to build broader understanding and reduce single points of failure.
- Resource provision: Tools, software, reference materials, or access to subject matter experts. Sometimes performance gaps aren't about skill — they're about lacking the right tools.
Supporting Performance in Predictive vs. Agile Environments
| Aspect | Predictive (Waterfall) | Agile |
|---|---|---|
| Performance Measurement | Formal KPIs tied to the project management plan; milestone-based reviews; EVM metrics for cost and schedule performance | Team velocity, burndown charts, sprint goal achievement, definition of done compliance; emphasis on team-level rather than individual metrics |
| Feedback Cadence | Often tied to project phases or quarterly review cycles; formal documentation expected | Continuous feedback through daily standups, sprint reviews, and retrospectives; real-time coaching is the norm |
| Development Approach | Planned training tied to project needs; formal skill development programs; budgeted in the project plan | Cross-functional skill development through pair programming, swarming, and knowledge sharing; team-driven identification of growth needs during retrospectives |
| Ownership of Improvement | PM owns the performance improvement plan; documents and tracks progress formally | Team collectively owns continuous improvement; the retrospective is the primary mechanism for identifying and tracking improvements |
How Performance Questions Appear on the PMP Exam
Performance support questions follow several recognizable patterns on the exam. Recognizing these patterns will help you identify the correct answer quickly:
Pattern 1: "A team member's performance has declined…"
The correct answer path: (1) Meet privately with the team member to understand the situation — there may be personal issues, unclear expectations, or resource constraints. (2) Provide specific, behavior-focused feedback on what you've observed. (3) Collaboratively develop an improvement plan with SMART goals. (4) Offer support (training, mentoring, adjusted workload). (5) Follow up to verify improvement. Avoid: public criticism, immediate escalation to HR, or ignoring the issue.
Pattern 2: "The PM needs to evaluate team performance…"
Look for answer choices that reference multiple data sources (KPIs, stakeholder feedback, peer input, self-assessment). PMI doesn't want the PM relying on a single metric or personal impression. 360-degree feedback is often the correct answer for comprehensive evaluations.
Pattern 3: "After providing feedback, what should the PM do next?"
The answer almost always involves following up to verify improvement. Look for "assess," "measure," "verify," or "review progress against the agreed goals." This tests whether you close the performance management loop.
Key Principles from PMBOK 7
PMBOK 7's Team performance domain explicitly states that high-performing teams require a supportive environment where members can grow, make mistakes safely, and continuously improve. The Value principle reminds us that team performance is not an end in itself — it serves the ultimate goal of delivering value to stakeholders. The Tailoring principle applies to performance management: the approach must fit the organizational culture, the individuals involved, and the project methodology.
The Leadership principle is also central. Supporting performance is fundamentally a leadership activity. The PM who views team members as resources to be extracted will get worse results than the PM who views them as people to be developed.
Study Checklist for Task 3
- ✅ Can you describe the five phases of the performance management cycle and the PM's role in each?
- ✅ Do you understand what SMART goals are and can you recognize a well-formed vs. poorly-formed goal?
- ✅ Can you distinguish between formal and informal feedback and know when each is appropriate?
- ✅ Do you understand 360-degree feedback — what it is, when to use it, and what it's not for?
- ✅ Can you list at least four approaches to supporting team member growth and development?
- ✅ Do you know that PMI expects the PM to follow up and verify that performance improvements actually occurred?
- ✅ Can you explain how performance support differs between predictive and agile environments?
Supporting team performance is where leadership meets execution. The principles you've learned here apply every day on real projects — and they appear frequently on the PMP exam. Review Task 4: Empower Team Members to continue building your People domain mastery, or return to Task 2: Lead a Team to reinforce leadership fundamentals.
← Back to ECO Study Guide Index | Practice People Domain Questions →