ChatDiagram
customer research · product design

Customer empathy map for a remote team manager

This empathy map describes a remote team manager who is trying to keep work moving without turning every day into a status meeting. The manager worries about missed handoffs, sees updates scattered across tools and hears teammates asking for clearer priorities. Their behaviors include weekly planning and requesting summaries from leads. The map identifies the underlying pain as time spent chasing information, with a desired gain of clear ownership and deadlines. It gives a product team a way to discuss the manager's situation before choosing features. The entries should be validated with research and kept separate from assumptions about what solution the manager prefers.

類型 矩陣圖標準 2×2 / N×M quadrant convention引擎 schematex-matrix更新時間 2026/9/24
Customer Empathy Map — Remote Team Manager
Drawing preview
需求

“Create a customer empathy map for a remote team manager choosing a work tool. In Thinks and feels, include worry that missed handoffs will hurt the team and a desire for visibility without constant meetings. In Sees and hears, include scattered updates across tools and requests for clearer priorities. In Says and does, include running a weekly planning meeting and asking leads for status summaries. In Pains and gains, include chasing updates as a pain and a shared view of ownership and deadlines as a gain.”

接著試試Add concern about onboarding new hires.Change the gain to fewer status meetings.
這張圖裡有什麼

看懂背後的決策。

01Anchor the context

Map the manager during active coordination work.

02Use evidence

Verify observations through interviews and diary studies.

03Design for outcomes

Focus on ownership clarity rather than feature requests alone.

Use when a team needs a shared, research-grounded view of a work role and its pressures.

瀏覽所有 矩陣圖 範本 →

常見問題

常見問題

Why use an empathy map for a work role?

It helps teams understand the context, pressures and desired outcomes behind a role's tasks.

Are pains the same as feature requests?

No. Pains describe difficulties; feature requests are proposed solutions that may or may not address them.

How is the map validated?

Use interviews, observation and behavioral evidence to confirm or revise each important entry.