In the summer of 2019, Henry Dimbleby sat down with a mandate few consultants ever get. The UK government had asked him to rebuild the country's entire food system from first principles, and he had the backing, the budget, and two years to get it right. When he finally delivered his review, it proposed fourteen recommendations.

Unfortunately, most of what he asked for never happened. The recommendation that touched taxes on sugar and salt, the one that would have hit food companies where it hurt, was quietly deferred to another white paper that took years to arrive. Meanwhile the land use framework, a recommendation that cost the government nothing and offended nobody, sailed through. Dimbleby had been right about almost everything. He had also misjudged something more important than the analysis itself.

Every engineer who has shipped a proposal nobody acted on will recognize this story before it finishes. There is a comforting belief that lives inside technical people, the idea that correctness is self-executing. Build the right architecture document, run the right benchmark, and the organization will simply see it and move. Dimbleby had more institutional power behind him than any engineer submitting a proposal will ever have, a formal government commission, cross-department cooperation, an eighteen-month runway, and even that was not enough to survive contact with an organization that had its own priorities. If a state-commissioned review can be picked apart into the convenient half and the ignored half, a design doc posted to a Slack channel has no chance on rigor alone.

The work is not writing the recommendation. The work is building the coalition that will still be standing when the recommendation becomes inconvenient.

Cheap agreement is not adoption

Look closely at what actually got approved from Dimbleby's fourteen recommendations, and a pattern appears immediately. The land use framework moved forward because it asked nothing of anyone with power to lose. The sugar tax and the meat reduction targets stalled because they asked food companies to give something up, and food companies had a seat at the table Dimbleby didn't control.

Engineering leadership does the same triage instinctively. A proposal to adopt a new observability standard gets approved in a week because it costs nobody anything they'll miss. A proposal to deprecate a system that a senior engineer built three years ago, or to change how a team is staffed, sits in a backlog indefinitely because somebody has to lose something for it to happen. The parts of your plan that get adopted first are rarely the parts that matter most. They are the parts that are cheapest for someone else to say yes to.

Framing decides who shows up to fight you

The most cutting criticism of Dimbleby's report wasn't about the food science. It was about how a sugar tax would affect a working parent doing the weekly shopping, a framing fight that had nothing to do with whether the nutrition data was sound. Dimbleby wasn't wrong about sugar. He lost a battle he never saw coming because he framed the problem in a way that made him easy to cast as the out-of-touch expert.

Engineers make the identical mistake when a system needs retiring. Frame it as "the previous team's decisions were wrong," and you have recruited every person who worked on that system into opposition, whether or not they say so out loud. Frame it as "the constraints that justified this in 2022 have changed," and you have described the same technical reality while leaving nobody with a reason to defend their own past decisions. The facts can be identical but the coalition you build or destroy is not.

What Dimbleby would tell you to do differently

Reflecting on years of watching his own recommendations get selectively adopted, Dimbleby kept returning to one gap: the report existed, but nobody with the power to act on it had been brought along before publication, only after. That is the reversal worth taking from his story. Build the case for sponsorship before you build the case for the idea. Find out who loses something if you're right, and have that conversation in private before you have it in a room full of people. Package the hard, necessary part of your proposal next to something cheap and visible enough that leadership can claim an early win from it.

Being right got Henry Dimbleby a very good report. It did not get him a changed food system. The lesson is not to be less rigorous but to spend as much care on who needs to be standing behind you as you spend on the fourteen recommendations themselves.

Until next time

Kayode