Introduction

Meet Sasha and Sara. These two fictional Development Engineering Managers are seasoned tech leaders with virtually identical profiles. Both are smart, appropriately trained, educated, and experienced. Both are gunning for the same strategic seat at the table. But their paths to get there couldn't be more different.

Sasha has spent the last two years laser-focused on reducing phased escaped defects and driving improvements in the quality of their delivered software, tightening the process, building a track record of technical rigor. Sara has spent that same time surfacing latent demand in existing products, working cross-functionally to deliver features that lock in a significantly large portion of their existing and potential user base.

Same departure line, Same destination... Very different directions on the compass.

Just based on these two different approaches to delivering value, who do you think is the best person to promote into a strategic role?

The question isn't who works harder. It's who's optimizing for the right game.(Supporting stat: Deloitte's 2025 Tech Leaders Survey found that for the first time, 52% of tech organizations are now viewed by the business as revenue generators rather than service centers — and 36% of CIOs now hold direct P&L responsibility. The mandate for business acumen has already arrived. The question is whether tech leaders have realized it yet.)

The Honest Truth About Your Job Description

Let's be direct: it is everyone's job to "profitably please the customer." If you don't know that, either you are poorly informed, or you just aren't listening.

Peter Drucker said it plainly back in 1954 —"The purpose of a business is to create and keep a customer."Not to run elegant systems. Not to hit quality metrics. Not to close tickets faster. Everything else is in service of that single truth.(Source: Drucker, P.F. (1954). The Practice of Management. Harper & Row. — ViaUC Berkeley Haas)

How you go about it changes by region, by industry, by customer segment, over time. But the North Star doesn't move. As a tech leader, you have to internalize this and carry it into every decision you and your team make. If you can't figure out how to profitably serve your target customer, you have a big problem — and no amount of technical excellence will cover for it.

Output vs. Outcome: The Mindset Gap

The difference between a tech leader and a tech business owner is what they measure. Tickets closed vs. customer problems solved. Code deployed vs. revenue enabled. Uptime vs. customer experience.

Here's a story that seems as old as time.

While working at a large software company serving the public sector, I watched an angry government customer grow even angrier when the customer support team manager proudly announced that the issue resolution cycle time had decreased by 15%.Things are heading in the right direction.The manager had worked nights and weekends to get there. They added staff, deployed a new ticketing system, and streamlined processes. The numbers looked great internally.

When the customer canceled the contract, they cited a completely different number: a netincreasein reported issues. They appreciated the faster turnaround on individual tickets. But they could no longer afford to dedicate their own resources to our software quality assurance. They were finding our defects and reporting them back. That wasn't the deal they signed up for.

The team was measuring throughput. The customer was seeking business outcomes.

That gap is exactly what the data bears out. McKinsey research shows that connecting digital investments to customer outcomes — not just operational metrics — can drive economic gains of 20–50% (Source: McKinsey — The New Economics of Enterprise Technology). But you can only capture that value if you're measuring the right things.

We need to speak their language, walk in their shoes, and understand their perspective. That's not a soft skill. That's survival.

What "Thinking Like a Business Owner" Actually Looks Like

I took a session from Nancy Duarte on delivering impactful presentations at a project management conference I happened to be attending. It might seem overly dramatic to say that the session changed my life, but it actually did. It made me completely intolerant of presentations that cannot convey their message coherently. You have to land the "So what?" When I don't hear it or can't figure it out, I zone out. Which is not always a good thing. Apologies to my wife. If you are a tech leader trying to convey your ideas to executives, you have to learn how to land the "So What?"

As a strategic-minded tech leader, you have to be asking that "So What?" question at every turn. What is the "So what?" for the customer? What is the "So what?" for the business? If you apply this lens consistently, it will cause you to make fundamentally different design, architectural, and engineering decisions. That is the essence of the customer-centric mindset and what will set you apart from other technical leaders.

If you deliver a solution with zero defects to a market that doesn't want your product, you will be looking for a job. Yes, we must deliver value that pleases our customers, or they won't buy from us. That also means the product has sufficient quality to deliver the expected capabilities effectively.

The business is already raising this expectation. Gartner's 2024 CIO and Technology Executive Survey found that only 48% of digital initiatives meet or exceed their business outcome targets. More than half of technology investments fall short of their promises. The "So what?" is no longer just a good idea.

(Source: Gartner - CIO and Technology Executive Survey (2024))

The Ceiling You'll Hit If You Don't Make the Shift

I love boating, and I took the course that qualifies you for a Captain's license. I wanted the knowledge. My biggest takeaway was simple: the ocean is deep, and it keeps its mistakes. I learned to listen to the mariners who had gone before me and to seek out what boaters call "local knowledge" so I could avoid the hazards ahead.

You do not have to shift your thinking to be more strategic. You can continue being the technical leader you are. You can sail into uncharted business waters without heeding the advice of those who have navigated them before you.

But understand the ceiling you are heading toward. Forrester Research shows that48% of business leaders rank cost reduction as their number one priority. That means tech leaders who cannot connect their work to customer value and business outcomes become the easiest line item to question when budget conversations get serious. The financial ceiling for those who choose not to learn the business is not theoretical. It is well-documented, and it is closer than it looks.

(Source: Forrester Business and Technology Services Survey, 2025 — via Forrester Business & IT Alignment)

My own research reinforces this at the team level. When 98.9% of respondents in a study of IT professionals pointed to lack of management support as the single biggest barrier to process adoption, they were describing a leadership alignment problem. Leaders who do not see the customer as the destination never fully commit to the work that serves them.

(Source: Williams, B.L. (2009). Information Technology Project Processes: Understanding the Barriers to Improvement and Adoption. Capella University, ProQuest UMI: 3387855)

The Path Forward

This is probably one of the most straightforward pieces I have had the pleasure of writing, because the path forward is genuinely simple. You do not have to overhaul everything. You do not have to reinvent yourself or get an MBA.

You just need to ask one question consistently: How does this make a customer's life better or the company more competitive?

If the answer is "It doesn't," you already know what to do. Stop, redirect, or deprioritize. Be smart. Do the right thing.

Companies that consistently apply this discipline are not doing anything magical. McKinsey research shows that high-performing IT organizations achieve up to 35% higher revenue growth than their peers. The gap between high performers and everyone else often comes down to this: They connect their work to outcomes that matter.

(Source: McKinsey — The New Economics of Enterprise Technology)

Some Final Thoughts

Bain and Company found that 88% of business transformations fail to achieve their original ambitions. That is not a technology statistic. That is a leadership statistic.

(Source: Bain & Company, 2024 — cited in industry transformation surveys)

The companies behind that number did not fail because they lacked the right tools or the right talent. They failed because their leaders, both technical and business, did not take full ownership of the outcome. They optimized for the wrong things. They lost sight of the customer somewhere between the backlog and the boardroom.

If you want to be the kind of strategic leader who stands apart and drives the change that actually moves the needle, you have to make the shift. Ask yourself the key question. Act accordingly. The promised land is on the other side of that decision.

What is holding you back from making it?