B2B SaaS User Persona Framework · CHAPTER 3 OF 5

Roles, responsibilities, and qualifications

Step 1 Role & Responsibilities

First, Identify the User’s Real Role

Start by identifying the user’s role in the software.

​

Examples:

RA Lead, RA Junior, QA Manager, QA Reviewer, QA Approver, Lab Analyst, Warehouse Operator, Finance Manager, Admin, Plant Head


The role name tells you what the user is expected to do inside the system.

But the role name is only the starting point.

User roles arranged on tilted cards beside the Upslide character.

RA Lead

QA Manager

QA Approver

Admin

Persona 5

Persona 6

RA Juniour

QA Reviewer

Lab Analyst

Plant Head

Persona 1

First, Identify the User’s Real Role

Start by identifying the user’s role in the software.

Examples:

RA Lead, RA Junior, QA Manager, QA Reviewer, QA Approver, Lab Analyst, Warehouse Operator, Finance Manager, Admin, Plant Head

The role name tells you what the user is expected to do inside the system.

But the role name is only the starting point.

User roles arranged on tilted cards beside the Upslide character.

RA Lead

QA Manager

QA Approver

Admin

Persona 5

Persona 6

RA Juniour

QA Reviewer

Lab Analyst

Plant Head

Persona 1

Understand the Full Responsibility, Not Just the Software Task

Most software supports only one part of a user’s work.

​

So you cannot understand the user only by looking at the screens they use.

Illustration accompanying Understand the Full Responsibility, Not Just the Software Task

Understand the Full Responsibility, Not Just the Software Task

Most software supports only one part of a user’s work.

So you cannot understand the user only by looking at the screens they use.

Illustration accompanying Understand the Full Responsibility, Not Just the Software Task

Example

In dossier software, the RA Lead may review and approve documents inside the system. But outside the system, they may also:

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Guide Junior RA members

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Coordinate with R&D teams

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Collect inputs from departments

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Communicate with health authorities

Illustration accompanying Example

Example

In dossier software, the RA Lead may review and approve documents inside the system. But outside the system, they may also:

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Guide Junior RA members

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Coordinate with R&D teams

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Collect inputs from departments

Example: Guide Junior RA members Coordinate with R&D teams Collect inputs from departments Communicate with health authorities

Communicate with health authorities

Illustration accompanying Example

Why Role & Responsibility Research Matters

Role and responsibility research helps identify:

What mistakes they must avoid

What decisions they make

What other teams depend on them

Illustration accompanying Role and responsibility research helps identify:

What the user is trying to complete

What information they need

What pressure they work under

Role and responsibility research helps identify:

What the user is trying to complete

What information they need

What mistakes they must avoid

What other teams depend on them

What decisions they make

What pressure they work under

Illustration accompanying Role and responsibility research helps identify:

Step 2 Qualification

Understand What the User Knows Before They Use the Product

Every SaaS role has a different level of knowledge.

​

Some users understand the process well.

Others need more guidance and validation.

​

Qualification helps designers decide how much support, speed, and control each user needs.

Junior User

Low domain knowledge

Understand What the User Knows Before They Use the Product: Junior User Low domain knowledge Senior User High domain knowledge

Senior User

High domain knowledge

Understand What the User Knows Before They Use the Product: Junior User Low domain knowledge Senior User High domain knowledge

Understand What the User Knows Before They Use the Product

Every SaaS role has a different level of knowledge.

Some users understand the process well.

Others need more guidance and validation.

Qualification helps designers decide how much support, speed, and control each user needs.

Junior User

Low domain knowledge

Understand What the User Knows Before They Use the Product: Junior User Low domain knowledge Senior User High domain knowledge

Senior User

High domain knowledge

Understand What the User Knows Before They Use the Product: Junior User Low domain knowledge Senior User High domain knowledge

Education

What educational background does this role usually require?

Training

What domain, compliance, process, or tool training does the user need?

Experience

What domain, compliance, process, or tool training does the user need?

Map Qualification in Three Layers

These details help the team understand how much guidance, control, flexibility, and validation the software should provide.

  • Education

    What educational background does this role usually require?

  • Training

    What domain, compliance, process, or tool training does the user need?

  • Experience

    What domain, compliance, process, or tool training does the user need?

Map Qualification in Three Layers

These details help the team understand how much guidance, control, flexibility, and validation the software should provide.

Education

What educational background does this role usually require?

Training

What domain, compliance, process, or tool training does the user need?

Experience

What domain, compliance, process, or tool training does the user need?

Professional Goals Matter More Than Personal Goals

In B2B SaaS, professional goals are more useful for design.

If users want to perform better in their role. They need to work faster, make fewer mistakes, and handle responsibilities with more clarity.

​

The software should help users perform better in their role.

Professional Goals Matter More Than Personal Goals: work faster Few mistakes handle responsibilities

work faster

Professional Goals Matter More Than Personal Goals: work faster Few mistakes handle responsibilities

Few mistakes

handle responsibilities

Professional Goals Matter More Than Personal Goals: work faster Few mistakes handle responsibilities

Professional Goals Matter More Than Personal Goals

In B2B SaaS, professional goals are more useful for design. If users want to perform better in their role. They need to work faster, make fewer mistakes, and handle responsibilities with more clarity.

The software should help users perform better in their role.

Professional Goals Matter More Than Personal Goals: work faster Few mistakes handle responsibilities

work faster

Professional Goals Matter More Than Personal Goals: work faster Few mistakes handle responsibilities

Few mistakes

handle responsibilities

FRAMEWORK CONTENTS

B2B SaaS User Persona Framework

Search documentation

Search scope

Search across all eight guides.

Diagram detail