3 ms·
Liked the article but it produced a weird dissonance in me. On the one hand I totally empathized with his frustration/excitement at building a cool bit of softw
by larksimian 11y ago
Liked the article but it produced a weird dissonance in me. On the one hand I totally empathized with his frustration/excitement at building a cool bit of software for himself. On the other hand I've never had problems managing my email inbox, mainly because I don't get that much relevant email.
In particular, since the Gmail tab redesign I've not had an issue keeping my Inbox unread count at 0(though with my Promotions/Updates/Forums tab unread count in the who-knows-how-manies). I guess this confirms his point about email protocols being dinosaurs, since the way Gmail implements its tabs is tied into their client implementations and doesn't work in other email clients.
The overall impression I ended up with was that Slate is simply using email for workflows it was never meant to support and is not very good at supporting. Email chains are not a good way to do project management/planning. It's good that they've started using Slack for chat-like communication. They should adopt some sort of project management app to manage projects. If you've got a user that's used to Gmail, they can learn Trello, for instance, in about an hour.
I tend to think about 3 levels of communication: chatting(text, audio, video); email; project related. Each level requiring additional structure and being a bit more cumbersome to use than the last when writing, but easier to use when reading/searching for information.
In that sense it makes sense to use 3 (sets of) tools for 3 different types of communication. The main downside is that it's somewhat complicated to transfer a conversation from one channel to another. However doing all 3 in one application leads to the risk of making a simple use case too complicated or a complicated use case impossible.
The ideal integrated communication app would need to provide IRC-like chat power, Hangouts/Skype like chat simplicity(+audio/video support), Gmail like email usability and auto filtering, and more than Trello-like project management/collaboration tools(for instance, having Google Doc-style shared documents properly integrated into it). All usable in interfaces designed for the particular level of communication you are engaging it at the time, but allowing you to move 'threads' of conversation up or down the hierarchy easily. I've not encountered anything that does this right. Heck just being able to properly integrate Gmail, hangouts chats and google docs/google doc comments between each other isn't possible and all those are made by the same company.
- tmail21 11y agoI like the way you imagine 3 levels of communication, viz. chatting, email and project related. However, I think the jump from email to project-related is too large. The amount of ceremony required for project tools is too high relative to email. In particular, these tools are based on static 'groups' or 'teams' and hence are nothing like email's per-message variation in users. Furthermore they are based on asymmetric permissions (owner vs. non-owner) which leads to an entirely different set of dynamics. I think a level between email and projects can bring a lot of benefits the author is looking for with only a modest increase in cognitive overhead. In this approach, there would be a first-class entity at the thread-level. So, the entire Discussion would be a first class entity. This solves a lot of the author's problems. You don't have random stuff showing up and disappearing from threads (based on Subject and based on whether you happened to be copied or not). Threads could easily have tracking numbers which would open up email to the 'outside world'. Also, once one has a first-class thread, one could associate append-only updateable content sections. This would be like attachments but without the versioning problems. In fact it would be easy to build a lightweight process framework, with tasks etc. on such a foundation. Disclaimer: Our company (https://tmail21.com https://tmail21.com) has built just such a system. It adds a first class entity at the thread level (which we call a TMail). It allows users to start with Simple Topic-Oriented Discussions and from there progress to Goal-oriented Discussions and from there to Lean Processes. Take a look and let us know what you think.