My Photo

Enter your email address:

Delivered by FeedBurner

Facebook

Support the Sharing Foundation

Creative Commons

May 2008

Sun Mon Tue Wed Thu Fri Sat
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

Beth's Blog: Flickr Photos


  • www.flickr.com
    This is a Flickr badge showing public photos from cambodia4kidsorg. Make your own badge here.

Beth's Blog: Channels, Screencasts, and Videos

Site Tracking




  • This is my Google PageRank™ - SmE Rank free service Powered by Scriptme


Categories

« Wikis for Curriculum Development and Instructional Materials | Main | I'm on Facebook, Now What? Book Giveaway (Give it to your Executive Director) »

The Urge To Edit Someone Else's Blogging or Social Networking Policy Is Irresistible


Photo by Nic's Events

I put out a query for examples of blogging and social network/media policies for nonprofits and got lots of good examples.    Donny Peterson couldn't resist the urge to edit someone else's blogging policy before sharing a copy his policy. That got me thinking about the process for developing the policy.   And, do all organizations with blog need a policy? 

  • How do you determine when a nonprofit blogging policy is needed?
  • How do organizations create policies?

Here's a story from behind the firewall of a large nonprofit organization - the names and particulars have been changed - but here's how the blogging process unfolded:

As the organization's blogger,  I facilitated creating the policy. There was/is a lot of fear about encouraging the use of social media in our ranks, so it seemed like a doable first step. Laying down rules makes everyone think they have more control and it helped everyone to feel better. My ulterior motive was to send the message that using social media is ok and even good for our institution. The more we tell our story, the more the public can understand our mission.

In truth, the policy (a term I'm discouraged from using since we can't really create a policy about what employees do or say on their own time - we use "guidelines") is quite vague. It goes on for a while but really just says, "Use common sense and please don't say stupid stuff. In fact, we'd love it if you told your personal institutional story in a constructive way."

To my knowledge, no one had ever told employees that they were allowed to talk about their job before. I think many were even scared to do it. Since we often operate in sensitive areas, most rules prohibit discussing specific client relations, etc. This opened the door for more transparency and handed more control of the message over to the employees and volunteers the organization belongs to.

I draft the policy and then it got handed around to pretty much all our many employees for edits and approval. It was about a 6 month process to getting it approved and distributed

So, is a blogging or social networking/media policy just a matter of cut and paste and edit similar web site policies,  accepted use policies, and other types of technology related internal policies?  Or is there a value in having the discussion?

Update: 4/12  More from Beth Dunn

Update 4/16  Blue Avocado (and some summaries here)

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/t/trackback/15140/28014542

Listed below are links to weblogs that reference The Urge To Edit Someone Else's Blogging or Social Networking Policy Is Irresistible :

Comments

It seems to me that if we are leasing a house, we go out and get a standard legal form and then add, edit or omit as we see fit. Rather than re-invent the wheel, a Social Networking Policy can be generalized to function across many cultures and contexts too. There are some other items that might go on my policy, but i think in general this version is fine. Plus, I can't imagine waiting 6 months to implement something so presently needed.

That being said, if you are a believer in Socio-Cognitive Learning theory, discussion is ALWAYS important. Discussing IS learning; and that is a quality of existence and benefit we ought not ever compromise; especially if it can lead to assuaging fears that arise when orgs adopt new technologies.

Post a comment

If you have a TypeKey or TypePad account, please Sign In