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

Technology Isn’t a Cost Center. It’s an Enterprise Value Creator.

 

When organizations discuss technology investments, the conversation often begins with cost. Hardware, software, cloud services, licensing, and staffing are all scrutinized because they appear on a budget. It’s understandable. Leaders have a responsibility to manage investments wisely.

The conversation can also become distracted by the latest platform, the newest capability, or whatever technology happens to dominate the headlines. While innovation is important, adopting technology simply because it’s new is no more effective than rejecting it simply because it costs more.

Technology has never created value simply because it costs less or because it’s the latest trend. It creates value by enabling organizations to operate differently, make better decisions, remove constraints, and pursue opportunities that would otherwise remain out of reach.

One example came while leading the modernization of a large enterprise environment. We were preparing to expand into the cloud while continuing to support mission-critical applications running in our existing data centers. The architecture needed to support modern cloud-native applications while maintaining compatibility with existing enterprise systems. It also had to provide high availability across multiple organizations that depended on shared services.

At the time, the cloud provider’s native load-balancing capabilities had not yet matured enough to provide the flexibility we required. We turned to a trusted technology partner whose products had served us well in our on-premises environment and who had begun offering a cloud-based solution. Their initial assessment was straightforward: what we wanted to accomplish wasn’t supported.

For many organizations, that would have ended the discussion. The architecture would have been redesigned around the limitation, and the opportunity to build a more capable foundation would have been lost. Instead, we challenged the assumption—not because we believed the vendor was wrong, but because the business outcome mattered more than accepting the first answer. Our engineers worked alongside the vendor’s engineering team until we developed an approach that supported modern containerized workloads, traditional enterprise applications, and our existing infrastructure as a unified platform. The solution preserved existing investments while creating a scalable path to the cloud. It also improved interoperability across agencies and freed developers to focus on delivering business capabilities instead of engineering around infrastructure constraints.

The architecture quietly continued to pay dividends long after the project was complete. Developers spent less time engineering around infrastructure constraints and more time delivering capabilities to the business. Our CI/CD pipeline became more efficient, operations became simpler, and each successive technology decision became easier because the foundation had been built to evolve with the enterprise instead of holding it back. What began as an infrastructure challenge became a catalyst for enterprise value creation, compounding over time through faster delivery, greater operational efficiency, and the freedom to adapt as business needs changed.

Earlier in my career, I learned the same lesson through virtualization. Most organizations justified virtualization by counting the number of physical servers they could eliminate. The hardware savings were real, but they represented only a fraction of the return. Reducing power consumption, cooling requirements, provisioning time, and operational effort allowed engineering teams to spend less time maintaining infrastructure and more time delivering value. Once again, the greatest return came not from the technology itself, but from the stronger foundation it created for everything that followed.

That’s why I’ve come to believe the greatest return on a technology investment isn’t measured when the project is finished. It’s realized in every capability the organization delivers more quickly, every constraint it no longer has to engineer around, and every opportunity it can pursue because the right foundation was put in place.

Technology should never be viewed as a cost center. Its greatest value isn’t in the systems we deploy, but in what they allow the enterprise to become.

- Tim

Tim Gabaree is a technology executive who writes about enterprise value creation, governance, operational leadership, and the role of technology in helping organizations grow and perform.

When Paying More Costs Less: A Strategy-to-Execution Lesson in 2 Minutes

A client approached us after a cloud modernization and application rationalization program had fallen behind schedule. The initiative supported approximately 3,500 users and included more than 1,500 applications. One year into a planned three-year effort, progress lagged expectations, and budget concerns were growing.

The delivery model relied heavily on junior personnel. Labor rates were low, but the work required experienced practitioners. Rationalization, change management, architecture, and delivery all depended on sound judgment. Discovery and rationalization lacked discipline. Change management was weak. Application modernization decisions often lacked the experience required to execute effectively.

The project appeared inexpensive on paper. Delivery told a different story.

After assessing the program, we recommended a different approach. We introduced experienced business process specialists, change management professionals, application rationalization experts, and senior cloud engineers. Labor costs increased by 50 percent.

The team rationalized more than 1,500 applications to fewer than 500. Approximately 400 applications were modernized and rebuilt for cloud operation. Roughly 40 were migrated through lift-and-shift approaches. Remaining applications were retained on-premises due to business or technical constraints or designated for retirement.

The original plan projected three years to MVP. We joined after the first year and achieved MVP with approximately one year remaining on the original schedule. This means that delivery accelerated by 33 percent. And despite higher labor costs, program spend decreased by 20 percent.

