Leadership vs management in finance: what actually changes when you lead a team
Most finance professionals land their first leadership role because they are technically excellent. They know the LCR inside out, they can build a PRA110 submission under pressure, they understand IRRBB modelling well enough to explain it to a generalist audience. None of that prepares them to lead people. This post works through the core distinction between leadership and management, grounds it in the realities of a finance or treasury team, and gives you something concrete to do about it.
Key questions this post addresses: What is the difference between leadership and management in a finance team? Which skills transfer from technical roles and which do not? What should you do differently from day one?
What the difference actually is
Management is about structure, process, and execution. A manager ensures the end of month reporting pack goes out on time, that run-off rate assumptions are reviewed and approved within your governance framework, that the team follows the right control framework. Good management keeps things working.
Leadership is something else. It is about direction, purpose, and motivating people toward a goal they cannot yet fully see. A leader helps the team understand why the work matters, not just what needs doing. That distinction sounds soft until you are trying to hold a team together through a regulatory change programme or persuade a sceptical analyst to approach a problem differently.
The best people in finance learn to do both. But they are genuinely different disciplines, and conflating them is where things go wrong.
A useful test: management answers the question "are we doing things right?" Leadership answers the question "are we doing the right things, and do people believe in them?"
Why finance teams blur this more than most
Finance and treasury functions tend to promote people on technical merit. That makes sense. You want your ILAAP lead to actually understand the liquidity stress assumptions they are defending to the PRA. But technical competence does not transfer automatically into the ability to motivate, develop, or influence people.
The specific tools that come up in your world (LCR, NSFR, IRRBB, HQLA classifications, PRA110 reporting) will vary depending on your function, whether that is liquidity risk, regulatory reporting, or treasury. The leadership challenge is consistent across all of them.
There is also a positional authority trap. When someone becomes a team lead or a head of, they sometimes assume the title does the work for them. People will follow instructions because of the org chart. But following instructions is not the same as being genuinely engaged, and in a specialist finance team where most people have strong views and real expertise, positional authority goes only so far.
The result is managers who are excellent at tracking deliverables and poor at building a team that wants to go beyond them.
How leadership thinking has evolved over time
The video traces the arc of leadership theory, and it is worth knowing because each wave of thinking left behind something useful.
Great Man and Trait Theory
The earliest theories, prominent in the early 20th century, assumed leaders were born, not made. Charisma, intelligence, decisiveness were seen as innate. The strong hereditary version of this idea has been largely set aside, but Trait Theory left one useful residue: certain personal characteristics do correlate with effective leadership, even if they can be developed rather than inherited. Modern research on personality and leadership emergence supports this weaker, more useful claim.
Behavioural Theory
A weekly note on treasury, liquidity and practical Python. No spam, unsubscribe any time.
This wave shifted focus to what leaders actually do, not who they are. Broadly, two dimensions emerged from studies conducted in the 1950s and 1960s: one oriented toward task completion and one oriented toward people, relationships, and morale. Both matter, and the insight that behaviour is learnable was important.
Contingency and Situational models
These added nuance. Hersey and Blanchard's situational leadership framework argued that the right style depends on the capability and willingness (the development level) of the person being led. A new graduate joining your FTP team needs a very different approach from a senior analyst with ten years of transfer pricing experience.
Modern approaches
Emotional intelligence, authenticity, servant leadership, and agile leadership bring the focus back to the leader's inner world and their relationship with the people they lead. These are not soft extras. In a finance environment where the stakes are high, emotional intelligence is what separates leaders who build teams that perform at a high level from those who burn people out or lose them.
No single theory is complete. Think of them as lenses. You will use different ones at different times.
The traits that show up in effective leaders
The video highlights three in particular. Here is what they look like in a finance context rather than in the abstract.
Self awareness
This means knowing your own defaults under pressure. If your instinct when a regulatory deadline is at risk is to take back control and do the work yourself, that is worth knowing. It can save a deadline in the short term and hollow out your team's capability over time. Leaders who are self-aware notice that pull and make a deliberate choice rather than just reacting.
In practice: after a difficult reporting sprint, ask yourself honestly what you did that helped and what you did that got in the way. Not what the team did. What you did.
Emotional intelligence
In a treasury or risk team, people carry real pressure: model uncertainty, PRA scrutiny, tight deadlines. Emotional intelligence means reading that pressure accurately and responding to the person, not just the task. It also means regulating your own responses when things go wrong.
A concrete example: your analyst has made an error in a liquidity report. Emotional intelligence is the difference between a conversation that finds the root cause and strengthens controls, and one that makes the analyst reluctant to flag errors in future. The second outcome is far more dangerous in a regulated environment.
Adaptability
Finance functions do not operate in a stable environment. A Basel rule change, a new PRA supervisory statement, a shift in the firm's funding strategy: any of these can reshape priorities quickly. Effective leaders can shift their approach without losing the team's confidence. That means holding direction firm while allowing the route to change.
Knowing when to lead and when to manage
This is the practical judgement that the distinction demands. The balance shifts with context.
A BAU reporting cycle (weekly LCR and NSFR packs, standard MI production) calls for more management. Clarity of process, clear ownership, consistent quality control. The team knows what good looks like. Your job is to keep the engine running and remove blockers.
A regulatory change programme (say, implementing a new IRRBB framework or restructuring HQLA classifications) calls for more leadership. The team cannot see the finished state yet. There will be ambiguity, and people will need to understand the purpose behind the work to stay engaged through the difficult middle. That requires direction, communication, and earned trust, not just task allocation.
Most roles require both, often in the same week. The skill is in reading which is needed and switching register deliberately rather than by accident.
If you find yourself managing everything, including the work that does not need you, ask whether you are managing because it needs managing or because it is more comfortable than leading.
What to do on day one
Abstract principles are not much use when you are walking into a team meeting for the first time as the person now responsible for the people in the room. Two specific things:
-
Listen before you change anything. Spend your first week or two asking questions and genuinely listening to the answers. What is working? What is frustrating? What do people think is being missed? You will learn things about the team, the processes, and the culture that no handover document will tell you. It also signals that you intend to lead rather than simply impose.
-
Be explicit about how you work. Tell the team directly what they can expect from you: how you prefer to communicate, how you will handle disagreements, what you will take off their plate and what you expect them to own. This is not about writing a personal user manual (though some people find that useful). It is about removing the uncertainty that comes with a new manager. People perform better when they know the rules of engagement.
Neither of these requires a leadership development programme or months of experience. Both can be done on day one.
The one thing to carry away: the next time you feel the pull to manage something yourself rather than lead through it, pause and ask whether you are serving the task or avoiding the harder conversation. That pause is where the shift from manager to leader actually happens.
Get the next one in your inbox
A weekly note on treasury, liquidity and practical Python. No spam, unsubscribe any time.
Practitioner notes on treasury, liquidity, regulatory reporting and practical Python.
