Tag Archive for: team

The Cost of Silence: Why Working Around That Coworker Problem Is Killing Your Productivity

Stop Wishing it Would Get Better—Here’s Why You Need to Speak Up Now

The Lingering Annoyance

You know the feeling. It’s that one specific thing with a coworker or team member that has been quietly gnawing at you for weeks, maybe even months.

It might be:

  • The deadlines that are constantly missed.
  • The small tasks that are consistently dropped.
  • The subtle, yet unmistakable, weird vibe in team meetings.

We’ve all been there, convincing ourselves with the same tired lines: “Maybe it’ll get better on its own. Maybe I’m overreacting. Maybe if I just work around it one more time…”

Here is the tough love you need: It won’t get better. You’re not overreacting. And you cannot successfully work around a core team issue forever.

The Four Ways Your Silence Is Costing You

When you choose to stay quiet, you aren’t being kind—you are simply choosing short-term comfort. And that comfort has a steep price tag for you and your team.

1. Exponential Growth of the Problem

That small annoyance is not static; it’s compounding. Every day the issue goes unaddressed, it becomes more normalized and more deeply ingrained in the person’s work habits. What was once a small course correction now requires a major intervention.

2. The Hidden Drain on Team Morale

If you see the issue, guaranteed, everyone else on the team sees it too. The resulting low-level anxiety and tension are what create that “weird vibe” in meetings. People are talking about the problem, but they are talking about it around the person, not to them. This erodes trust and makes the whole environment heavier.

3. You Are Paying the Compensation Tax

Look closely at your own task list. Are you staying late? Are you double-checking work that shouldn’t need it? When a team member consistently falls short, you—and others—are forced to fill the gap. You are essentially paying a Compensation Tax on your own time, energy, and productivity to make up for someone else’s gap.

4. The Conversation Gets Harder, Not Easier

The longer you wait, the more history you have to unpack. It is far easier to say, “I noticed this on the last two reports,” than to say, “For the last two months, your performance has been an issue.” Delaying makes the necessary conversation feel higher-stakes, more emotional, and more career-limiting than it needs to be.

The Shift: From Avoidance to Action

The core of this issue is recognizing that you are not being kind by staying quiet; you are just being comfortable. And that comfort is actively costing you your time, your energy, and your team’s ability to trust.

What if you could confidently have that conversation—the one that solves the problem—without it being awkward, messy, or detrimental to your professional relationship?

It is possible to navigate these difficult conversations with grace, clarity, and a focus on positive results. You need the right framework, the right language, and the confidence to speak up.

Ready to Stop Working Around the Problem?

If you’re tired of sacrificing your sanity and productivity to avoid a five-minute conversation, it’s time to learn how to lead through conflict.

Let’s discuss strategies for transforming difficult conversations into productive outcomes.

➡️ Schedule a time to discuss how to navigate these conversations here:

5 Minute Communication Game Changer: SPARK

Does any of this resonate with you?

 

“I don’t know why communication is such a struggle!”

“Performance from some team members just isn’t where it needs to be.”

“I’m constantly fixing things and putting out fires. There just aren’t enough hours in the day.”

 

These are statements I hear from leaders all the time as they grind through misaligned expectations, communication break downs, accountability challenges and fixing the issues left behind by poor performance.

 

It’s painful, but it doesn’t have to be this way.

 

What if told you there is a simple, effective communication method that will save you time, help your team perform at their best and free you up to focus on the work that matters instead of running from fire to fire?

 

It’s called the SPARK method and, it takes 5 minutes or less.

 

Imagine a member of your team is taking on a task or project. This is a perfect time to use SPARK. Here’s how it works:

 

Set Expectations:

Collaboratively determine the expectations of the task. What’s the basic criteria like deadline? What does success look like? Are there barriers that need to be removed or other tasks that need to be reprioritized to meet expectations? Invest the time to get clear here-it will save you a ton of time and frustration later.

 

Purpose:

Whenever starting a task or project, no matter how big or small, you must explain the WHY. Not only does this give context, but it helps you move the team beyond a task master mindset. Ignite their engagement by showing them how their work connects with the bigger goal or strategy.

 

Action & Attention:

I once two weeks researching and compiling a competitive analysis report at my manager’s request.  I walked into his office to present my findings feeling very confident about the final product. My manager took one look at my report and said, “this isn’t really what I was looking for.” All of that time and energy wasted and I still missed the mark. Ouch.

 

You see, my manager did a great job explaining the expectations and the purpose of the project, but then he left me to my own devices. He trusted me to take action, but he didn’t follow up with attention. There was no check in to make sure I was on the right track.

