Why "Stay in Your Lane" Quietly Stalls Your Team

"Stay in your lane" stalls teams because the lanes are usually out of date. Roles shift, people leave and job descriptions get set aside, but the habit of waiting for permission stays. The work that falls between two roles sits there until a customer notices.

This one's been on my mind all week. Across several teams this year, I've watched capable people go quiet because of a line on an org chart. They cared. They'd just decided somewhere along the way that it wasn't their lane.

Why "stay in your lane" sounds right

"Stay in your lane" sounds like respect for roles, for boundaries and for other people's work. Sometimes it is exactly that, and I'll get to when it's the right call.

But on most teams I work with, the lanes were drawn for a version of the company that doesn't exist anymore. People leave, roles merge, and job descriptions get set aside the minute it's all hands on deck. When the lines move that fast, waiting for permission means the work waits too.

And it usually waits in the worst spot: right between two people who each assumed it was the other's. That's not a lane. That's a ditch.

The nice version is still costly

Kim Scott has a name for the polite version of this in Radical Candor: ruinous empathy. You care about the people involved, so you stay quiet to keep the peace. She picked the word radical because "so many of us are conditioned to avoid saying what we really think." Staying in your lane can be that same habit wearing a name badge.

Four lessons from this year's report card

These came from real teams this year, with the details changed.

The title isn't the knowledge

I've watched this happen more than once. Someone holds a lead role, then the role shifts under them: a new structure, a new manager, a job description that quietly changes. They still have the history, the relationships and the read on what clients need. But the confidence to speak up leaves with the title, and "it's not my place anymore" slowly becomes a reason to sit back.

I get it, and most of us have felt some version of it. Waiting for someone to hand you clarity is frustrating. The way out is to go get it, and the person who knows the history is usually the best one to do that.

Ryan Holiday has a useful frame for this in Ego Is the Enemy. He calls it the canvas strategy: "Find canvases for other people to paint on." In ancient Rome, an anteambulo walked ahead of his patron and cleared the way, and the person clearing the path often ends up steering it. You don't need a title to clear the path.

The person who raised a hand

This one comes up a lot. Someone spots a problem coming down the pipe, like a vendor change, a broken handoff or a number that doesn't add up, and it's going to land on a customer. It's not their account and not their call. The ones who lead anyway raise a hand and bring a recommendation with it.

The decision still belongs to the owner. It just gets made with the facts on the table instead of after a customer notices. That's the whole idea in one line: see it, name it and bring a plan.

The project that sat in the "not mine" pile

Picture a big project with a hard deadline that lands between two teams. Everyone can see it coming, and each side assumes the other has it. So it sits in the not-mine pile for weeks. Somebody finally grabs it with days to spare and drags it over the finish line, but there's no time left to do it well. Something goes sideways, and the scramble costs more than the project ever would have.

Whoever finally grabbed it did the right thing. They just did it too late. Raising a hand in week one is cheap, and rescuing the project in the final week isn't.

The title I gave up

I've changed titles myself. It's uncomfortable, especially in an industry where people know your name and your last role. I've also talked with seasoned leaders weighing a role without the big title, worried about how peers would read the move. What I've learned is that people remember what you fixed, not what was on your badge.

Ready for the how? The six moves I use before crossing a lane are in How to Lead Without Authority: the lane check.

What the four stories have in common

In every case, the person closest to the problem knew first and said nothing, or said it late. Nobody was lazy. The lane lines told them it wasn't their call, so they waited for someone whose call it was. Meanwhile the cost went up every week the work sat still.

The fix isn't to tear the lanes down. It's to treat what you can see as yours to raise, even when the decision isn't yours to make.

When staying in your lane is the right call

Staying in your lane is good advice when crossing would mean overriding someone's decision or quietly doing their job for them. Fixing things around people feels helpful, but it hides the problem and wears out whoever does the fixing. The line to watch: raise it out loud, with a plan, and let the owner decide.

The final bell

Lanes are useful. They tell you where to start. They were never meant to tell you where to stop caring. On a team that's built to learn, everybody gets a turn at the front of the classroom.

Want help applying this with your team? Let's chat.

Related reading: Stop Writing Dust Magnet Decks: How To Build A Strategic Framework That Actually Gets Used

Frequently asked questions

What does "stay in your lane" mean at work?

It means sticking to your own role and leaving other people's work to them. It's useful for avoiding stepped-on toes, but it backfires when the work that matters falls between two roles.

Why is "stay in your lane" bad advice?

It isn't always bad advice, but it goes wrong when lanes are out of date or unclear. Work that sits between two people waits until it becomes urgent and expensive.

What is ruinous empathy?

Kim Scott's term in Radical Candor for staying quiet to protect someone's feelings. It feels kind in the moment and costs the team later.

How do you speak up about a problem that isn't yours?

Tell the owner first and bring a recommendation, not a finished decision. Let them decide, then offer to help with the next step.

About the author: Krystal Crowe is the founder of Hickory Grove Consulting, a Wisconsin practice focused on marketing strategy, web development and fractional marketing leadership. She works inside credit union, nonprofit, veterinary and small business teams to get everyone on the same lesson plan.