Quick answers
- How do you explain a blocker?
- State the blocker, impact, what you've tried, and what you need.
Key takeaways
- State the blocker, impact, and what you've tried.
- Be specific.
- Raise early.
- Suggest next steps when you can.
Instead of → Say
| Instead of | Say |
|---|---|
| I'm stuck | I'm blocked on the deployment. I need production credentials. I've submitted the access request. |
| Something is wrong | CI is failing on the new test. I've isolated it to the auth mock. I'm debugging. |
| I can't continue | I'm waiting on the API design from backend. I've pinged them. Can we escalate? |
Example dialogue
You: I'm blocked on the auth integration. We need a staging token from DevOps. I've requested it—it's been two days. Can someone follow up?
Manager: I'll chase that. Can you switch to the fraud task meanwhile?
You: Yes. I'll pick the auth back up when we have the token.
Common mistakes
- Being vague.
- Waiting too long.
- Not saying what you've tried.
Frequently asked questions
- When should I raise a blocker?
- As soon as it prevents progress. Don't wait for the next standup.
- How do I explain a technical blocker?
- State what's failing, why it matters, and what you've tried. Offer to switch tasks if useful.
Related
Ready to practice?
Try a scenario with AI and get feedback on your communication.
Start practicing