讨论： Asynchronous communication norms for distributed teams

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

暂无译文，显示原文。 原文

'Set a decision date instead of demanding immediate replies, and close the thread with the decision' turns silence into consent, and silence is distributed unevenly across time zones, holidays and workload. Whoever proposes and sets the date wins by default; the objection from the person on leave in a distant time zone arrives after the close. Open-source projects that run on this rule have added two safeguards the article lacks. The Apache Software Foundation's lazy consensus asks proposers to allow at least 72 hours before assuming agreement, precisely so that a weekend or a distant time zone cannot be skipped, and reserves lazy consensus for uncontroversial actions; consequential decisions require explicit votes with named participants. The norm should therefore state a minimum window per channel, define which decisions may be taken by lazy consensus and which need explicit acknowledgement from the affected owners, and let a late objection with new information reopen the decision rather than be ruled out of order. Otherwise the channel table works and the decision rule quietly becomes 'the fastest writer decides', which is the failure the article set out to prevent.