Labor cost and delivery cost are not the same thing. Lower hourly rates often look attractive during procurement, but delays, rework, poor decisions, and deferred value rarely appear on the same spreadsheet.

Experienced personnel cost more per hour. The total cost of delivery often tells a different story. Organizations should evaluate the total cost of delivery rather than the hourly cost of labor because sometimes paying more costs less.

The Last Two Across the Finish Line

 

Many years ago, I attended the Ranger Indoctrination Program (RIP), which is now known as the Ranger Assessment and Selection Program (RASP).

One of the events was a five-mile run that had to be completed within a strict time limit. It was designed to create stress and accelerate attrition. 

About halfway through, I caught up to another candidate who was struggling and out of breath. He was in good physical condition, muscular and built more like a bodybuilder than a runner. He wasn’t a quitter, but this event just wasn’t his strength. I had a choice to keep my pace and finish comfortably, or slow down and help him. I slowed down and stayed with him. We spent the rest of the run pushing each other to finish. By the time we approached the finish line, everyone else had already crossed. Several candidates had already been dropped for not making it in time. The Black Hats (what our instructors were called) saw us coming from a distance. We were the last two across the finish line. And they informed us that we'd both passed. We’d moved on to the next round.

At the time, I didn’t think much about the decision, as during Infantry Basic Training, Advanced Individual Training, and RIP, one lesson was endlessly repeated: 

Never leave your buddy behind.

As you could probably guess at this point, this story isn’t really about running or about my experience as a Rippie. It’s about a lesson that has stayed with me for more than thirty years.

And I’ve seen the same principle apply in business: Some of the best teams I’ve been part of were built by people willing to invest time and energy in helping others succeed, even when there was no immediate benefit to themselves. Likewise, many of the best leaders I’ve worked with understood that their job wasn’t to win alone. It was to help the team cross the finish line together.

What Mom and Dad Really Gave Me

 

Back in the early 1980s, I wanted a computer more than anything. It was a Commodore VIC-20, for those who are curious. The problem was that my family simply couldn’t afford one. We were of modest means, and there was very little disposable income. My mom and dad were honest with me about it. They told me they wished they could help, but the money just wasn’t there.

At the time, I had a paper route and picked up odd jobs at stores near where we lived. So I started saving. Before long, I realized that at the pace I was earning money, it would take years to buy a computer. To a kid, that was FOREVER.

I asked my parents again if there was any way they could help me get one sooner. Once again, they explained that they simply couldn’t afford to buy me a computer. But instead of leaving it there, they encouraged me to think differently. They suggested I use my paper route money to buy a lawn mower, rake, and basic equipment to start mowing lawns in the neighborhood. They explained that it would take time and work to get there, but it could eventually earn enough money for the computer I wanted.

So that became the plan.

For about five months, I saved every dollar I could. I got about halfway to what I needed for the equipment. Then my mom and dad surprised me. Quietly, without telling me, they’d been saving what little they could to help cover the rest. Looking back as an adult, I have no idea what they sacrificed to do that for me, especially knowing how tight money already was. But they somehow found a way.

Their sacrifice and guidance changed the direction of my life.

Together with my savings and their help, I bought the mower and equipment and started a lawn-mowing business during the summers. In the winters, I shoveled snow. What started as a way to earn money for a computer turned into a foundation for learning responsibility, discipline, customer service, and the value of creating opportunities instead of waiting for them.

By the age of 11, I finally bought that VIC-20.

More importantly, though, the experience taught me lessons far beyond that. Mom and Dad showed me what love looks like through sacrifice. They taught me the value of work, perseverance, gratitude, and ownership. They could’ve simply said no and left it there. Instead, they helped me find a path forward and quietly supported me however they could along the way.

I’ve never forgotten that and am forever grateful.

Thanks for reading.

Tim

Capital Discipline is Operational Discipline

 

If you have not read my earlier post, “Stability is Underrated,” I would probably start there first. This is really the financial side of the same conversation.

Healthy organizations usually think about money the same way good operators think about infrastructure.

Idle systems create waste. So does idle capital.

A lot of companies become so focused on controlling spending that they stop thinking carefully about whether their money is actually working once it reaches the balance sheet. Cash starts accumulating with no clear deployment strategy. Then six months later, leadership is simultaneously talking about cost pressure while large amounts of capital sit untouched, earning almost nothing because nobody wanted to make decisions around reserves, treasury management, reinvestment timing, or debt reduction priorities.

