The Only Thing I Want From a Leader
Most leadership advice is complicated. A framework, a maturity model, a five-stage transformation curve — anything that turns leadership into a discipline you can study your way out of practicing.
Here is the uncomplicated version. Put the right person in the right position. Give them a clean mandate. Give them full support. That’s it. That’s the job.
I see the pattern very often: programs don’t stall because the technology is wrong. They stall because someone was put in a role without the authority to hold it, and no one above them noticed — or no one above them was willing to say so.
Easier said than done — on purpose
I’m not pretending this is simple to execute. It isn’t. People and work evolve on different clocks. The program director you appointed eighteen months ago was the right call then. The program has changed shape twice since. Has their mandate changed with it, or is everyone still operating off the org chart from the kickoff deck?
That gap — between what a role was and what a role has quietly become — is where drift lives. Not in the vendor contract. Not in the go-live date. In the space between what someone was authorised to do and what the program now actually needs them to do.
Right people don’t need to be managed. They need to be unblocked.
I’ve watched a council appoint a genuinely capable project sponsor and then, six weeks later, route every material decision back through an executive steering group that met once a month. The sponsor had the judgment. They didn’t have the mandate. So the program slowed to the speed of the calendar, and everyone called it “governance.”
Compare that to a CFO I advised who did something almost unremarkable: she named a business lead, told the steering committee in writing what that person now had authority to decide without escalation, and then spent her own time doing three things — removing blockers the business lead flagged, protecting the program from scope creep coming from other executives, and showing up to say what the program was actually for when people started forgetting. She didn’t run the program. She made it possible for someone else to.
That’s the difference. Right people, put in right places, take care of process, technology, culture, coordination, cohesion, teamwork — the entire operational machinery — on their own. You didn’t hire them to be told how to do that. You hired them because they already know.
What’s actually left for you to do
If the right person is in the right seat with a real mandate, your job as the leader shrinks to four things: support them, empower them, manage the exceptions that are genuinely yours to manage, and hold the vision so the whole effort stays pointed at something worth reaching.
Notice what’s not on that list. Reviewing their decisions before they’re allowed to act on them. Sitting in on meetings they’re capable of running alone. Building a status report that exists so you can tell your own boss you’re “across it.” That’s not oversight. That’s a leader doing the job they already delegated, badly, twice.
The point
Most executives think their job is to have the answers. It isn’t. Your job is to make sure the people who do have the answers are in the seats where their answers matter — and then to have the discipline to stay out of their way while still being there when they need you.
That’s not a management style. It’s a form of trust with consequences attached, which is the only kind of trust that means anything. If you can’t name, right now, who has full authority over the parts of your program that aren’t yours to run — you haven’t done the one thing leadership actually asks of you. Everything else is motion.
