Some UX improvement for starting chat threads - Create a subject
R
R C
Hey guys!
I think you are actually very close already with the existing functionality that each chat is its own subject. Your structure of chats belonging to each relevant Space, Folder, or list means that when they are initiated, you have good confidence they are in the right context.
One thing though is that I've found the UX is a little awkward. It's not clear that the chat is its own subject, but in effect it behaves like that.
My team uses a chat app Twist that does this well:
This way of starting the chat prompts the user to write down what they want to talk about, and the others in the team can simply add in their comments. At the end in Twist, it's resolved by another comment saying how it was resolved. This concept could work beautifully in ClickUp if you had the ability to convert this to a task or list to allow even further work and evolution. Great for ideation that leads to real work and deployed features!
I think this would be a great solution to some of the discussion here:
Thanks guys!
Log In
Waleed Elaghil
Hey R C! Thanks for the detailed feedback 🙂
I'll definitely discuss this with the team.
Can you provide more context about how you and your team use the ClickUp's Chat view?
Thanks!
R
R C
Waleed Elaghil: Waleed, good to hear from you on this!
Yes, no problem:
We are using Chats right now just as we would in Twist or Asana, the other two tools we like that have "rounded out" this feature:
- You can create a subject and content, like in Email. So if you want to, say, write a general update about a Project that's in a list. Or some general comment about "Finance," that might be a folder. Possibly ask a question as well around some content that's in a List or Folder.
- The ability to force a comment on "close" also makes sure you have assurance that the Chat is "completed." You can then come back and see what a decision was about, that you used the Chat for, for example (Decisions are also a good use of this feature).
I would propose you make the "forced comment on close" I just described optional, as some teams may not want to use that
Right now, this is somewhat awkward as Chats don't start out with you being prompted to enter a topic of the Chat. They just start up with the subject "Chat"
Then, the threads are all the same. I think it would be better - and this is what Asana and Twist do - if the initial comment, that's associated with that topic - stood out. The threads would just be responses to that. Very similar to how Email works, and a big reason why I think you could legitimately propose teams exit Email with this function more polished.
Hope that was what you were looking for, thanks for the interest! Would really love to see you guys make this happen!
P
Patrick Fallon
R C: a thought on this in terms of implementation in the current incarnation of ClickUp...it would be super helpful if, when you add a comment in Chat View and link it to a specific task, that all the comments that are linked to that task actually show up in the comments section of the task view. Because Chat View is associated with a Task List and all comments are created equal, you can't really have a Chat View that is spefically targeted on one sub-task list topic except by renaming the Chat View based on the topic you want to discuss. I guess that would be the way to do it and then add more Chat Views to that Task List for each new topic you want to discuss.
Bill
Another good example of this is how Asana does it:
They make a big claim that you can eliminate internal Email via their Conversations tool. I think with this additional feature in Chats, we would get very close to having the same huge benefit in ClickUp!