Pulse Check: Empathy Mapping Your Product Manager, Pt. 2
Summary
Key Insights
-
•
Empathy mapping with large groups can reveal nuanced insights into product managers’ daily realities and pressures.
-
•
Product managers often compromise on feature usability to meet hard deadlines, intending to iterate later.
-
•
Cross-functional collaboration challenges for product managers include balancing meetings with execution time.
-
•
Synthesizing user research insights into accessible formats remains a key challenge for boosting product team decision-making.
-
•
Visibility and traceability of work via tools like Jira are essential for coordination between UX and product teams.
-
•
Metrics and impact are high-pressure areas where product managers feel accountability for product success in business terms.
-
•
Empathy must be thoughtful and evidence-based, acknowledging the limitations of sensory metaphors that can exclude some team members.
-
•
The relationship between UX and product managers benefits from ongoing dialogue, trust-building, and shared strategic goals.
-
•
Similar empathy mapping exercises could be extended to engineers and sales teams to foster broader organizational understanding.
-
•
Organizational leadership should facilitate workflows that enable hybrid vigor, helping diverse roles collaborate productively rather than compete.
Notable Quotes
"Product managers are trying to keep up with deadlines but often launch hard-to-use features hoping to make them better later."
"We put product managers at the center to map what they see, say, do, and also think and feel based on our collective experiences."
"It’s really hard for product managers to find time for actually doing the work because of all the meetings."
"Synthesizing user feedback in a way that’s easy for product managers to consume is one of the hot topics right now."
"Empathy mapping uses sensory metaphors but can exclude people with disabilities if we’re not careful."
"We have to ask how confident we are in our empathy—whether it’s evidence-based or just assumptions."
"Product and UX ought to be allies presenting a united front at the table, not competing for supremacy."
"We each bring different skills, temperaments, and interests, so there’s no one perfect relationship model between roles."
"Taking a pause to reflect on what our counterparts are experiencing can help us partner better, rather than react defensively."
"Leadership needs to design workflows that favor hybrid vigor instead of ambiguous relationships that frustrate everyone."
Or choose a question:
More Videos
"It’s not on researchers to simply be resilient — systems and structures need to adapt and support them."
Brian MossWhat Does it Mean to be a Resilient Research Team?
March 9, 2022
"One of our UX ambassadors transitioned to a full-time UX designer role after the academy."
Vasileios XanthopoulosA Top-Down and Bottom-Up Approach to User-Centric Maturity at Scale
January 8, 2024
"Maturity is not linear; the tanker company had a lot to learn from the speedboat, and vice versa."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"I always like to try to introduce a wild card from a slightly orthogonal field to spark the thinking."
David Cronin Uday Gajendar Peter Morville Kendra ShimmellDiscussion
May 13, 2015
"If you design for everyone, no one is satisfied — start with specific solutions then generalize."
Craig VillamorResilient Enterprise Design
June 8, 2017
"Most teams want to build for 50, 100 people and migrate years of data instead of starting small."
Sofia QuinteroBeyond Tools: The Messy Business of Implementing Research Repositories
March 10, 2022
"City Hall is often risk-averse, and professionals of color face extra penalties for taking risks in their careers."
Justin Entzminger Terrance Smith Tracy M. Colunga Mai-Ling GarciaRisk and Reward: How to Diversify the Field of Civic Innovators and Designers
November 17, 2022
"In agile, you can’t move fast and break information strategy; you need a parallel track to feed changes into production."
Bram WesselEnterprise Information Architecture
January 10, 2020
"Stakeholders might say no to research involvement if the context and relevance aren’t clear, or the ask seems overwhelming."
Roberta Dombrowski Sam Duong WoloszynskiMaking Research a Team Sport
March 11, 2022
