The video above is part of Module 4 of the Leadership Essentials Course and covers the full framework for communicating vision in a way that moves people to act, not just inform them.
Most finance leaders can set a direction. Fewer can make their team genuinely care about it. This post gives you a practical framework for closing that gap, grounded in treasury, risk, and regulatory team contexts where the default culture is metrics over meaning.
The sections below cover what a vision actually does, the three qualities it needs to stick, how to communicate it so people feel it rather than just hear it, and how to embed it into everyday work so it outlasts the all hands presentation. You can jump to whichever section is most relevant to where you are right now.
What a Vision Actually Does
A vision is not a goal. As a working definition (not a universal law): a goal is a number with a deadline, and a vision is a picture of a future state that gives the work meaning. Reasonable people frame these things differently, but the distinction is useful because goals produce activity while a shared vision produces conviction.
In treasury and finance teams, the default is metrics. That is understandable. Our world runs on numbers. But telling your team that the goal is "to reduce FTP disputes by 20% before year end" tells them what to do, not why it matters or what kind of team they are part of. People can comply with a target. They have to believe in a direction.
A real vision answers three questions your team is always quietly asking: Where are we going? Why does it matter? Where do I fit in? When your communication answers all three, people move with purpose rather than just following instruction.
The Three Qualities of a Vision That Sticks
A vision needs to pass three tests. Miss any one of them and it either gets forgotten, ignored, or treated as decoration on a slide.
Clear enough to repeat. If someone cannot explain the vision to a colleague without looking at their notes, it is not clear enough. This is common in finance leadership, where vision statements get buried in strategy documents full of abbreviations and qualifications. Clarity means someone can say it back to you in one or two sentences without losing the meaning.
Meaningful enough to feel. A vision has to connect to something people actually care about. Not corporate values from a poster. Real things: professional pride, doing work that holds up to scrutiny, being part of a team people want to join, making a genuine difference to the organisation or to customers. If the vision does not touch any of that, it stays in the rational part of the brain and never moves people.
Concrete enough to act on. Abstract vision statements fail because people cannot translate them into Monday morning decisions. A vision that says "we will be the best risk team in the bank" needs enough texture that someone in the team knows what it looks like in practice. What decisions does it shape? What standards does it set? What would they do differently tomorrow?
Make People Feel It, Not Just Hear It
The communication of vision is where most leaders shortchange themselves. They state the destination clearly enough and then stop. The gap between hearing a vision and feeling it is bridged by storytelling and relatable language.
Consider the difference between these two versions of the same message from a head of regulatory reporting, speaking to their team ahead of a PRA110 remediation programme.
Version one: "Our goal is to become a trusted, strategic partner to the business, moving beyond transactional reporting."
Version two: "There is a moment we are all working towards. It is the moment when the CFO walks into a major liquidity decision and the first call she makes is to us. Not because we sent her the right numbers, but because she trusts us to help her think. That is what this team is capable of, and that is the standard we are building towards."
Both say the same thing. Only one makes you want to be part of it. The second version is a stylised illustration, not a script to copy verbatim. The point is the structure: a specific human moment, a named person, and a concrete description of what trust looks like when it is real.
Storytelling works because it puts people inside a future they can picture. Use specific, human scenarios rather than abstract language. Put a real person (or a plausible composite) at the centre of the story. Describe what it looks and feels like when the vision is real, not just what the metrics will show.
You do not need to be a natural storyteller. You just need one or two concrete scenarios that illustrate the future you are describing. Draft them, say them out loud, and refine them. Specificity is what makes the scenario convincing.
A weekly note on treasury, liquidity and practical Python. No spam, unsubscribe any time.
A Worked Example from a Finance Team Context
Picture a liquidity risk team of eight people, spread across two sites, running daily LCR reporting and supporting the ILAAP submission cycle. The team lead wants to shift the team's identity from "report producers" to "the people whose analysis the board actually relies on."
She does not open the next team meeting with a slide on strategic objectives. Instead she describes a specific moment from the previous ILAAP cycle: the risk committee asked a question about the stress scenario assumptions that no one in the room could answer on the spot. The team's written analysis had already covered it, but no one had read it closely enough to know that. She then describes what it would look like if the team were known well enough for their work that the committee chair had read it before walking in.
That is the vision. It is grounded in work the team already does. It is specific enough to act on (better executive summaries, clearer scenario narratives, stronger relationships with the risk committee secretary). And it connects professional pride to a real outcome the organisation cares about.
No grand language required. The scenario does the work.
Authenticity Beats Polish Every Time
Plenty of leaders work hard on the delivery of vision: the slide design, the structure, the carefully rehearsed phrases. What matters far more is whether the person in front of the room actually believes what they are saying.
People who work in audit and risk disciplines develop strong habits of pattern recognition. They notice when assumptions do not hold, when numbers do not reconcile, and when what someone says in a meeting does not match how they actually make decisions. That same instinct applies to leadership communication. If your stated vision does not match the priorities you actually defend, people will notice.
Personal experience is your most powerful tool here. If you have a story from your own career that illustrates why a particular kind of work matters, or what happens when a team gets it right, use it. It does not have to be dramatic. A moment where rigorous liquidity analysis shaped a significant funding decision, or where the ICAAP team was brought into a board discussion because their judgement was trusted, tells people something real about what the work can mean.
Genuine conviction is not the same as enthusiasm or performance energy. It is quieter and more durable. It shows up in the consistency of your decisions, not the intensity of your delivery.
If you want to go deeper on how your personal leadership style shapes all of this, the post on situational leadership is worth reading alongside this one.
Weave Vision Into Everyday Communication
A vision presented once at an all hands, then never mentioned again, is just a presentation. The leaders who actually shift team culture are the ones who weave vision into the fabric of ordinary communication.
That means referencing it in team meetings when you make a decision or set a priority. It means bringing it into one to ones when you are discussing someone's development. It means using it as a lens when you give feedback, connecting the behaviour you are recognising or redirecting to the direction you are all moving in. It means being explicit when you decline something because it does not fit where the team is going.
None of this requires grand speeches. It requires the discipline of returning to the same few themes consistently so that over time people internalise them. Think of it less as broadcasting and more as repetition with variation. The underlying message stays the same. The context in which you surface it changes.
A useful test: if you removed all formal strategy sessions, could someone new to your team piece together your vision from the way you run day to day meetings and conversations? If the answer is no, the vision is not yet embedded.
From Big Picture to Individual Contribution
One of the most common failures in vision communication is staying at altitude. The leader articulates a compelling direction but never connects it to what it means for the person sitting in front of them.
For each person on your team, the vision needs a personal translation. That does not mean a separate vision for each individual. It means you have done the work of understanding how their specific role, skills, and contribution connect to the bigger picture.
For a regulatory reporting analyst, the link might be that their precision and reliability is what gives the team the credibility to have a strategic voice with senior committees. For a junior treasury associate, it might be that the quality of their cash flow analysis is what allows the team to advise with confidence rather than hedge every answer. Neither of those is a stretch. Both are true. But you have to say them explicitly. People rarely make the connection themselves.
This is also where individual development conversations become a vehicle for vision, not just performance management. When you discuss someone's growth in the context of where the team is heading, you give their development meaning beyond the next appraisal cycle.
Build Ownership, Not Compliance
Compliance is what you get when people understand the rules. Ownership is what you get when people share the goal. The difference in output shows up most clearly in the quality of decisions made without you in the room.
Ownership comes from involvement. If you want people to own a direction, they need to have had some part in shaping it, or at minimum in understanding the reasoning behind it. That does not mean leadership by committee. It means being transparent about how the vision was formed: what you saw, what you were trying to respond to, and what alternatives you considered.
It also means connecting the team's direction to what individual team members already value. If someone is motivated by professional rigour, show how the vision demands and rewards that. If someone cares about developing others, show how the team's growth creates that opportunity for them. You are not inventing motivations. You are making real connections between what already matters to them and what the team is building towards.
The post on servant leadership explores how this kind of orientation towards the team's growth underpins the most durable forms of influence.
The Practical Takeaway
Pick one upcoming interaction this week: a team meeting, a one to one, or a feedback conversation. Use it to connect something specific back to the direction your team is building towards. Not a speech. Just one deliberate sentence that ties the moment to the meaning.
Do that consistently and the vision stops being something you present. It becomes something your team lives inside.
If you want to go further with the full Leadership Essentials Course, browse what is available at the Academy catalogue or explore the learning paths for a structured route through the material with a certificate at the end.

The Complete Leadership Development Programme
In today’s rapidly changing business world, technical expertise alone is no longer enough.
Take the courseGet the next one in your inbox
A weekly note across Finance & Treasury, Innovation & Automation and Career Development. No spam, unsubscribe any time.
Notes across finance and treasury, innovation and automation, and career development, written by practitioners who do the work.
