5 ms·

No worry it's a perfectly fair point. In our experience, Notion is a great tool and can work within small teams adapted of product and technical people. But th

No worry it's a perfectly fair point. In our experience, Notion is a great tool and can work within small teams adapted of product and technical people. But the complexity of their structure makes it really hard for non technical people to apprehend. Channels make Slite easy to use for anyone in your team. The second thing is that Notion is built like google docs or paper with a loose notion of team : it's an open tool, where permissions can get messy pretty fast. We have teams of 150+ people on Slite for this reason.

ianstormtaylor 9y ago
Do you have any info on what makes the teams concept better than those in Notion / Google Docs / Paper? I also have the vague feeling that those tools have hard to understand team permissions, but I'm unclear on how Slite solves this in a better way. Either way, sounds interesting. Congrats on the launch!
- christophepas 9y ago
  Well the 'team' is actually defined in Slite, while google docs, paper or notion have rights granted on each folder / page / doc for a loose set of people. The easy way to see that is by checking a Google Drive structure : you have "My Drive", then some folders, some shared, some not, and in parallel "Shared with me" gathering documents that can come from outside your team, and that you can also put in "my drive"... It's centered around individuals and weirdly works for them, but is absolutely not suited to organize and retrieve content as a team. Slite actually creates a well defined private space for your team, which makes it possible to share by default. When I update our roadmap or our hiring process, I know all the relevant people can see the channel highlighted, and can get updated. In another tool, the authors would have to push a link by email or irc to get their team updated. And this mereley because they knew that else nobody would see it had changed and nobody could retrieve it in a shared folder structure. Completely side but awesome job on Slate! We have spent a lot of time working on editors, and might switch to it at some point, so keep up the good work!
  - ianstormtaylor 9y ago
    Thanks! Glad to hear it :D happy to answer any questions if you do. That makes sense re: teams, thanks!

ianstormtaylor 9y ago

Do you have any info on what makes the teams concept better than those in Notion / Google Docs / Paper? I also have the vague feeling that those tools have hard to understand team permissions, but I'm unclear on how Slite solves this in a better way. Either way, sounds interesting. Congrats on the launch!

christophepas 9y ago
Well the 'team' is actually defined in Slite, while google docs, paper or notion have rights granted on each folder / page / doc for a loose set of people. The easy way to see that is by checking a Google Drive structure : you have "My Drive", then some folders, some shared, some not, and in parallel "Shared with me" gathering documents that can come from outside your team, and that you can also put in "my drive"... It's centered around individuals and weirdly works for them, but is absolutely not suited to organize and retrieve content as a team. Slite actually creates a well defined private space for your team, which makes it possible to share by default. When I update our roadmap or our hiring process, I know all the relevant people can see the channel highlighted, and can get updated. In another tool, the authors would have to push a link by email or irc to get their team updated. And this mereley because they knew that else nobody would see it had changed and nobody could retrieve it in a shared folder structure. Completely side but awesome job on Slate! We have spent a lot of time working on editors, and might switch to it at some point, so keep up the good work!
- ianstormtaylor 9y ago
  Thanks! Glad to hear it :D happy to answer any questions if you do. That makes sense re: teams, thanks!