Conversely, sometimes organizations treat debt emotionally instead of operationally. Some leadership teams become so focused on eliminating debt entirely that they unintentionally restrict their own flexibility and delay investments that would have improved scalability or long-term operating health. Other environments go too far the opposite direction and operate as if cheap debt automatically excuses weak operational discipline underneath.

Usually, the healthiest organizations sit somewhere in the middle.

The strongest operators I have seen usually stay focused on flexibility:

• Enough liquidity to absorb problems without panic

• Enough discipline to avoid unnecessary exposure

• Enough operational consistency to keep investing during uncertain markets

• Enough structure that capital keeps moving intentionally instead of sitting untouched for years

That does not mean taking reckless risks.

Usually it means the opposite.

Some organizations quietly build strong long-term positions simply by staying disciplined while everybody else swings between overexpansion and overcorrection. Excess cash gets parked intelligently in low-risk instruments instead of sitting dormant. Capital projects get prioritized based on operational impact instead of internal politics or whoever speaks the loudest during budget season. Leadership stays realistic about what actually improves scalability versus what simply sounds impressive in a board presentation.

The environments that scale best usually understand a few things:

• Stability creates flexibility

• Predictability lowers operational stress

• Consistent cash management creates room for investment later

• Simple playbooks scale better than emotional decision-making

• Healthy debt and healthy liquidity can coexist

Most of this is not glamorous work. Nobody announces a major press release because reserve strategies became more disciplined or because treasury management quietly improved in the background.

But those things compound over time.

The same way operational debt compounds when organizations ignore process problems too long, financial inefficiency compounds when capital stops moving with purpose.

Good operators usually understand that stability and growth are not opposites.

Consistency creates room for growth.

- 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

Words Carry Weight

 

Years ago, when I was serving in the 3rd U.S. Infantry Regiment (The Old Guard), a few of us had gone out to Murphy’s in Old Town Alexandria after payday. When we returned later that night, another soldier stopped me outside our barracks.

“Hey Gabaree!”

He asked why I was there. I assumed he meant why I was out that late and told him I was probably a little too inebriated and needed to go sleep it off.

He stopped me again.

“No. Why are you HERE?”

He meant, “Why I was in the Old Guard?”

At the time, the question felt oddly philosophical for the middle of the night after a few drinks, but I shrugged and answered honestly. I told him it was an honor to help provide funeral honors for families who had lost someone in service to our country. That it mattered to make every detail as perfect as possible so families knew their loved one was respected and honored properly.

Months later, that same soldier stopped me in a hallway and thanked me.

I was confused until he explained that the night we spoke, he had been planning to go AWOL. He was leaving for good and trying to decide whether any of what we were doing mattered. Something about that conversation changed his mind.

I’ve thought about that moment many times over the years.

Words carry weight. Most of the time, we do not realize when someone is searching for meaning, encouragement, or simply a reason to keep going. We are usually caught up in our own world and do not always realize how much impact a few words can have.

I’m thankful that conversation went the way it did. If I had answered differently, things might have turned out very differently for him.

It became a reminder to me to be mindful of what we say. Sometimes a few words can change the direction of someone’s life.

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.

Three Moments That Shaped My Leadership Philosophy

Three experiences across my career fundamentally shaped how I think about leadership. One reinforced that accountability always flows upward. Another revealed how gatekeeping limits organizations. The third demonstrated what happens when leaders create space for people to contribute beyond their job descriptions. Together, they continue to influence how I lead today.

Accountability Flows Up

When I was an enlisted soldier, our Executive Officer was known for keeping distance from those he viewed as beneath him. He rarely asked for help and tended to dismiss contributions that came from lower ranks.. One evening, as he prepared to attend a congressional dinner, his dress uniform was not properly pressed, and his brass was not shined. It would have reflected poorly on him and on our unit. 

I knocked on his open door and offered to help him press his dress blues and shine his brass. The offer was not received well. He took offense at the idea that an E4 would offer assistance and viewed it as a challenge to his authority. I was ordered to do push-ups and told I would be recommended for a summary Article 15 for insubordination.

The next day, I was called into the Commanding Officer’s office. Present were the CO, the XO, the First Sergeant, my Platoon Leader, Platoon Sergeant, and Squad Leader. The CO ordered push-ups. Two hundred each. Everyone in the room. Including himself and the XO.

Afterward, the CO explained the reasoning: 

If a problem reaches the CO without being resolved, leadership has already failed. Accountability does not stop at rank. It compounds as authority increases.

