(Apologies if this has already been suggested, I couldn’t find a similar one).
I’d like to propose a small (hopefully) change that could significantly improve the Threads UX for us and, maybe, for everyone.
Current workflow:
Go to a space → Click "New" → Select "View/Thread" → Search for the right entity among thousands → Name the thread
Result: A new redundant view is created in the space, along with a thread in the Threads section.
That’s five steps just to start a conversation. It’s a lot of friction.
Proposed Workflow:
Right-click any entity with comments → Click "Pin as Thread" or "Create Thread"
Result: A thread is created with the entity’s name as the default title (editable).
That’s just two steps. Or even one, if the entity is already selected, which is the most common use case. Someone is reviewing an entity and decides to start a discussion. That moment should be seamless.
In our experience, this friction is a major reason why Threads aren’t used more often. It takes too much effort to initiate one.
This change would make it easy to spin up a lightweight, contextual discussion and close it once it’s no longer relevant.
Bonus idea: let the thread be visible only to participants - anyone who commented or was mentioned (to keep things focused and clean).
It is same way it works now but with Pin thread it would create thread named same as Entity and then if would appear inside Threads and as Thread itself and then you could move it anywhere you want. This just makes sense to me.
This would have to be solved by fixing thread permissions. Now when you invite observer they can see all the threads ever created and it goes same for members I think. Also you can mention anyone inside whole workspace as observer without any entity or space permission.
It could stay the same as now - under the Threads top section. No need to show the thread view specifically, just a thread channel is enough. Threads are for easy to access discussions.
Also it could be closed same way as now - right-click on a thread and click Delete.
Not necessarily.
Potentially, the visibility of a Thread could be determined by whether or not the person is watching the entity that the thread belongs to.
This solution could stay outside of permissions. Just the “default visibility”. Anyone could still join the thread, but it’s visible to comments participants only by default.
I think this is what I’m unclear on. The ways to view discussions (comments on an entity) right now are in a thread view, or in the comments field of the entity. How would a “thread channel” be different, as it sounds like you are still talking about threads consisting of the comments from an entity? (or by “thread channel” are you referring to the “Threads” top level section in the sidebar?)
Sorry for the confusion. Yes, I’m talking about “Threads” top level section in sidebar. IMO threads are for easy-access communication and no explicit thread view in a space is needed. Nevertheless I understand that it might be useful to have thread views, but in most cases IMO “Threads” top level section is the way to go.
Currently, most of our used threads are thread views in spaces. They are used as general conversation for each department. Perhaps this might change if threads ever move on from being experimental. But in this way they have replaced our need for Slack. I actually don’t know of anyone in our org, other than myself, who uses the Threads section (almost everyone has left the threads feature off but can still see and use any thread views that have been made in their spaces).