It’s not enough to set expectations and communicate the purpose. To ensure the right actions are taken to get the project done, you must give that team member and that project a measure of attention.

 

This is the step that is most often skipped by leaders with the universal reason, “I don’t have time to check in and give attention to every person and project on my team.”

 

So, let me ease your mind. When I say “give attention” I’m talking about a regular, proactive check in. This could be a chat on Teams, a text, a quick call or popping into a team member’s workspace. The intention is to check in on progress and action, answer questions and remove anything standing in the way of success. When done effectively, this should take you less than 5 minutes.

 

Real Time Feedback & Coaching:

Since you’re already checking in and giving your attention and support, this is the perfect time to offer real time feedback, advice and coaching, both positive and constructive.

 

If the project or task is on the right track, offer specific kudos. If things are not on track, this is the time to course correct.

 

Had my manager taken this step with me, it would have saved us both a lot of time and the project would have been a success…the first time around.

 

Keep it Going:

Keep the communication going. If there was a correction to be made from real-time feedback and coaching, this is the place to follow up on it.

 

When the task or project is complete, this is where you compare the initial expectations with the final results.

 

These conversations are the most powerful when they’re ongoing.

 

The SPARK method can be used in team meetings, 1:1 conversations, your daily standing meetings and even in conversations you have with your boss. The best part-these conversations take 5 minutes or less.

 

Would you like to reclaim your time? Would you to communicate with impact and help your team do the same? Would you like to take the pain out of performance conversations? Then give the SPARK method a whirl.  

Not getting what you expect? This could be why

I handed Maya the crucial product comparison project with visions of a meticulous, organized Excel spreadsheet complete with a concise summary of findings.

 

Unfortunately, what I received was not even close to what I envisioned.

 

A week later, there we were, huddled around a table, surrounded by endless pages of raw data, most of which we couldn’t make heads or tails of. Maya tried to explain some initial observations, but there was no comprehensive report, and no succinct summary.

 

Our frustration and disappointment were palpable. Maya, because she genuinely believed she had delivered precisely what I wanted. And me, because an entire week had slipped through our fingers with almost nothing to show for it. The looming project deadline was dark cloud on our calendar.

 

So what went wrong?

 

It was a disaster, and the blame rested squarely on my shoulders. I had failed to communicate my expectations clearly, and I hadn’t bothered to ask Maya about hers. I made careless assumptions that led us down this path.

 

I assumed Maya’s past successes were an automatic guarantee of success this time-even though she had never done a project list this. I thought she instinctively knew what data to collect and how to present it. When she didn’t come to me with questions or concerns, I naively believed she was on the right track. Those assumptions, those shortcuts, cost us big time. They cost us precious time, wasted effort, and pushed the entire project perilously close to the brink of failure.

 

But there is a way out of this chaos. It’s called mutual expectations.

 

These conversations are lifelines that answer the critical questions of when, what, how, and why tasks should be done. They form the bedrock of performance and the linchpin of accountability.

 

Imagine a world where both you and your team members share a common understanding. This world is brimming with confidence because there’s a clear, agreed-upon roadmap. Desired outcomes are defined; measurements of success are crystal clear. No one is in the dark.

 

In our case, we hadn’t had those discussions. We hadn’t talked about the results we were aiming for or what the finished product should even look like. Maya was left stumbling in the dark, unaware of what specific information to gather, where to find it, how to assess its relevance, or even how to present it. The ‘why’ was absent too, which left us all adrift.

 

But it doesn’t have to be that way. There is a straight forward process to ensure clear, mutual expectations. Simply follow these steps:

  1. Clearly explain the project and emphasize its importance.
  2. Define the desired outcomes and success metrics.
  3. Lay out the steps, share necessary resources, and be explicit about the project’s boundaries.
  4. Ask questions, offer support, and clarify expectations. Can they handle it? Do they have the bandwidth? What questions do they have? What do they expect from you during this project?
  5. Most importantly, ensure that everyone is on the same page and document those expectations for reference.

 

Don’t make the costly mistake of assigning a project and saying, “Let me know if you have questions.” Instead, regularly check in with your team members. Address any questions, tackle minor challenges before they become colossal obstacles.

 

These expectation conversations aren’t limited to specific projects. They are your lifeline during team meetings, one-on-ones, role changes, shifting priorities, system updates, process alterations, or policy revisions.

 

I guarantee you, when you establish mutual expectations, you will see results. Work becomes seamless, efficient, and your team? They’re infused with newfound confidence and a sense of ownership that propels them to unprecedented heights. The solution is right there – it’s mutual expectations, and it’s your ticket to success.