When a programme that matters is in trouble, the instinct is to reach for a bigger expert. Whatever the work is about, the search is for the most seasoned specialist in it, someone who has done this many times and will surely see what has gone wrong. It is the responsible move, the one nobody in the room argues with, and it is usually the wrong one.
A programme of that size rarely fails because the people on it do not understand the work. The specialists are already there, and between them they know, or can find, the technical answer. What has broken is somewhere else: a team that has lost confidence, stakeholders pulling in different directions, decisions that will not hold for a fortnight, bad news that no one will carry upward. None of that yields to another expert. Bringing one more in adds an able voice to a room that already has too many, and leaves the part that was actually failing exactly where it was.
There is a particular way the expert appointment makes things worse, and it is worth being precise about, because it is not obvious. A leader brought in for the depth of their knowledge tends to lead from that knowledge. They go to the detail, because the detail is where they are surest of themselves. They form a view fast and hold it hard, and when the specialists already on the programme see it differently, the instinct is to overrule rather than to ask. The people who hold the current state of the work, the ones who know what was tried last month and why it failed, learn that their read is not wanted, and they go quiet. A programme that lacked direction is now also losing the knowledge it already had. The appointment meant to rescue it has quietly narrowed it to one person’s judgement, and that person is busy being the cleverest specialist in the room rather than running it.
I learned this on a programme that was, by the time I came to it, some way into trouble. It was large, it mattered a great deal to the organisation running it, and the specifics of what it was building are not the point, which is rather the point. The strategy had been sound. The budget was there. The people were capable. And it was slipping, in the way these things slip, through no single failure, in a steady loss of grip: decisions deferred, confidence draining, the parts no longer adding up to the whole.
I was not the deepest expert in that room. I was a long way from it, and that turned out to matter in a direction I had not expected. Because I could not out-argue the specialists on their own ground, I had to do something else: trust them, and make it safe for them to tell me the truth. The first weeks went less on the work than on the people doing it, finding where the confidence had gone and why, getting the disagreements into the open where they could be settled, and making a small number of decisions that then held. I got a few things wrong early, and the value of not being the expert was that I could be told so, by people who were, without it turning into a contest. The programme came back. It came back because the people who knew how to fix it were finally being led, by someone with no stake in being right about the detail.
What that programme taught me has an old name. Knowing about something is not the same as knowing how to do it. The first is the work itself: the systems, the methods, the failure modes, everything you can write down, look up, and hand to someone else. The second, leading the people who do that work, is a different capability, and it does not transfer the same way. Knowing-about is abundant; on any serious programme it is already in the building, several times over. Knowing-how, the capacity to take a group of capable people who have lost their way and carry them through the long, unglamorous middle of a hard thing until it is finished, is the scarce one. It is the one the appointment most often fails to buy.
I spent my early career in the infantry, where the lesson arrives without subtlety. The person in command is rarely the most expert at any single task in front of them, and the job was never to be. The job is to hold a group of people to a purpose when it would be easier to drift. It took me longer than it should have to see that a boardroom programme and a section of soldiers were, in this one respect, the same thing.
None of this is an argument against expertise, and it would be a foolish one to make. A programme with no one who understands the work is in a different and worse kind of trouble. The leader has to know enough to ask the questions that matter and to tell a good answer from a confident one. The point is narrower and more useful than ‘expertise gets in the way’. It is that depth of knowledge is not the thing the appointment should be chosen for, that it predicts almost nothing about whether someone can lead a programme through its hard middle, and that past a certain point the expert who cannot stop being the expert becomes a liability in the chair. Enough fluency to judge the work, certainly. The deepest specialist in the room as the person running it, rarely.
Which brings it back to the decision that was yours to make. If you are reading this with a programme that matters on your desk, you are most likely its sponsor rather than the person who will run it day to day. You will not lead it. You will choose who does, and that choice is the whole of your leverage. The instinct, under pressure, will be to appoint for the safest-looking reason: the most senior name, the deepest domain record, the person already trusted and to hand. Each of those feels responsible. None of them is the question. The question is who will still be holding the thing in its eighth month, when the attention that gathered around its launch has moved to the next priority and the work has turned from interesting to merely hard.
And there is a harder version of the choice, which is whether the right person is inside the organisation at all. Sometimes they are, and the real cost is pulling them off three other things that also matter, because a programme that cannot be allowed to fail cannot be led in the margins of someone’s week. Sometimes the cleaner answer is to bring in someone whose entire job, for as long as it takes, is this one outcome and nothing else. That is a harder thing to admit than a budget line, and it is the right call more often than it is the chosen one.
So the discipline is simple to state and uncomfortable to follow. Appoint for the capacity to lead the experts. Judge the candidate on whether they can hold a room of people who know more than they do and still move them to a decision that holds, and treat depth of domain knowledge as a useful bonus rather than the qualification. Then, having chosen that person, refuse to let them carry it part-time, in the margins of everything else they are responsible for. The expertise is already in the room. What the programme has been missing is someone to lead it, and that has always been the scarcer thing, and the more decisive.