2016-01-19: Updated with some corrections. Strikeouts indicated former erroneous material now amended or deleted, and italics show new explanations.
I’ve been closely watching the development of work chat vendor Fleep, and since I reviewed the product in August (see Work chat tool Fleep has native task management: Is that a key feature, or just nice to have?) the company has addressed so many areas I won’t try to cover them all, I’ll let them do that for you.
I am just going to focus on the slash commands, tasks, and email integration.
Slash commands — Fleep’s chat (or ‘conversations’ as they call them), support a number of commands that are preceded by a slash (‘/’):
/pin <message> — create a new pinned message
/task <message> — create a new task message
/taskto @someone — create and assign a new task
/bug <message> — create a new bug report task with ((bug))
/add <email> — add new members to the conversation
/kick <email> — remove members from the conversation
/leave — leave conversation
When these are used in the context of a chat, when a chat message with a leading command is posted, the action is taken. In the screenshot below, I have just invited Doppelganger Jones to the AdjectiveNoun conversation, assigned him a task ‘please write up a plan’, and I have formed a new chat message at the bottom to create a second task also assigned to him.
Here’s the task pane opened after those tasks were created.
One of the weaknesses of Fleep’s task model is that the tasks have very little metadata. I can understand why they might not need comments or notes — it’s a chat app, after all — but due dates are fairly essential.
Tasks are completed by checking the task box. I found it odd that pinning a task — which moves a message to the top of the chat window and stops it from scrolling away — leads to the task losing its ‘taskness’: it becomes just another message. Odd.
Documents can be added to the conversation — including Google and Dropbox docs —
but these aren’t attached to messages or tasks: they’re just dropped into the chat. And one or more documents/files can be added to messages or tasks.
Once added, they also show up in the ‘Files’ pane, the one with the paperclip icon.
Personally, I might have designed them to do both. That limitation seems particularly irksome with tasks.
It’s great that Fleep tasks (and messages) can have attachments, since passing along a description of the work to be done, or a document to be approved are commonplace activities.
Also note in this case I was trying to attach a Google doc, but somehow Fleep instead creates and attaches a PDF of the doc. So my colleagues on Fleep can’t use this as a way to open and coedit the Google doc, but just to look at an immediately out-of-date pdf of the doc. This is dumb. If I were actually using Fleep in production I would copy and paste URLs to docs, instead. And Fleep provides a text markup for that, in this form:
link<<text>> — adds an inline link with the text in the angled brackets
And that works really well, in fact:
Clicking on the preview or the
URL link opens the Google doc, and since I copied a share URL that allows for editing, my colleagues would be able to view, comment, and or edit the Google doc, in place.
Returning to tasks, the task pane can include ‘sections’ that can be used to arrange tasks into subsets.
I like the capability to layout the sections in this way
, and when coupled with the ability to ‘clone’ conversations, teams could create and reuse project templates to help regularize the work in project conversations. Too bad that the ‘clone’ function for projects only copies the set of contributors, and doesn’t include — for example — the tasks defined in the conversation. If it did, teams could create and reuse project templates to help regularize the work in project conversations. Alas, not today.
Fleep now supports [email protected], so that I can alert others to messages, like ‘Can someone take a look at the timeline in this doc to check it’s up to date? https://docs.google.com/document/d/1bwF55zWtnJOtUsDheIoRgwmC7Geq7ZVcT9Ho-UYnd3w/edit?usp=sharing<<Report>> @doppelganger.jones’.
Note that the user identity in Fleep for Fleep users is an email address:
This is by design. Fleep is tightly integrated with email, so that non-Fleep users can be invited to conversations simply by adding their email. If they aren’t a Fleep user, they can participate through email. This leads to all messages — including tasks — being sent to them, and their responses showing up in the conversation. Emailed tasks just look like messages at present, so email only participants can’t check them off, for example.
More importantly to me is that emails directed to Fleep aren’t treated as tasks but as messages, although they can be converted to tasks. And the model is that a new conversation is created with the other person for these emails. There is no way to direct them to an existing conversation. That’s a different slant than I am used to, from tools like Todoist.
I have not touched on all features of the tool, but probably enough to get a sense for what using it feels like. Fleep is at core, a classic work chat tool, based on contextual conversation (see Contextual conversation: Work chat will dominate collaboration). Unlike leading competitors, however, Fleep has integrated task management.
At the same time, the limits on Fleep’s task model would chafe anyone who believes that richer capabilities are essential — like multiple assignment, subtasks, due dates, start dates, notes, comments, attachments, and so on. However, the fact that tasks and other messages can be brought back into context when looking at a task by selecting ‘show in conversation’ does counter some of the issues with notes, comments, and attachments, so long as they are in fact truly contextualized.
I hacked a link from a task to a day on my Google Calendar to represent a due date, but that just indicates the direction they might take if they start thinking about due dates and calendar integration. Here’s the edit for the task:
This manual approach is just too much work, although I certainly could get the first order benefits simply by putting the due date in the text of a task.
Obviously, I’d rather have a calendar integration so that tasks with due dates would automatically show on my Google Calendar, and so would anyone else, I bet.
If the team at Fleep continue their development at the breakneck pace of 2015, they may in fact be countering some of these issues, and their focus on integration with a wide spectrum of developer tools seems to represent the same arc of adoption that we saw first with Hipchat, and later with Slack. We should anticipate the same disperal pattern, where the developers in a company infect non-developers with the ease of use and depth of the developers’ work chat platform, and they in turn begin to infect other non-developers across the company and the company’s ecosystem.