in reply to Email subject lines should be written:

Am I the only one that agonizes over subject line wording and content long after having finished writing the e-mail itself?

Especially when you're sending to a diverse group of recipients. You've got to make sure that everyone grasps the gist of the mail no matter their perspective or role.

On a related note, I've seen some just blindingly awful post titles in Seekers of Perl Wisdom. I'm thinking that writing those uses a similar set of rules =P

Composing good subject lines is an art, imo.

Strange things are afoot at the Circle-K.

  • Comment on Re: Email subject lines should be written:

Replies are listed 'Best First'.
Re^2: Email subject lines should be written:
by FloydATC (Deacon) on Sep 20, 2012 at 18:28 UTC
    Same here. I work in an environment where I often have to reply to technical questions with lots of internal and external people already cc'ed, people often possessing... uhm... different skill sets. (Those skill sets may in certain cases overlap very poorly with what that person might have found useful in his or her work)

    You don't want to be too technical but you don't want to skip over important details and you certainly don't want to come off as patronizing even though everyone knows atleast one person on the cc list won't even understand what the email is about in the first place.

    -- Time flies when you don't know what you're doing