If you're client-facing, you sit between two legitimate but often competing needs. The client wants more, faster, now. Your team needs sustainable pace, focus time, and reasonable expectations. Both are right. Your job is to manage the tension without sacrificing either.
Why this matters
Over-committing to clients burns out your team. Burnout leads to quality degradation, missed deadlines, and people quitting. Ironically, the over-commitment that was supposed to make the client happy ends up making everything worse.
Under-communicating with clients, on the other hand, creates dissatisfaction and micromanagement. The balance is about buffering your team from chaos while keeping clients informed and satisfied.
The principles
You absorb the urgency. When the client says "we need this by tomorrow," your team doesn't need to hear that panic. You translate it into something realistic: "Client has an urgent request. Realistically we can deliver by Friday. I'll manage their expectations."
Don't commit without checking. "Let me check what's realistic and get back to you" is one of the most protective phrases in your vocabulary. Never say yes to a timeline without understanding what your team can actually do.
Push back on unreasonable demands. Kindly but firmly. Your team can't do that on your behalf because they're not in the conversation. You are their advocate.
Communicate capacity honestly. "Our team is at capacity for the next two weeks. We can start this on March 1, or if it's urgent, we'd need to defer another feature. Which do you prefer?"
What good looks like
Buffering urgency: Client says they need it tomorrow. You tell the client "Let me check what's possible" and then tell the team "Client has an urgent request. What's realistic?" Then manage the client's expectations based on the real answer.
Managing capacity: "I want to be transparent: we're at capacity through the 15th finishing committed features. We can take this on after that, or if it's truly urgent, we need to decide what to push back."
Protecting quality: "We could rush this in two weeks, but quality would suffer and we'd likely need rework. I'd recommend four weeks to do it right once. Which approach fits your goals better?"
Why It Works
Buffers the team from panic. Sets honest expectations. Gives the client options. Protects quality and sustainability.
Tips
- Never commit to a timeline without checking with your team first
- Translate "ASAP" into actual dates
- Push back on unrealistic deadlines, kindly but firmly
- Protect team focus time by batching client questions
- Build buffer into estimates
- Say no to constant scope additions
- Celebrate team wins with the client to build appreciation
How this connects
This combines setting boundaries, managing expectations, gentle pushback, handling unrealistic requests, and building sustainable relationships that last because nobody burned out midway through.
Things to try
- Next urgent request: don't commit immediately. Say "let me check what's realistic."
- Track when you over-commit. What drives it? People-pleasing? Fear of losing the client?
- Build realistic buffers into every estimate.
- Batch client questions into designated times rather than interrupting the team constantly.