methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session1-3 days (1 day for synthesis, 1 day for persona creation, 0.5-1 day for validation)Workshop or asyncPersona Profiles

Session: Personas

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with Internes Team. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Persona Profiles. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Synthesize research

    4-8 h

    Collect interview highlights as stickies. Run affinity mapping: cluster by similar behavior, goals, pain points. Identify 3-5 clusters (often more is over-factored). Hint: Anyone who clusters by demographics (age, gender) produces weak personas. Behavior and goals are the right dimensions.

    FacilitatorPersona Profiles
  2. 2

    Phase 2: Design persona profiles

    3-5 h

    Create one persona profile per cluster: name (fictitious but memorable), photo, short context story, goals (3-5), pain points (3-5), behavior, representative quotes. Add realistic details from interviews. Hint: Stock-photo personas without substance are ignored. Concrete quotes and behavior make personas usable.

    FacilitatorNeeds Summary
  3. 3

    Phase 3: Quant validation

    2-4 h

    Check personas against quantitative data: how large is each segment? How are behaviorals distributed? If data contradicts the personas, adjust them. Hint: Personas without quantitative anchors drift. If Persona X only covers 1% of the user base, the team should know that before treating it as driving.

    FacilitatorScenario Notes
  4. 4

    Phase 4: Stakeholder validation

    1-2 h

    Validate personas with stakeholders (sales, support, service). Who has regular customer contact? Do personas match their experience? Hint: Sales and support often see different personas than the research team. If major differences exist, review research coverage or refine personas.

    FacilitatorPersona Profiles
  5. 5

    Phase 5: Team activation

    1-2 h

    Distribute personas in the team, post them in design spaces, reference them in backlog templates. Name one champion per persona who challenges decisions through that persona lens. Hint: Personas stored away in a drawer have no effect. Visibility and active use are the levers.

    OwnerNeeds Summary
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerPersona Profiles
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Personas

Goal

Artifact: Persona Profiles

Working Question

Which distinct user groups with different needs, goals, and behaviors can be derived from research, and which of them drive design decisions?

Context

Interview notes or transcribed highlights; demographic quantitative data; known internal persona attempts and their weaknesses; persona purpose (design decisions vs marketing messaging vs strategy).

Setup

  • Format: Method session
  • Duration: 1-3 days (1 day for synthesis, 1 day for persona creation, 0.5-1 day for validation)
  • Mode: Workshop or async
  • Participants: A UX researcher as owner; one to three researchers with direct interview context; a Product Manager for segment prioritization; one to two designers for persona format and visuals.
  • Owner: A UX researcher as owner
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Persona Profiles. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Affinity mapping board (Miro, FigJam) for research synthesis; persona template with fields (name, photo, demographics, goals, pain points, behavior, context, quotes); optional quantitative data export (analytics, CRM).

Preparation

Collect research highlights as stickies on an affinity board. Cluster by behavior patterns. Define the persona template (what to include, what to omit). Clarify the persona purpose explicitly (design vs marketing).

Agenda

  1. Phase 1: Synthesize research (4-8 h) Owner: Facilitator Action: Collect interview highlights as stickies. Run affinity mapping: cluster by similar behavior, goals, pain points. Identify 3-5 clusters (often more is over-factored). Hint: Anyone who clusters by demographics (age, gender) produces weak personas. Behavior and goals are the right dimensions. Output: Persona Profiles

  2. Phase 2: Design persona profiles (3-5 h) Owner: Facilitator Action: Create one persona profile per cluster: name (fictitious but memorable), photo, short context story, goals (3-5), pain points (3-5), behavior, representative quotes. Add realistic details from interviews. Hint: Stock-photo personas without substance are ignored. Concrete quotes and behavior make personas usable. Output: Needs Summary

  3. Phase 3: Quant validation (2-4 h) Owner: Facilitator Action: Check personas against quantitative data: how large is each segment? How are behaviorals distributed? If data contradicts the personas, adjust them. Hint: Personas without quantitative anchors drift. If Persona X only covers 1% of the user base, the team should know that before treating it as driving. Output: Scenario Notes

  4. Phase 4: Stakeholder validation (1-2 h) Owner: Facilitator Action: Validate personas with stakeholders (sales, support, service). Who has regular customer contact? Do personas match their experience? Hint: Sales and support often see different personas than the research team. If major differences exist, review research coverage or refine personas. Output: Persona Profiles

  5. Phase 5: Team activation (1-2 h) Owner: Owner Action: Distribute personas in the team, post them in design spaces, reference them in backlog templates. Name one champion per persona who challenges decisions through that persona lens. Hint: Personas stored away in a drawer have no effect. Visibility and active use are the levers. Output: Needs Summary

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Persona Profiles

Closeout

  • Update result artifact: Persona Profiles
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Persona Profiles: Personas

Working Question

Which distinct user groups with different needs, goals, and behaviors can be derived from research, and which of them drive design decisions?

Context

Interview notes or transcribed highlights; demographic quantitative data; known internal persona attempts and their weaknesses; persona purpose (design decisions vs marketing messaging vs strategy).

Participants

  • Owner: A UX researcher as owner
  • Participants: A UX researcher as owner; one to three researchers with direct interview context; a Product Manager for segment prioritization; one to two designers for persona format and visuals.

Input

Affinity mapping board (Miro, FigJam) for research synthesis; persona template with fields (name, photo, demographics, goals, pain points, behavior, context, quotes); optional quantitative data export (analytics, CRM).

Template

Personas Working Template

Goal

Evidence-based archetypes of different user groups.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Persona Profiles:
  • Needs Summary:
  • Scenario Notes:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Persona Profiles is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Personas Working Template

View templateCompact working template for Personas with context, input, output artifacts, and next step.
markdown

personas-working-template.md

Compact working template for Personas with context, input, output artifacts, and next step.

Personas Working Template

Goal

Evidence-based archetypes of different user groups.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Persona Profiles:
  • Needs Summary:
  • Scenario Notes:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Persona Profiles.
  • Review personas annually for freshness because the market changes. For larger research rounds, create a new version with date. Mark outdated personas explicitly as archived, not deleted (history is valuable).
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet