Force Multipliers

 

What separates exceptional organizations from average ones isn’t that people work harder. It’s that one person, one decision, or one improvement changes everything else.

Activity and effectiveness aren’t the same thing. The better question is this: Where will one investment make the greatest difference?

Sometimes it’s technology. Sometimes it’s a process. More often, it’s a person others overlooked. Once you start looking for force multipliers, you begin seeing them everywhere.

The names in the following stories have been changed.

One of the first people who taught me what a force multiplier looked like was an engineer I’ll call Bob.

Before I interviewed him, I was advised not to hire him because English wasn’t his first language. I ignored the advice, and we interviewed anyway. After a panel interview, everyone reached the same conclusion. He was technically gifted, thoughtful under pressure, and unusually collaborative.

I was told a second time not to hire him. I respectfully disagreed. I remember saying, “If we don’t hire him, someone else will.”

The issue was never Bob’s ability. It was whether we were willing to slow down long enough to listen before judging him by an accent. Hiring him remains one of the best decisions I ever made.

Every conversation brought a fresh perspective, and every significant issue became a team effort until it was resolved.

Bob made everyone around him better.

Another engineer taught me an equally important lesson. I’ll call him John.

John spoke slowly. He greeted everyone with “Boss” because that was his way of showing respect. He rarely said more than necessary, and because of that, some people underestimated him almost immediately.

One morning I was instructed to terminate him because he “didn’t seem smart enough” and wasn’t in the office at eight a.m.

What no one realized was that John had worked until two o’clock that morning, preventing a significant network issue from becoming a major outage. He had called me during the night so we could work through the problem together. He wasn’t absent; he was recovering after protecting the organization while everyone else slept.

John wasn’t exceptional because he was technically gifted. He had remarkable judgment. He knew when to act, when to ask for help, and when something deserved immediate attention.

That experience reinforced something I’ve never forgotten. Leaders can’t confuse style with substance. Some of the greatest force multipliers don’t look like force multipliers until you give them the opportunity to demonstrate what they’re capable of.

Force multipliers aren’t always people. Sometimes they’re created by giving people a voice.

At one organization, we made what many considered a controversial governance change. Every major steering committee would include at least three engineers, and those engineers had veto authority.

Some worried it would slow decisions. It did exactly the opposite. The people closest to the work finally had a voice. Architects caught design flaws. Operations identified implementation issues. Engineers challenged assumptions before they became expensive mistakes. Meetings became shorter. Projects moved faster. Rework dropped dramatically—not because we held more meetings, but because the right people were helping shape decisions before they became expensive.

One of my teams spent nearly eight hours every week preparing slide decks. By introducing AI into the process, we reduced that effort to roughly three hours. The real benefit wasn’t the five hours we saved. Those five hours became time to solve problems, meet with stakeholders, improve solutions, and create value no AI could deliver.

I’ve learned that sometimes the multiplier isn’t innovation at all. Sometimes it’s discipline.

One individual consistently challenged every initiative. He questioned every proposal and often frustrated the rest of the team. Many viewed him as an obstacle. I saw someone who cared deeply about getting the right answer. Instead of minimizing his influence, I recommended he lead the steering committee.

Once responsible for balancing everyone’s priorities instead of defending only his own, his skepticism became one of the organization’s greatest strengths. He still asked difficult questions, but now those questions improved enterprise decisions instead of slowing them down.

Sometime later, another engineer on my team had become increasingly frustrated. His day-to-day responsibilities no longer challenged him, but through several conversations I learned he had independently earned three ITIL certifications because he was fascinated by process improvement and finding better ways for engineers to work.

Rather than asking him to continue work that had become routine, I challenged him to think bigger. I asked him to help us rethink our IT governance—how decisions were made, how technology aligned with business objectives, and where frameworks like ITIL could have the greatest impact. I wanted him to help shape how the organization operated—not simply implement processes.

What started as an engineer looking for a new opportunity became a broader transformation in how we governed technology. He found work that inspired him. The organization found a leader.

The greatest force multiplier I’ve ever experienced wasn’t a person, a process, or a technology. It was culture.

