Choose the most professional and effective way to report blockers, ask for help, and follow up — in 5 realistic IT scenarios.
Blocker reporting — 5 key phrases
"I'm blocked on [task] — waiting on [person/team] for [specific item]."
"I need help with [specific thing] — could [person/team] [action]?"
"Can someone take a look at PR #[number]? It's been open for [time]."
"In the meantime, I'll [alternative work] so I'm not idle."
"Quick update: [blocker] is resolved — I'm unblocked on [task]."
0 / 5 completed
1 / 5
You can't continue with your task because you're waiting on database access credentials from the DevOps team. How do you raise this blocker professionally?
A complete blocker statement has four parts: task + cause + action taken + ETA. "Blocked on the user analytics feature" names which task is blocked. "Waiting on database read credentials from DevOps" names the exact dependency. "I've already sent a request — ticket #OPS-441" shows you're not passive — you've acted. "ETA is tomorrow morning" tells the team when to expect resolution. Compare: "I'm blocked" tells the team nothing. "DevOps hasn't given me what I need" sounds like blame without context.
2 / 5
You need a code review from a senior engineer but they haven't responded for 2 days. How do you raise this in standup without sounding passive-aggressive?
State the fact, show the urgency, offer a path forward without blame. "I don't want it to block the sprint" signals awareness of team impact. "Is there anyone available to review it?" offers an alternative solution. "Should I ping [senior engineer] directly?" asks for permission to escalate — professional and collaborative. Saying someone is "ignoring" your PR is inflammatory. "Not sure what's happening" sounds passive. Raise the concern, propose solutions.
3 / 5
You're blocked because the API specification you need to implement against hasn't been finalized. Which response is most helpful for your team lead?
Blocked does not mean stopped — show what you're doing while you wait. "I can start with mock data in the meantime" demonstrates initiative and avoids dead time. "Before I can write the integration tests" clarifies exactly what the dependency gates. "Can we get a confirmation date?" makes a specific, actionable request to the team lead. "As usual" is sarcastic and unprofessional. Never express frustration in standup — focus on facts and next steps.
4 / 5
You're not technically blocked, but you're struggling with a complex algorithm and think you need help. How do you ask most professionally?
Distinguish between "blocked" (cannot proceed) and "could benefit from help" (can proceed but slowly). "I'm not blocked, but..." is an honest framing. "Pair-programming session on the graph traversal algorithm" names the exact type of help needed. "Someone with graph experience" targets the right kind of helper. "For an hour this afternoon" is a bounded, reasonable ask. Vague requests like "I might need help at some point" make it impossible for teammates to plan or volunteer.
5 / 5
Your blocker was resolved overnight. How do you update the team at the next standup?
When a blocker resolves, close the loop clearly — reference the original ticket or issue. "Ticket #OPS-441 is resolved" links directly to the item mentioned yesterday, helping anyone who missed the previous standup. "I'm unblocked and back on the analytics feature" gives a clear current status. "No issues now" is the clean sign-off. This kind of follow-through shows professionalism and helps the team lead track blockers. "My blocker is gone" is acceptable but lacks the specificity that builds team trust.