liveBook · Manning

Safety rule

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A safety rule is a collectively agreed constraint on behavior intended to protect open and respectful participation in a group activity.

A safety rule is a working agreement that a group explicitly accepts to protect open, respectful participation. It gives a facilitator and participants a shared reference point when behavior undermines the session. Rules are not imposed once and forgotten: the group can add or change them, but only with everyone’s agreement. section 6.3.2 section 6.5

Establish safety rules at the beginning, alongside the agenda, roles, and expectations. Ask for explicit consent rather than assuming silence means agreement; a raised-hand check can confirm that everyone understands and accepts the rules. Invite participants to contribute rules that help them participate safely. section 6.3.2

Use safety rules as a facilitation practice:

  • Name a rule that supports open discussion, such as “nobody holds the monopoly to the truth.” section 6.3.2 section 8.3.2
  • Adapt rules to the setting; for an online session, agree to disable unnecessary notifications and communication programs. section 6.3.2
  • Pause for disagreement about a rule before continuing, rather than allowing an unresolved objection to remain implicit. section 6.3.2
  • Refer back to the agreement when the group shows a pattern of not complying with it. section 6.5 section 8.3.2

Opening two modeling groups

When a larger group divides into smaller modeling groups, begin by discussing safety agreements before work starts. Ask whether participants understand and agree that no one has a monopoly on the truth. The agreement can support participation across divergent models and provide a way to address later patterns that exclude or silence viewpoints. section 8.3.2 section 8.3.2

Safety rules work with, rather than replace, attention to rank, social power, resistance, and conflict. A facilitator still needs neutrality and observation to notice tensions and emotionally charged hotspots. The rules provide a shared boundary for addressing those moments without treating one person’s perspective as the only valid account. section 6.3.2 section 8.3.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Explains rule-setting, explicit consent, adaptation, revision, and referral after noncompliance, while deferring conflict management details.
Examples
Uses the truth-monopoly agreement, online notification limits, raised-hand consent, and divided modeling groups.
What it assumes
Assumes participation in a facilitated group session and teaches safety-rule setup from the opening.
What you can do after
Operate/configure it by co-creating, confirming, revising, and invoking agreements during collaborative sessions.
How it connects
Connects safety rules with ranking, working agreements, neutrality, resistance, conflict resolution, and Big Picture EventStorming.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.