On one program, a junior engineer made a mistake that briefly disrupted network connectivity for an entire headquarters building.

Leadership immediately wanted a name.

I refused.
The team owned the mistake.
The team owned the solution.

Sometime later, another significant outage occurred. Once again, fingers immediately pointed toward the network team. Instead of assigning blame, we investigated. The root cause turned out to be a DevOps change.

I contacted the leader privately—not to identify someone to blame, but to understand what happened and how we could prevent it from happening again. We focused on corrective actions and stronger guardrails instead of blame. 

Gradually, something changed. People stopped hiding mistakes. Instead of waiting for investigations, they stepped forward.

“This was our change.”
“Here’s what happened.”
“Here’s the fix.”
“And here’s what we’re changing so it doesn’t happen again.”

Accountability replaced blame. Problems surfaced earlier. Solutions arrived faster. Trust became a force multiplier.

When I walk into an organization today, I’m still asking the same question:
Where will one investment make the greatest difference?

Sometimes it’s a person.
Sometimes it’s giving the right people a voice.
Sometimes it’s technology used well.
Sometimes it’s a culture built on trust.

The answer rarely begins with asking people to work harder.
It begins by recognizing the force multipliers that make everyone better.

– Tim

Stability is Underrated

 

A lot of leadership discussion today revolves around disruption, rapid transformation, aggressive scaling, and moving faster than everyone else. Some of that absolutely matters. Markets and technology change and organizations have to adapt.

But most environments do not actually fail because they lack another transformation initiative.

Usually, they struggle because basic operational consistency starts breaking down underneath them.

Sometimes processes and expectations change depending on who is leading the meeting that week. Different teams have different ways to solve the same problems. This leads to inconsistent reporting. Escalations can become emotional instead of procedural. Onboarding playbooks don’t stay up to date, and institutional knowledge lives inside individuals instead of an operational structure. This makes steady growth hard.

The organizations that tend to scale well are often the ones that become a little boring operationally. Good onboarding. Predictable governance. Defined and consistent ownership. Repeatable processes. Stable escalation paths. Consistent communication. People know what success looks like and how decisions get made without needing constant interpretation from leadership every single time something changes.

That kind of stability creates room for organizations to actually grow.

Without it, scaling usually means multiplying confusion.

I think this is part of the reason some organizations keep hiring smart people and still struggle operationally. Intelligence alone does not create consistency. A strong operating model does. So do simple playbooks that people can actually follow under pressure instead of beautifully designed processes nobody uses after the consultants leave.

The funny part is that this kind of operational discipline rarely gets celebrated publicly because it’s not exciting. Nobody announces a major press release because the escalation process got cleaned up or reporting structures finally stabilized across departments.

But those things matter.

Especially in environments trying to scale without burning people out or creating constant operational chaos underneath the surface.

Most organizations do not need more drama.

They need more consistency.

-Tim

Complexity Compounds

After enough years in IT, you start noticing that most technology problems are not really technology problems. Usually, the systems already exist. The engineers know the issues. The business has known the pain points for years. What’s usually missing is ownership and consistency.

A few years ago, I was in an environment running ServiceNow, Salesforce, and NetSuite with overlapping functions spread across all three. None of them were bad platforms. The problem was years of growth and departmental decisions had blurred responsibilities between systems. Teams were entering the same data multiple times. Reporting varied depending on which platform someone trusted more that week. Integrations became fragile. The software itself was only part of the cost. It took time and discipline to consolidate responsibilities and simplify workflows, but once that happened, operations got noticeably smoother almost immediately.

The more environments I work in, and the more mistakes I make and grow from along the way, the less interested I am in shiny platforms and giant transformation announcements. Most organizations run better when things get simpler.

AI as the Civic Moonshot: How Companies Can Profit by Building Toward the Public Good

A colleague recently suggested I read The Technological Republic by Alex Karp. Not long after, I came across Ross Andersen’s article in The Atlantic titled “Every Scientific Empire Comes to an End.” Karp writes as a chief executive working inside the technology industry. Andersen, a journalist and historian of ideas, explores the topic through a global and historical lens. Their approaches may be different, but their message is the same: when science and engineering lose their connection to civic purpose, we lose progress.

