Library / Community Building Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:35:10 UTC

CB.11:8 - Common Anti-Patterns and How to Avoid Them

FailureBetter move
Keep the founder’s preferred format because it once workedRecover current uses and compare feasible arrangements with affected people.
Claim that relationships will survive loss of the platformObtain willing contact and activity arrangements and observe their use.
Name a successor without providing time, access or capabilityEstablish and try the contributions their receiving work needs.
Copy every discussion and contact into a new spaceRecover permitted uses and transfer only what the receiving arrangement may use.
Treat separation as failure while keeping an unresolved common resourceAllow different purposes and provide terms for the dependency that remains shared.
Preserve every old document as current guidanceRetain useful explanations with their conditions and distinguish an archive from maintained support.
Announce closure while leaving promised responses ownerlessSettle or transfer the actual obligations and give their receivers a reachable answer.
Maintain a pause with no next decisionName the resumption condition or review date and decide again when it arrives.