Where AI Creates Real Value in Finance

Artificial intelligence is not replacing finance.

It will change what finance professionals spend their time doing.

For decades, finance organizations have focused on collecting data, reconciling transactions, producing reports, and explaining what happened. Those responsibilities remain essential, but AI is changing how much time is required to complete them.

The real opportunity is not simply automating existing work. It is allowing finance teams to spend more time helping the business make better decisions.

AI Is an Accelerator, Not a Strategy

Organizations often begin their AI journey by asking:

“What tasks can we automate?”

A better question is:

“What decisions could we improve if our people had more time, better information, and stronger analytical tools?”

Finance has always been responsible for turning information into decisions. AI simply expands its ability to do that work faster and at greater scale.

Moving Beyond Reporting

Most finance organizations already possess large amounts of data.

Financial statements.

Forecasts.

Vendor spending.

Capital projects.

Procurement.

Contract performance.

Cash flow.

Operational metrics.

Historically, much of the finance team’s effort has been devoted to collecting, validating, and presenting that information.

AI allows those activities to become increasingly automated.

That creates capacity for work that generates greater organizational value:

• evaluating investment alternatives
• modeling strategic scenarios
• identifying operational inefficiencies
• improving forecasting accuracy
• strengthening vendor oversight
• supporting capital allocation decisions

The objective is not fewer finance professionals.

It is better use of financial expertise.

Better Decisions Require Better Data

Artificial intelligence amplifies the quality of the information it receives.

Organizations with fragmented systems, inconsistent data definitions, or poor governance should expect AI to expose those weaknesses rather than solve them.

Successful AI adoption depends on disciplined data management, clear ownership, consistent definitions, and governance that ensures information can be trusted.

Technology cannot compensate for poor data quality.

Finance and Technology Must Lead Together

AI adoption should never be viewed as an isolated technology initiative.

Finance understands business value.

Technology understands platforms, integration, cybersecurity, and implementation.

Together, they create solutions that are technically feasible, financially responsible, and operationally sustainable.

The strongest AI programs emerge when CFOs and CIOs work as partners rather than customers and service providers.

Governance Determines Long-Term Success

As AI becomes embedded within forecasting, financial planning, reporting, procurement, and decision support, governance becomes increasingly important.

Organizations should establish clear expectations for:

• data quality
• model transparency
• regulatory compliance
• human review of significant decisions
• security and privacy
• accountability for AI-generated outputs

Trust is built through governance, not automation.

AI Should Augment Human Judgment

The greatest contribution AI can make to finance is not replacing analysis.

It is creating more time for it.

Finance professionals are uniquely positioned to evaluate tradeoffs, challenge assumptions, assess risk, and allocate capital. Those responsibilities require judgment, experience, and business context that AI cannot provide independently.

Organizations that use AI successfully will automate routine work while elevating the strategic role of their finance teams.

That is where the greatest value will be created.

AI is changing finance, but its greatest contribution will not be producing reports faster. It will be giving finance leaders more capacity to guide better decisions across the enterprise.

What Total Football Teaches Us About Adaptive Organizations

One of the most influential business articles I’ve ever read wasn’t really about manufacturing.

It was about adaptability.

While reading Making Mass Customization Work by B. Joseph Pine II, Bart Victor, and Andrew C. Boynton, I was reminded of an entirely different discipline: Total Football.

Originally developed and popularized by Ajax and the Dutch national team, Total Football challenged one of the fundamental assumptions of team sports. Instead of rigid positional responsibilities, every player understood the broader system. As one player advanced, another instinctively filled the space. The team remained balanced because everyone understood both their own role and how their role fit within the larger objective.

The lesson extends far beyond football.

Adaptability Creates Competitive Advantage

Organizations often define people by job titles.

Engineers engineer.

Project managers manage projects.

Security teams secure systems.

Operations teams operate infrastructure.

Specialization is important, but organizations become fragile when work depends too heavily on rigid organizational boundaries.

The most resilient organizations develop people who understand how the entire system works, not just their individual responsibilities.

When priorities change, customer needs evolve, or unexpected problems emerge, those organizations adapt far more effectively because people know how to collaborate beyond functional silos.

Every Team Needs Positional Flexibility

Positional flexibility does not mean everyone performs every job.

It means individuals understand enough about adjacent functions to contribute when circumstances require it.

I’ve consistently found that organizations perform better when engineers understand customer impact, project managers appreciate technical constraints, security teams participate early in architecture discussions, and infrastructure teams understand business priorities.

People remain specialists.

But they stop becoming isolated specialists.

Shared Awareness Is More Valuable Than Perfect Processes

Many organizations attempt to solve complexity by adding process.

Process certainly has value, but process alone rarely creates adaptability.

Shared awareness does.

Teams that communicate continuously, understand organizational priorities, and trust one another make better decisions even when situations change unexpectedly.

That principle explains why high-performing organizations often respond to disruption more effectively than organizations with more documentation or more rigid governance.

The difference is not process maturity.

It is collective understanding.

Leadership Creates the Conditions

Adaptive organizations do not emerge by accident.

