4 ms·
I building an microblogging tool for company internal communication. One thought I had, was, enforcing a delay for every message written. But I don't know if
by k__ 5y ago
I building an microblogging tool for company internal communication.
One thought I had, was, enforcing a delay for every message written.
But I don't know if I choose one or ten minutes, or if it's a good idea at all.
Or if I should just impose a fequency, like times a day new messages, etc
The idea I had was something like in the "Do nothing" article here.
People could write messages and might even delete them a few minutes later, because they solved themselves.
Also, it would remove "emergencies" communication from the timelines.
- mauli 5y agoNice idea coming to my mind reading your problem: time based growing circle visibility The person's close cycle is seeing the post first, then his team, then sub-org, until everyone has it on the news feed. Poster can choose to pause/stop the growth. Peiple getting the link are able to view all details, but do not immidiatelly have it on their timeline.
- sovietmudkipz 5y agoI like this idea. It maps nicely to the concept of ‘andon cord’ applied to software engineering. If an engineer has an issue, pull the cord to broadcast to someone on your team. Then your entire team. Then a sister team. Then eventually to everyone in your org. Maybe even the initial message only gets sent out after a reasonable amount of minutes, in case the engineer wants to rescind the call for help.
- k__ 5y agoInteresting idea. Thanks for the input!