011 Empathy at Work: The Hidden Pressures of Product and Design

🎧 Listen to this episode on Apple Podcasts, Spotify, or your favorite platform.

Empathy Is a Product Skill

In product and design work, we talk a lot about empathy for users.

We build personas. We conduct research. We analyze pain points. We map journeys. We remind each other, rightly, that there is a human on the other side of the screen.

But in our conversation for Episode 011 of Pixels & Priorities, J and I kept circling around another version of empathy that does not get nearly enough attention:

Empathy for the people building the product with us.

Product managers, UX designers, researchers, developers, product owners, stakeholders, and leaders are all carrying pressures that are not always visible from the outside. And when we forget that, collaboration suffers. Requests become transactions. Urgency turns into friction. Our teams start fighting the same battles over and over again.

Empathy is not a vanity workplace value. It is operational, and it affects the quality of our communication, the usefulness of our systems, the strength of our collaboration, and the sustainability of our work.

Empathy Starts When the Script Breaks

J shared a story from one of his earliest jobs teaching adult swim lessons. He was working with adults who were afraid of the water, and one student did exactly what he was instructed to do while learning to float. Then he started to sink.

That moment mattered because it was not only about teaching technique, but it was about recovering while building trust in a scary situation. The student was afraid, and the rest of the class was watching. J had to adjust quickly while staying aware of how everyone in the situation was experiencing that moment.

“I have to be empathetic to how they’re feeling so I can help them.” - J Schuh

That is product and design work in miniature.

We can walk into a meeting with the right process, the right tool, the right roadmap, or the right design system. But people have fears, pressures, different experience levels, and varying needs. When the standard script breaks, empathy is what helps us respond to the actual humans in front of us.

We Do Not Always See Each Other’s Pressure

One of the strongest parts of our conversation was the recognition that product managers and designers often work closely together while still not fully understanding each other’s internal pressure.

As a product manager, I know I may be asking a designer for something that seems straightforward from the outside, while inside that request is a whole constellation of constraints: design systems, accessibility, creativity, time, stakeholder expectations, user needs, and quality standards.

“You can’t force yourself to be innovative and creative. You’ve got to have a little planned space.” - Metsy Rose

Creative work needs oxygen. If every design request is treated like an emergency, we should not be surprised when the work starts to feel squeezed, reactive, or less thoughtful.

J also reflected on the product side and the pressure PMs carry: timelines, revenue expectations, leadership asks, analytics, prioritization, stakeholder negotiation, and the constant guessing game of what will create value. That mutual recognition is important.

Empathy does not mean one role always gets its way. It means we stop treating another person’s constraints as invisible.

Curiosity Builds Trust Faster Than Critique

A recurring thread in our conversation was curiosity.

Not performative curiosity. Not the meeting-room version where we say “help me understand” while a fragment of resentment starts to take hold. We need real curiosity.

J talked about approaching product practices by asking, “What is the why behind why you’re doing this?” We must use curiosity as a tool to reframe potential critique into an invitation.

Empathy at work often begins with small, ordinary questions:

• Can you show me how you did that?
• Am I giving you enough context?
• What pressure am I not seeing from your side?
• What would make this request easier to work with?
• What do you need earlier from me next time?

Those questions may seem small, but they create the soil trust grows in.

I shared that sometimes simply asking a coworker to teach you something small, even a shortcut they used, can help build connection. You are recognizing their skill and knowledge to create a moment of shared learning. It signals that you see them as someone with expertise worth learning from.

The “Unholy Trinity” That Derails Meetings

We’ve all raced for the mute button or quickly turned off our cameras in meetings weighed down with the “unholy trinity” — justification, rationalization, and blame.

It’s the uncomfortable meeting where everyone is talking, but the conversation isn’t moving forward. People explain why they did what they did and defend their decisions. They point toward other teams to subtly shift blame.

J’s recommendation was to recognize where you are and shift the conversation toward what needs to happen next to avoid letting blame consume the room:

“However we got here, whatever the reason, we are being tasked to move forward from where we are.” - J Schuh

For product managers and UX professionals, this is especially relevant because our work often lives in ambiguity. Requirements change. Mid-work research reveals inconvenient truths. Timelines compress. Stakeholders disagree. When that happens, emotionally intelligent teams can acknowledge reality without turning every meeting into a courtroom drama.

Systems Should Make Work More Human

We also talked about systems, both big and small.

