The missing piece in your user research toolkit

So last week I found myself stuck in a consulting client meeting where everyone was talking past each other. The marketing team wanted one thing, the product folks another, and the CEO kept asking, "But what do our users actually want?"

I sat there thinking how we'd spent thousands on research but still couldn't agree on basic user needs. That's when I pulled out an empathy map.

I've noticed that teams often dive straight into solutions without truly understanding their users. We collect data, sure, but rarely take the time to step into our customers' shoes and see the world from their perspective.

Empathy maps changed that for my team. These visual tools help us capture what users say, think, do, and feel in a way that transforms abstract research into actionable insights. I've seen firsthand how they break down communication barriers between departments.

The beauty of empathy mapping lies in its simplicity. The classic version has four quadrants – Says, Thinks, Does, and Feels — though I've found adding "Sees" and "Hears" can provide even more context for certain projects.

What matters isn't the exact format but the conversations it sparks. Here's what works in my experience:

• Start with a clear purpose. Are you trying to align your team around user needs? Inform a specific design decision? The goal shapes everything that follows.

• Ground your map in reality. The most valuable maps come from actual user data – interviews, surveys, support tickets – not assumptions. I've watched teams realize how much they'd been projecting their own preferences onto users when confronted with real feedback.

• Make it collaborative. Bring together people from different departments to fill out the map. The magic happens when your developer suddenly realizes why that feature the marketing team kept pushing for actually matters to users.

• Keep it alive. The best empathy maps evolve as you learn more. I keep ours visible and revisit them regularly, especially when we're making crucial decisions.

I've found empathy mapping most valuable during early project phases and stakeholder presentations. Nothing convinces leadership to greenlight a project like showing them you truly understand your target audience's pain points.

That said, they're not for every situation. For straightforward projects with well-understood users, a quick check-in might be sufficient. The key is using empathy maps as tools for insight, not checkbox exercises.

What's your experience with empathy mapping? Have you found other methods that help your team truly understand users? Hit reply and let me know.

And If you're curious about trying empathy mapping with your team, I'd be happy to share the template that's worked best for us. Just reply to this email.

Until tomorrow,
— Shashank

P.S.

If you found this valuable, I'd appreciate you forwarding this email with one person who might need this perspective right now.

And if you are the one who received it, you can subscribe here.