Notion - Powering Wikis and SoPs
Use Cases and Deployment Scope
We leverage Notion as an internal Wiki and to centrally manage all of our SoPs. We had previously used it as a broader productivity and communications platform within our organization but found that it was almost too flexible. Pairing it back to be our Wiki and hub for SoPs has helped keep everything centralized. It's easy for the team to manage and edit.
Pros
- Internal Wiki
- Managing internal documentation
- Drag and drop experience
- Easy to use
Cons
- It's almost too flexible at times
- More controls to restrict how pages / content / dashboards can be structured
Likelihood to Recommend
We originally implemented Notion with the intention that it would be our "everything platform" because of its flexibility. We did however end up finding out that there is such a thing as having too much flexibility as it quickly became a wild hub of different dashboards, pages, templates, etc. In the end we paired back our usage and focused on using Notion as a Wiki and hub for all of our SoPs (Standard Operating Procedures) for this it has been very valuable. Its easy for the team to create and update this content while maintaining a consistent look and feel. The content is also easily searchable and now that we have defined uses we have created a good library of templates.
