Photo by Mariia Berezovsky on Unsplash
In my last post, I wrote about what happens when communication breaks down: decisions stall, priorities become unclear, and small gaps in accountability can eventually create very real operational consequences.
But recognizing the need for clarity is one thing. Asking for it—particularly when you are waiting on a peer, senior leader, or another department—is another.
Many leaders struggle with the follow-up. They don’t want to appear impatient, overstep, or create unnecessary tension. So they wait. Or they send a vague “just checking in” message that is easy to overlook and does little to move the work forward.
There is a better approach.
Effective follow-up is not about applying more pressure. It is about providing more context. Instead of simply asking someone for an answer, explain what depends on that answer. “I need your decision by Wednesday” can feel like a demand. “We need a decision by Wednesday in order to keep production on schedule” communicates the same urgency while also explaining why it matters.
That distinction is important. When people understand the impact of their response—or lack of one—they are better equipped to prioritize. You are no longer asking them to respond simply because you need something. You are giving them information they need to make a decision about the work.
The same principle applies when priorities compete. Rather than repeatedly pushing for your request to move to the top of someone’s list, ask for clarity about where it belongs. “If this needs to move behind the other priorities this week, that’s fine. I just need to understand the timing so we can plan accordingly.”
That is not passive, and it is not aggressive. It is clear.
Strong leaders learn how to create urgency without creating unnecessary friction. They communicate the need, connect it to the broader impact, and give the other person an opportunity to respond or reprioritize.
Sometimes leadership means making the decision. Other times, it means making it easier for someone else to make one.
Either way, the goal is the same: less ambiguity, better alignment, and work that keeps moving forward.
