Cover letter:

(Insert name of CEO and other company executives)

I’m contacting you in regards to a proposal I think would greatly benefit the company (see attached proposal).

I’ve recently found employee blogging to be a source of contention in your company. I think working together to correct this situation before it gets out of hand is the best solution for all parties.

Please take the time to read the attached info. I’m asking if you would please pass this info on to anyone you feel could help the cause. I’ve also sent this to the corporate offices as well as the main human resource department.

Your time is appreciated. Please feel free to contact me at any time with questions or concerns you may have.

Thank you,

Sarah Nielson

Problem Defined:

Due to recent events taking place within your company and its non-existent blogging policies I, an employee on your staff, have been asked to stop blogging without a company policy stating why this should be considered unethical behavior.

You, as a corporate company, should have policies in place before coming to me with such a request. I’ve never signed any documents stating I will not blog on my personal time, nor have I been provided with a company handbook stating this is unethical behavior.

In order to ask an employee to stop blogging on their personal time, I feel you should be able to come to them with evidence why they should do so.

Alternative course of action:

If the following aren’t in breach then please consider refraining from making blogging a “company” issue:

Intellectual Properties are not revealed.

Confidential and proprietary information not revealed.

Company name not revealed.

Company location not revealed.

Co-worker names not revealed.

Blogs written on personal time, not company time.

Take into consideration some public companies have embraced blogging with certain limitations, i.e. IBM. Here is their current policy:

1. Know and follow IBM's Business Conduct Guidelines.

2. Blogs, wikis and other forms of online discourse are individual interactions, not corporate communications. IBMers are personally responsible for their posts. Be mindful that what you write will be public for a long time—protect your privacy.

3. Identify yourself – name and, when relevant, role at IBM – when you blog about IBM or IBM-related matters. And write in the first person. You must make it clear that you are speaking for yourself and not on behalf of IBM.

4. If you publish a blog or post to a blog outside of IBM and it has something to do with work you do or subjects associated with IBM, use a disclaimer such as this: “The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions.”

5. Respect copyright, fair use and financial disclosure laws.

6. Don’t provide IBM’s or another’s confidential or other proprietary information. Ask permission to publish or report on conversations that are meant to be private or internal to IBM.

7. Don't cite or reference clients, partners or suppliers without their approval.

8. Respect your audience. Don't use ethnic slurs, personal insults, obscenity, etc., and show proper consideration for others' privacy and for topics that may be considered objectionable or inflammatory – such as politics and religion.

9. Find out whom else is blogging on the topic, and cite them.

10. Don't pick fights, be the first to correct your own mistakes, and don't alter previous posts without indicating that you have done so.

11. Try to add value. Provide worthwhile information and perspective.

Proposed course of action:

1. Put into place company policies defining what is allowed and what isn’t when it comes to personal weblogging.

2. Add addendum to employee contracts regarding weblogging.

3. Add section to company handbook stating what weblogging practices are expected from employees.

4. Consider adding a section to the Non-Disclosure agreement defining what can be discussed about the company.

Works cited:

http://www.ibm.com/blogs/zz/en/guidelines.html

http://www.michaelhanscom.com/eclecticism/2003/10/23/even-microsoft-wants-g5s