Clearing Blockers for Your Team

In cross-team work, blockers often appear as delays, unclear ownership, or conflicting priorities. You might see a team member waiting on another department for

Level: Team lead
Setting: Cross-team
Core skill: Removing friction
Common pitfall: Blaming the team
Practice to try: A weekly blocker sweep

What this looks like in real work

In cross-team work, blockers often appear as delays, unclear ownership, or conflicting priorities. You might see a team member waiting on another department for a decision, or a project stalled because two teams have different definitions of "done." These are not personal failings; they are systemic friction points that slow everyone down. As a team lead, your role is to spot these friction points early and clear them so your team can keep moving.

For example, a developer might be blocked because the design team hasn't finalized a component. Or a marketer might be waiting on data from analytics to launch a campaign. In each case, the blocker is not the person; it's the gap between teams. Your job is to bridge that gap, not to assign blame. When you clear blockers, you show your team that you are there to support them, not to judge them.

Real work is messy, and cross-team dependencies are a fact of life. The most effective leads treat blockers as puzzles to solve together, not as evidence of incompetence. They ask, "What's in the way?" and then work to remove it. This mindset shift is the foundation of clearing blockers effectively.

Why it trips people up

Many new leads fall into the trap of thinking their job is to manage people, not to manage the work environment. When a blocker arises, they might instinctively look for someone to blame—often the team member who is stuck. This reaction is understandable but counterproductive. It creates a culture of fear, where people hide problems instead of surfacing them. Over time, this erodes trust and slows everything down.

Another reason it trips people up is that clearing blockers requires cross-team influence, which can feel uncomfortable. You might not have authority over the other team, so it's easier to push your own team harder rather than negotiate with peers. But pushing harder doesn't remove the blocker; it just adds pressure. The real work is in building relationships and understanding the other team's constraints.

Finally, some leads confuse busyness with progress. They see their team working long hours and assume everything is fine, missing the subtle signs of blockage. By the time the blocker becomes obvious, it has already caused delays and frustration. Recognizing these traps is the first step to avoiding them.

The mistake that quietly hurts

The most damaging mistake is blaming the team when things stall. It's a quiet killer because it often goes unspoken. You might not say it outright, but your tone, your questions, or your body language can convey disappointment. Team members pick up on this and start to feel that they are the problem. They become defensive, less likely to ask for help, and more likely to burn out.

Blaming the team also misses the root cause. If someone is blocked, it's usually because of a process gap, a misalignment, or a resource constraint—not because they are lazy or incompetent. By focusing on the person, you ignore the system that created the blocker. This leads to quick fixes that don't last, and the same blockers reappear.

Moreover, blaming the team damages your credibility as a leader. People want to follow someone who has their back, not someone who throws them under the bus. When you blame your team, you signal that you are not a safe pair of hands. Trust evaporates, and with it, your ability to lead effectively. The antidote is to shift from blame to curiosity: ask what's blocking progress and how you can help remove it.

A practice you can repeat

One concrete practice is a weekly blocker sweep. Set aside thirty minutes each week to review all active work with your team and identify anything that is slowing them down. This is not a status update; it's a focused session on obstacles. Ask each person, "What is one thing that, if removed, would make your work easier this week?" Then, for each blocker, decide on a next step: who will address it, and by when.

The key is consistency. By making the blocker sweep a regular ritual, you normalize the idea that blockers are expected and that addressing them is part of the job. It also gives you a running list of friction points to tackle with other teams. Over time, you'll spot patterns—maybe a recurring dependency on another team's approval—and can work to fix the root cause.

To make it effective, keep the meeting short and action-oriented. Don't let it turn into a complaint session. Focus on solutions and ownership. After the meeting, follow up on the actions and report back on progress. This shows your team that you take their blockers seriously and that you are willing to do the work to clear them. The weekly blocker sweep is simple, but it builds a culture of removing friction rather than tolerating it.

What to say and do

When you notice a blocker, your first response should be curiosity, not judgment. You might say, "I see you're waiting on X. What would help you move forward?" This opens a conversation without assigning blame. If the blocker involves another team, you can offer to help: "Let me reach out to Y and see if we can get that decision. I'll keep you posted." This takes the burden off your team member and shows you are actively removing friction.

In cross-team meetings, use phrases that focus on the problem, not the person. For example, "It seems like we have a dependency that's causing delays. How can we work together to resolve it?" Or, "What do you need from us to unblock this?" These questions shift the conversation toward collaboration. Avoid saying things like "Why hasn't this been done?" which implies fault.

When you commit to clearing a blocker, follow through. Say, "I'll take care of this by Thursday," and then do it. If you can't resolve it, be transparent: "I wasn't able to get a commitment from the other team yet. Here's what I'm trying next." Your actions speak louder than words. By modeling this behavior, you teach your team that blockers are solvable and that you are their partner in removing them.

When the stakes get higher

When deadlines are tight or the project is high-visibility, blockers can feel like emergencies. The pressure to deliver can make you want to push your team harder, but that's exactly when blaming the team becomes most tempting—and most harmful. Instead, double down on clearing blockers. In high-stakes situations, your team needs to know you are removing obstacles, not adding to them.

You may need to escalate blockers faster. If a cross-team decision is stuck, don't wait for the weekly sweep. Reach out directly to the other team's lead and ask for a quick sync. Be clear about the impact: "This is blocking our launch on Friday. Can we get 15 minutes to resolve it?" Escalation isn't about blame; it's about prioritizing the work.

Also, consider temporarily reallocating work to reduce dependencies. If one person is blocked, can they help someone else? Can you adjust the plan to work around the blocker? High stakes require flexibility. But always keep the focus on the system, not the individual. When you stay calm and solution-oriented, you set the tone for your team. They will learn that even under pressure, the goal is to remove friction, not to find fault.

Questions new leaders ask

Q: What if the blocker is caused by someone on my own team? A: It's still a blocker, not a personal failing. Address it privately and curiously. Ask, "What's making this hard?" and work together to remove the obstacle. If it's a skill gap, provide support or training. If it's a process issue, fix the process. The goal is to help them succeed, not to punish.

Q: How do I clear blockers when I don't have authority over the other team? A: You influence through relationships and clear communication. Explain the impact of the blocker and ask for their help. Offer to make it easy for them—maybe you can provide the information they need or adjust your timeline. Most people want to help; they just need to understand why it matters.

Q: What if I can't remove the blocker? A: Be transparent with your team. Explain what you tried and what you'll try next. Sometimes you can work around it or adjust the goal. The key is to keep them informed and show that you're actively engaged. They'll appreciate your honesty and effort, even if the blocker persists.