Something has been heavy on my mind as annual planning and budget season get underway: how we allocate capital when trade-offs become uncomfortable.
Every autumn, conference rooms become arenas of competing priorities. Line-item requests overflow the spreadsheet, and leadership teams are tasked with reconciling finite capital against infinite ambitions. In technology and relevant operations, the gravitational pull is almost always toward visible progress such as new enterprise platforms, customer-facing digital features, and shiny roadmap milestones that look impressive in an executive summary deck.
Imagine you are finalizing your fiscal plan, and after weeks of trimming and defending allocations, you find yourself with exactly $200,000 left in discretionary capital. Two competing proposals sit on your desk:
- Option A: Greenlight an ambitious new technology rollout that promises exciting operational capabilities, satisfies vocal business stakeholders, and gives you a marquee deliverable to showcase at the next board meeting.
- Option B: Fund market-equity adjustments and merit increases to bring critical members of your core team up to the market median compensation baseline.
Which one do you sign?
Choose the people. Every single time.
Herb Kelleher, the legendary co-founder and longtime CEO of Southwest Airlines, spent decades proving that corporate governance often gets the fundamental order of operations backward. He anchored his entire business model on an uncompromising premise:
“Clients do not come first. Employees come first. If you take care of your employees, they will take care of the clients.”
In enterprise technology and multi-unit brands, we frequently worship deliverables, roadmaps, and feature velocity. We fall in love with the output. But over thirty years in enterprise leadership, one enduring reality has proven itself in every boardroom and server room. Projects do not build culture, weather storms, or sustain operations. People do.
To see why this decision shouldn’t even be close, you have to look past the surface excitement of a new software deliverable and examine the underlying economic behavior of what capital actually buys.
The Depreciating Asset vs. The Compounding Engine
When you look at capital allocation through a rigorous operational lens, the contrast between funding an initiative and funding your team is stark.
A project is, by its very nature, a depreciating asset. The moment code is deployed or a platform launches across your network, its value begins to erode. Maintenance cycles commence, security vulnerabilities emerge, underlying frameworks require patching, and technical debt starts to accumulate. What feels like a cutting-edge achievement on day one becomes tomorrow’s legacy platform that your future team will eventually have to refactor or replace.
Worse, capital projects carry an inherent operational drag. Every new system introduced into an enterprise requires integration maintenance, user onboarding, ongoing vendor management, and continuous change management across your footprint. The initial capital outlay is rarely the true cost, rather it is merely the entry fee into a continuous lifecycle of upkeep and diminishing returns.
Your team, conversely, is an appreciating, compounding engine.
When you invest in your people, their value does not decay, it accelerates. Their domain expertise deepens with every production challenge they resolve. Their operational velocity increases because they understand the historical reasons why systems were architected the way they are. Their cross-functional relationships strengthen across finance, operations, and field units, cutting through organizational friction faster than any project management software ever could. Every dollar poured into your team compounds in value year after year. Dollars poured into a standalone project while ignoring team health begin evaporating on day one.
Yet despite this clear divergence in long-term asset value, organizations routinely starve the appreciating asset to feed the depreciating one. To understand the true peril of that choice, you have to look at the hidden financial wreckage created when you treat talent compensation as an afterthought.
The Hidden Math of Talent Deficits
Choosing a capital project over market equity is often rationalized as “advancing the strategic business agenda.” In reality, it is borrowing unhedged capital against your team’s goodwill at exorbitant interest rates.
Frederick Herzberg pointed out decades ago in his Motivation-Hygiene Theory that compensation functions as a primary workplace hygiene factor. While competitive pay alone might not create deep intrinsic passion, being paid below market median actively breeds resentment, anxiety, and disengagement. You cannot rally a team around an ambitious, high-stakes technology transformation when individuals are quietly wondering how they are going to keep up with inflation or whether their market value is being exploited.
When key operators, engineers, and product managers inevitably leave mid-flight for market pay elsewhere, the resulting balance sheet shock is catastrophic:
- Direct Replacement Premiums: The hard costs to recruit, interview, hire, and sign qualified replacements typically consume between 50% and 150% of the role’s annual base salary in recruiter fees, executive time, and signing incentives.
- Severe Ramp-Up and Productivity Lag: It takes an average of six to nine months for an enterprise engineer or operations lead to gain the architectural fluency needed to contribute at the level of the departed veteran, creating a massive hidden productivity tax across the entire department.
- Loss of Undocumented Tribal Knowledge: The architectural nuances, vendor handshake agreements, and the critical “why” behind legacy system quirks walk out the front door, leaving the remaining team guessing during high-stakes outages.
- Cultural Contagion and Retention Cascades: Turnover is rarely an isolated event. When one well-respected team member leaves for market compensation, it signals to their peers that loyalty is penalized and the only path to fair pay is an external exit, triggering a cascading wave of resignations.
- Critical Project Failure and Capital Waste: The ultimate irony is that the very project you prioritized with that $200,000 stalls, misses its launch deadlines, or fails outright because the architectural context and driving hands behind it have vanished.
When you add up the recruiter commissions, the delayed deliverables, the emergency contractor fees brought in to patch the holes, and the lost velocity, you realize a brutal financial truth that you didn’t save $200,000 at all. You spent three times that amount just trying to climb back to where you started.
A Personal Reflection
Earlier in my career during annual budget cycles, the pressure to demonstrate forward momentum through visible rollouts was intense. It is easy to fall into the trap of believing that executive leadership is measured by how many shiny line items you can check off for the executive committee or report to the board.
Experience teaches a humbling truth. Every platform, POS rollout, and digital architecture you deploy is only as resilient as the human beings standing behind it.
A project plan has never stayed up past midnight to troubleshoot a critical Sev-1 outage across thousands of locations. A software license does not take a nervous junior engineer aside to teach them how to navigate a difficult vendor negotiation. A presentation deck does not rally cross-functional teams when an enterprise rollout goes sideways in the middle of a high-volume rush.
When you prioritize a capital project over market fairness, your team hears one message loud and clear. The deliverable matters more than the creator.
Final Thoughts
Leadership is fundamentally about capital stewardship, and the highest-return investment an organization will ever make is in the people who execute the work.
When budget trade-offs become painful, resist the temptation to prioritize short-term monuments over long-term capability. A project delivered on the backs of an underpaid, exhausted team is not a victory, rather it is a deferred liability. Fix the foundation first. When your team knows they are valued, protected, and compensated with dignity, their commitment and creativity will deliver three better projects for you tomorrow than the one you delayed today.
📚 Recommended Reading
Multipliers: How the Best Leaders Make Everyone Smarter by Liz Wiseman.
In this landmark leadership study, Wiseman explores why some leaders drain capability and intelligence from their teams (Diminishers) while others amplify and multiply the native intelligence of the people around them (Multipliers). Wiseman demonstrates that organizations often mistakenly believe they need more headcount, bigger capital budgets, or new external initiatives to solve problems, when in reality their existing workforce holds vast reserves of untapped capability. When leaders invest in their people’s growth, remove institutional friction, and build an environment of trust and equity, they don’t just retain talent, they unlock two times the discretionary effort and problem-solving velocity of their teams without needing to buy their way forward.