BoardSnap is an iOS app that reads a whiteboard persona map — the user's context, goals, behaviors, frustrations, and key decisions — and produces a structured persona document in one snap.
Personas are supposed to ground product decisions in a real user's reality. A persona built from actual research — interview quotes, behavioral data, observed workflows — is worth having. A persona built from assumptions and stock photos is decoration.
The problem with most persona documentation isn't the research — it's the format. Persona docs in Notion or Confluence become static pages that get viewed on week one and never again. They're usually formatted like marketing copy — padded with demographic details that don't affect product decisions and light on the behavioral specifics that do.
A persona built on a whiteboard — where the team is forced to write only what they know and what matters — is usually more honest and more useful than one written in a template. The whiteboard forces compression. You can't write three paragraphs about the persona's morning routine when you only have half a column to work with.
Write the persona name at the top (fictional but specific: 'Sarah, Senior PM at a 150-person B2B SaaS company'). Then: job title, team size, environment (remote/office), tools used daily, decision-making authority. Two to three sentences max.
Three to four goals — what the persona is trying to achieve in their role. Professional goals, not product goals. 'Ship the roadmap without scope creep,' 'Build credibility with engineering,' 'Reduce time in meetings.' Goals are the lens through which they evaluate every tool they use.
Three to four specific frustrations — not 'things that could be better' but real, named pain that the persona actively experiences. Quote from interview data if you have it. 'I can never find last week's retro notes' is a frustration. 'Documentation could be better' is not.
How does the persona actually work? What tools do they use and how? Where do they cut corners? When do they ask for help? Behaviors are what they do, not what they say they do — look at the gap between the two.
One sentence that captures the persona's worldview. Derived from a real interview if possible. 'I don't have time to learn another tool — it needs to just work.' This sentence should be large enough to read from across the room. It's the persona's north star.
What would make this persona adopt a new tool? What would stop them? Triggers and barriers are the most actionable part of the persona for sales, marketing, and product. Be specific: 'Adopts when a teammate recommends it,' 'Blocked if requires IT approval.'
Open BoardSnap. The persona board has labeled sections, a key quote in large text, and bullets throughout. BoardSnap AI reads each section and the key quote as the document header.
A structured persona document with: persona header (name, role, context), goals, frustrations, behaviors, the key quote as a pull quote, and decision triggers/barriers. The output is paste-ready into a design brief, product strategy doc, or team wiki. No design tool required.
The team had three distinct buyer/user personas: the economic buyer, the champion, and the end user. Each got its own whiteboard section. BoardSnap read all three and produced three separate persona docs from one snap — each clearly delineated by the persona name header.
The team's persona had been written 18 months earlier. The research team ran 20 new interviews and updated the whiteboard persona with new quotes and revised frustrations. BoardSnap produced the updated persona doc. The team pinned it to the BoardSnap project — all future chats about product decisions referenced it.
A workshop was designed specifically to get engineering, design, and marketing aligned on the same persona. Each team contributed to the whiteboard in a facilitated session. BoardSnap captured the collaborative output — the resulting persona was more trusted than previous versions because every team had contributed to it.
One detailed persona comfortably. Two personas if you're side-by-side with reduced detail per persona. For three or more personas, use one board per persona and snap each separately — they'll live in the same BoardSnap project and can be compared via the AI chat.
You can tape a printed photo to the whiteboard — BoardSnap will include a note that a photo was present in the output but can't describe the image in detail. The text-based persona content is what BoardSnap captures. Skip the photo on the whiteboard; add it in the digital doc after.
Yes. Numbers, percentages, and statistics written on the board are read accurately. Write quantitative data clearly — one number per line, with its label. '73% use mobile first' is readable; a dense paragraph of statistics is harder to parse.
Snap the board, ship the action items in ten seconds.