Roles and Responsibilities Workshops

Introduction

Your team has capable people and clear job titles. Yet nobody agrees on who owns the decision, who sends the update, or who handles the exception. A new project or AI tool makes this worse, because it quietly changes how work gets done.

A roles and responsibilities workshop is a structured conversation that makes ownership, expectations, overlaps, gaps, and shared work visible. The evidence for acting is solid: a 2008 meta-analysis of 169 samples found role ambiguity was among the stressors most strongly tied to lower job performance.

This guide covers why the workshop matters, how to prepare and facilitate it, which formats to choose, and how to adapt it for people-centered AI adoption.

Key Takeaways

  • A workshop clarifies who owns what without isolating roles.
  • Shared understanding matters more than a finished diagram.
  • Separate "where responsibility belongs" from "how the work gets done."
  • AI rollouts need extra clarity on judgment, exceptions, and learning support.

Why Run a Roles and Responsibilities Workshop?

Start with three terms that people often blur:

  • Role: a position or function
  • Responsibility: an area of ownership or accountability
  • Activity: a specific action that supports a responsibility

Unclear ownership shows up as duplicated work, missed tasks, conflicting decisions, slow handoffs, and tension over who should be consulted or informed. These costs rarely come with a reliable dollar figure, so look at your own team's friction instead of inventing one.

A good workshop produces:

  • Agreement on individual and shared responsibilities
  • Visibility into overlaps and gaps
  • Clearer interfaces between roles
  • A documented basis for future decisions

When should a team hold one?

Hold it at the start of a new team, project, transformation, or AI rollout. Atlassian's kickoff exercise compares each person's view of their role with how others see it.

The University of Minnesota also recommends clarifying roles after a major change. Repeat the session when membership, technology, reporting lines, or responsibilities shift.

It also helps when you see recurring escalations, stalled decisions, conflicting expectations, or work that keeps landing in "someone should handle that."

What roles and responsibilities should be addressed?

There is no universal set of five roles. Tailor the names to your team, but make every relevant function visible. Five adaptable categories:

  • Executive sponsor or decision owner
  • Business or process owner
  • Manager or change lead
  • Subject-matter or frontline representative
  • Implementation or operations owner

Five responsibility categories to explore:

  1. Making or approving decisions
  2. Carrying out the work
  3. Coordinating and communicating
  4. Managing risks and escalations
  5. Gathering feedback to improve adoption or performance

How to Prepare for a Roles and Responsibilities Workshop

Define scope before you invite anyone. Name the project, workflow, team, or initiative, and state whether you're mapping current ownership, future ownership, or both.

Then set a concrete outcome. Strong outcomes include:

  • An agreed responsibility map
  • A list of decision rights
  • Shared team responsibilities
  • An action list for unassigned work

Who should participate?

Invite people who:

  • Do the work
  • Make decisions
  • Depend on the work
  • Are affected by role changes

Add representatives from adjacent teams when handoffs are central.

Pick a neutral facilitator. The International Association of Facilitators says facilitators serve the group's process impartially and disclose conflicts of interest. The facilitator should make disagreement discussable and stop senior voices from setting the answer early.

Materials, board design, and ground rules

Build a physical or digital board with:

  • A space for each role
  • An area for shared team responsibilities
  • A "limbo" area for unassigned work
  • A parking lot for topics to revisit later

Ground rules should encourage:

  • Specific examples
  • Equal participation
  • Curiosity

Make clear that questioning ownership is not criticizing a person.

Send the purpose, participants, expected prep, and draft agenda in advance. People should arrive ready to discuss responsibilities, not discover the purpose in the room.

How to Facilitate a Roles and Responsibilities Workshop

Open with purpose and definitions

Explain the goal, desired output, decision approach, and timeboxes. Define roles, responsibilities, activities, shared ownership, and unassigned work before mapping begins.

Ask people to focus on where responsibility belongs. Park process debates ("how should we do this?") as later action items.

Generate responsibilities individually first

Give everyone quiet time to list responsibilities for each role:

  • Work they do
  • Work they expect from others
  • Work with unclear ownership

HBR recommends 10-20 minutes of silent brainstorming, which keeps louder voices from anchoring the room.

Use one responsibility per note and start each with a specific action verb. Clarify vague entries later.

Map the current state

Review notes, merge duplicates, and clarify ambiguous language. Place each responsibility under the role that currently owns it rather than jumping to the ideal future.

Collective ownership goes in the shared area. Unclear items go to limbo instead of forcing premature agreement.

Surface gaps, overlaps, and disagreement

Ask the group to flag responsibilities that look misplaced, duplicated, or overly concentrated. Useful questions:

  • Who makes the final decision?
  • Who performs the work?
  • Who needs to be consulted?
  • Who must be informed?
  • What happens when the normal process fails?

