Communicating Delays & Blockers ยท Lesson 2 of 3

Raising a blocker

Study notesAbout 3 minutes. A full lesson with quick checks is on its way.

In short

If you're stuck, say so early and ask for exactly what you need. Silent days are days nobody can plan around.

In your work

You can't test a client's payment integration because the sandbox keys haven't arrived. By late morning you post in the team channel what's blocked, what you've tried and who you need to hear from.

What the UK rules say

  • The BCS Code of Conduct asks you to take on only work within your professional competence, so asking for help when you're out of your depth is part of the job.

What to do

  1. Set yourself a time limit before asking, such as an hour or two.
  2. Say what's blocked, what you've tried and exactly what you need.
  3. Ask in the team's usual channel, and tag the person who can help.
  4. Work on something else useful while you wait.

Watch out for

  • Waiting to be asked how it's going.
  • Asking 'any ideas?' without the details someone needs to help.

In your organisation

Where does your team raise blockers, and how quickly should you expect a reply?

Your employer's own policies come first.

Sources

UK law and guidance, explained for learning. Not legal advice.