Personas

A persona is a fictional user archetype that stands in for a group of similar end users, summarizing their goals, motivations, behaviors, and key traits.

Key Points

  • Personas are built from real research and observations, not guesses or stereotypes.
  • They capture user goals, motivations, behaviors, and pain points relevant to the product.
  • Teams use personas to guide prioritization, acceptance criteria, and design decisions.
  • Personas should be revised as new user insights emerge during the project.

Example

A product team creating a mobile health app defines "Busy Brenda," a 35-year-old working parent who wants quick, reliable meal and workout suggestions. Her motivations include saving time and staying healthy, and her pain points are complex navigation and long setup. The team uses Brenda's persona to prioritize a one-tap daily plan feature and streamline onboarding.

PMP Example Question

During backlog refinement, the team is torn between building an advanced reporting dashboard or simplifying onboarding. Which artifact best helps them decide by focusing on user goals and motivations?

  1. Definition of Done
  2. Personas
  3. Risk Register
  4. Sprint Goal

Correct Answer: B — Personas

Explanation: Personas represent target users and their goals, guiding choices toward the features that best serve user needs.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Run the drill before the incident runs you

Design, run and prove OT drills and tabletop exercises before an incident tests your team. OT Incident Drills and Exercises includes 24 lessons and practical exercise materials, delivered through HKSM Courses for US$47 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course