Civic purpose is the belief that progress should serve the public and improve lives. It keeps innovation focused on long-term value. Without this, even the most powerful technologies can lose direction, fall out of public trust, or even do harm. The real value of new tools comes not just from their capabilities, but from how they are used and who they serve.

Andersen illustrates his point through history. He traces the rise and collapse of the Soviet Union, showing how a country once rich in scientific achievement lost its edge. Early on, national vision and investment drove breakthroughs. Later, political pressure and authoritarian control stripped science of its independence and impact. Over time, authoritarian control strangled openness, and scientists who showed too much independence, such as the one Andersen profiles, were pushed out, even under Gorbachev’s reforms. After the Soviet Union collapsed, a new kind of threat emerged. Oligarchy drained resources from public institutions as state assets were rapidly privatized. Research centers withered, funding vanished, and many of the country’s best minds left for opportunities abroad. The decline did not happen all at once. Scientific work was slowly pulled into politics, then sidelined. Big ideas gave way to resource extraction, and the broader promise of knowledge lost its place in the public imagination.

Karp approaches from a different angle. He is not writing about state control or oligarchy, but he is just as concerned about what weakens long-term progress. In The Technological Republic, he focuses on how companies, especially in the West, often organize themselves around short-term targets. The pursuit of quarterly results shapes what gets attention and what does not. Complex or long-term projects tend to fall away. Over time, the larger sense of direction fades. Civic goals are not rejected outright; they are simply forgotten. Unlike Andersen’s account of stagnation under pressure from the state, Karp’s story is about stagnation through distraction. In both cases, ambition dries up.

Andersen and Karp both touch on something deeper that often gets missed: without direction, progress tends to stall. Science, when disconnected from public purpose, loses momentum. Business, when focused only on short-term gain, stops building anything meaningful. The question is not whether companies should choose between purpose and profit. The question is how to build a model where one reinforces the other. This is where artificial intelligence (AI) enters the conversation.

Artificial intelligence is a rare opening

It creates a chance to reconnect technological progress with broader public goals. Unlike past waves of innovation, AI is not a single invention or product line. It is a foundational shift, already underway, that can support large-scale outcomes. These systems are improving early detection of disease, helping reduce food waste through precision agriculture, and accelerating the development of clean energy materials. In practical terms, artificial intelligence is already delivering value in places that matter.

What will determine its impact now is how it is used and for what reason

Companies that align their use of artificial intelligence with broader public benefit do more than contribute to society. They also position themselves for longer-term strength. That strength shows up in how they attract talent, how customers view the brand, and how new partnerships take shape. These are not side effects. They are competitive signals.

The intent behind artificial intelligence matters. It is not just about what a system can do, but how it does it. Companies that build with privacy in mind, protect systems from misuse, make their tools accessible across communities, and explain how decisions are made will stand out. These principles are no longer optional. They are now part of what it means to build credibility in the market.

This is where alignment becomes a strategy

The market is already paying attention to public value, but what is often missing is integration. Most organizations have some kind of community engagement or cause marketing. Many speak up during cultural moments or awareness campaigns. These efforts may reflect good intentions, but they rarely shape core business decisions.

Artificial intelligence offers a more grounded path. It gives companies a way to center their capabilities on goals that stretch beyond quarterly results. That approach does not replace performance. It strengthens it.

When purpose becomes part of how a company operates, not just how it communicates, everything changes. Growth becomes more stable. Teams stay longer. Public support builds over time. And the business becomes harder to disrupt.

• A logistics company can use artificial intelligence to cut fuel use through better routing, reducing emissions and operating costs at once.
• A regional hospital system can partner with vendors to pilot diagnostic models that improve outcomes for underserved populations.
• A food manufacturer can use artificial intelligence to detect contamination patterns or optimize energy use across plants.
• A financial services firm can use intelligent automation to widen access to loans or improve fraud detection in real time.
• A construction company can use predictive modeling to prevent injuries, protect lives, and reduce insurance costs.
• A consumer goods brand can use generative systems to reduce time to market for product testing, while also lowering waste.

