In any group of humans, things will sometimes go sideways. Whether it's simple unintentional miscommunication or more extreme unacceptable behavior, we need to have an agreed upon protocol to resolve these situations ourselves or to escalate in the case that one-to-one resolutions are unachievable.
This is the process for incident resolution at Rands Leadership Slack and process is documented culture.
When an incident occurs, we ask that per the Code of Conduct for those involved to resolve peacefully:
“If you see someone violating any part of this Code of Conduct, we urge you to respectfully dissuade them from such behavior. Expect that others in the community wish to help keep the community respectful, and welcome your input in doing so.”
This is easier said than done, but this is Rands Leadership Slack. Our expectations are that everyone here is hoping to learn about the craft of leadership; peaceful resolution of complex human situations is leadership 101.
Resolution amongst the individuals will not always be achievable. In this case, the reporter or observer of the incident has a choice. They can share the incident with #rands-slack-rules to seek feedback, and perhaps resolve the incident, or they can raise the incident with the Administrators (see below for specifics). We understand the need for the latter workflow, but we highly encourage the former because, again, this is a community focused on leadership. Our hope is that the debate will help educate this sub-community of humans interested in the rules and culture that govern this small corner of the Internet.
When ready and if appropriate, the reporter needs to send an Administrator a direct message with the following information.
- What’s the nature of the incident or Code of Conduct violation?
- Who is involved in this incident?
- What material supports this situation?
- Any privacy concerns? (Reporter consent is required before sharing any information regarding the incident)
With this information in hand, the Administrators will strive to respond to the reporter as quickly as possible with an estimate of when they think they’ll be able to triage and resolve this incident. In extreme cases, the administrator may suspend one or more accounts until they are able to triage and resolve an incident.
Incident resolution can vary from hours to days depending on the availability of those involved. Once the incident is resolved, the Administrators will communicate the resolution to the reporter and other other parties relevant to the incident. In extreme cases, the Administrators will communicate the resolution with #rands-slack-rules with reporter permission.
In cases that result in account suspension, the individual suspended may appeal the decision starting one week after the suspension by sending a mail to an Administrator with justification for overturning the appeal. If a suspension is overturned, the new context will be shared with #rands-slack-rules
- “Is situation XYZ an incident?” Unsure if there’s a CoC violation? Ask in #rands-slack-rules and/or DM the administrator. We'll help.
- “How many incidents have you handled since this place started?” Nine as of Feburary 2018.
The administrator(s) of Rands Leadership as of Feburary 19th, 2018:
@rands (Michael Lopp)
V1.3 of this Code of Conduct was published on February 14th, 2018.
This Code of Conduct is released under the CC0 public domain license.