Why “Staying in Your Lane” Might Be Hurting Your Team

“Stay in your lane.” Few phrases capture the modern workplace tension as neatly as this one. It promises clarity and focus, and most of the time it is offered with the best of intentions. But the same words that bring order to a team can also quietly build the silos that hold it back. So before we repeat the advice, it is worth asking what it actually does to the way a team works together.

I hear it everywhere right now. From leaders, from team members, in workshops and corridors. Usually it is said with good intentions. Know your role. Respect other people’s expertise. Do not tread on toes.

And there is real wisdom in it. Clear roles and responsibilities are the foundation of any high-performing team. When people understand what they own and where they add the most value, work flows. There is less duplication, less confusion, less stepping on each other.

So I want to be careful here, because I am not arguing the phrase is wrong. I am arguing it might be quietly doing some damage too. Because the same words that create clarity can also create silos. And silos are one of the biggest barriers to the kind of team performance organisations are chasing right now.

When staying in your lane works

Let’s give the phrase its due first.

There is a version of staying in your lane that is genuinely smart. Dr Heidi Gardner, a Harvard-based expert on cross-silo collaboration and author of Smart Collaboration and Smarter Collaboration, made this point when she joined me on the Thriving Leaders Podcast. We have all become deeply specialised in our own areas of expertise, she explained, and in the pursuit of becoming truly good at something, we have had to put boundaries around what we know.

It is not a flaw. That is what expertise is. As Heidi put it, if you are an expert in one field, you should team up with an expert in another, rather than crossing lanes and pretending you are an expert in everything.

So when staying in your lane means working to your highest and best use, it is not a problem. It is what allows a team of specialists to do together what no individual could do alone.

The trouble starts when the lane becomes a wall.

When the lane becomes a wall

Here is where it gets harder.

In Thriving Teams: When Teams Unite, Align & Achieve, I talk about what happens when people do not feel safe to take ownership. They put their head down and deliver in their patch. They self-protect by staying in their own lane. It often looks like the team is operating in silos rather than in a unified way.

Notice the language there. The very phrase we use to describe good role clarity is also the phrase that describes self-protection. The two can look identical from the outside.

When staying in your lane tips into silo behaviour, a few things start to happen.

People stop contributing outside their patch. In meetings, they hold back unless the topic is squarely theirs. “Not my area,” they think, so they say nothing. The result is that you lose diversity of thought at exactly the moment you need it most. The person from finance who notices something in the marketing plan stays quiet. The newest team member who sees the obvious flaw assumes someone more senior has already thought of it.

Collaboration narrows. Cross-functional work slows down because everyone is optimising their own area rather than the whole. Heidi made a really valid point on the podcast. Optimising within a silo is fine, she said, as long as you are only solving problems inside that silo. But the problems organisations face now are rarely that tidy. They are complex, cross-functional and multidisciplinary. The work spills across lanes whether we like it or not.

And here is the part that worries me most. When people stay rigidly in their lane, you lose the One Team mindset.

The One Team mindset, and what staying in your lane costs it

A One Team mindset is when people make decisions for the greater good of the whole organisation, rather than just their own patch, team or department. It breaks down silos. It is what separates a genuine team from a collection of individuals who happen to share a reporting line.

When everyone stays strictly in their lane, that mindset quietly erodes. People start to see their role as defending their territory rather than contributing to the bigger picture. Decisions get made for the team, not the organisation. The us-versus-them dynamic creeps in.

I see this most often with senior leaders, who instinctively treat the team they lead as their first team, and the leadership team they are part of as secondary. It is a natural instinct. But it drives exactly the siloed behaviour we are trying to avoid, where leaders protect their own patch rather than lifting their gaze.

This is why I think collective accountability matters so much. It is the antidote to the wall. Collective accountability is system-wide ownership across teams, functions and stakeholders. It is no longer about putting your head down and delivering only in your own lane. It is about the shared outcomes for the organisation. Where it is missing, teams work in isolation, like islands doing their own thing, and the finger-pointing and blame follow close behind.

How leaders keep the lane without building the wall

If the goal is role clarity without silos, the practical question is how you hold both at once. This is where being deliberate about accountability helps. In my work with leadership teams, a few moves consistently make the difference.

Make the interdependencies visible. People defend their lane partly because they cannot see how it connects to anyone else’s. I often run a simple exercise where team members share what they are accountable for and the impact it has on others. It almost always surfaces the same realisation: our work is far more interdependent than we assumed, and we need each other to succeed.

Be explicit about decision rights, not just tasks. Silos harden when people own responsibility without authority, or when nobody is clear on who actually makes the call. Naming who owns what, and where decisions are shared, removes the ambiguity that makes people retreat to safe ground.

Build team rhythms that reward lifting your gaze. If every meeting is a round of status updates, people stay in their lane by design. Shifting even one regular meeting from information-sharing to genuine shared decision-making changes what the team is rewarded for.

Recognise collaboration, not just individual delivery. Performance systems often over-reward the person who nailed their own patch. If cross-functional contribution is never noticed, do not be surprised when people stop offering it.

None of this asks anyone to abandon their expertise. It asks the team to treat the boundaries between lanes as places to connect rather than places to stop.

So is it a helpful phrase or not?

Here is where I have landed, at least for now.

Stay in your lane is helpful when it means knowing your role and bringing your full expertise to it. It is unhelpful when it becomes permission to disengage from everything else.

Heidi put the distinction better than I could. Staying in your lane is useful, she said, when it means drawing on your best and highest use. It becomes a problem when it means sticking your head in the sand, pretending the other lanes do not exist, or being too afraid to ask questions and find the connections across them.

That latter stalls progress every time.

The real skill is not choosing between staying in your lane and crossing into everyone else’s. It is holding both. Knowing your lane deeply, and staying curious about everyone else’s. Owning your patch, and lifting your gaze to the whole.

The best teams I work with do not ask people to abandon their lane. They build enough psychological safety and shared accountability that people feel able to contribute beyond it. To put a hand up in a meeting that is not strictly theirs. To ask the question no one else is asking. To make the call that is right for the organisation, not just their corner of it.

So next time you hear stay in your lane, it might be worth pausing. Is it creating clarity? Or is it quietly building a wall? Because the goal was never for everyone to drive in perfect parallel lines. The goal is for the whole team to arrive somewhere together.

Frequently asked questions

What does “staying in your lane” mean at work?

It usually means sticking to your own role,expertiseand responsibilities rather than involving yourself in others’ areas. Used well, it creates role clarity and respect for expertise. Used poorly, it becomes an excuse to disengage from anything outside your immediate patch, which drives silos.

Is staying in your lane good or bad for teams?

Both, depending on how it is applied. It is helpful when it means working to your highest and best use and trusting others to do the same. It is harmful when it stops people contributing diverse perspectives, slows cross-functional collaboration, or erodes a One Team mindset.

How do you break down silos without losing role clarity?

Keep clear roles and decision rights, then deliberately build the connections between them. Make interdependencies visible, shift some meetings from status updates to shared decisions, and recognise collaboration as well as individual delivery. Strong psychological safety and collective accountability let people contribute beyond their lane without confusion about who owns what.

Work with Claire

Silos rarely fix themselves, because the behaviours that create them feel safe to the people inside them. This is the work I do with leadership teams: helping them keep role clarity while building the trust and collective accountability that let people collaborate across boundaries. If your team is pulling into its lanes when you need it pulling together, let’s start a conversation about team coaching. You can also hear more conversations like this on theThriving Leaders Podcast.