Map Your Top Three Communication Bottlenecks — and Fix One Before Monday.

Most communication problems persist because the fix seems too big. Here’s how to make it small enough to actually do this week.

Most communication problems aren’t mysterious. If you asked the people experiencing them, they could probably name them immediately: the decision that always seems to route back to the founder, the handover that always generates questions, the client conversation that always starts with the same misaligned assumption.

The reason these problems persist isn’t that they’re hard to diagnose. It’s that the fix always seems larger than the bandwidth available. Addressing them feels like a project — something to get to when things are less busy, when there’s more time, when the current sprint is done.

This week’s tip removes that excuse by making the fix as small as possible. Not a project. One concrete action. Before Monday.

The Real Problem

Tolerating a communication bottleneck has a compound cost. Every week it remains unfixed, it generates the same friction, the same rework, the same delay. The cost isn’t one-off — it’s recurring. And the total cost of not fixing it, accumulated across weeks and months, is almost always far larger than the cost of the fix itself.

The mental accounting error is treating the fix as a large cost (a project, a conversation, a system to build) and the tolerance as a small cost (just the friction of this week). But the tolerance recurs. The fix is one-off. When you run those numbers honestly, the case for fixing it is usually clear.

The Big Idea

Identifying your most costly communication bottleneck and taking one targeted action to fix it — even a small action — is more valuable than a comprehensive communication improvement plan that never gets started. Progress beats planning. Small fixes compound. One problem solved this week is one that won’t cost you next week.

How to Make It Work

1. List Your Top Three

Set a timer for 10 minutes and write down the three communication patterns in your business that cause the most recurring friction. Be specific — not ‘communication is unclear’ but ‘when I brief a task, I always get follow-up questions about X.’ Not ‘meetings are ineffective’ but ‘our Tuesday check-in regularly ends without a clear decision on Y.’

The specificity is what makes the next step possible.

2. Identify the Most Costly

Of your three, which is generating the most operational cost right now? Not necessarily the most annoying or the most visible — the most costly in terms of rework, delay, or eroded trust. That’s your target.

This distinction matters because easy fixes aren’t always the most valuable fixes. Start with the one that’s costing you the most, even if it’s not the most straightforward.

3. Design One Concrete Fix

Based on the bottleneck pattern you’ve identified, choose one specific action from this list: write a decision authority document that clarifies what can be decided without you; create a brief template that pre-answers the most common follow-up questions; establish a meeting-outcome protocol with a named decision-maker and documented next steps; or have the 10-minute conversation that addresses the assumption that’s been running unchecked in the background.

One action. Concrete and completable before Monday.

4. Do It, Then Tell Someone

Complete the action this weekend. Then — and this part matters — tell the people affected. Not as a grand announcement. Just a clear, simple communication: ‘I’ve set up X to address Y. Here’s how it works and what it means for you.’

The action fixes the bottleneck. The communication ensures the fix is visible and usable. Both are necessary.

Why This Works

Small, targeted fixes to communication patterns compound across weeks and months. One bottleneck cleared this week means one less recurring friction next week, and the week after that, and the week after that. Over a quarter, the operational difference between a business that systematically fixes its communication bottlenecks and one that tolerates them is significant.

🛍️ RESOURCE
If your communication bottleneck shows up in client onboarding — unclear expectations, repeated clarifying questions, mismatched assumptions at the start of an engagement — the Client Onboarding Hub in my Etsy shop builds the structure that prevents those patterns from the very first interaction → ETSY LINK

The Real Goal

A business where communication problems get fixed — not tolerated — as a matter of operational habit. One bottleneck per week is a pace that produces significant results over a quarter without requiring a major project. That’s the compound return on small, consistent action.

💬 Your Turn

What’s the one communication bottleneck you’re going to fix before Monday?
Name it in the comments.
Naming it publicly is often the commitment that makes it actually happen.

⏭️Up Next

Next week is an Operationally Speaking week — we’re looking at Decision Latency, the hidden delay between when a decision could be made and when it actually gets made, and what it costs. See you Monday.

Similar Posts

  • Knowing the Lesson Doesn’t Mean You’ve Learned It

    At Amazon, I used to sit new starters down and walk them through it: watch what I do, not what I say. If I said we protected focus time but answered every ping in thirty seconds, that was the real rule, and they’d copy the real rule, not the stated one. I could explain that…

  • Batch Your Decisions. Build Your Defaults.

    Two operational habits that directly tackle Decision Fatigue — and give your best thinking back to the work that deserves it. This week we’ve been unpacking Decision Fatigue — the cognitive depletion that comes from too many low-level decisions reaching you before the important ones do. Today’s post is about the fix. Not the mindset…

  • You Can’t Delegate What No One Can See

    For a while I was the office manager at an NGO, which is a job title that meant almost nothing about what I actually did. On paper it was reception, some admin, ordering supplies. In practice I was also doing the accounts payable, half the procurement, and quietly keeping track of which grant reports were…

  • The Meeting That Outlived Its Usefulness

    For the first six months of running YVO, my invoicing was a mess in exactly one way. Not the numbers — those were always right. The timing. Some months invoices went out within a day or two of the work being done. Other months they went out two, three weeks late, whenever I happened to…

  • A Business Without SOPs Is Renting Its Success.

    Every time you fix the same problem twice, you’re paying rent on a business that should own its processes by now. Here’s how to start building instead. Here’s a question worth answering honestly: how many times this week have you explained something that already happened last week? The same onboarding question. The same client communication…

  • The Quick Question That Wasn’t Quick At All

    Years ago, when I was doing web design work, I had a client who loved to send “quick questions.” A message about a font choice on a Tuesday morning. A call about a broken link on Wednesday afternoon. A five minute favour to check whether something looked right before they showed it to their own…

Leave a Reply

Your email address will not be published. Required fields are marked *