You can be the best driver in the world—but if the car isn’t right, you won’t win.
That’s the image I often use when I explain how programmes succeed or fail. A Formula 1 driver doesn’t just show up on race day. They need:
A world-class car
A team of mechanics and engineers
A factory behind them with resources and precision
And the right environment to operate under pressure and deliver under scrutiny
Without those elements, even elite talent won’t succeed.
In transformation, it’s the same. You can have brilliant people, but if the environment is broken—no governance, no rhythm, no trust, no support—you’ve just put a world-class driver in a broken-down car.
As a leader, my job is to build the car. Tune the engine. Align the pit crew. Fuel the strategy. I don’t just empower teams with words—I give them everything they need to perform.
Lesson 1: Empowerment Begins with Environment
A lot of leaders say they empower their teams. But empowerment without the right environment is hollow. I believe in giving my leaders a world-class car—fully equipped to go out and perform.
That environment includes:
Clear governance structures and escalation paths
Delivery rhythms: stand-ups, review sessions, playbacks, QA checkpoints
Agile rituals balanced with real-world delivery discipline
Tools, systems, and—crucially—the resources and budget to actually get it done
I’ve always believed that one of the greatest risks to delivery is starving teams of what they need and then holding them accountable anyway.
Empowerment isn’t just about encouragement—it’s about infrastructure, systems, and funding. It’s about creating clarity, removing friction, and backing your people with conviction.
Lesson 2: Business Buy-In Isn’t Optional—It’s the Engine
If the environment empowers the team, business engagement legitimises the mission. No programme can succeed if the business views it as something that’s “being done to them.”
You’re not just asking for budget. You’re asking for time. Attention. Active participation.
In every country delivery I’ve led, we positioned ourselves not as a separate delivery arm—but as a partner solving business pain points. We were clear: “We’re here to serve you. You are part of this. You are not being bypassed—you are being equipped.”
Stakeholder sessions weren’t compliance-driven. They were purpose-driven. And we made sure the investment wasn’t just financial. It was also relational. It was about time from local CFOs, engagement from SMEs, and buy-in from ops leaders who were already running at full tilt.
When that dynamic is healthy—when business stakeholders believe it’s their solution, not your rollout—transformation becomes real.
Lesson 3: Sponsors Set the Tone and Carry the Mandate
People often think the programme sponsor is a figurehead. They’re not. They are the anchor point for the entire enterprise.
A strong sponsor brings:
Visibility in key forums
Voice in alignment conversations
Weight when engagement needs to happen across divisions or countries
In one major programme, we had a sponsor who regularly attended steering committees, showed up in the right meetings, and reinforced our alignment to the organisation’s strategic goals. They spoke with clarity and conviction: “This is our direction. This programme is executing that strategy. Let’s get behind it.” That kind of tone-setting changed everything.
I’ve also had to coach sponsors—not as a criticism, but to align on role and influence. One of my earliest conversations with every sponsor includes: “This is what makes the difference. This is why 90% of programmes fail—because sponsors go missing.”
The best sponsors know: they don’t just endorse the programme—they personify its legitimacy.
Lesson 4: Anticipation Is a Leadership Discipline
A mentor once told me:
“Donald, I pay you to solve problems and keep them away from me. And second—no surprises.”
That guidance shaped my leadership style.
I’ve always led with “radar thinking”—long-range anticipation of what could go wrong and proactive design to prevent it. A great example is in contractor retention. Too often, organisations sign six- to twelve-month contracts and wait until the last few weeks to decide on renewals.
But by then, it’s too late. Talented people are already looking for their next role 3–4 months out. And once you lose them, you lose momentum, continuity, and culture.
In one programme, I raised this as a major risk well ahead of time. I proposed we offer multi-year contracts for the core team, locking in our top talent and removing unnecessary churn. It was accepted—and we never had a single gap in our leadership team.
But radar leadership isn’t just about contracts. It’s about reading a room before a board meeting. It’s about anticipating questions before they’re asked. It’s knowing which problems to quietly resolve, and which ones need to be surfaced.
Those two principles—solve problems, and keep surprises off the table—don’t contradict. They balance each other. One gives teams autonomy. The other ensures leadership stays ahead of the curve.
Lesson 5: Quiet Leadership Is Still Leadership
One of the most powerful roles I play as a leader is the one that happens offstage.
If a team lead is walking into a high-stakes workshop, I’ve already had the one-on-one with the stakeholders. I’ve provided the context. I’ve socialised the objectives. I’ve made sure the ground is firm before the first foot hits it.
That’s not about protecting people. That’s about setting the stage so they can shine.
Behind the scenes, I’m brokering alignment, managing expectations, clearing blockers. I’m orchestrating the energy in the room before the team ever steps into it.
Quiet leadership doesn’t mean invisible leadership.
It means intentional leadership.
It’s not about being loud. It’s about being strategic. It’s not about being the centre of attention. It’s about creating clarity and confidence in others.
I’ve stepped into difficult rooms, tense territories, high-profile programmes—and the most impactful moments I’ve created weren’t on stage. They were in the prep. In the tone I set. In the relationships I built quietly over months, so that when my team arrived, they were welcomed, not resisted.
That’s where trust is built. Not just between you and the team—but between the team and the environment you’ve cultivated for them.
Outcome: Collaboration Wins—Not Command and Control
At Old Mutual, we were operating across 12 countries, each with its own context, pressures, and leadership structures. As a Group-led programme, we had to show up with humility, clarity, and a collaboration-first mindset.
From Day Minus One, I made this clear to every team member:
“We don’t come to dictate. We come to partner.”
We built a matrix delivery model. Our role was to equip, enable, and support. We served. We listened. We engaged. We empowered.
And because of that, every country felt respected. Every team leaned in. Every milestone was owned by both Group and Country—because we made them feel part of the build, not victims of a rollout.
Collaboration isn’t a soft skill. It’s the strategic unlock that makes transformation possible.
Final Reflection
As a leader, I’ve never believed my role is just to steer.It’s to build the track, tune the engine, and clear the path—so the people I trust can deliver without distraction.
Those two principles I learned early still guide me:
Solve problems, and keep them away from me. And second—no surprises.
They sound simple, but they create balance. One is about empowerment. The other is about situational awareness.
You don’t lead great teams by micromanaging.You lead them by designing the environment, building the relationships, and removing the noise—so the work can speak for itself.
Great delivery isn’t loud. It’s deliberate. It’s orchestrated. And it’s led with purpose.