Global Threads View Option
- Matt Birtch
We tested a number of options for a Global Threads solution where users could collect threads that are important to them.
Status | Decided |
|---|---|
Impact | High / Medium / Low |
Driver | @Matt Birtch |
Approver |
|
Contributors | |
Informed |
|
Due date | |
Outcome | Option 4: Inbox-style global threads view |
Options considered
| Option 1 | Option 2 | Option 3 | Option 4 |
|---|---|---|---|---|
Description | Utilizing the RHS to show a list of global threads - access to this via a new threads icon in the top right corner | A global threads ‘channel’ view that displayed truncated threads, but occupying the full-width | A slack-style threads ‘channel’ with inline replying and a linear list of all relevant threads | An inbox-style list with summary view of relevant threads |
Results | Users found this to be asking a lot of the real estate in the RHS Users assumed that the threads were contextual to the channel they were viewing | Many felt it wasn’t a great use of the real estate available | Users found this view not very ‘consumable’ Users pointed out their frustration with Slack’s approach Messages often got missed because as soon as users enter the Global Threads view, all messages in the view are marked as read | Users found this easiest to consume large amounts of information more quickly It felt somewhat familiar with other software Mental model users have |
Outcome
The inbox-style view offered users the best ability to consume their threads and felt like the right model for a place to ‘collect’ threads they follow.