My last two pieces were about agents, accounts and who owns them. This one is about people, because in my experience that is where security programmes succeed or stall.
For several years, until this summer, I led one of three workstreams on a large privileged-access programme at a global bank: 30-plus people, a legacy platform to decommission by a date that would not move, and a great deal of work to land before it. Most of the team were senior contractors. Many had long service in the organisation and carried knowledge that no handover fully passes on. They cared about the outcome and had strong views on how to get there. Any of them could have left whenever they chose.
More than any plan, what kept that team committed was whether they believed I cared about them and about their work. People can tell.
Caring looks like curiosity
It is easy for anyone running a plan to let their interest stop there: is the task on track, can it be marked done. Teams notice that quickly.
I am not a developer. But I made the effort to understand what my teams were building and why it was hard, well enough to follow the argument when an engineer told me something would take longer than planned. That is the level a leader needs: enough to ask a good question and to recognise a weak answer. Without it you cannot weigh a technical objection, so you end up accepting all of them or overruling all of them, and the team loses faith either way.
The date conversation that kept coming back
The pushback I heard most was about dates. The plan was unrealistic; the release could not land by then. We would talk it through, replan, and agree a date. Weeks later, because something had taken longer than expected or because pressure had built up again, the same concern was back.
Each time there was a balance to strike. On one side, listening properly, and replanning or rescoping releases where the concern was real. On the other, keeping people clear that we had been brought in to decommission a platform by a fixed date, and that meeting it was the job.
What I tried to change was the question. “Tell me all the reasons this won’t work” turns the leader into a complaints line. “How could we make this work?” makes it a shared problem and puts every lever on the table. Can we hire? Can we get more time from people we already have? What can we drop, or move to a later release? Is there a case for more budget? Some of those answers come back as no. Even then, the team is working on the problem with you.
Listen, then decide
Listening comes first, but after a point a leader has to form a view: what the priorities are, who is right in a disagreement, and why. Then hold it. You will not make everyone happy, and some grief comes with the job.
Most of the hard calls I made were about what not to do. There were improvements the team and I wanted to make, and against a fixed date some had to wait: at times we moved something across as it was, or reused existing code rather than rebuilding it. Nobody enjoyed those decisions, me included, but the date required them.
A firm call is easier to accept when there is a track record behind it. If people have seen you listen, and seen you side with them when they were right, most will accept a decision they do not like. On a long programme it is give and take: sometimes you back the team’s view, sometimes you overrule it, and both work as long as people can see the reasoning.
That means explaining decisions. A call is often shaped by things the team cannot see from where they sit. You cannot share everything, but you can nearly always share why.
Directness, both ways
I like direct conversation. Over time, it is what people trust.
With project managers, it means telling them when you do not believe an estimate, when you are not comfortable that an issue is still open, or when they have put off a difficult conversation with someone in their own team.
It has to work the other way too. If you are direct with people, they need to be able to be direct with you: to tell you a date is unrealistic, or that one of your decisions has made their job harder. They will only do that if they have seen you take it well. Respect runs both ways as well. Teams can come to see the lead as a role rather than a person, someone who hands down decisions without seeing what happens on the ground, and sometimes the lead has to say so, including telling someone that they have let them down.
Say who matters
If someone’s work is carrying a release, tell them, and be specific. Recognition should be earned and measured. But treating good work as simply expected is a quiet way to lose the people you can least afford to lose. It also means noticing when someone is carrying too much, before they have to tell you.
Energy matters too. Leading a complex delivery is tiring, and I found that if I did not visibly bring it, I could not expect it from anyone else.
Three questions for your next planning meeting
- When your team says a date is unrealistic, do you ask how it could work, or only why it won’t?
- Could the people affected by your last unpopular decision explain why you made it?
- Does the person carrying your most important release know that you know?
Where I am on this
The team I led was a mix: some people I hired, others were there before me or were hired by others. The principles above applied to all of them.
I have since set up on my own to do this kind of work for mid-size regulated firms. Next, I will write about leading a team you rarely see in person. If you have had to answer question one, I would like to hear how it went.
First published on LinkedIn on 29 October 2026. Discuss it there, or write to hello@aevixadvisory.com.