Ep241: Roundabouts and Stop Signs: A Framework for Letting Your Team Move

Most organizational bottlenecks aren't caused by bad people or unclear strategy. They're caused by systems that require everything to stop before anything can move forward.

In this episode, David Wheatley draws on the surprisingly rich comparison between four-way stops and roundabouts to examine how leaders can shift from permission-based cultures to flow-based ones. He introduces a yield-based decision framework — a practical model that gives teams the authority to move forward on low-stakes decisions without waiting for a green light, while preserving real checkpoints for high-cost or irreversible ones.

If your team feels perpetually stalled, or if you find yourself as the sign-off on things that probably shouldn't require you, this episode offers both a reframe and a concrete place to start.

Learn more about Humanergy's work: https://www.humanergy.com

Join the Humanergy community on LinkedIn.

Sign up for our FREE leadership workshops. 

Transcript

Roundabouts and Stop Signs as a Modern Business Challenge Humanergy Leadership Podcast Host: David Wheatley

Welcome to this episode of the Humanergy Leadership Podcast. This one's titled "Roundabouts and Stop Signs as a Modern Business Challenge." It builds on an episode from around Christmas time with Judy Brown and Rick Eigenbrod — I think that was episode 235. I'm David Wheatley, your host for today.

Thinking about roundabouts and stop signs — they both serve the same ultimate purpose: getting you through an intersection without a collision. But roundabouts and four-way stops operate on a fundamentally different philosophy. One relies on interruption, the other relies on flow.

The primary difference is in how traffic is managed. A four-way stop is a stop-and-go system. A roundabout is a yield-and-go system.

Safety is where roundabouts truly shine, though they often feel more intimidating to new drivers. In a standard four-way intersection, there are 32 potential conflict points — places where vehicles can crash. In a roundabout, that number drops to eight. Because everyone is moving in the same direction, the possibility of a head-on or T-bone collision is virtually eliminated.

If someone runs a stop sign, the result is often a high-speed, 90-degree impact or a head-on collision — the most lethal types of accident. The geometry of a roundabout forces drivers to slow down, usually to 15 to 20 miles per hour. If a crash does occur, it's typically a low-speed sideswipe or glancing blow, which rarely results in serious injury.

Beyond safety, there are real environmental and time differences. Four-way stops require every car to come to a complete halt, even if no one else is at the intersection. That wastes fuel and increases emissions. Roundabouts allow cars to maintain momentum. According to the Insurance Institute for Highway Safety, replacing stop signs or signals with roundabouts reduces vehicle delays by between 62 and 74%.

I acknowledge that while roundabouts are objectively safer, they do have a steeper learning curve — I found that out as an Englishman in America. Minor fender benders can actually increase temporarily when a community first installs a roundabout, but the number of fatalities almost always drops by about 90%.

So how does this apply to business?

Applying the physics to business operations reveals a lot about why some companies feel stalled while others seem to move with effortless momentum. In a professional context, these aren't just road designs — they're governance models.

The four-way stop represents a highly centralized, bureaucratic process. Everyone must come to a complete halt and wait for their turn, or for a specific authority to signal them forward.

A few examples of what that looks like in practice:

The Stop Sign — requiring sign-offs from multiple department heads for minor expenses. The Queue — a centralized ticketing system where every task, regardless of urgency, sits in a linear line. The Conflict — "who got here first?" syndrome, where teams fight over resources based on arrival time rather than the value of the project.

The roundabout, by contrast, represents decentralized, flow-based operations. It relies on clear rules — the yield — and constant movement rather than rigid stopping points.

The Yield — instead of waiting for a go signal, employees are empowered to act as long as they aren't colliding with something already in motion. They're given the big picture to guide their flow. The Flow — information moves in a circle where everyone can see the traffic, the project status, and merge in when there's an opening. Low-speed fender benders — minor mistakes happen because people are moving fast, but project fatalities are rare because the system doesn't allow for high-speed, head-on disasters.