None of these requires a moonshot budget. They require intention.

Civic purpose does not mean charity

Karp writes that artificial intelligence will reflect the society that builds and trains it. If we aim it only toward monetization, that is what it will mirror. But when companies choose to shape these systems with shared values in mind, something better happens. The market responds to products and services that improve lives, especially when people see those outcomes clearly. That feedback loop (public value, visible impact, trusted brand) is profitable.

A civic-minded approach does not ask companies to sacrifice growth. It gives them a better reason to grow. And it creates room for more durable success than companies chasing isolated wins. Public support builds resilience. Employees stay longer when they know their work matters. Investors notice when a company is part of the solution to large problems. And as artificial intelligence becomes more central to how businesses operate, those who align early will shape the narrative.

What a modern civic pact looks like:

• Fund broad goals, not just marketing campaigns. Leaders should support internal teams that want to explore uses of artificial intelligence in service of public benefit. That exploration is not overhead. It is positioning.
• Track longer outcomes alongside quarterly ones. Boards can ask how capital is supporting multi-year bets. That transparency signals confidence, not drift.
• Keep the door open to global talent. Organizations benefit when immigration brings in new knowledge. Retaining that edge means building environments where people want to stay.
• Speak clearly. Companies that describe what they are building and why it matters do better in the public eye. The benefit is not in hiding ambition, but in connecting it to something larger than themselves.

The upside is real and durable

A civic-minded innovation strategy creates more than ideas. It attracts talent, builds resilience, and reinforces trust. And it does this while generating revenue and competitive advantage. That is not a tradeoff. That is the definition of durable growth.

Andersen ends his article by comparing American science to a crumbling empire. That outcome is avoidable. We still have the resources, the talent, and the tools. What we need now is the clarity and resolve to apply them with purpose.

Artificial intelligence can be that rallying point. But only if we build it not only to scale, but to unify.

The most effective organizations are those that root purpose in how they operate and govern. When purpose guides decisions from the project level to the boardroom, it becomes more than a message. It becomes part of the business. Companies that make this shift early help shape public trust and strengthen long-term value. Leadership that lasts comes from building what people can believe in.

The choice to lead this way rests with those shaping the future: scientists, engineers, founders, board members, and the communities they serve. And it begins with a serious question, asked before any major initiative:

Will this move the country forward, or only the stock ticker?

Answer well, and there is no need to pick between civic purpose and profit. You get both. And you build something that endures.

Practical IT Governance for Mid-Sized Companies

Technology decisions are business decisions. For mid-sized companies, where capital, talent, and management attention are limited, effective IT governance helps ensure those decisions support growth rather than create unnecessary cost, risk, or complexity.

IT governance does not need to mean additional bureaucracy or layers of approval. At its best, it establishes clear decision rights, accountability, and priorities so leaders can make informed choices about technology investments, cybersecurity, vendors, data, and operations.

Aligning Technology with Business Priorities

Every technology investment should support a defined business objective. That may include improving customer experience, enabling growth, reducing operating costs, strengthening resilience, or meeting regulatory requirements.

Without a clear governance process, organizations can accumulate disconnected systems, redundant vendors, and projects that consume resources without producing meaningful business value. Governance creates a disciplined way to evaluate proposed investments, compare competing priorities, and confirm that funding is directed toward the organization’s most important needs.

Managing Risk Before It Becomes Disruption

Cybersecurity, regulatory compliance, business continuity, data protection, and third-party risk cannot be treated as isolated technical concerns. They require business ownership and informed executive oversight.

Effective governance clarifies who may accept risk, who is responsible for remediation, and how material concerns are communicated to leadership. This allows organizations to address vulnerabilities based on business impact rather than relying solely on technical severity or reacting after an incident occurs.

Controlling Cost and Complexity

Technology costs often increase gradually through overlapping applications, underused licenses, fragmented infrastructure, and vendor agreements that are renewed without sufficient review.

Governance introduces discipline into purchasing, architecture, and lifecycle decisions. It helps leaders understand not only what a technology costs to acquire, but also what it will cost to integrate, secure, operate, support, and eventually replace.

