Introduction

You invested in the system. You ran the demos. You got sign-off. And now, six months after go-live, half your team is still working around the tool instead of inside it. This is not a technology problem. It is a leadership problem. Skills gaps are widening, and over 77% of CFOs acknowledge they need digital skills their teams don’t currently have (Grant Thornton, 2024). The gap is real, and it is yours to close.

1. Why resistance happens, and why CFOs underestimate it

Resistance rarely comes from bad faith. It comes from fear of losing expertise, from processes never redesigned before go-live, and from teams told what was changing but not why it mattered to them. According to RGP research (CFO Dive, 2026), skills gaps now rank among the most significant barriers to realizing technology ROI. Meanwhile, 86% of CFOs say technical debt is a moderate or significant barrier to enterprise technology adoption. Teams are not refusing change. They are overwhelmed and under-equipped.

The pattern we see repeatedly at Penon Partners is this: the ERP or automation tool is implemented on top of broken processes, with no structured onboarding and no clear owner for adoption. The result is a system that gets bypassed, not because it is bad, but because no one made it easier to use than the old workaround.

2. What does effective adoption actually require?

It requires three things, in order: process redesign before go-live, structured capability building during rollout, and visible sponsorship from finance leadership throughout. None of these are optional.

On capability: over 70% of CFOs are already prioritizing investments in digital technologies (HCLTech, 2023), yet most underestimate what it takes to bring teams along. BGSF (2024) is clear: to maximize technology value, CFOs must prioritize upskilling, starting with skills assessment and comprehensive training. That is not a nice-to-have. It is a transformation dependency. HCLTech stresses that change management is vital in driving user adoption: communicate the reasons for change, address concerns, and provide adequate training. For a practical framework, the article on how analytical dimensions cut financial reporting time by 30% shows how upstream choices drive team behavior. The CFO Dive analysis on AI adoption challenges confirms: skills and change management are the deciding factors.

Conclusion

Technology does not transform finance functions. People do, when they are properly equipped, clearly led, and given processes worth following. If your adoption is stalling, resist the urge to blame the tool or the team. Look at what was designed before go-live, what training was actually delivered, and whether you are visibly leading the change. That is where the problem almost always lives.