> "Asana looks like it is made for complex projects run in a particular way with lots of information density, but introduces too many concepts and lays them out too haphazardly to be useful for casual projects or casual usage. "
This feels very true to me. A big part of becoming effective with Asana for us was deciding which concepts to use, and how (like: decide what are sections for, and stick to it), which we don't (like conversations).
This feels very true to me. A big part of becoming effective with Asana for us was deciding which concepts to use, and how (like: decide what are sections for, and stick to it), which we don't (like conversations).