Having your Pilot organization tailored to your needs from the start eases adoption and maintenance. In this article we have outlined some high-level strategies for you.
Wikis
Wikis let you organize your knowledge into meaningful categories and help you manage who has access to the information.
When you set up your different wikis the first thing to do is to map out the content that you would like to include in your knowledge base and then the (groups of) people that need access to that content. You want to create wikis around the different groups of people that need access to the same set of information.
The overlap between audience and content forms the blueprint for setting up your channels. You can read more about this and the different approaches for setting up and structuring your account -> How to Structure Your Pilot Account.
Tip: We recommend starting with one Wiki to get the hang of how Pilot interacts with your Google Workspace folders.
Setting up wikis will not only help with organizing the content but also help you maintain the information.
We recommend appointing at least one admin per wiki who is responsible for the upkeep and organization of its contents.
Wiki Permissions
Pilot is designed for collaboration and gives you flexibility when it comes to sharing your knowledge with others (both inside and outside of your organization).
We recommend most wikis to be set up with Standard permissions to encourage people to actively contribute to the knowledge base as much as possible.
You have 3 different options that you can combine to cover all different needs:
Standard
Anyone within your Google Workspace account can access your wiki.
Private
Limits access on an “invite only” basis.
Public
Anyone with a link to your wiki can access it.
User Permissions
Of course, not all information should be editable or accessible to all users, and this is where our cascading permissions come in.
Content
When adding content to your wikis we recommend using a similar folder structure for each. This makes it easier to navigate the content in your account, gives people clarity on what they should document, and is more visually pleasing.
Each team could for example have its handbook, OKRs, and a place to document their meetings.
Furthermore, we recommend creating a welcome document for each Wiki. One that explains what can be found in this wiki and has an overview of the most important docs.