Beyond Results—Why \"That People Stuff\" Matters More Than You Think

"All I care about are results! I don't want anything to do with that people stuff!"

A Chief Information Officer said this to me. Out loud. In a meeting at the headquarters of a multinational company.

I'll admit—I was secretly stunned.

Here was a successful executive. Years of leadership experience. An Executive MBA in Leadership somewhere on the résumé. Leading a sizeable IT organization with significant budget and strategic responsibility.

And yet, somehow, the idea that "that people stuff" might actually matter—if not to him personally, then certainly to the people he was working with—had never quite landed.

I was there as a conflict resolution specialist because this CIO and his direct report, the Director of Procurement, had been at odds for over a year. Aggressive behavior on one side. Avoidance on the other. What should have been a collaborative relationship had deteriorated to the point where basic communication had become nearly impossible.

And in that moment, hearing those words, I understood why.

Results matter. Of course they do.

As a leader, you're accountable for outcomes. Revenue targets. Product launches. System uptime. Strategic initiatives delivered on time and on budget.

No one's arguing against results.

But here's the part that often gets missed: Results don't happen in a vacuum. They happen through people. With people. Because of people.

When you dismiss "that people stuff"—communication, trust, psychological safety, interpersonal dynamics—you're not just ignoring soft skills. You're ignoring the very mechanism through which your results actually get delivered.

Think about it.

You can have the best strategy in the world. But if your leadership team doesn't trust each other enough to have honest conversations, that strategy won't get executed well.

You can hire the most talented people. But if they're afraid to speak up when they see problems, you'll miss critical information until it's too late.

You can set ambitious goals. But if collaboration breaks down every time there's pressure, you'll hit bottlenecks that slow everything down.

"That people stuff"? It's not separate from results. It's how you get them.

I see this more often in technology and engineering-driven fields. And (as an ex-techie) I think I understand why.

Tech culture tends to be data-driven, metrics-focused, and outcome-oriented. These are valuable qualities. They drive innovation, efficiency, and accountability.

But they can also create blind spots.

When everything is measurable—lines of code, system performance, customer acquisition costs—it's easy to prioritize what shows up in dashboards and reports. And much harder to prioritize things like team cohesion, communication quality, or trust, which feel more intangible.

There's also a cultural narrative in tech that celebrates the "brilliant jerk"—the high performer who delivers exceptional results despite (or sometimes because of) being difficult to work with. This reinforces the idea that results and relationships are somehow separate, even opposing forces.

But here's what I've learned working with leaders across industries, from fintech startups to established multinationals: The leaders who deliver sustainable results—not just short-term wins, but long-term organizational health—don't treat people and performance as separate things.

They understand they're deeply connected.

Let me tell you what happened with that CIO and his Director of Procurement.

By the time I was called in, the situation had escalated significantly. A year of unresolved tension had created:

📌 Passive-aggressive email chains that included multiple people (and accomplished nothing)

📌 Decisions being made in silos, leading to misalignment and rework

📌 Other team members feeling forced to "pick sides"

📌 Strategic initiatives delayed because collaboration was impossible

📌 Both individuals stressed, defensive, and convinced the other was the problem

And the cost? Not just to morale or team culture, but to actual business outcomes.

Projects were stalled. Resources were wasted. The organization's ability to respond quickly to market changes was compromised.

All because two smart, capable leaders couldn't work together—and the system around them hadn't created space to address it.

This is what ignoring "that people stuff" looks like in practice. It doesn't stay soft or intangible. It becomes hard business impact.

So what's the alternative?

It's not about being nice for the sake of being nice. It's not about endless team-building exercises or turning every meeting into a therapy session.

It's about recognizing that human capital—and how you care for it—is a strategic asset, not a distraction from the work.

This means:

📌 Creating space for dialogue, especially when tensions surface. Not smoothing over disagreements to "keep the peace," but addressing them constructively before they calcify into entrenched positions.

📌 Building trust as a leadership capability. Understanding that trust isn't just a feel-good concept—it's what enables speed, innovation, and resilience in complex environments.

📌 Developing emotional intelligence alongside technical expertise. The ability to read a room, understand what's not being said, and navigate interpersonal dynamics is just as valuable as strategic thinking or technical know-how.

📌 Recognizing that collaboration is a skill that can be strengthened. Teams don't automatically work well together just because you hire talented people. They need clarity, psychological safety, and sometimes support in learning how to navigate differences productively.

In the case of that CIO and his Director of Procurement, our work together wasn't about making them best friends. It was about helping them understand what was underneath their conflict—competing priorities, different communication styles, unspoken assumptions—and creating a structure for working together that didn't require them to like each other, just to collaborate effectively.

Can it work? Yes. But it will take time, willingness to look at their own contributions to the dynamic, and a recognition that results and relationships aren't opposites—they're partners.

Notes to my reader:

📌Yes, I am still using em-dashes in my writing. Not all em-dashes come from AI. #savetheemdash

📌 Throughout most articles, examples are drawn from composite experiences and patterns observed across organizations—modified to protect confidentiality while remaining grounded in real dynamics that leaders face.