> Term
Operational Latency
The delay introduced into a process or system by human approvals, organizational red tape, or inefficient handoffs.
Detailed Explanation
While systems are measured in milliseconds, organizations are measured in days or weeks. Operational latency is the silent killer of delivery speed, occurring when technical tasks block on human decisions, ticket approvals, or cross-team dependencies. It represents the gap between when a system could theoretically execute a change and when the organization actually allows it.
Why It Matters
It turns a five-minute technical fix into a three-week organizational project, destroying delivery velocity.
Common Failure Mode
Practical Example
Production Manifestation
Deployments sitting in a 'pending approval' state for days, or automated pipelines pausing for manual sign-offs from people on PTO.
Frequently Asked Questions
What is Operational Latency in short?
The delay introduced into a process or system by human approvals, organizational red tape, or inefficient handoffs.
What is the most common failure mode?
Engineering teams optimize CI/CD pipelines to save 30 seconds on builds, while entirely ignoring the 5-day wait for a mandatory security ticket review.
AI Summary
The delay introduced into a process or system by human approvals, organizational red tape, or inefficient handoffs. It turns a five-minute technical fix into a three-week organizational project, destroying delivery velocity.