Product playbooks. Design systems. Repeatable processes. Team rituals. Personal workflows. Tiny automations. Shared templates. Better intake practices.

Systems can sound cold, but when they are created thoughtfully, they are deeply human. A good system reduces repeated stress and recurring confusion.

“We need the energy to deal with the new stuff, and we won’t have it if we’re fighting the same battles over and over again.” - Metsy Rose

That is one of the biggest reasons that systems matter.

New stresses will always come. New tools, new leadership asks, new customer needs, new market shifts, new AI workflows, new organizational changes.

If teams are already exhausted from re-solving the same preventable problems, they do not have enough creative or emotional energy left for the truly new challenges.

J connected this to the idea that if we want consistent success, we need systems that scale. Motivation is not enough. Heroics are not enough. “Everyone just work harder” is not a strategy. It is a burnout recipe.

Small-S Systems Count Too

Not every team has the budget, authority, or maturity to implement large enterprise systems. That does not mean we are powerless.

In the episode, I talked about the difference between capital-S Systems and lowercase-s systems. Large systems are wonderful when organizations can support them, but small systems can still change the daily experience of a team.

A small system might be:

• a clearer design request template
• a shared intake checklist
• a recurring product and design sync
• a lightweight decision log
• a better way to document handoffs
• a weekly “what’s unclear?” check-in
• a personal automation that saves the team time

There are still a lot of opportunities to help you and your team build processes and systems that make you more productive, more efficient, and by doing those things, you are helping your team as humans as well.

Efficiency and empathy are not enemies. When done well, efficiency protects people from unnecessary friction.

Take Your Own Shoes Off First

Near the end of the episode, J reminded us that, “Before you step into somebody else’s shoes, you have to take your own shoes off.”

We all carry our own pressures, preferences, histories, deadlines, assumptions, and ways of working. Product may wonder why design cannot move faster. Design may wonder why product cannot provide more runway. Developers may wonder why the requirements keep shifting. Stakeholders may wonder why everything takes longer than expected.

Empathy asks us to pause long enough to notice what we are bringing into the room. That pause can change the conversation.

Instead of assuming design needs A, B, and C from me, maybe I need to ask whether A, B, and D would be more useful. Instead of assuming a product playbook is “always in progress” because someone failed to finish it, we need to recognize that product maturity evolves with leadership, tools, economic pressure, organizational structure, and team needs.

Empathy helps us see the system, not just the symptom.

Practical Ways to Apply This at Work

Here are a few ways product and design teams can bring this conversation into daily practice:

Ask better intake questions
Before handing work to another team, ask what information would help them do better work faster.

Build check-ins outside the chaos
Do not wait for an urgent request or escalated issue to ask how collaboration is going.

Name the pressure without weaponizing it
It is okay to say, “I know this timeline is tight.” It is not okay to use pressure as an excuse to disregard everyone else’s reality.

Reduce repeat battles
If the same problem happens three times, it probably needs a system, not another heroic rescue.

Recognize good work specifically
A simple “thank you” is nice. A specific thank-you is better: “That solution solved a problem I had not even seen yet.”

Questions for Reflection

1. Where are product and design repeatedly misunderstanding each other on your team?
2. What small system could reduce stress or confusion this week?
3. Are you checking in with collaborators only during urgent moments, or also when there is room to listen?

Key Takeaways

• Empathy helps product and design teams understand the pressures each role is carrying.
• Trust is built through small moments of curiosity, recognition, and follow-through.
• Systems should reduce repeated stress, not simply increase output.
• Better, faster work cannot come at the expense of the humans doing the work.
• Product and design teams need check-ins outside moments of urgency.

Final Thoughts

Empathy is not extra. It is part of how good product and design work gets done.

When we understand each other’s pressures, we make better requests. When we build trust, we move through conflict faster. When we create thoughtful systems, we protect the energy people need for creative, strategic, human-centered work.

The goal is not simply better, faster, more efficient work.

The goal is better, faster, more efficient work without sacrificing the humans in the room.

– Metsy
Co-host, Pixels & Priorities

Stay Connected

🎧 Listen to new episodes every Tuesday on Apple Podcasts, Spotify, or your favorite podcast platform. Please leave us a rating, submit a review, and share with a friend. It helps more people find the show and join the conversation.

Connect on LinkedIn: Metsy Rose | J Schuh | Pixels & Priorities