Resolve priorities before peripheral details

Take marked items one at a time, starting with the greatest operational risk, decision delay, employee confusion, or customer impact.

If the group stalls, record the competing interpretations, name a decision owner, and park the topic with a next step. One disagreement shouldn't eat the session.

Nielsen Norman Group suggests reserving 20-30 minutes at the end for parked items, or scheduling follow-up within 1-2 days.

Roles workshop facilitation timeline with brainstorming and follow-up timeboxes

Close with documentation and follow-through

Summarize agreed roles, responsibilities, decision rights, shared work, unassigned items, and open questions. Read it aloud so people can correct misunderstandings.

Convert decisions into owners and actions, distribute the final map, and schedule a review for when the team, workflow, or technology changes.

Workshop Formats and Tools

Format Best for
Role expectation matrix Mismatched expectations and handoffs
Venn diagram Responsibilities that span functions
Card sort Broad task inventory
RACI, DACI, or delegation mapping Decision clarity

Role expectation matrix

Ask what each role should expect from every other role, then discuss points of dissonance. A simple version compares the role, what the holder believes they own, and what others believe they own. Use it to align expectations, not to build rigid walls that block collaboration.

Venn diagram for shared responsibilities

Use overlapping circles when work genuinely spans business, technical, people, or customer-facing functions. Label the center "shared" only if the team can explain how decisions, execution, and accountability work there.

Responsibility card sort

Write concrete tasks on cards. Participants place each under the role they believe owns it, with separate spots for shared, unassigned, or disputed items. Run it silently and individually when hierarchy might sway answers, then discuss the cards placed differently.

RACI, DACI, or delegation-based mapping

Use these when you must separate who does the work from who approves and who is consulted or informed. Cornell's RACI guidance calls for one accountable person per item. DACI adds a single approver, and Delegation Poker defines seven levels of delegated authority.

RACI DACI and Delegation Poker decision authority comparison

RACI has limits. Overused, it turns bureaucratic and blurs decision authority with input. Don't give multiple people ultimate accountability for one decision unless you can explain how conflicts get resolved.

How to choose the right format

Match the tool to the problem. Tools prompt conversation; they don't replace judgment. The best format helps your team discuss hard ownership questions openly and document a usable agreement.

Applying Role Clarity to AI Adoption

AI adds responsibilities most team maps don't include:

  • Selecting use cases
  • Approving tools
  • Validating outputs
  • Protecting sensitive information
  • Handling exceptions
  • Monitoring workflow impact
  • Training employees
  • Communicating role changes

NIST's AI Risk Management Framework says AI-risk roles, responsibilities, and communication lines should be documented and clear, with defined human-oversight processes. It doesn't prescribe job titles or an exception workflow, so your team has to decide those.

The human side of changing work

Document the human side of the change:

  • Where employee judgment stays essential
  • What people must learn
  • Who protects learning time
  • How concerns get escalated

The gaps are real. KPMG's survey found 84% of workers wanted more AI training, and Pew found 52% of U.S. workers worried about future AI use at work.

Include middle managers and frontline experts. They translate executive expectations into daily practice, answer questions, notice confusion, and adjust workflows after launch. Gallup data shows employees whose managers strongly support AI use are more likely to use it frequently, though that's an association, not proof of cause.

Human roles and responsibilities supporting successful AI adoption

Structured support for rollouts

Christina Muller's Carrying the Rollout™ workshops, offered as half-day or full-day sessions, help leadership teams sort what is theirs to own, what to hand back, and who decides during each wave of AI change.

Frequently Asked Questions

What is the purpose of a roles and responsibilities workshop?

It creates shared clarity about who owns decisions, tasks, expectations, handoffs, and unresolved work. The result is less duplication and fewer gaps.

What are the five main roles in a team that a roles and responsibilities workshop addresses?

There's no universal list. Common adaptable categories are executive sponsor, business or process owner, manager or change lead, subject-matter or frontline representative, and implementation or operations owner.

What are five common responsibilities of team members covered in a roles and responsibilities workshop?

Common responsibilities include decision-making, execution, coordination and communication, risk and escalation management, and feedback for improvement.

What examples of roles and responsibilities are covered in a roles and responsibilities workshop?

Examples include approving decisions, managing a workflow, validating AI outputs, training users, communicating changes, handling exceptions, and escalating risks.

How long should a roles and responsibilities workshop take?

It depends on team size, number of roles, complexity, and conflict level. Atlassian's published play uses 15 minutes of prep and a 60-minute session for 2-8 people. Larger or more contested teams need more time with clear timeboxes.

Who should facilitate a roles and responsibilities workshop?

A trusted, neutral facilitator with group-process skills works best. That matters most when the project manager or a senior leader is personally involved in the ownership disputes.