Flow constraint
Also known as Security approval
Definition
A flow constraint is a limiting policy, capability, dependency, or resource that reduces effective movement. A constraint can be structural or temporary and may move after an intervention.
Flow constraint in practice
A flow constraint is a limiting policy, capability, dependency, or resource that reduces effective movement. A constraint can be structural or temporary and may move after an intervention.
A concrete example
An illustrative team can implement ten changes weekly, but only three can receive a required security review. The review capability constrains end-to-end flow, so adding implementation capacity would enlarge the queue.
How to use the signal
Compare this measure with cycle time, throughput, work in progress, and queue time. Define the start and finish events, inspect distributions instead of relying on one average, and record the policy behind any comparison. A useful measure should lead to a specific question about flow rather than a score for an individual.
Limitations
A visible queue does not prove which constraint caused it. Confirm the mechanism with owners and time-ordered evidence, distinguishing temporary events from persistent limits.
How this relates to Weave
Weave's engineering intelligence can help teams inspect delivery activity and timing around flow constraint. Use those signals to find patterns and test workflow improvements, while keeping the team's work system as the source of truth for product, operational, and dependency context.
Explore Engineering intelligence