LEARN. PRACTICE. GROW.Concept and mechanism
A leading indicator is useful when it allows action before the response option is lost. Growing queue delays may indicate cut-off exposure but do not prove the degradation’s cause. Relate the signal to context, threshold, and time needed to intervene. If activating contingency takes a day, detecting delay only at the window’s end is too late. A missed intermediate milestone may be a more useful trigger. Validate the signal with specialists and distinguish a hypothesis from a conclusion. The register should show what is known, what remains unconfirmed, and who tracks developments.
Guided application
Look for common causes across entries. If application and data depend on the same identity service, two records may describe different effects of one event. Preserve those relationships to avoid duplicated exposure or unsupported independence. Reuse checklists as aids while adding current-context sources. In facilitation, gathering individual input before public discussion can reduce the influence of an initial senior opinion. New technologies can also change risk sources: allowing an AI assistant to execute restarts creates different consequences from summarizing tickets. This example applies source and authority concepts; it does not mean a new PMI-RMP exam domain has been announced.
A shared rollback specialist can constrain two windows simultaneously; separate records do not make events independent.
Common pitfalls
Trigger too late; logs as causal proof; probabilities added for the same event; silence as consensus.
Related topics: Priority, expected cost, and confidence · Compare options and size reserves
A good register preserves relationships and anticipates when action is needed.
Reference: PMI-RMP Exam Content Outline · PMI-RMP five-domain ECO, updated-2024 public document