Team Personas

Personas in PushBackLog are AI-modelled representations of the different roles and perspectives on your team. They are used to inform refinement, surface blind spots, and generate richer acceptance criteria.

What Personas Are Not

Personas are not user accounts. They do not log in or take actions in the system. They are documents that describe a person’s role, background, goals, and concerns — and the AI uses them as context when generating suggestions.

Viewing Personas

Click Personas in the sidebar to see all personas in your organisation. Each card shows:

• Name and role
• A short bio
• Key goals and frustrations

Creating a Persona

1. From the Personas list, click New Persona.
2. Fill in:
   • Name — a realistic name (e.g. “Christy Arthur”)
   • Role — job title or functional role (e.g. “Senior Engineer”)
   • Bio — 2–4 sentences describing background and expertise
   • Goals — what this person is trying to achieve
   • Frustrations — pain points this person commonly encounters
3. Click Save.

AI-Generated Personas

Click Generate for an AI-suggested persona based on common roles in product teams. Review and edit the suggestion before saving.

Hiring into the Roster

A Roster is an org-level record of which personas are assigned to specific projects. “Hiring” a persona into a project’s roster means that persona’s perspective will be taken into account during AI refinement and suggestion.

How Personas Influence AI

When you run an AI refinement session on a backlog item, the system selects relevant personas from the project roster and prompts the AI to generate acceptance criteria and edge cases from each persona’s perspective. For example, a “Security Engineer” persona will surface security-related edge cases more readily than a “Marketing Manager” persona.

Personas vs Human Users