Response Rights – Outbound messages vs. inbound responses / commenting on posts
planned
B
Ben Grynol
Ability for a sender to create "response rights" on a message
As a example, if we had 1,000 people and a Head of People wanted to send out a transactional message about a company event in a "General" group
In this case, they might only want to transmit information and aren't looking for additional input from the team – (information doesn't need to be transformed about an event announcement)
The sender wants to minimize downstream distraction for the team by turning off "Response rights" so that the thread isn't open for commenting from the entire team
ie- it's highly distracting and causes communication noise / overhead when hundreds of people can comment on a transactional message that doesn't need N+1 input
- "can't wait for the event"
- "it's going to be fun"
- "going to be late"
- etc....
S
Sam Corcos
planned
B
Ben Grynol
Another sub-feature of this could be where a person could "Request rights" to comment and the sender would receive a notification that they would approve / reject
The hypothesis is that "commenters" wouldn't request rights if they didn't have something valuable to add to a thread
An example where this feature would help is this thread which was informational to inform the team about a Phishing scheme
There are 9 "noise" comments on the thread as of 4pm on 6/6, and none of the comments added value to the thread, but distracted team members by receiving more "information to process" in their inboxes
If the thread was sent as being "closed for commenting" off the hop, it would have minimized distraction for everyone who keeps getting notified every time someone adds to the thread (assuming none of the participants who initially received the thread changed their subscription settings specifically for the thread)