What is The Playbook?
The Playbook represents 9Y’s policies, institutional knowledge and best practices.
Prefer to use processes as documented in the Playbook, whenever possible.
If what is documented can be improved, please propose a change.
Edits are encouraged by everyone (⬅ Using Confluence’s commenting feature is a great way to suggest changes). If you see a small mistake, or would like larger changes, just use the Feedback System
Keep pages small, simple and searchable. One piece of knowledge per page, otherwise it becomes hard to find things.
Stick to the existing conventions. Rather than enumerate all the rules here in an undecypherable wall of text, just have a look around at some pages in the playbook and the patterns should be self-evident. Please don’t secretly invent your own styles.
Don’t add content into folder pages.
Don’t create additional nesting levels inside the Gameplans groups. But feel free to add new groups.
Status: always add
Access Restriction: always add if the document is restricted. You need to do this manually. This is how it looks:
The DRAFT state means the document is currently in draft status and the owner is still working on it. It is the author's responsibility to get it reviewed with the relevant owner/reviewer.
Status colour Yellow title Draft
LIVE indicates the page has been reviewed and is reflecting the current status for this topic.
Status colour Green title LIVE
FLAGGED documents, are previously LIVE documents that have been flagged because there is something wrong, e.g. out of date, inconsistent, etc. When the owner applied changes to fix those issues, the status can be updated to LIVE again.
Status colour Red title FLAGGED
By default everything in the playbook is public (to the world, not just our internal team). If you want to prevent that, you'll need to manually restrict pages. You can use groups such as "Core Team". Always signal this at the top of your document.
Real example at the bottom of this page 👇