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.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
A product team is researching collaboration needs among managers of distributed teams.
Key decisions
- Anchor the context: Map the manager during active coordination work.
- Use evidence: Verify observations through interviews and diary studies.
- Design for outcomes: Focus on ownership clarity rather than feature requests alone.
When to reuse this
Use when a team needs a shared, research-grounded view of a work role and its pressures.
Frequently asked questions
Why use an empathy map for a work role?
Are pains the same as feature requests?
How is the map validated?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.