The #1 Trait Product Managers Need: Empathy

If I had to reduce great product management to a single trait, it wouldn’t be technical depth, business acumen, or even strategic thinking.

It would be empathy.

In my experience, empathy is the trait that most directly determines whether a product team ships features or delivers real value. It shapes how problems are understood, how tradeoffs are made, and how teams operate under pressure.

Frameworks help. Empathy decides.

What Empathy Really Means in Product Management

Empathy in product management is often oversimplified.

• It’s not just talking to customers

• It’s not agreeing with every stakeholder

• And it’s definitely not saying yes to everyone

  
  

Empathy is the ability to truly understand:

• the problems people are trying to solve

• the constraints they operate under

• and how your product fits into their real-world context

  
  

Great PMs don’t just collect requirements… they interpret reality.

And that reality spans customers, developers, and stakeholders across the business.

Empathy for Your Customers

Most product failures don’t come from lack of effort. They come from shallow understanding.

Too many teams stop at UI requirements or feature requests. True empathy goes further: it asks how customers actually behave, not how we wish they would behave.

This matters even more in B2B and B2B2C environments, where the buyer is often not the end user. In those cases, your customer’s customer is frequently the one living with the consequences of your product decisions.

A Real Example: Shift Swapping at ADP

At ADP, I worked on a feature called Shift Swapping. The documented requirement focused on allowing employees to request manager exceptions when they couldn’t make a shift.

But that wasn’t how the world worked.

In reality, employees almost always solved the problem themselves by coordinating directly with coworkers and swapping shifts informally. Managers simply approved the outcome after the fact.

The real problem wasn’t exception handling. It was enabling peer-to-peer shift swaps, with lightweight manager approval.

Had I built exactly what was written in the requirement, we would have delivered a technically correct solution that missed the real need entirely.

Empathy changed the solution.

Empathy for Your Development Teams

Empathy doesn’t stop with customers.

Some of the most persistent dysfunction in product organizations stems from a lack of empathy between product and engineering.

PMs think engineers inflate estimates.

Engineers think PMs ignore complexity.

High-performing teams understand a simple truth: product and engineering succeed or fail together.

One of the most useful mental models I’ve seen is the iceberg: what customers see, the UI, workflows, and visible features, is the tip of the iceberg. Maybe one-eighth of the total effort.

The remaining seven-eighths live below the surface:

• architecture

• APIs

• data integrity

• security

• scalability

• and technical debt

Engineers must account for all of this when estimating work. PMs need to trust that reality, even when it’s uncomfortable.

A Real Example: Re-Architecting at Deloitte

At Deloitte, I inherited a cloud migration platform that worked well for small projects but failed at enterprise scale. The easy path would have been to keep adding infrastructure and layering features on top.

Instead, I asked the architects and engineers a harder question: What would it take to build this platform correctly for the scale we’re targeting?

Their answer wasn’t incremental improvement. It was a full re-architecture: six months of rebuilding the core platform under a modern, modular, .NET-based microservices architecture.

That decision required empathy:

• trusting engineering judgment

• understanding long-term tradeoffs

• and resisting short-term pressure to ship valuable features

It was the right call and it unlocked scale that incremental fixes never would have.

Empathy for Your Stakeholders

Product managers don’t operate in isolation. Leadership, sales, customer success, and marketing all experience the product differently and their success depends on how well the product teams supports them.

Empathy here means understanding their realities.

• Sales teams are on the front lines with prospects every day. Their feedback reveals market friction early.

• Customer Success teams live with the product after launch. If onboarding is painful, they feel it first.

• Marketing teams need early involvement to shape positioning and enable effective launches.

Empathy doesn’t mean building everything stakeholders ask for. It means listening with intent, recognizing patterns, and making informed tradeoffs.

Empathy Does Not Mean Saying Yes

This is important. Empathy is not about consensus or appeasement.

Empathy is about:

• listening deeply

• acknowledging constraints

• and making decisions that reflect an understanding of real problems, even when the answer is “no”

The most effective PMs I’ve worked with are empathetic and decisive. They make people feel heard even when tradeoffs don’t go their way.

Why Empathy Is the One Trait That Scales

Across every stage of the product lifecycle: discovery, delivery, launch, and iteration, empathy shapes outcomes.

It improves:

• product-market fit

• team trust

• decision quality

• and long-term velocity

Frameworks can be taught. Tools can be learned.Empathy must be developed and modeled by product leaders.

If there is one trait I look for when hiring PMs, mentoring leaders, or evaluating teams, this is it.

Empathy isn’t soft.

It’s strategic.