The objective is not simply to spend less. It is to spend intentionally and avoid complexity that creates recurring costs, slows execution, and limits future choices.

Establishing Clear Decision Rights

Many technology problems are ultimately decision-making problems. Projects stall when ownership is unclear, business and technology teams operate with different assumptions, or no one has authority to resolve competing priorities.

A practical governance model defines:

• which decisions remain within technology teams

• which require business sponsorship

• when finance, legal, cybersecurity, or operations must participate

• who approves exceptions

• and how unresolved risks are escalated

Clear decision rights reduce delay, improve accountability, and prevent issues from being passed between functions.

Governing Vendors and Technology Partners

Mid-sized organizations often depend heavily on external providers. Managed-service firms, cloud platforms, software vendors, consultants, and implementation partners may control critical parts of the operating environment.

Governance ensures these relationships are managed according to performance, risk, cost, and business value. Contracts should include clear expectations, measurable outcomes, accountability for service failures, and regular reviews of whether the relationship continues to meet the organization’s needs.

Vendor governance is particularly important during periods of rapid growth or acquisition, when overlapping contracts and inconsistent standards can quickly erode anticipated value.

Using the Right Level of Governance

A mid-sized company does not need the same governance structure as a global enterprise. The process should be proportionate to the organization’s size, regulatory environment, complexity, and risk.

A practical model may include:

• an agreed technology strategy

• a prioritized investment portfolio

• architecture and cybersecurity standards

• defined approval thresholds

• regular risk and performance reporting

• vendor and contract reviews

• and a small cross-functional forum for major decisions

The goal is to create enough structure to improve decisions without slowing the organization unnecessarily.

Governance as an Enabler of Growth

Strong IT governance is not designed to prevent action. It enables the organization to move with greater confidence because leaders understand the risks, costs, dependencies, and expected outcomes of their decisions.

For mid-sized companies, that discipline can be a competitive advantage. It allows limited resources to be focused on the initiatives that matter most, reduces avoidable complexity, and creates a more stable foundation for growth.

Technology creates value when it is connected to business priorities, governed with discipline, and measured by outcomes. IT governance provides the structure that makes that possible.

Cybersecurity Resilience Is an Operating Capability

Most organizations invest heavily in preventing cyberattacks.

Far fewer invest equally in their ability to continue operating when prevention inevitably fails.

That distinction matters.

Cybersecurity resilience is not measured by whether an organization experiences an attack. It is measured by how effectively it prepares for disruption, responds under pressure, recovers critical operations, and learns from the experience.

In today’s environment, resilience has become an operational capability rather than simply a cybersecurity objective.

Cybersecurity Is a Business Responsibility

Cybersecurity is often viewed as a technology function.

It isn’t.

Every significant cyber incident affects business operations, customer confidence, regulatory compliance, financial performance, and organizational reputation. While technology teams manage many of the controls, resilience requires leadership across the enterprise.

Executives, business leaders, legal counsel, communications teams, finance, operations, human resources, and technology all play critical roles before, during, and after an incident.

Organizations that recognize cybersecurity as an enterprise responsibility consistently respond more effectively than those that treat it solely as an IT problem.

Resilience Begins Before an Incident

Technical safeguards remain essential.

Identity management, multi-factor authentication, vulnerability management, endpoint protection, network segmentation, backups, monitoring, and security awareness all reduce organizational risk.

However, resilience requires additional capabilities.

Organizations should understand which business services are most critical, define recovery priorities, establish decision-making authority, exercise incident response plans, evaluate third-party dependencies, and ensure leadership understands its responsibilities during a crisis.

Preparation determines performance.

Leadership Matters Most During Uncertainty

Technology leaders are expected to provide calm, informed decision-making when information is incomplete and pressure is high.

That responsibility extends well beyond technical remediation.

Leaders must balance operational continuity, regulatory obligations, customer communication, executive decision-making, and organizational confidence while technical teams investigate and recover.

Resilient organizations develop these leadership capabilities before they need them.

Tabletop exercises, executive simulations, and cross-functional planning often provide greater long-term value than simply purchasing another security tool.

