<?xml version="1.0" encoding="utf-8"?>

Roles and responsibilities

Roles and responsibilities Bad Practice
Roles and responsibilities Best Practice

Workshops conducted at the early stages of a project usually lead to the definition of roles and responsibilities. Documenting this information helps avoid confusion about who on a team is responsible for each task.

For example, is your UX designer responsible for user research and information architecture on a project, or do you have a UX researcher or information architect to take care of those tasks? Who does the UX copy for designs — UX writers, UX designers, or UI designers? Who is responsible for aggregating and analyzing UX research findings? How does the team process bugs?

The goal is not to create a long-read document that takes time and effort to scan. Team members and other stakeholders should be able to access this workshop deliverable whenever they need to find and refresh data quickly.

Pro Tip: Assigning too many responsibilities to one person can lead to burnout. This can be prevented by hiring a new team member or extending sprint periods.

Improve your UX & Product skills with interactive courses that actually work