News for hackers. Stuff that matters.
Re:Why you should ALWAYS CC someone by philbarr on Wednesday May 09, 2012 @04:49AM (#3947634)
Perhaps, over the last two months you've been running the experiment, you've been thinking about actually wanting a response and have automatically been constructing better emails that people feel they can reply to. Unlike the "brain-dump" ones I sometimes get that just don't deserve a response.

To be perfectly honest, if there's more than one person on the email, I'm more likely to hope it's not my problem...

Re:Why you should ALWAYS CC someone by eric-hu on Wednesday May 09, 2012 @05:37AM (#3947755)
So to design a better controlled experiment, the OP should write a statistically significant number of emails (>100...maybe 1000+) without sending them. An app should perform a double-blind study by randomly choosing half those emails to go to multiple recipients (all but one being fake) and choosing the other half to go to one recipient only.

Anyone see any holes in this approach?

Re:Why you should ALWAYS CC someone by mcherm on Wednesday May 09, 2012 @06:26AM (#3947871)
"without sending them" is unnecessary. Modify your email client to randomly choose (AFTER you write your email) whether or not to CC Alex. Or just flip a coin after writing it and before hitting send.
Re:Why you should ALWAYS CC someone by Tyrannosaurs on Wednesday May 09, 2012 @06:20AM (#3947856)
How about the idea of writing 100+ e-mails without sending them?

You'd be better off having a mail plug-in randomly selected whether to add a cc at the time of sending rather than hoarding them.

Your mechanism is valid as a trial but not particularly workable in the real world.

You might want to also control for factors such whether the mail is internal or external (assuming it's a company), message length (longer messages might be more or less likely to be properly read and responded to), message importance (you'd expect more replies to higher importance messages), attachments and so on.

Re:Why you should ALWAYS CC someone by dcminter on Wednesday May 09, 2012 @05:29AM (#3947730)
Ack. Always address one of the recipients by name in the body of the email to ensure that it's not SEP'ed.
Re:Why you should ALWAYS CC someone by adityar on Wednesday May 09, 2012 @05:31AM (#3947737)
isn't there a name for that? something like diffusion of responsibility. the same reason we don't help one person in trouble when there's more than one potential helper...
Re:Why you should ALWAYS CC someone by ackien on Wednesday May 09, 2012 @05:45AM (#3947782)
The bystander effect/Genovese syndrome: http://en.wikipedia.org/wiki/Bystander_effect

Perhaps the effect is quite different when there is just one other bystander, as opposed to a whole crowd of them.

Re:Why you should ALWAYS CC someone by ekanes on Wednesday May 09, 2012 @06:58AM (#3947955)
Yes, but there's a critical difference. In this case there's a clear recipient - someone asked to do something/reply. In the case of the Genovese effect, no-one is specifically asked to do anything, and no-one does.
Re:Why you should ALWAYS CC someone by lunchbox on Wednesday May 09, 2012 @06:23AM (#3947865)
Re:Why you should ALWAYS CC someone by smanek on Wednesday May 09, 2012 @05:45AM (#3947779)
Re:Why you should ALWAYS CC someone by philbarr on Wednesday May 09, 2012 @05:36AM (#3947753)
Re:Why you should ALWAYS CC someone by dsirijus on Wednesday May 09, 2012 @05:43AM (#3947774)
But this technically isn't diffusion. It's concentration of responsibility.
Re:Why you should ALWAYS CC someone by dsirijus on Wednesday May 09, 2012 @04:52AM (#3947641)
Well, I've always tried to construct my e-mails to the best of my ability. I didn't noticed any change in my content - it has all been pretty standard.
Re:Why you should ALWAYS CC someone by tg3 on Wednesday May 09, 2012 @09:02AM (#3948317)
Unfortunately you not noticing any change in the content doesn't make for very reliable or convincing statistical results. Thus the suggestions for making the experiment blind to you by choosing whether or not to CC after you compose the email.