Description
A cross-functional team drafts, over two sessions, a one-page agreement on how it will work together, including how it will use and commission research.
A team operating agreement is a short written statement of how a cross-functional team will interact, approach problems and escalate issues. Merholz and Skinner suggest topics including how the team integrates as one unit, a communication plan, availability of key people for working sessions, stakeholder approvals and timing, escalation and issue resolution, and assumptions about deliverables (timing, type, fidelity). Distinctively, they include how the team works with the research or insights group: access to existing insights and the timing, recruiting, protocols and field research for new studies. The agreement is built in two sessions separated by at least a day, so first ideas can settle before they are finalised. Related practices protect maker time and keep a shared terminology document.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Active
- Goal
- Support a decision
- Stage
- Strategy
- Data
- Qualitative
- Effort
- Hours
Steps
- Facilitate a first session with the full team: brainstorm agreement topics without judgement, discuss them and build an affinity diagram.
- Include how the team will access existing research and commission new studies (timing, recruiting, protocols, fieldwork).
- Let the ideas rest for at least a day.
- Reconvene to review, modify ideas and categories, and finalise the list.
- Publish the agreement as a one-page document or slide alongside or within the team charter.
- Revisit it when team membership or ways of working change.
Sources
- Org Design for Design Orgs (Merholz & Skinner, 2016)
- Product Management for UX People (Crumlish, 2022)
- User Experience Management (Lund, 2011)
Also known as
- Working agreement
- Team charter agreement
Categories
- Design
- Design & Product Practice