Practice : Obstacle Removal as a Leadership Practice

Purpose and Strategic Importance

Obstacle Removal as a Leadership Practice is the structured discipline of leaders actively seeking, escalating, and resolving the impediments that prevent teams from doing their best work. It positions leaders not as directors of work but as enablers of it — using their authority, influence, and cross-boundary access to clear the path for those doing the delivery.

Teams face obstacles every day that they cannot resolve alone: policy constraints, cross-team dependencies, tooling gaps, unclear ownership, and organisational friction. Leaders are the only people with the positional access to address many of these. When they treat obstacle removal as a primary leadership responsibility — not a distraction from "real work" — they unlock disproportionate delivery value.

Description of the Practice

  • Leaders actively solicit obstacles from teams in regular cadences, not just when escalated to.
  • Obstacles are categorised: what can the team resolve, what needs the leader, what requires cross-boundary escalation.
  • Leaders track open obstacles to resolution, not just acknowledgement.
  • Systemic obstacles — those appearing repeatedly across teams — are addressed at their root.
  • Leaders measure team impediment burden and treat reductions as a delivery improvement metric.

How to Practise It (Playbook)

1. Getting Started

  • Ask in every team meeting: "What is slowing you down right now? What do you need that you do not have?"
  • For every obstacle raised, categorise: can the team resolve it? Can you resolve it now? Does it need escalation?
  • Act on at least one obstacle per week and close the loop with the team: "I resolved — here's what I did."
  • Track open obstacles — a log visible to the team demonstrates that obstacles are being taken seriously.

2. Scaling and Maturing

  • Create a standing impediment backlog — visible, prioritised, and owned.
  • Look for patterns: if the same type of obstacle recurs, address the systemic cause, not just each instance.
  • Use cross-leader forums to address obstacles that cross team boundaries — don't let these stall at the seam.
  • Measure reduction in time lost to impediments as a leading indicator of flow improvement.

3. Team Behaviours to Encourage

  • Teams surface obstacles early rather than working around them silently.
  • Individuals feel confident that raising an obstacle will result in action, not just acknowledgement.
  • Teams distinguish between obstacles they can self-serve and those that genuinely require the leader.
  • Obstacle removal creates visible momentum — the team sees progress on what was blocking them.

4. Watch Out For…

  • Leaders who acknowledge obstacles but take no action — this is worse than not asking.
  • Treating every obstacle as the team's problem to resolve, removing the leadership accountability.
  • Addressing symptoms (this specific blocker) without addressing causes (why this type of blocker keeps appearing).
  • Leaders who create obstacles through their own governance requirements, then expect teams to work around them.

5. Signals of Success

  • Teams raise obstacles earlier because they trust that action will follow.
  • The average time an obstacle remains open decreases over time.
  • Systemic obstacles are addressed at root, not just managed individually.
  • Teams report that the leader is one of their most effective unblocking resources.
  • Delivery velocity and flow metrics improve as the impediment burden reduces.