Logo
Tutorials Articles Code Playground
Sign In Get Started
Module: Meetings and standups

Explaining blockers

Explaining Blockers in Meetings & Stand-ups

When working in software development, encountering roadblocks is inevitable. Effectively communicating these "blockers" is crucial for team progress. Here's how to do it clearly and professionally in meetings and stand-ups:

I. What is a Blocker?

A blocker is anything preventing you from completing your current task or making progress towards your sprint goal. It's not just a difficulty; it's something that stops you. Examples:

  • Dependency Issues: Waiting on another team, a specific API, or a third-party service.
  • Technical Challenges: A bug you can't resolve, a complex integration issue, or a lack of necessary knowledge.
  • Access Problems: Missing permissions, inability to access environments, or unavailable tools.
  • Information Gaps: Unclear requirements, missing documentation, or needing a decision from a stakeholder.
  • External Factors: Unexpected urgent requests, critical production issues requiring immediate attention.

II. Key Principles for Explaining Blockers

  • Be Concise: Respect everyone's time. Get to the point quickly.
  • Be Specific: Avoid vague statements like "I'm stuck." Provide details.
  • Focus on Impact: Explain why it's a blocker and how it affects progress.
  • Suggest Potential Solutions (if possible): Demonstrates initiative and problem-solving.
  • Request Specific Help: Clearly state what you need from others.
  • Be Proactive: Don't wait until the last minute to raise a blocker.

III. Phrases & Sentence Starters (for Stand-ups & Meetings)

A. Identifying the Blocker:

  • "I'm currently blocked on..."
  • "I'm waiting for... which is preventing me from..."
  • "I've hit a roadblock with... because..."
  • "I'm unable to proceed with... due to..."
  • "I'm facing an issue with... which is impacting my ability to..."

B. Providing Details (Specificity is Key!):

  • Instead of: "The API isn't working."

  • Try: "I'm blocked on the user authentication API. I'm receiving a 500 error when attempting to retrieve a token, and I've confirmed the request parameters are correct. I've checked the API documentation and haven't found a solution."

  • Instead of: "I need help with the database."

  • Try: "I'm blocked on updating the database schema. I'm trying to add a new column to the 'users' table, but I'm concerned about potential data migration issues. I'd like to discuss the best approach with [Name] to avoid downtime."

C. Requesting Help:

  • "Could someone with experience in [technology/area] take a look at this with me?"
  • "I need [Name] to review [document/code] so I can move forward."
  • "I'm hoping [Name] can help me get access to [environment/tool]."
  • "I need a decision on [question/requirement] from [Stakeholder] to proceed."
  • "I'd appreciate any suggestions on how to resolve this issue."

D. Suggesting Solutions (Demonstrates Initiative):

  • "I've tried [solution 1] and [solution 2], but neither worked. I'm thinking [potential solution 3] might be a viable option."
  • "I believe the issue might be related to [potential cause]. I'm planning to investigate further, but any insights would be helpful."
  • "Perhaps we could schedule a quick pairing session to troubleshoot this together?"

IV. Example Stand-up Updates:

  • Good: "I'm blocked on getting access to the staging environment. I've submitted a request to IT, ticket number is #1234. I'm hoping to have access by this afternoon so I can continue testing the payment integration."
  • Good: "I'm blocked on the design specs for the new user profile page. I've reached out to [Designer's Name] for clarification on the layout. I'll continue working on the backend logic in the meantime."
  • Less Effective: "I'm stuck on the user profile page." (Too vague - doesn't explain why or what help is needed.)

V. Important Considerations:

  • Don't Blame: Focus on the problem, not who caused it. Avoid accusatory language.
  • Be Honest: Don't downplay blockers or try to "tough it out" if you genuinely need help.
  • Follow Up: If a blocker isn't resolved immediately, follow up with the relevant people after the meeting.
  • Document: Keep a record of blockers and their resolutions for future reference. (e.g., in your project management tool).

By following these guidelines, you can effectively communicate blockers, minimize delays, and contribute to a more productive and collaborative team environment.