Beth Weeks, Executive Vice President, Development, Planview
Ask CIOs and CFOs how well they work together and you’ll get a flattering answer. In KPMG’s 2025 CFIO & CIO Collaboration Survey, nearly all (92%) respondents across both roles said they see their relationship with the other as “somewhat” or “very” collaborative. They also see themselves as “unified” in their vision for their business’ technology strategy.
The rest of the findings contradict this sentiment. Firm barriers to communication and understanding remain in place. Chief among them? Different priorities and goal and variations in technical knowledge, with more than one-third (39%) of respondents citing these challenges as ongoing. Ownership also emerged as a key driver of tension; both groups see themselves as the primarily responsible for AI decisions (CFOs: 59%; CIOs: 61%). Most telling of all, the single most-cited point of contention between the two roles was how they assess ROI.
That picture’s a bit less rosy, and the cost associated with allowing the disconnects it reveals is growing rapidly as the year comes to a close. With AI strategies and technologies reaching a new level of pragmatism and maturity in the coming year, spend on deployments get their first taste of real scrutiny for the first time. Here’s what I expect to see as CFOs and CIOs navigate 2027’s AI landscape.
1: The metrics gap becomes a block.
At the heart of CIO–CFO misalignment lies a difference in how each leader measures success. CIOs typically focus on innovation, speed, and the delivery of digital experiences. Meanwhile, CFOs work in metrics of waste mitigation, predictability, and return on investment. Both are necessary within a healthy and successful organization but only when the business can find balance between them. All too often, that’s where things fall apart.
It’s no one’s fault. It’s the foreseeable result of the “every department for itself” approach that defined the early days of digitalization. Leaders built specialized tech stacks to support their needs, which siloed records, metrics, and definitions of success. Because they could not see across these departmental lines, each team’s work began to feel like it happened in isolation, with their goals, indicators, and priorities becoming the be-all and end-all of decisions.
The problem is that an organization isn’t a collection of departments; it’s a single entity that should work toward a shared goal. That’s impossible when finance sees one thing and IT sees another, and each group measures success by different metrics based on one small part of the whole. It’s no wonder they are struggling to find common ground.
In 2027, allowing those silos to stand will get too expensive to bear. If leaders don’t act quickly to close the gap between teams, more technology initiatives to stall at the funding stage—and not for lack of merit but because no one can express that merit in terms finance recognizes.
2: Conversations shift from what things cost to build to what deserves to exist.
For most of the past decade, the CIO’s real constraint was capacity. Engineering time was scarce, so prioritization happened by default. Teams built based on the manpower they had, and the CFO funded headcount accordingly. That arrangement is ending soon if it hasn’t already.
AI has made ideas, code, and initiatives cheap. Generating a prototype, a plan, or ten thousand lines of code is no longer the hard part. What AI doesn’t do is decide which of those things should exist, and that’s where I expect the CIO–CFO relationship to change most profoundly.
The friction will look familiar but run in a new direction. CIOs will field more requests than ever with fewer obvious reasons to say no, because the marginal cost of starting something has collapsed. CFOs will see a portfolio that keeps expanding without a matching change in outcomes, and they’ll stop asking what the next initiative costs and start asking which ones should’ve been stopped already.
That’s a conversation neither side is equipped to have or familiar with navigating. Planview’s 2025 benchmark research found that 60% of organizations still lack timely, accurate data about their own work. Deciding what to stop requires that evidence, and neither side currently has it.
Expect the defining budget argument of 2027 to be about subtraction rather than addition. The organizations that handle it well will be the ones that made prioritization an explicit, shared discipline before AI forced the issue.
3: Agentic AI forces flow metrics into both groups’ vocabularies
Uncovering it all starts with flow metrics: time, efficiency, and load. These measures of bottlenecks, friction, and waste originated on factory floors and in manufacturing outfits, working their way into delivery planning in the past few years. In 2027, they’ll find a place in C-suites across industries and sectors.
They’ve never been a finance instrument, and most CIOs don’t bring them into budget conversations either, but agentic AI tools will force them into these conversations. As agents take on more execution, portfolios will combine human teams, software, and autonomous work inside the same funding decisions. Headcount stops describing what’s happening, and cost-per-project stops explaining why one worked and another didn’t. In this environment, flow is the measure that still holds weight.
CIOs will need to use this approach to pinpoint how delays affect product launches, how inefficiencies drain ROI, and how improvements accelerate time to value. On the other side, CFOs will need to open their definition of value creation to include them, too.
One more prediction I feel confident in is that none of this will resolve in 2027—at least not completely. What will change, though, is that leaders will begin recognizing the impact of the disconnect in their budgets. That’s powerful motivation to admit where tension still sits and put in the work to resolve it.
The organizations that pull ahead will be the ones with CIOs and CFOs who see their dynamic with clarity and agree on what to measure now. That way, they won’t have to talk about what to roll back alter. By this time next year, that will be the clearest divide between enterprises getting real returns on AI and enterprises still explaining why they haven’t yet.
##
ABOUT THE AUTHOR

Beth Weeks is the executive vice president of development at Planview. She leads the software development team for Planview’s products that deliver Strategic Portfolio Management, Professional Services Automation, Enterprise Architecture, and Ideation capabilities. Beth has served in software executive roles for the last 20 years and helped software companies transform their enterprise on-premises products to well-architected Software as a Service (SaaS) and Platform as a Service (PaaS) solutions. She also has experience building highly productive and collaborative teams, which are globally distributed through North America, EMEA, and India.






