BoardSnap is an iOS app that reads an empathy map whiteboard — Think & Feel, See, Hear, Say & Do, Gains, and Pains — and produces a structured user empathy summary in one snap.
Empathy maps are the fastest way to align a team on who the user actually is. Fill the six quadrants — Think & Feel, See, Hear, Say & Do, Gains, Pains — and you force the team to consider the user's full context, not just their immediate task. A team that's done this exercise designs differently from one that hasn't.
The empathy map loses its value as a communication tool the moment it's taken off the wall. Teams who don't see the map regularly lose the user understanding it was supposed to embed. A photo on Slack doesn't help — nobody reads a photo of a sticky-note-covered whiteboard for insight.
A structured text summary of the empathy map is a shareable, searchable artifact. It can be pinned in a BoardSnap project and referenced in every future chat about product decisions. 'What would our user in the empathy map think about this pricing change?' becomes an answerable question.
Standard empathy map layout: Think & Feel (top center — the user's inner world, thoughts and feelings they don't always express), See (top right — what they observe in their environment), Hear (top left — what they hear from others), Say & Do (bottom center — their verbal and behavioral outputs), Pains (bottom left — fears, frustrations, obstacles), Gains (bottom right — wants, needs, hopes, dreams). Write the user persona name at the top.
What does the user care about most? What worries them? What motivates them? Source these from interview notes, not assumptions. Write direct quotes in quotation marks where possible — 'I feel like I'm always behind' is more useful than 'user is stressed.'
See: the user's physical and digital environment — what they look at regularly. Hear: what colleagues, managers, friends, and media tell them. Say & Do: what they say in public vs. what they actually do. The gap between Say and Do is usually the most interesting insight in this section.
Pains: specific frustrations, obstacles, and risks the user fears. Gains: specific outcomes, aspirations, and success criteria. These two quadrants feed directly into the value proposition canvas if you're doing that exercise next.
Dot vote across all six quadrants. One dot = this insight is important to understanding the user. Circled items with three or more votes are the insights that should drive design decisions. Star them.
Open BoardSnap. Six quadrants with labeled sections, sticky notes or written content, and circled priority items. VisionKit handles the perspective. BoardSnap AI reads each quadrant's label and content.
A structured empathy map summary with each quadrant labeled and populated. Starred high-priority insights appear in a 'Key Insights' section at the top. Think & Feel, See, Hear, and Say & Do are summarized separately. Pains and Gains are listed as bullet points that feed directly into product prioritization. The output is paste-ready into a design brief, research report, or product strategy doc.
A five-day design sprint started with an empathy map session. The team had two hours of interview data to synthesize. The empathy map session took 60 minutes. BoardSnap produced a summary that served as the user brief for the rest of the sprint. Every design decision referenced it.
A researcher built an empathy map from interview data to validate a persona hypothesis. The Think & Feel quadrant revealed a significant gap between the assumed motivation (efficiency) and the actual motivation (avoiding embarrassment in front of peers). BoardSnap captured the insight. The persona was updated before it influenced the roadmap.
A sales team built an empathy map for the economic buyer — the person who signs the contract, not the end user. The Say & Do gap was large: they said 'we prioritize innovation' but their actual purchase history showed conservative, low-risk choices. BoardSnap's structured output changed the sales team's pitch strategy.
A persona describes who the user is — demographics, role, background. An empathy map describes what they experience — their thoughts, feelings, and environment. Empathy maps are best built from fresh research data. Personas are a synthesis of empathy maps plus behavioral and demographic data. Build the empathy map first; it feeds the persona.
Yes, but label it clearly as an assumption map rather than a research-based empathy map. Assumption maps are still useful for identifying gaps in your user knowledge. Run them before designing — they show you what you don't know.
Yes. Quoted text is read as-is and preserved in the output in quotation marks. This is a useful feature — direct quotes in the empathy map output make the most compelling evidence for design decisions.
If each persona has its own clearly delineated section — separate empathy maps side by side, or different colored marker per persona — BoardSnap reads them as separate maps. Label each with the persona name prominently.
Snap the board, ship the action items in ten seconds.