Taking jokes, just one subset of such emails, as an example: For you, a particular joke may be a waste, but having the team culture be such that it is open to jokes, may provide benefits beyond each individual joke.
Still, great idea, and maybe the objections I raise could be overcome just by the right wording.
Some of the 'send to all' emails were pretty important, so I had to read them, but a lot of them added nothing, and were sent to 400'000 people. I think each inappropriate global send to all cost $1000+, assuming people disgarded it pretty quickly.
+Low estimate, assuming it takes 1 second to disgard the email, everyone reads it, and gets paid minimum wage.
This program posts news to thousands of machines throughout the entire civilized world. You message will cost the net hundreds if not thousands of dollars to send everywhere. Please be sure you know what you are doing.
Ah the old days.....
Was there a time when this was actually true?
This in itself could be a nice plugin for your mail. You need 3 values to be able to calculate it:
* Number of employees the mail will be sent to (hard with aliases, easier with Outlook PDLs)
* Average fully burdened cost of employees (managers should know this, or you can default to something like $120K)
* Estimated time to read (based on wordcount and an average reading speed)
From there you can get the "hours wasted reading this mail" and "cost of this email".
EDIT: You could go above and beyond and use an open rate percentage to more accurately determine the cost, but that's not something an email client could record, it'd be server side.
The second problem is that there are managers who do send out de facto spam and probably could use the feedback.
Are you kidding? That's the whole point!
Presumably, the boss allowing it in the first place is a signal that they're interested in this feedback from their employees.
1. Non-optional delivery/read receipts Various clients have these, but it would be nice if these were universally supported and could be made non optional. This is useful so that when I don't get a response and have to go hound someone, my first question doesn't always have to be "Hey, did you get that E-mail??"
Speaking of responses...
2. Response required flag Be able to mark an E-mail as requiring a response from a specific recipient. Such E-mails could be presented differently in the recipient's client, highlighted or called out in a different color. Client software could generate a TODO list out of them, issue reminders if the E-mail has been un-replied-to for more than some configurable period of time, etc. The longer the message is ignored, the more annoying the presentation might be. This highlighting could be silenced by either a. replying to the E-mail, or b. clicking an "ignore" button (which also sends notice of the ignore action back to the sender). The sender could also cancel the flag after the message is sent.
3. Response required by date As an enhancement to the above, instead of a flag, a date/time by which a response is needed. This could allow the recipient's client software to display these E-mails in a sane priority order.
- A variation: to have emails you want to send go in a pending pool moderated by a team of trusted confidants, to avoid sending out email that is a waste of time.
I agree trusted confidants is an improvement, but probably not enough on its own.
With these metrics it could then work out which members of the company send out the least well received emails. There are certainly some people where I work who have a very low interesting email ratio. These people would be prompted to sort this out.
One risk would be the employee that just sends out jokes would of course appear to be highly effective. Some algorithms would be needed to filter out work vs play emails.
To creep employees out, these metrics could be readily available to management and used in their performance reviews as part of all the other data obtained about them!
That would make total sense as a sideline for somebody like mailchimp.
I think one of the reasons why no one's ever done this is that with traditional email, it's impossible for the sender to know how many people one email has reached, or will reach. But I think Threadable (recent YC startup) could actually do this.
Check it out!
Edit: As I've said in the past when posting ideas on HN, if you think this is worth doing, please run with it! I make no claim on "owning" the idea, and all I ask is that if it makes you a billionaire, you commission of bust of me to install in your parlor. (Bronze or marble only, please.)