Measurement Performance Domain
Lesson 1 of 3
Measurement Domain: Baselines and Meaning
Build performance measurements that support decisions rather than producing decorative dashboards.
Why Measurement Exists
Measurement supports judgment. The exam often presents teams drowning in data while missing key risks. Strong project managers define a small set of meaningful indicators tied to scope health, schedule confidence, quality trend, and value delivery. If a metric does not influence a decision, it is noise.
Characteristics of Useful Metrics
- Clearly defined and consistently calculated
- Linked to a decision owner and threshold
- Sensitive enough to detect meaningful drift
- Visible to the people who can act on it
- Balanced across progress, quality, and value
Weak vs Strong Metric Framing
Weak Framing
- Track everything available
- Report data without interpretation
- Use one metric to represent all health
Strong Framing
- Track indicators tied to decisions
- Explain trend and likely impact
- Use a balanced metric set
Setting an Effective Baseline
- 1Define what normal performance looks like for the current phase.
- 2Confirm data source quality and collection cadence.
- 3Set action thresholds for yellow and red conditions.
- 4Document who investigates variances and by when.
- 5Review baseline relevance after major approved changes.
Exam Shortcut
If answer choices include 'collect more data' versus 'analyze trend and take targeted action,' the latter is usually preferred unless measurement quality is clearly unreliable.
PMP Decode Rule
Measure to decide, not to impress.
Practice this topic
Reinforce this lesson with scenario questions tagged Quality, Schedule, Value Delivery.
Go to Practice