| I've used this workflow, and it's generally terrible. There's so many repositories of information that the definitions of what goes where become nebulous and subjective. E.g. does an architecture diagram for an app go in the team-scoped file store so it can be live edited during architecture discussions, or does it go in the KB store because it is meta information in a way, or does it go in the task manager because that architecture is an artifact of some actual work? I could see valid arguments for any of the 3. My experience is that things become better by using fewer tools, even if that means the chosen tool is somewhat less well suited than a more specialized tool. E.g. I would replace the team-scoped file store and the KB store with a git repo. It's not as good, but it's good enough, and one less place to search. A company should use either chat or email, but not both (both is fine as long as it's explicit that email exists largely for HR to mass-email people and to get calendar events). That cuts it down to a file store/KB, a digital communication method, a task manager, and in-person events. Removing potential duplicate use cases makes it much harder to use the wrong tool for a particular thing. Nothing but the KB is suitable for storing documentation. Nothing but the task manager is suitable for organizing work. I think some of these features just aren't worth the overhead of having another location to search through. Live editing is neat, but I'd happily get rid of it to not have to search through another data source. |