The Commanding Officer made it clear that leadership should never use authority to protect pride or avoid embarrassment.

That moment clarified something fundamental for me. Leadership means leading from the front and owning the environment you create. When problems reach the surface, leaders should first examine the environment they created before assigning blame elsewhere.  And sometimes individuals serve an important role by demonstrating what leadership should not look like.

Gatekeeping Limits Organizations

Years later, in a civilian organization, a peer shared his frustration with me. He served as a senior director for community outreach. He was effective in his role and deeply committed to the mission. Outside of work, on his own time, he had earned a PhD in organizational management.

There was no clear path for him to grow beyond his position.

At the time, I was leading several process improvement initiatives and saw an opportunity to leverage his expertise. I raised the idea with the CEO. The response was immediate and firm. I was told that I would not be authorized to matrix resources from other departments. Organizational management was her responsibility. If I needed assistance, I should come directly to her.

What stood out was not the decision itself, but its effect.

The organization already possessed expertise that could have advanced the mission, yet that capability remained unused because collaboration across organizational boundaries was discouraged.

Over time, I have seen this pattern repeat. Organizations rarely suffer from having too much talent. They suffer when existing talent is prevented from contributing. It limits them. When leaders confine people to narrow roles, they reduce institutional capacity. When problem-solving is centralized instead of shared, bottlenecks form. When potential is measured only by current titles, organizations quietly train their people to stop bringing their best ideas forward.

Creating Space for Capability

In another role, we were facing a growing attrition problem. Engineering teams were working excessive hours week after week. Burnout was setting in, morale was slipping, and we were beginning to lose people we could not easily replace.

One of my managers, whose formal role was in network engineering, approached me with a proposal. He suggested that we step back and revamp our processes. His idea was to document what was working, identify what was not, and put practical guardrails in place so engineers could focus on meaningful work without constant interruption, while still leaving room for innovation.

What the organization had never fully leveraged was that he had earned several ITIL certifications on his own. He had the training and the perspective, but had never been given the opportunity to apply it.

The proposal aligned well with a broader roadmap we were building. But even without that alignment, I would have approved it. It was a thoughtful solution to a real problem and a chance for someone to contribute beyond a job description.

We moved forward.

The impact was immediate and lasting. Processes improved. Rework declined. Engineering teams regained focus. Attrition slowed. Just as importantly, that manager grew. He became part of the solution, gained confidence, and expanded his role within the organization. Others noticed as well, up and down the leadership chain, from the CEO to the engineering teams. The success helped shift the culture. Staying in one’s lane mattered less than contributing to shared outcomes.

What stood out was not the framework itself, but the outcome of creating space for capability to surface. The organization benefited, the team benefited, and the individual benefited.

The Common Thread

In each of these situations, leadership either failed or succeeded for the same reason. Whether ego took precedence over responsibility, or responsibility created room for others to contribute.

Looking back, these experiences taught me that leadership is less about authority than stewardship. Authority can direct people, but stewardship develops them. The leaders I continue to admire are those who create environments where accountability is shared, expertise is welcomed regardless of title, and success is measured by organizational outcomes rather than personal control. 

Every organization already contains more potential than it fully utilizes. One of leadership’s greatest responsibilities is creating the conditions where that potential can emerge.

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.

Dude: A Brief Sentiment Analysis Case Study

“Dude.”

That one word has done a lot of heavy lifting over the years. It can express pure joy, serious concern, light frustration, or awkward silence. You can say it with a smile, a sigh, a sneer, or a shrug. But how would a computer know the difference?

That’s where sentiment analysis in natural language processing (NLP) comes in.

In this post, we’ll take a walk through the history of sentiment analysis, unpack how it works, and then dive into a fun example using the word “dude” to show how context shapes interpretation. Whether you’re a developer, a linguist, or just curious about how computers try to understand us, this breakdown offers a human-first explanation of how meaning is built word by word.

An EXTREMELY Short History of Sentiment Analysis

Back in the early 2000s, people started using computers to figure out how folks felt about stuff they wrote online. This kind of thing is now called sentiment analysis, though some called it opinion mining at the time. The earliest attempts were pretty simple. They relied on lists of words that people had marked as either good, bad, or somewhere in between. If you wrote, “I love this,” the system saw the word “love” and called it a positive message. That was the whole idea.

In those early systems, if someone wrote something like “That movie was great,” the software would pick out the word “great” and flag it as positive. That worked fine when people meant exactly what they said. But the problems started showing up fast. Sarcasm, for one, could throw everything off. Take a sentence like “Yeah, great job breaking the build again.” That’s clearly not meant as praise.