Leaders create environments where collaboration is rewarded, information moves freely, and expertise is valued regardless of organizational boundaries.

That often requires cross-functional projects, rotational assignments, shared objectives, and deliberate investment in developing broader business understanding—not simply deeper technical specialization.

People become more valuable when they understand how their work enables everyone else’s success.

Technology Organizations Need This More Than Ever

Artificial intelligence, cloud platforms, cybersecurity, data engineering, enterprise architecture, and software delivery have become deeply interconnected.

No single discipline can solve today’s enterprise challenges independently.

Technology organizations increasingly succeed through coordinated expertise rather than isolated excellence.

The leaders who build adaptive organizations recognize that the goal is not to eliminate specialization. It is to create enough shared understanding that teams continue moving forward when priorities shift.

The Best Teams Think Like Systems

Total Football demonstrated that extraordinary teams are built on flexibility, trust, communication, and shared purpose.

The same is true for modern organizations.

Competitive advantage increasingly belongs to organizations that can learn faster, adapt sooner, and coordinate more effectively than their competitors.

That begins with leaders who build systems where people understand more than their own position—and recognize that the success of the organization depends on how well those positions work together.

Who Carries the Risk? Lessons from Technology Contracting

One of the most important questions in any technology contract is not the price.

It's: Who carries the risk when conditions change?

Technology projects rarely unfold exactly as expected. Supply chain disruptions, cybersecurity requirements, inflation, changing business priorities, labor shortages, and evolving technical standards all affect cost, schedule, and delivery. Well-structured contracts recognize those realities by clearly allocating risk between the customer and the service provider.

Understanding those tradeoffs is an important leadership responsibility.

Fixed Price Does Not Mean Fixed Risk

Many organizations assume a fixed-price contract transfers all financial risk to the contractor. In practice, risk is shared, even when pricing is fixed.

If specialized hardware becomes unavailable, labor costs rise unexpectedly, or regulatory requirements change during execution, someone ultimately absorbs those additional costs. The question is whether the contract anticipated those possibilities and assigned responsibility appropriately.

In federal contracting, that balance is particularly important. Government agencies seek cost certainty and responsible stewardship of taxpayer resources. Contractors, meanwhile, must manage delivery risk while maintaining financial viability. Successful partnerships recognize that long-term performance depends on both objectives being achieved.

Innovation Changes the Equation

Risk allocation also works in the opposite direction.

As organizations improve delivery methods, automate repetitive work, standardize platforms, or streamline operations, the cost of delivering services often declines. Those efficiencies create opportunities for contractors to improve margins while remaining more competitive in future procurements.

In competitive markets, many of those operational improvements are ultimately reflected in lower bid prices or greater value delivered to customers. Organizations that continually improve how they work often compete more successfully than those relying solely on lower labor rates.

Contracts Should Encourage Better Outcomes

The strongest technology contracts are not designed simply to control cost. They encourage behaviors that improve long-term outcomes.

When incentives are aligned, organizations invest in automation, standardization, cybersecurity, quality, and continuous improvement because those investments benefit both parties. When incentives are poorly aligned, organizations may optimize for short-term contract performance at the expense of long-term operational success.

Technology leaders should evaluate contracts not only for commercial terms but also for how effectively they distribute risk, encourage innovation, and support sustainable performance.

Leadership Beyond the Contract

Technology contracting is ultimately an exercise in governance.

Leaders must understand where risk resides, how changing market conditions affect delivery, and whether contractual incentives continue to support the organization’s strategic objectives.

The goal is not simply to negotiate the lowest price. It is to create partnerships that remain resilient as technology, markets, and organizational priorities evolve.

The organizations that consistently achieve the best outcomes understand that effective contracting is less about transferring risk than managing it intelligently.

Technology Investment Requires Economic Judgment

One of the biggest misconceptions about technology leadership is that technology decisions are primarily technical decisions. They are not.

The best technology investments are business decisions grounded in economics.

Throughout my career leading infrastructure and operations teams, we regularly evaluated competing priorities: modernizing aging infrastructure, introducing new capabilities, improving cybersecurity, reducing operational risk, and maintaining reliable service. Technical feasibility was rarely the difficult part. The challenge was determining where finite resources would create the greatest long-term value.

That requires more than data.

Data Doesn’t Make Decisions

Technology organizations collect enormous amounts of data.

Asset inventories. Incident counts. Mean time to recovery. System utilization. Cloud costs. Vendor performance. Security events. Project budgets.

Those metrics are valuable, but by themselves they rarely answer the most important leadership questions.

Should we replace the platform this year?

Should we modernize now or extend the lifecycle another eighteen months?

Should cybersecurity funding increase ahead of application modernization?

Should we standardize globally or maintain local flexibility?

Those are economic decisions informed by technology—not technology decisions informed solely by data.

Looking Beyond Initial Cost

Organizations often focus on acquisition cost because it is easy to measure. The more meaningful question is total organizational impact.

A less expensive solution may require higher operating costs, greater administrative effort, increased cybersecurity exposure, or additional downtime over its lifetime. Conversely, a larger upfront investment may reduce operating expense, simplify support, improve resilience, and provide flexibility for future growth.

