Command Palette

Search for a command to run...

Blog

Programmes Fail at the Handoffs

In development and corporate programmes alike, results are lost between teams rather than inside them.

Working with a consulting team supporting foundation-funded programmes, I saw a pattern that I had also seen in a factory and a bank branch: the work inside each team is usually fine. Results are lost at the handoffs.

Where handoffs fail

Between design and delivery. A programme designed in an office meets a different reality in the field. If field teams cannot feed back quickly, the design does not adapt.

Between delivery and measurement. Data collected for reporting is often not the data needed to improve the programme.

Between funders and implementers. Reporting requirements can crowd out the work itself if nobody asks which reports are actually used.

What helps

  • A single owner for each outcome, not just each activity.
  • Short feedback loops: monthly learning conversations rather than annual evaluations.
  • Fewer, better indicators that the people doing the work also find useful.
  • Written assumptions, so that when results disappoint, the team can see which assumption failed.

The general lesson

An example of a handoff going wrong

Imagine a skilling programme. The design team defines the curriculum, a training partner delivers it and a placement team connects graduates to employers. Each team meets its own targets: courses designed, people trained, interviews arranged. Yet placement rates disappoint.

When someone finally walks the full journey, the gaps appear. The curriculum was designed around job roles that local employers no longer hire for. Trainers noticed but had no channel to report it. Placement staff found employers wanted skills not covered, but their feedback went into a quarterly report nobody in design read. Every team did its job; the programme still failed.

How to find handoff problems

  • Follow one beneficiary, customer or order from start to finish and note every point where responsibility changes hands.
  • Ask each team what they receive and what they pass on, and whether either is ever late, incomplete or wrong.
  • Look for information that is collected but never used. It usually marks a broken loop.

Designing for handoffs

Good programmes assign an owner to the end result, not only to each stage, and give that owner the authority to change the earlier stages. They also build in short, regular conversations between teams, because written reports rarely carry the nuance that makes feedback useful.

A test for leaders

Ask any team leader two questions: who receives your work, and when did you last ask them whether it was useful? If the answers are vague, there is a handoff problem waiting to be found. In my experience, fixing one important handoff often improves results more than any new initiative.

Organisations draw boxes on charts. Outcomes travel along the lines between the boxes. Anyone trying to improve results, in a charity, a company or a government, should map those lines first.

Command Palette

Search for a command to run...