As people started realizing those basic systems had limits, they began using machine learning instead. They trained models on examples of real sentences that had already been labeled by humans. That way, the models could start noticing patterns, instead of just individual words, but also how those words fit together. It was a big improvement, though there were still plenty of things that tripped the models up. Nuance, slang, and certain expressions were especially tough.

Things really took off once deep learning entered the picture. That led to the rise of transformer models like BERT, RoBERTa, and GPT. These tools look at full sentences instead of just scanning for keywords. They’re good at picking up on how words relate to each other, even when the meaning isn’t obvious at first glance.

Today, sentiment analysis plays a big role in how companies understand what people are saying online. It helps with everything from reading product reviews to powering virtual assistants. Still, even with all that progress, words like “dude” remind us that language isn’t always so easy to pin down.

Dude, Seriously?

Let’s run through a few real examples to get a feel for how tone and phrasing can completely change what someone means when they say “dude.” It’s the same word each time, but the way it’s delivered makes all the difference.

Example 1: “Dude! That was amazing.”
• Sentiment: Positive
• Clues: Exclamation point, enthusiastic phrasing.
• Meaning: The speaker is impressed or excited.

Example 2: “Dude… seriously?”
• Sentiment: Negative
• Clues: Ellipsis, questioning tone.
• Meaning: The speaker is annoyed or disappointed.

Example 3: “Dude.”
• Sentiment: Neutral or ambiguous
• Clues: Single word with period. Depends on tone or situation.
• Meaning: Could signal disbelief, frustration, or deadpan humor.

Example 4: “Hey dude, how’ve you been?”
• Sentiment: Neutral or friendly
• Clues: Used as a casual greeting.
• Meaning: Likely informal and friendly.

Example 5: “Duuuuuude”
• Sentiment: Unknown
• Clues: Stretched word. Could mean excitement, fear, or awe.
• Meaning: Depends entirely on context.

The challenge for any algorithm trying to score these sentences is that each one uses the same word in a completely different way. That’s where context modeling becomes essential.

How Sentiment Analysis Actually Works

Let’s break down how a modern NLP system would attempt to figure out the emotional meaning behind each of those sentences.

Step 1: Preprocessing

Before doing any serious interpretation, the system prepares the input:

• It normalizes stretched words like “Duuuuude” to reduce them to a usable form.
• It preserves punctuation where necessary, since an ellipsis or exclamation mark can drastically change the meaning.
• It converts everything to a consistent format for easier parsing.

Step 2: Tokenization and Syntactic/Semantic Parsing

The system splits each sentence into tokens, then identifies each word’s role. Is “dude” being used as an interjection? A subject? A nickname? The system uses dependency parsing and part-of-speech tagging to figure that out.

Step 3: Contextual Modeling with Transformers

Now the model looks at the full sentence—or even surrounding text. This is where transformer models shine. Instead of analyzing one word at a time, they consider the entire context. The model returns a sentiment score with a probability estimate.

Example:
• Input: “Dude, that’s not funny.”
• Output: Negative sentiment with 91% confidence

Step 4: Post-Processing or Human Review

Depending on the use case, the result might be sent to a dashboard, a chatbot, or a reviewer. In areas like healthcare sentiment monitoring or financial trend analysis, human review is often used to avoid mistakes.

What If You Built a “Dude Analyzer”?

Let’s say you wanted to build a small classifier that detects sentiment behind different uses of “dude.” You’d go through a few steps:

1. Collect Training Data: Grab examples from Reddit or X (formerly Twitter). Label each one by sentiment.
2. Clean and Preprocess: Normalize stretched words, preserve punctuation, and account for slang.
3. Fine-Tune a Model: Use something like DistilBERT and train it on your “dude” examples.
4. Test Accuracy: Run unseen samples through it and see how well it does, especially on sarcasm.
5. Deploy and Share: Make it available with something like Flask or Streamlit.

Final Thoughts

Language is personal. It shifts, adapts, and resists tidy categories. A word like “dude” can hold excitement, annoyance, confusion, or comfort—all depending on how it’s said and who says it.

That’s why sentiment analysis is still such a challenge. Machines are getting better, but they’re still learning the art of tone, timing, and context. As long as people keep saying “dude,” we’ll keep finding new ways to teach computers what that really means.

“Dude.”

Leadership Does Not Require an Org Chart

One of the most important leadership lessons I’ve learned is that leadership is not granted by a title.

