The Finance Leader's Job Has Changed. You're Not Just Reporting the Numbers — You're Running the Program.
A conversation with a colleague recently stayed with me longer than most. We were talking about the pace of AI adoption — how fast finance teams were expected to move, what was realistic, what the roadmap actually looked like for organisations without a dedicated technology team. At one point, he said something that cut through all of it: "Half the stuff we're supposed to be adopting is already obsolete by the time we get to it."
He wasn't wrong. And the frustration behind that observation points to something important about what the finance leader's role has actually become.
The traditional job description of a finance leader — close the month, produce the management reporting pack, manage the audit, present to the board — hasn't disappeared. But those tasks now sit inside a much larger responsibility that most finance leaders are carrying without it being explicitly named: directing a continuous programme of change, prioritisation, and adaptation in an environment where the tools, the regulations, and the expectations are shifting faster than any individual can track.
That's not a finance job anymore. It's a programme management job. And most finance leaders are already doing it — they just haven't recognised it as such.
What Programme Management Actually Means in a Finance Context
Programme management, in its formal sense, is the coordinated management of multiple related projects to achieve strategic objectives that couldn't be achieved by running each project independently. It involves setting direction, managing interdependencies, allocating resources, tracking progress against outcomes, and making trade-off decisions when things conflict.
Sound familiar? It should. That's what a finance leader does every day — they just do it under different labels.
Managing the Payday Super transition while simultaneously preparing for staged NDIS reform milestones while also building out an AI-assisted reconciliation process while also closing each month and keeping the reporting pack current — that's not a list of tasks. That's a programme with competing timelines, shared resources, and interdependencies that need to be actively managed. The difference between a finance leader who handles this well and one who doesn't isn't usually technical knowledge. It's the ability to hold the full picture, sequence the work intelligently, and make deliberate choices about what gets done when and at what level of quality.
Most finance leaders develop this capability through experience, not through training. And most of them exercise it without naming it — which means they don't always get credit for it, and more importantly, they don't always apply it as deliberately as they could.
|
4+ major change streams
Payday Super, aged care reform, NDIS reform planning, sustainability reporting, and AI adoption — all sitting on finance leaders' desks across the 2025–27 transition window simultaneously
|
83%
Of finance leaders identify AI adoption as a key force reshaping their function — yet most are managing that adoption alongside a full existing workload with no additional resourcing
|
The Direction-Setting Gap
Here's where a lot of finance functions come unstuck. The technical work — closing the month, producing the reports, managing the audit — gets done because it has hard deadlines and clear accountabilities. The direction-setting work — deciding which AI tools to adopt, what processes to redesign, how to sequence the compliance transformation programme — often doesn't. It gets fitted in around the edges, delegated inconsistently, or deferred until a crisis forces the decision.
The result is a finance function that's reactive rather than adaptive. It responds to each new change as it arrives — scrambling to implement Payday Super in the final month before go-live, adopting AI tools without a governance framework because the deadline pressure doesn't allow for it, producing management reports in a format that hasn't been reviewed for two years because there's no bandwidth to question it.
This isn't a criticism — it's a structural problem. Finance leaders are typically resourced for the ongoing operational work, not for the programme management layer that sits above it. In organisations without a dedicated finance transformation team or a technology partner, that programme management responsibility either falls on the finance leader personally or it doesn't get done.
What's changed in 2026 is the volume and pace of that programme management work. The number of concurrent change streams landing on finance teams — regulatory, technological, and operational — has reached a point where the informal, edges-of-the-job approach isn't sufficient anymore. The direction-setting needs to be deliberate, resourced, and treated as a core part of the finance leader's role rather than a bonus activity.
Three Practical Shifts Finance Leaders Can Make Now
Recognising that you're running a programme — rather than managing a function — changes how you spend your time and what you prioritise. Three practical shifts follow from that recognition.
Make the programme visible. A finance leader managing five concurrent change streams needs to have those streams mapped somewhere — with owners, timelines, dependencies, and status — in the same way they'd expect any other significant project to be tracked. Most finance leaders are doing this mentally, which means it's invisible to their team, their CEO, and their board. Making it visible has two effects: it creates accountability, and it creates a shared understanding of why certain things are being prioritised over others.
Distinguish operational delivery from programme direction. The monthly close needs to happen. The payroll needs to run. These are operational deliverables, and they have to be protected. But the finance leader who spends all their time in operational delivery has nothing left for the programme direction work — and the programme direction work is what determines whether the function is fit for purpose in 12 months. The split between these two modes of work needs to be deliberate, not whatever's left over after the operations are done.
Treat technology adoption as part of the programme, not a separate initiative. AI tool adoption, process redesign, and governance development are not IT projects that sit alongside finance. They are finance programmes that happen to involve technology. The finance leader who hands this off to IT — or who defers to a vendor's implementation plan without finance-led oversight — ends up with technology that doesn't match finance's actual requirements. The programme ownership needs to stay with the finance leader.
What This Means for Finance Teams That Are Already Stretched
The honest tension here: the finance leaders who most need to shift into programme management mode are the ones with the least capacity to do it. Small finance teams in NFP, NDIS, and SME organisations are managing the same breadth of regulatory change and technology adoption pressure as their larger counterparts — with a fraction of the resourcing.
There's no magic solution to that, but there are two things that help. First, being explicit about capacity constraints with the board or executive team — not as a complaint, but as a programme management communication. "Here are the change streams we're managing, here is the resourcing we have, and here are the trade-offs we're making as a result." That conversation reframes the resource constraint as a governance issue, which is what it is.
Second, being selective. Not every technology trend needs to be adopted. Not every regulatory change creates the same level of risk. A finance leader who has mapped the programme can make deliberate choices about sequencing — addressing the highest-risk items first, building the foundation before the advanced layers, and being honest about what has to wait.
The colleague who said the roadmap was obsolete before they reached it wasn't wrong about the pace of change. But the answer isn't to run faster. It's to get better at deciding which direction to run in — and then holding that direction with enough consistency that the team can actually build momentum.
RELATED ON FINANCE INTELLIGENCE
On the AI governance layer that makes programme direction meaningful — how to actually build human oversight into automated finance processes. Read: 87% of CFOs Want a Human in the Loop on AI. Here's How You Actually Build That Governance Layer →
Finance function stretched across too many change streams?
PFL provides senior-level outsourced finance, management reporting, and AI automation for Australian NFP, NDIS, and SME organisations. We work with finance leaders to take the operational load off their plate — so they can focus on the programme direction work that actually moves the function forward.
Talk to PFL →Timothy, CPA
Managing Director of Professional Financelink (PFL). 20+ years in finance leadership across NFP, NDIS and SME sectors. Operates across multiple organisations simultaneously — which has a way of making the programme management dimension of finance leadership very concrete very quickly.
SOURCES
- Wolters Kluwer — 2026 Future Ready CFO Report (via FutureCFO)
- PwC Australia — Five Trends Shaping the CFO's Agenda in 2026
- Australian Government — Securing the NDIS for Future Generations Reform Timeline
- Fair Work Ombudsman — Payday Super: New Rules Starting 1 July 2026
Comments
Post a Comment