Link to current text
CB.11:8 - Common Anti-Patterns and How to Avoid Them
| Failure | Better move |
| Keep the founder’s preferred format because it once worked | Recover current uses and compare feasible arrangements with affected people. |
| Claim that relationships will survive loss of the platform | Obtain willing contact and activity arrangements and observe their use. |
| Name a successor without providing time, access or capability | Establish and try the contributions their receiving work needs. |
| Copy every discussion and contact into a new space | Recover permitted uses and transfer only what the receiving arrangement may use. |
| Treat separation as failure while keeping an unresolved common resource | Allow different purposes and provide terms for the dependency that remains shared. |
| Preserve every old document as current guidance | Retain useful explanations with their conditions and distinguish an archive from maintained support. |
| Announce closure while leaving promised responses ownerless | Settle or transfer the actual obligations and give their receivers a reachable answer. |
| Maintain a pause with no next decision | Name the resumption condition or review date and decide again when it arrives. |