It is demonstrated through action.

Organizations often associate leadership with authority, reporting structures, or formal responsibility. Those things certainly matter, but they are not what make people choose to follow someone.

Leadership is ultimately measured by influence—by the ability to help others grow, solve problems, and move forward together.

Leadership Is a Daily Choice

Some of the strongest leaders I have known exercised influence without formal authority.

They mentored new employees.

Shared knowledge freely.

Made introductions that helped someone else’s career.

Offered thoughtful feedback.

Recognized potential in people before others saw it.

None of those actions required permission.

They simply required a willingness to serve.

Influence Exists Everywhere

Leadership opportunities appear far more often than most people realize.

Helping a colleague navigate a difficult decision.

Connecting two people who could benefit from knowing each other.

Sharing lessons learned from a challenging project.

Volunteering professional expertise within the community.

Taking time to coach someone earlier in their career.

These moments rarely receive recognition.

They often create the greatest long-term impact.

Growth Is Part of Leadership

Every season of a career offers opportunities to learn.

Some periods involve building organizations.

Others involve developing new skills, expanding professional networks, reflecting on experience, or exploring different perspectives.

Growth is not something leaders pause until circumstances become ideal.

It is part of leadership itself.

Leaders who continue learning remain better prepared to help others when new opportunities emerge.

Service Builds Credibility

Leadership rooted in service creates trust.

People remember those who invested in them without expecting immediate return.

Organizations remember leaders who shared credit, developed talent, and strengthened teams rather than protecting personal status.

Those habits build credibility that extends well beyond any individual role or organization.

Leadership Is Portable

Titles change.

Organizations change.

Responsibilities evolve.

The ability to influence, encourage, teach, and develop others travels with you.

That may be the most enduring form of leadership.

When leaders focus less on position and more on contribution, they discover that opportunities to serve exist in every stage of a career.

Leadership is not defined by where you sit on an organizational chart.

It is defined by the positive impact you leave on the people around you.

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.

What Crafting Espresso Taught Me About Developing Teams

Outside of technology, one of my favorite hobbies is making espresso.

Good espresso is remarkably unforgiving. Small adjustments to the beans, grind size, water temperature, or extraction time can dramatically change the result. At first glance, it seems like a hobby built around precision.

The longer I’ve practiced it, however, the more I’ve realized it is actually about understanding potential.

Every coffee bean is different.

The goal isn’t to force every bean to behave the same way.

The goal is to understand what allows each one to perform at its best.

I’ve come to believe leadership works much the same way.

Great Teams Are Not Built from Identical People

Technology organizations often focus on finding the “perfect” candidate.

In reality, high-performing teams are built by combining people with different experiences, perspectives, and strengths.

Some excel at solving complex technical problems.

Others communicate exceptionally well with customers.

Some thrive under pressure.

Others quietly improve processes that make everyone around them more effective.

Leadership begins by recognizing those differences rather than trying to eliminate them.

Development Requires Intentional Investment

Coffee does not become exceptional by accident.

Neither do people.

The strongest leaders invest time in coaching, mentoring, and creating opportunities for others to grow. Sometimes that means technical development. Sometimes it means giving someone responsibility before they feel completely ready. Often it simply means believing in someone’s potential before they believe in it themselves.

People usually rise to expectations that are supported with trust and opportunity.

Leaders Create the Environment

An espresso machine cannot compensate for poor beans.

Likewise, talented people often struggle in environments where priorities are unclear, collaboration is discouraged, or leadership creates unnecessary obstacles.

One of the most important responsibilities of leadership is creating conditions where people can succeed.

That includes clear expectations, psychological safety, meaningful feedback, and the freedom to solve problems rather than simply execute instructions.

When those conditions exist, performance improves naturally.

The Best Leaders Serve the Team

The phrase servant leadership is sometimes misunderstood.

It does not mean lowering standards or avoiding accountability.

It means recognizing that a leader’s responsibility is to help others perform at their highest level.

Leaders remove obstacles.

They develop capability.

They create opportunities.

They recognize potential that others may overlook.

The success of the team becomes the measure of the leader.

Excellence Is Never Finished

One of the reasons I enjoy making espresso is that there is always something to improve.

A slightly different grind.

A better extraction.

A new bean.

Leadership follows the same path.

No team is ever truly finished developing.

No leader is ever finished learning.

Both improve through curiosity, patience, thoughtful refinement, and the willingness to keep making small adjustments over time.

The goal is never perfection.

It is creating an environment where people—and the organization—continue getting better.