Guide · 8 minute read

Why plans don't become results

Most strategies, programmes and personal goals don't fail everywhere at once. They stall at one point, the binding constraint, while everyone works hard on everything else. More effort spread across the plan doesn't close the gap. Finding and removing that one constraint does. This guide gives you four practical steps, each with a worked example, to do it in about 20 minutes.

The weakest link sets the pace

A team with a clear goal, strong skills and good funding will still stall if nobody owns the decision that unlocks the work. Systems thinkers call this a leverage point; operations people call it the bottleneck. The idea is the same: progress moves at the speed of the weakest part, so reports that average everything out hide the real problem.

This is why well-funded plans with talented teams still disappoint. The money and talent pour into parts of the plan that were never the limit, while the one blocked part quietly decides the outcome.

Find your binding constraint in 20 minutes

Do this alone or with your team. Write answers down — a constraint nobody writes down stays vague enough to ignore.

1. 1. Write the result, not the activity

   5 min

   State the change you want to see in the world in one sentence, with a date. "Train 400 farmers" is an activity. "400 farmers selling at the district market by June" is a result. If you can't picture the evidence, the plan is still an intention.

   Example: a district health team rewrites "run 12 radio talk shows on immunisation" as "measles vaccination coverage in Karamoja up from 61% to 75% by December, verified in the DHIS2 monthly report." Now everyone knows what done looks like, and a radio show that doesn't move the number can be questioned.

2. 2. Score the seven drivers honestly

   5 min

   Rate each from 1 to 5: clarity of the result, ownership, capability, resources, incentives, feedback, and alignment of the people involved. Then name the three forces draining energy: friction, drift and competing priorities. Don't average. The lowest score limits everything above it.

   Example: a small NGO scores itself clarity 5, resources 4, capability 4 — but ownership 2, because three people "share" the result and nobody's week is shaped by it. That 2 is the plan's real speed limit, no matter how good the rest looks in the annual report.

3. 3. Name the one binding constraint

   5 min

   Ask: if this one thing were fixed, would the others start moving on their own? The constraint is usually not money. It's often unclear ownership, no feedback loop, or a decision nobody is allowed to make. Pick one. Fixing three things at once fixes none.

   Example: a county roads programme kept requesting more budget. The 20-minute check showed the real constraint was that no engineer could approve a variation under 5 million shillings without a committee that met quarterly. One delegated authority later, stalled works restarted within a fortnight — with the same budget.

4. 4. Choose two moves and an evidence test

   5 min

   Pick at most two actions that attack the constraint directly, and for each write what you'll see when it has worked: a document signed, a number changed, a behaviour observed. Effort doesn't count. Check again in two weeks and close the move only when the evidence is there.

   Example: for the ownership problem above, move one is "name a single accountable owner in writing by Friday" — evidence: the signed delegation letter. Move two is "owner reviews the result number every Monday" — evidence: four consecutive weekly review notes. Both are verifiable; neither is "work harder".

A full worked example, start to finish

A youth-employment programme in Kampala had trained 2,000 young people but placed fewer than 200 in work. The team assumed they needed more training places. Running the four steps told a different story:

• Result rewritten: "600 graduates in verified paid work within 90 days of completing training, by March."
• Lowest driver: feedback, scored 2 — nobody tracked what happened to graduates after the ceremony.
• Binding constraint: no employer relationships. Training was supply; nobody owned demand.
• Two moves: appoint one employer-liaison owner (evidence: signed role letter), and sign ten employer commitments before the next cohort starts (evidence: ten letters of intent).

Six months later placements had tripled — without adding a single training place. The plan didn't need more effort; it needed the constraint named.

Common traps

• Treating a busy activity report as proof of progress.
• Naming "lack of funds" before checking ownership and feedback.
• Launching ten fixes at once so nobody can tell which one worked.
• Never going back to check whether the change actually happened.
• Choosing a constraint that is comfortable to work on instead of the one that is binding.

Related guide

If your plan is sound but nothing is happening, read why strategy execution fails — the seven predictable places a chosen strategy breaks, and the specific fix for each.

Questions people ask

What is a binding constraint?

The single weakest part of a plan that limits the whole thing. Like the narrowest section of a pipe, it sets the flow for everything else. Improving any other part while it stays blocked changes nothing.

Why not fix several problems at once?

Because you stop being able to tell what worked, and attention is itself a limited resource. Fix the binding constraint first; when it moves, re-run the check — a different constraint usually takes its place, and you repeat.

Does this work for personal goals too?

Yes. The same four steps work for a national programme, a company target or a personal goal. The drivers are the same; only the scale of the evidence changes.

How often should I re-check the constraint?

Every two to four weeks, or whenever a move closes. Constraints shift as you fix them, so the diagnosis is a habit, not a one-off workshop.