How to Build a User Persona in Miro

Create a new Miro board titled 'User Personas' in your product team's folder. Use frames to define the board structure: one large frame per persona, plus a summary frame at the top with a comparison matrix. Set the board permissions so your product and design teams can edit while engineering and leadership have comment access. This prevents personas from becoming a PM-only artifact.

• Create the board in your team's shared Miro space
• Add a frame template for each persona you plan to build
• Set permissions: product and design can edit, engineering and leadership can comment

Before building the persona, import your raw research data onto a staging area of the board. Use sticky notes for key quotes from user interviews, screenshots of relevant survey responses, and behavioral data from your analytics tool. Cluster these notes by theme using Miro's grouping feature. The clusters that emerge become the foundation of your persona rather than assumptions about who your user is.

• Import interview quotes, survey highlights, and behavioral data as sticky notes
• Color-code notes by data source (interview, survey, analytics, support ticket)
• Cluster notes by theme and label each cluster

Create the persona header with a name, role, and a one-sentence context line that captures their work situation. Skip the demographic details unless they are directly relevant to product decisions. Instead, focus on their organizational context: team size, reporting structure, how they are measured, and what tools they use daily. Add a behavioral archetype label (e.g., 'the firefighter PM' or 'the data-driven optimizer') that makes the persona memorable in conversation.

• Name the persona with a memorable archetype label
• Document role, team size, reporting structure, and performance metrics
• List their current daily tool stack

Add a two-column section: Jobs to Be Done on the left and Pain Points on the right. For each job, write it in the format 'When [situation], I want to [action], so I can [outcome].' Rate each pain point on a 1-5 intensity scale using Miro's voting dots. This quantification prevents the loudest stakeholder from inflating the importance of pain points that do not match research data.

• Write 5-8 jobs-to-be-done in the situation-action-outcome format
• List corresponding pain points with a 1-5 intensity rating
• Link each pain point to the research evidence (interview quote or data point)

Add a workflow section showing how this persona currently solves their core problem. Use Miro's flowchart shapes to create a simple process diagram of their existing workflow, highlighting the friction points with red callouts. This is the section that engineers find most useful because it shows the current state they are replacing. Include time estimates for each step so the team can quantify the impact of removing friction.

• Map the current workflow as a simple flowchart in Miro
• Highlight friction points, workarounds, and manual steps
• Add time estimates to each step for impact quantification

Document what this persona evaluates when considering a new tool or workflow change. Include their buying criteria (security, integrations, pricing model, team adoption effort), their likely objections ('we already use X for this'), and what would make them champion your product internally. This section is gold for positioning, marketing copy, and sales enablement.

• List 4-6 decision criteria ranked by importance
• Document the top 3 objections this persona would raise
• Identify what internal advocacy for your product looks like from this persona

In the summary frame, create a matrix with your personas as columns and key dimensions as rows (primary job, biggest pain, willingness to pay, adoption barrier). This lets anyone glance at the board and understand how your personas differ without reading every section. Share the board link in your team's Slack channel and reference it in your next sprint planning session to establish the habit of consulting personas during prioritization.