4 ms·
Looking at this page, https://slite.com/use-cases https://slite.com/use-cases, I feel like this kind of product is an anti-pattern. The reason that it's hard t
by tarr11 9y ago
Looking at this page, https://slite.com/use-cases https://slite.com/use-cases, I feel like this kind of product is an anti-pattern. The reason that it's hard to find things in slack or docs is because these apps do not well understand the underlying structure of the data and so are relegated to either full-text search, or some sort of naive clustering algorithm. Although Slack has made some advances here - such as adding context-specific buttons for actions.
Will Slite do a better job at understanding our bug reports than Github? Or understanding our applicant tracking system then Greenhouse? Our customer support than Zendesk? Every one of these tools have a search feature.
The value of Google Docs is that it stays out of my way, lets me create freeform notes, and integrates with the rest of Google. Probably the same for Paper, or any other team notes solution. Once something gets complex enough, creates work for teams, or is mission critical, it either needs to be actively managed by a team member, or move into an automated tool that does that management for us. I can't imagine the solution would be to centralize all these disparate workflows in a tool like this.
- christophepas 9y agoThat's a super interesting point and I fully agree those examples are not well suited for all teams, especially not for larger ones. I still think having all the information compartmentalized is a waste of time. The integrations that we are developing aim at solving this : Slite will integrate with your github documentation and your Greenhouse pipe so that the members that need the information but don't use the tool everyday (typical in an hiring process) can see the information while those whom it's the job will keep using it as usual.