Team People Metrics: Avoiding Demoralization and Measurement Pitfalls
PMBOK v8 Definition
Team People Metrics refer to the measurements used to track project team performance and progress. According to PMBOK v8, if measures and goals are set that are not achievable, project team morale may fall as the team continuously fails to meet targets. Setting stretch goals and aspirational measures is acceptable, but people also want to see their hard work recognized. Unrealistic or unachievable goals can be counterproductive. This concept is part of the Project Performance Domain (Section 2.1.6.7).
Why It Matters for the Exam
The PMI exam frequently tests your understanding of how metrics impact team motivation and performance. Questions appear in situational scenarios where a project manager must choose between setting aggressive targets versus realistic goals. The exam also tests your ability to identify measurement pitfalls that can demoralize the team or distort behavior.
Key Points to Remember (for the exam)
- Demoralization Risk: Unrealistic or unachievable goals cause team morale to fall as the team continuously fails to meet targets. Stretch goals are acceptable, but people need to see their hard work recognized.
- Hawthorne Effect: The very act of measuring something influences behavior. Measuring only output volume encourages quantity over quality.
- Vanity Metric: A measure that shows data but does not provide useful information for making decisions (e.g., page views vs. new viewers).
- Misusing Metrics: People may distort measurements or focus on the wrong thing when metrics are poorly designed.
- SMART Criteria: Metrics should be Specific, Measurable, Achievable, Relevant, and Time-bound to be effective.
- Actionable Metrics: Project teams should focus on measuring only what is relevant and ensure metrics are actionable.
- Recognition Balance: Instantly recognizing and celebrating successes and "quick wins" keeps the team motivated and highlights continuous progress.
Typical PMI Exam Example
A project manager sets a goal for the development team to complete 50 user stories per sprint. After three sprints, the team averages only 30 stories. Team morale drops, and members begin rushing work, creating defects. What should the project manager have done differently?
Answer: The project manager should have set achievable goals aligned with team capacity, recognized completed work, and used metrics that balance quantity with quality.
PMI Exam Traps
-
Trap: Confusing stretch goals with unrealistic goals Reality: Stretch goals are acceptable and aspirational; unrealistic goals cause demoralization and are counterproductive
-
Trap: Thinking all metrics are equally valuable Reality: Vanity metrics show data but provide no useful decision-making information; only actionable, relevant metrics matter
-
Trap: Assuming measurement is neutral Reality: The Hawthorne effect proves measurement influences behavior—you must design metrics carefully to avoid encouraging wrong behaviors
-
Trap: Focusing only on output metrics Reality: Measuring only deliverable volume encourages quantity over quality and customer satisfaction
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Team Performance Domain | Part of | Metrics are a key component of measuring team performance within this domain |
| SMART Criteria | Constraint | Metrics must adhere to SMART criteria to be effective and avoid demoralization |
| Stakeholder Engagement | Impact | Poor metrics demoralize the team; good metrics with recognition improve engagement |
| Quality Management | Complements | Metrics drive process improvements and increase likelihood of project success |
Quick Review Questions
-
A project team consistently fails to meet targets, and morale is dropping. What is the most likely cause according to PMBOK v8?
-
A project manager decides to measure only the number of deliverables produced per week. What measurement pitfall is most likely to occur?
-
A dashboard shows 10,000 website page views, but the project manager cannot make any decisions from this data. What type of metric is this?
-
During a sprint review, a team celebrates completing 8 out of 10 planned stories. The project manager criticizes them for not completing all 10. What principle is being violated?
-
A team starts focusing on creating low-value deliverables to increase their output numbers. Which effect explains this behavior change?
PMBOK v8 Reference
Section 2.1.6.7 - Measurement Pitfalls (pages 27-28) Section 2.1.5.3 - SMART Criteria Section 2 - Project Management Performance Domains