Recovery Is Part of Security

Organizations often focus heavily on preventing attacks while giving less attention to recovery.

Yet resilience depends on the ability to restore operations safely, validate system integrity, communicate transparently, and return the organization to normal business operations with confidence.

Recovery planning should address not only technology restoration but also business processes, vendor coordination, customer communications, regulatory reporting, and lessons learned.

Recovery is where preparation becomes operational performance.

Continuous Improvement Strengthens Resilience

Every incident, near miss, audit, and exercise provides an opportunity to improve.

The strongest organizations continually evaluate what worked, what failed, and where governance, technology, communication, or decision-making can be strengthened.

Cybersecurity resilience is not a project with a completion date.

It is an organizational capability that matures over time through disciplined leadership, continuous learning, and operational experience.

Resilience Creates Confidence

No organization can eliminate cyber risk entirely.

What leaders can control is how well their organizations prepare, respond, recover, and adapt.

Organizations that invest in resilience protect far more than their technology. They protect customer trust, organizational reputation, operational continuity, and the confidence that stakeholders place in their leadership.

In the end, cybersecurity resilience is not measured by avoiding every attack. It is measured by an organization’s ability to continue fulfilling its mission when adversity inevitably arrives.

Why Technology Leaders Must Speak the Language of Finance

One of the most valuable lessons I have learned throughout my career is that technology leadership is fundamentally a business discipline.

Technology decisions influence capital allocation, operating expense, productivity, risk, customer experience, and long-term enterprise value. Yet many organizations still treat finance and technology as separate conversations.

The most effective organizations recognize they are the same conversation viewed from different perspectives.

Technology Is an Investment Portfolio

Every organization has more technology opportunities than it has resources to pursue them.

Infrastructure modernization.

Cybersecurity.

Cloud adoption.

Artificial intelligence.

Data platforms.

Application modernization.

Digital transformation.

The question is rarely whether these initiatives have value.

The question is which investments should be made first.

Finance brings discipline to capital allocation.

Technology brings understanding of operational capability, technical risk, and long-term sustainability.

Together, they determine where limited resources will create the greatest business value.

Speaking a Common Language

Technology leaders often explain solutions in technical terms.

Finance leaders evaluate decisions through business outcomes.

Both perspectives are necessary.

When proposing a major technology initiative, executives should be able to explain not only how the technology works, but also how it affects revenue, operating expense, productivity, resilience, customer experience, regulatory compliance, and enterprise risk.

Successful technology leaders translate technical decisions into business outcomes.

That translation builds trust.

Cost Is Only One Dimension

Technology discussions frequently begin with cost.

The more important conversation is value.

A larger initial investment may reduce operating expense for years.

Infrastructure modernization may reduce outages, improve productivity, strengthen cybersecurity, simplify vendor management, and accelerate future initiatives.

Artificial intelligence may reduce repetitive work while allowing highly skilled employees to focus on higher-value analysis.

The objective is not minimizing technology spending.

It is maximizing organizational return.

Better Decisions Require Partnership

Finance should not evaluate technology investments after decisions have already been made.

Likewise, technology should not treat financial review as a final approval step.

The strongest organizations involve finance early in technology planning and technology leaders early in financial planning.

That partnership produces more realistic business cases, stronger prioritization, better forecasting, and more disciplined execution.

It also improves organizational confidence because investment decisions are based on shared understanding rather than competing priorities.

Leadership Beyond Technology

The role of today’s technology executive extends far beyond infrastructure and applications.

Technology leaders help organizations allocate capital, manage enterprise risk, evaluate acquisitions, improve operations, strengthen governance, and enable long-term growth.

Those responsibilities require financial fluency as much as technical expertise.

Understanding finance does not make technology leaders less technical.

It makes them more effective business leaders.

A Shared Objective

Finance and technology ultimately pursue the same objective: creating sustainable enterprise value.

Finance provides financial discipline.

Technology provides operational capability.

When both functions work together from the beginning, organizations make better decisions, invest more wisely, and execute with greater confidence.

The strongest technology leaders do not simply understand technology.

They understand how technology creates business value.

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.

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.