Technology leaders should evaluate investments across the full lifecycle rather than focusing on purchase price alone.

Cybersecurity Is an Economic Decision

Cybersecurity provides one of the clearest examples.

A Zero Trust initiative is often viewed as a security investment. In reality, it is also an economic investment.

Reducing the likelihood of a successful attack protects far more than technology assets. It reduces operational disruption, protects organizational reputation, strengthens regulatory compliance, lowers recovery costs, and preserves leadership’s ability to execute strategic priorities.

The return on investment is measured not only in avoided incidents, but in organizational resilience.

Modernization Should Be Continuous

I have also found that infrastructure modernization benefits from an economic perspective rather than a purely technical one.

Many organizations historically replaced major portions of their infrastructure on fixed multi-year cycles. While straightforward administratively, this often concentrated cost, increased operational disruption, and allowed technology to age significantly before replacement.

A rolling modernization strategy frequently produces better outcomes. Incremental upgrades distribute capital requirements more evenly, reduce operational risk, incorporate technological improvements more quickly, and avoid large-scale end-of-life events that strain both budgets and engineering teams.

The objective is not simply newer technology. It is better capital allocation.

Turning Information into Better Decisions

Technology organizations generate abundant data.

Leadership creates value by transforming that data into information that supports better decisions.

That requires understanding organizational priorities, financial constraints, operational risk, customer impact, regulatory obligations, and long-term strategy—not simply interpreting dashboards.

The most effective technology leaders do not ask, “Can we implement this?”

They ask, “Will this create lasting value for the organization?”

That distinction is where technology leadership becomes business leadership.

Leadership and Accountability in Healthcare Technology

Technology has become inseparable from patient care. Electronic health records, clinical systems, medical devices, cybersecurity, data analytics, and digital workflows all influence how safely and effectively care is delivered. As healthcare organizations become increasingly dependent on technology, leadership within IT becomes more than an operational responsibility—it becomes a responsibility to patients.

Successful healthcare technology organizations are built on three principles: accountability, trust, and continuous improvement.

Leadership Creates the Environment

Healthcare technology leaders operate in an environment where change is constant. New clinical applications, cybersecurity threats, regulatory requirements, interoperability standards, and evolving patient expectations require organizations to adapt without disrupting care.

That adaptation begins with leadership.

Leaders establish the vision, set priorities, remove barriers, and create an environment where teams are encouraged to solve problems rather than simply maintain systems. Innovation is important, but innovation must always support safer, more reliable patient care. New technology should improve outcomes, simplify workflows, and reduce risk—not create additional complexity.

Just as important, leaders must build confidence across the organization. Technology initiatives succeed when clinicians, administrators, and operational leaders understand why change is occurring and believe the organization can execute it successfully.

Accountability Builds Trust

Healthcare depends on trust, and technology organizations earn that trust through accountability.

Patient information must remain secure. Clinical systems must remain available. Infrastructure must perform reliably. When technology supports life-critical operations, accountability cannot be delegated—it must be embedded throughout the organization.

Leaders establish clear expectations, define ownership, measure performance, and create transparency around results. More importantly, they foster an environment where issues are identified early rather than hidden until they become crises.

The strongest technology organizations are not those that never experience problems. They are the organizations that identify issues quickly, respond effectively, learn from failures, and continuously improve.

Serving the Organization

Leadership is not measured by authority alone. It is measured by how effectively leaders enable others to succeed.

Technology professionals perform at their best when they understand the organization’s mission, have the resources they need, and know their expertise is valued. Leaders who invest in developing people, encourage collaboration across departments, and remove unnecessary obstacles create teams capable of solving increasingly complex challenges.

That culture extends beyond the IT department. Healthcare technology is inherently collaborative. Clinical staff, finance, compliance, operations, cybersecurity, and technology teams must work together to achieve shared outcomes. Leadership creates the conditions that make those partnerships successful.

Continuous Improvement

Healthcare organizations cannot afford to become comfortable with yesterday’s solutions.

Continuous improvement means evaluating systems, processes, governance, security, and workflows with the expectation that they can always become more effective. It also requires listening—to clinicians, patients, technology professionals, and business leaders—to understand where improvements will have the greatest impact.

Technology should never be implemented simply because it is new. It should be adopted because it demonstrably improves care delivery, strengthens resilience, reduces risk, or enables the organization to fulfill its mission more effectively.

Leadership in Service of Patient Care

Technology is now fundamental to nearly every aspect of modern healthcare. The responsibility of healthcare technology leaders extends well beyond infrastructure, applications, or cybersecurity. Their work influences clinical outcomes, operational performance, regulatory compliance, and the trust patients place in the organizations that care for them.

Organizations that combine clear accountability, collaborative leadership, and a commitment to continuous improvement are better positioned to navigate change while maintaining the reliability, security, and resilience that modern healthcare demands. Ultimately, effective healthcare technology leadership is not measured by the systems it deploys, but by the confidence it creates and the care it enables.