Working Agreements — Facilitator Script & Timeboxed Agenda

Purpose and outcomes

This facilitation script helps a group co-create clear, actionable working agreements (team norms) that are owned by the team and revisited regularly. Use it to reduce hidden expectations, make collaboration predictable and fair, and create simple measures that let the team know whether agreements are working.

Intended outcomes

• A prioritized set of 6–10 concise working agreements the team accepts and can enact immediately.
• Named champions for each agreement and a 3-month review plan with simple measurements.
• A shared record (copyable template) that the team can refer to and update.

Logistics

Recommended duration: 75–90 minutes. Adjust timing for larger groups or deeper drafting.

Materials: sticky notes (physical or digital), markers, voting dots or polling tool, timer, shared doc for final agreements.

Participants: entire team. Facilitator: neutral guide (rotating facilitator is ideal). Timekeeper: optional.

Agenda and facilitator script (timeboxed)

1. Welcome & framing — 5 minutes

   Facilitator: “We’re here to make how we work together more explicit so we spend less time guessing expectations and more time doing good work. Today we’ll create a short set of agreements we can test for three months. These should be behaviors we can see and act on, not values statements.”

2. Brief examples & ground rules — 5 minutes

   Facilitator: “Examples of concrete agreements: ‘Start meetings on time and end on time,’ ‘Share documents 24 hours before the meeting,’ or ‘Name the decision and who decides.’ Avoid vague phrases like ‘be respectful’ unless tied to observable actions.”

3. Individual ideation (silent) — 7–10 minutes

   Prompt: “Write one idea per sticky note for behaviors we should keep, stop, or start doing to collaborate better.”

   Facilitation tip: Encourage specificity (who, when, how). Use 5–10 minutes depending on team size.

4. Share & cluster — 10–15 minutes

   Process: Participants post notes, then the group silently clusters similar ideas for 5–8 minutes. Facilitator helps label clusters with neutral headings.

   Script: “Let’s group similar ideas so we can see patterns. Don’t debate while clustering — we’ll surface differences later.”

5. Clarify & merge duplicates — 8 minutes

   Facilitator: For each cluster, invite quick clarifying questions (one or two) and merge overlapping items into a single short statement. Aim for behavior-focused phrasing: action + context + (optional) frequency. Example: ‘Share agendas 24 hours before meetings’ instead of ‘prepare better for meetings.’

6. Dot-vote to prioritize — 7–10 minutes

   Each person has 3–5 votes (depending on number of clustered items). Vote on the items that will make the biggest difference. Use physical dots or a quick poll tool.

   Script: “Place your votes on the items you think will most reduce friction or improve predictability. Don’t overthink it — pick the changes that would matter this month.”

7. Draft final wording — 10–15 minutes

   Take the top-ranked items (aim for 6–10) and turn them into short, observable working agreements. Use the template: When [context], we [behavior].

   Example drafts:

   • “When we meet, we start on time and end on time.”
   • “Before meetings, we post the agenda and any needed materials at least 24 hours in advance.”
   • “We call decisions explicitly: R = who decides; I = who is informed.”
8. Assign champions & owners — 5 minutes

   For each agreement, ask: who will be the champion for making this visible and helping the team follow it? Champions are not gatekeepers — they remind, collect examples, and help with the 3-month review.

9. Commitment & next steps — 5 minutes

   Read agreements aloud, ask for voice or thumbs-up. Record final agreements in a shared document and add to team onboarding docs, meeting templates, or project charters. Set a calendar reminder for the 3-month review.

Measurement prompts & 3-month review plan

Simple, observable signals are best. Propose 2–4 measures for the review that team members can honestly track.

• Adherence signals (examples): % of meetings that start on time, % of agendas posted 24 hours prior, number of missed commitments per sprint.
• Experience signals: short anonymous pulse (2 questions) measuring whether people feel agreements improved clarity and reduced friction.
• Operational signals: number of rework events tied to unclear decisions, or number of escalations caused by unmet expectations.

3-month review agenda (60 minutes):

1. Quick data review: show adherence and pulse results (10 minutes).
2. Stories and examples: what worked, what didn’t (20 minutes).
3. Decide: keep, revise, retire each agreement (20 minutes).
4. Assign next 3-month champions and set new measures if needed (10 minutes).

Sample working agreements (copyable)

• Start meetings on time and end within the scheduled time.
• Post meeting agendas and relevant documents at least 24 hours before the meeting.
• Name the decision required and who owns it before discussions begin.
• Ask clarifying questions first, then offer recommendations.
• Raise blockers within 48 hours in the team channel and suggest next steps.

Facilitation tips & psychological safety

• Create an environment where ideas are collected before critique; silent ideation lowers conformity pressure.
• If tensions arise, surface them as data: “I hear two views — let’s test the one that solves the biggest pain for a month.”
• Encourage experimentation: treat agreements as hypotheses that can be modified after the review.

Remote adaptations

Use a digital board for ideation (Miro, Jamboard, sticky-note apps). Use the platform’s poll feature for dot-voting and a shared document for final agreements. Keep timing tighter (shorter clustering) if attention spans are limited.

Record template (to copy into your team doc)

When to revisit sooner

If a repeated conflict, missed commitments, or a safety/quality incident is directly caused by unclear agreements, convene a short ad-hoc review rather than waiting three months.

Closing

Working agreements are a team-made operating system. Keep them short, observable, and testable. The goal is less to police behavior and more to create predictable collaboration and reduce the hidden costs of assumptions.