Systems & Organizations
Stop Building Decision Funnels
Most firms think funneling every request to a single gatekeeper speeds execution, but it actually creates a hidden traffic jam.
2026-09-241 min read
Imagine a bustling city intersection where every car must wait for a single traffic light before proceeding. The light’s purpose is to impose order, yet drivers soon learn to circle the block, honk, and cut corners, turning a smooth flow into gridlock. In organizations, the “single‑point decision funnel” works the same way: a solitary manager or committee signs off on all project scopes, budgets, and timelines, believing that central authority prevents chaos.
What actually happens is a cascade of delays, as each request adds to the queue, and the gatekeeper’s bandwidth becomes the system’s bottleneck. Teams start padding their proposals with extra detail to pre‑empt questions, which inflates paperwork and stalls momentum. When the queue stretches, people bypass the gate, creating unofficial shortcuts that erode accountability and re‑introduce the very chaos the funnel intended to avoid.
The remedy is to replace the funnel with a roundabout—multiple, low‑authority decision lanes that intersect and keep traffic moving, while still preserving safety through clear right‑of‑way rules. By distributing authority, you turn a single choke point into a self‑balancing flow where each team can keep moving as long as they respect the shared signals.
Key insights
A single decision gate turns every request into a queue, amplifying latency as volume grows.
Distributing authority into parallel lanes keeps work flowing while preserving alignment through shared “right‑of‑way” norms.
Why it matters
Ignoring the funnel’s drag lets projects stall, eroding trust in leadership and driving talent to leave.
The hidden shortcuts that emerge when people circumvent the funnel sow parallel processes that later collide, creating costly rework.
Use this tomorrow
1Open the last five decision‑request emails you sent and note how many required a follow‑up clarification from the gatekeeper; aim to reduce that count by routing the next request through a peer‑review instead.
2In your next sprint planning, identify any story that still needs sign‑off from the central committee and reassign its approval to the relevant functional lead; observe whether the story’s start date moves forward.
Go deeper
The roundabout analogy comes from traffic engineering, where designers discovered that eliminating a stoplight and adding a circular intersection reduced accidents and travel time, even though drivers had to navigate a more complex path. In organizations, the same principle applies: you trade a simple, but capacity‑limited, hierarchy for a slightly more intricate, but higher‑throughput, network of decision owners. The key is to define clear escalation rules so that when lanes intersect, teams know whose signal overrides whose, preventing deadlock.
The approach isn’t a free pass for chaos; without explicit coordination protocols, multiple lanes can still collide, leading to duplicated effort. Therefore, establish a lightweight “right‑of‑way” charter that outlines which decisions are final at each level and how conflicts are resolved, similar to traffic signs that dictate yielding.
