> 🧩 A Moral Fabric pattern, free for any nonprofit to use and adapt.
Distributed and part-time teams tend to invent presence theatre. People announce every break and every appointment, notifications stay on so replies come within minutes, and within a few months the implicit norm is instant availability. Nobody chose it, everybody enforces it, and deep work becomes something you do in the evening.
Make asynchronous the default, and be explicit about what nobody has to announce.
- Not a break, not a walk, not deep work, not an appointment. Colleagues aren't tracking your hours; response norms already tell them when to expect an answer.
- Required only when you're unreachable for three days or more. For fixed recurring days off, automate it — see Automate your Slack status for fixed days off .
- You decide when to check, not the tool. This only works if response times are written down, so it pairs with Communication norms .
- Response norms are measured in days. A genuinely urgent thing gets a call, which is why the escalation route has to exist.
- Ask directly and assume positive intent: "did you see this — when can I expect a reply?"
- This one is set by example, not by policy. Whoever leads the team answering messages on holiday establishes the norm silently, and no written policy will undo it.
Decision test: can a colleague in another timezone do a full, useful day's work without needing a synchronous answer from anyone? If not, the missing piece is usually documentation, not discipline.
Write the list of what nobody has to announce, and say it out loud once in a team meeting. Permission has to be given explicitly; people won't assume it.
Turn notifications off together, in the meeting, on everyone's devices. Left as homework it doesn't happen.
Define the urgent escalation route, so switching off feels safe.
Move the recurring information people were fishing for in chat into the tracker or wiki. Async fails on missing documentation, not on willingness.
Have leads visibly not work while off. That is the whole intervention.
Working-time and rest rules still apply — async is not a licence for always-on. Contracted days for part-time colleagues are contractual, not a preference: expecting Friday replies from someone who works four days is a change to their contract, not a nudge. Several European countries have right-to-disconnect legislation, and where it applies it sets a floor under all of this. If you employ people across borders, the rules of each country of employment apply, not those of your head office.
Record your organization's choices:
- What nobody has to announce, and when a status is expected
- Core overlap hours, if you want any
- The urgent escalation route, and who may use it
- Whether notifications-off is advice or the norm
- How on-call or duty rosters work, if you run them