Short answer
Reliability means meeting agreed expectations predictably and communicating early enough to respond when a commitment is at risk.
About Reliability
Meets agreed expectations predictably and communicates early when commitments are at risk. Reliability depends on clear, reasonable agreements and consistent follow-through, not perfection, constant availability, or silent overwork.
Use this competency for
- Assessing whether agreed work arrives with the expected timing, quality, and communication.
- Setting expectations for managing commitments and making delivery risk visible early.
Do not use this competency for
- Do not use it when expectations were unclear, conflicting, unreasonable, or materially outside the person's control.
Important distinctions
Ownership
Ownership covers responsibility for outcomes and proactive obstacle removal. Reliability emphasizes predictable fulfillment of explicit agreements.
Quality
Quality concerns characteristics of the output. Reliability concerns whether the agreed output and communication occur consistently.
Expectations by level
IC1
Meets defined commitments
Meets clear commitments for own work and seeks guidance as soon as an unfamiliar issue threatens timing or requirements.
Observable behaviors
- Confirms the deliverable, timing, and completion conditions.
- Uses agreed checks before marking work complete.
- Signals a delivery risk while there are still response options.
Examples
- Delivers an assigned item on the agreed date after completing the named checks.
- Flags a missing input early and proposes a revised sequence.
IC2
Manages ambiguous commitments
Independently sets and meets realistic commitments for ambiguous work with dependencies, adjusting agreements transparently when conditions change.
Observable behaviors
- Plans commitments using known capacity, dependencies, and risk.
- Keeps affected partners current without waiting for a status request.
- Renegotiates an agreement with clear consequences and a new basis.
Examples
- Sets a delivery range after identifying an unresolved external dependency.
- Revises a milestone before it slips and confirms the impact with partners.
IC3
Improves reliability across teams
Improves predictable delivery for complex work across teams by addressing recurring commitment, dependency, or visibility failures.
Observable behaviors
- Defines shared expectations for critical cross-team handoffs.
- Uses delivery patterns to identify systemic sources of missed commitments.
- Creates proportionate controls for high-impact reliability risks.
Examples
- Establishes readiness criteria for a handoff that repeatedly failed.
- Changes a planning cadence after analyzing recurring late dependencies.