We can also see this philosophy in the agile approach to software development.

To transition from a stop-and-go culture to a flow-based one, leaders can adopt three specific strategies.

One: Replace permissions with yields. In a four-way stop, you can't move until it's your turn. In a roundabout, you move if the coast is clear. Give your team "check, then go" authority. Instead of asking, "Can I do this?" the rule becomes, "I am doing this unless I see a conflict with an existing priority." That keeps momentum alive.

Two: Simplify the conflict points. Roundabouts are safer because they reduce 32 conflict points to eight. Audit your meetings and approval chains. If a document needs 10 signatures, you have 10 conflict points where the project could die. Reduce these touchpoints to the absolute minimum necessary to prevent a crash.

Three: Design for low-speed iteration. Roundabouts work because they force cars to slow down slightly to enter. Don't aim for 100 miles an hour on a project if it requires a stop sign every mile to check for safety. Aim for a steady 30 miles an hour where the team can make real-time adjustments without stopping the entire engine. This is the essence of agile methodology.

A four-way stop feels safer to a micromanager because they can see every car stopped. A roundabout feels chaotic because everything is moving. But the roundabout gets 70% more people to their destination faster, with fewer injuries.

To help your team make this shift, you can build what I'd call a yield-based decision framework. This moves the burden of momentum from the manager — the traffic light — to the individual contributor — the driver. The goal is to keep vehicles moving unless there is a clear, immediate reason to stop.

The framework allows team members to move forward on tasks without waiting for a formal meeting or a green light, provided they follow three checks.

Check one: The Clearance Check — is the lane open? Before starting a new initiative, the team member must look at the current traffic. If the task doesn't conflict with the top three quarterly priorities, the lane is clear. Proceed without asking — simply log the start in a shared project tracker.

Check two: The Merging Rule — who has the right of way? In a roundabout, you yield to those already in the circle. If your project requires resources — time, budget, or people — already committed to a moving project, you must yield. Negotiate directly with the project's owner to see if there's a gap you can merge into. Only involve leadership if a collision or deadlock occurs.

Check three: The Speed Limit — low-stakes iterations. Roundabouts only work because everyone slows to a manageable speed. Any decision that is reversible and costs less than a defined threshold of dollars or hours is a low-speed decision. Take the turn. Don't stop to ask for permission. If it's a high-speed decision — irreversible or high-cost — that's your stop sign. Bring it to leadership.

So how do we actually implement more roundabouts?

First: Purposely build circles. You can't have a roundabout without a clear view of the traffic. You need a shared, real-time dashboard — something like Trello, Asana, or Monday.com — where everyone can see what's currently in the circle and what the overarching picture of success looks like.

Second: Define the exit ramp. Be very clear about what a finished project looks like. In a roundabout, if you don't know your exit, you just keep spinning.

Third: Celebrate glancing blows. In this system, people will occasionally make small mistakes because they're moving autonomously. Treat these as low-speed sideswipes. Fix the dent, learn from the merge, and keep the traffic moving.

This is a significant shift for many leaders — moving from being the police officer on point duty directing traffic to the city planner, providing the big picture and pushing decisions down to the local level.

Stop being the bottleneck in your own success.

In a four-way stop, the system only moves as fast as the person with the stop sign allows. When you insist on every decision crossing your desk, you aren't ensuring safety — you're manufacturing delay.

Here's my challenge to you: Replace one approval with a yield this week.

Identify a recurring decision that currently requires your sign-off. Redefine it. Tell your team they have the right of way to proceed, as long as they don't collide with a predefined set of three strategic priorities. If the lane is clear, they move.

Then build the circle and step out of it.

A roundabout only works if the driver can see the traffic. Your job is to create radical transparency. Build a shared dashboard where every project is visible to everyone. Once the team can see the flow, they'll naturally learn to merge, yield, and exit — without you having to blow a whistle.

What are your stop signs? And how are you going to turn them into roundabouts?