20110720 fose 2011 sm governance

3,022 views
2,998 views

Published on

This workshop delivered July 20, 2011 at FOSE 2011 described the elements of a social media governance framework, identified structural and policy statements to include in the social media policy, and describes strategies for capturing and managing social media-generated content as records.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,022
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
24
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The first step many organizations take to manage Web 2.0 is to try to block them. This is unrealistic for a number of reasons.
  • Moving into mainstream
  • Technology changes much faster than the law or policies can keep up with. That’s why it’s better to use a comprehensive policy that can cover new technologies as they appear.
  • Here’s Best Buy’s policy. There is a little more to it, but fundamentally this is it. And while it doesn’t cover records management, compliance, etc., if your employees embrace it (and are trained on how it applies) it will cover the vast majority of issues found in much more detailed policies. http://www.bby.com/2010/01/20/best-buy-social-media-guidelines/
  • Zappos is a $1b clothing and shoe retailer – and their Twitter policy is only 7 words.
  • Here’s a very succinct Twitter policy from a blog by an HR-focused law firm, GruntledEmployees.com. “Our Twitter policy: Be professional, kind, discreet, authentic. Represent us well. Remember that you can’t control it once you hit “update.””
  • Official vs. unofficial includesDisclaimers (this is or is not official; disclaimer of responsibility if it isn’t)Also includes a link to his social media policy
  • Whether approval is required to create an account (official only)It’s also useful, as CSU does, to list all the official accounts somewhere on the website.
  • This includes things like:What user names are appropriate, and whether to use the organization as part of it (e.g. Dell_JeffW)Pictures – same thingBio – same thing, plus things like official account, name (and sometimes personal Twitter handle) of the person behind the account, etc. Different types of contact informationIt’s also valuable to have guidelines for what types of contacts are appropriate. An official federal government account could “friend” Barack Obama on Twitter, but probably shouldn’t friend his re-election campaign or the Democratic Party (and even if it did the Republican Party as well, it’s still problematic). Similarly, it might look a bit odd for an energy company account to “friend” a parody account like BPGlobalPR, or a competitor, or an unsavory group, etc.
  • Pretty straightforward here. Three main points:If third party content is allowed, it should be reviewed so people don’t upload pornography, etc. If it is reviewed, the organization may have some responsibility to remove things that are inappropriate. This should be spelled out clearly and adhered to rigorously – all goes back to transparency. If an official account “likes” something on Facebook, or retweets something on Twitter, this could be considered approval or even recommendation – and if it’s something offensive, or illegal, or otherwise inappropriate, this could cause serious issues.
  • The policy should outline what types of groups are appropriate and what types of groups should be out of bounds. This is especially important for official commercial accounts but could be applicable even to personal accounts where the connection could be made to the organization because of the employee’s visibility. For example, it would be inappropriate for an official in charge of elections to be a member of a Facebook group focused on reelecting one candidate or another. Moreover, there are any number of groups dedicated to patently offensive or illegal causes; having accounts associated with these types of groups could bring significant risk to the organization and its brand. ~Another related area involves conveying a perception of approval of content that might be controversial, offensive, or illegal. For example, both a Facebook “like” and retweeting content on Twitter are often perceived as approval of that content. If an official account or the personal account of a senior manager retweets a sexist joke or something that condones illegal drug use, that could also cause serious issues for the organization.
  • Pretty straightforward
  • These are specific to government. It’s always a good idea to link back to the organization’s home website and vice versa so it’s clear that the account is an official one. Because of public records and sunshine laws, it’s important for the agency to be open about whether comments are allowed or monitored and whether it believes them to be covered under such legislation. And for public safety accounts in particular, such as fire departments or police, the account should note whether it’s monitored and what the “official” mechanisms are to report safety issues.
  • This is an example of a guideline for how to engage those that comment on your social media, and those that post or comment on third party sites. This triage chart from the American Society of Chemical Engineers is not for every user in the organization, but it can be quite useful for those responsible for monitoring and engaging comments about the organization such as public affairs.
  • These are specific to government. It’s always a good idea to link back to the organization’s home website and vice versa so it’s clear that the account is an official one. Because of public records and sunshine laws, it’s important for the agency to be open about whether comments are allowed or monitored and whether it believes them to be covered under such legislation. And for public safety accounts in particular, such as fire departments or police, the account should note whether it’s monitored and what the “official” mechanisms are to report safety issues.
  • Here’s an example of this from the Seattle Fire Dept – it clearly says “This site is not monitored. Call 911 for emergencies.” It also notes the applicability of public records laws and has a link to the main website.
  • The first step is to determine whether or not something is in fact a record. Just as we know that most email messages are not records, for most organizations their Facebook fan page updates will not be records either. In other words, we have to ask the same questions about these tools that we’d ask about any other type of information:Does it document a transaction or a decision? If it does, it’s probably a record. Is it captured in another form? This is the biggest reason why most social networking sites like Facebook and Twitter wouldn’t need to be captured as records – in most cases they are being used as another transmission mechanism for information stored elsewhere. Now, just because it isn’t a record doesn’t mean it couldn’t be discoverable or a public record and subject to FOIA-type laws. Again, same considerations here as for other types of information. [twitter]Determine whether something is a record or not according to its content and context.[/twitter]
  • Prepare for discovery. This means having the same type of data map you have in place inside the organization, but with listings of all the services you use, the accounts used there, etc. At a minimum you should list any official use of services and official accounts. It also means understanding the process for getting at that information in the event of litigation, FOIA request, etc. The time to put that process in place is before the subpoena is received. For hosted tools, such as FB or Twitter, it may mean taking periodic snapshots of what is posted to them. Right now there aren’t a lot of tools that do this; one way that can be effective is to capture the RSS feeds generated by these tools. As updates are made, they are published through the RSS feed, which can be saved locally. It might also require working with the third-party vendor in the event that some information or some updates are not available through RSS – for example, web-based email. It’s also important to note that at least for commercial solutions there is very little ability to put or enforce legal holds or to prevent a user from deleting an account, at least without a subpoena and without doing it before the user knows to delete it. [twitter]Prepare for discovery in advance, including listing official use of services and accounts.[/twitter]
  • As we just noted, the records management or communications policies (or both) should address the use of these tools. We’ll look at some examples of policies over the next few slides. At a minimum, the policy should address: Identity, relationship, and transparency – is the account official or unofficial?Security, confidentiality, and sensitive informationComments and responses to commentsResponding to others’ posts on commercial sitesAccuracy and ethicsMonitoring and auditing[twitter]Address these tools in the records or communications policies (or both). [/twitter]
  • How to capture content will depend first on one key variable: where is it stored? The vast majority of social media sites are either hosted solutions or commercial ones – that is, users’ data is not stored inside the organization’s firewall, but on some third party data center outside the control of the organization. This can present a significant issue because how and how long the data is stored is almost entirely dependent on the site’s Terms of Service. If the Terms are changed from retention for 7 years to retention for 2 weeks, or to permanently, it presents a real problem for the records program. And depending on the site this is almost certainly non-negotiable with the exception of governmental entities with the force of the law behind them. ~It’s also the case that some regulatory regimes have geographical aspects that, for example, require particular content to be stored inside a country’s boundaries, or prohibit it from being stored in certain countries’ boundaries. This can present issues for services that store information in the cloud and that might have numerous data centers spread around the world. ~Once the organization has determined what to capture, the next step then is to save that information locally. This is almost always a copy – in other words, saving social content from Facebook does *not* delete it from there. There are a number of ways to accomplish this that we will review over the rest of this module.
  • Finally, there are enterprise versions of every Web 2.0 application. These enterprise versions are often available to be hosted inside the firewall, meaning that security is much more robust. Access can be secured to them much more effectively. They can be integrated into the organization’s identity infrastructure – whether Active Directory or something else – such that any change, post, comment, edit, update, etc. can all be tracked and, more importantly, tracked to a specific named user. No anonymous postings here. Of course, you have to pay for an enterprise version, but what you’re really paying for is a level of peace of mind. And you still get many of the same benefits – ease of use, familiarity with the type of tool, rapid and agile collaboration across geographical and time boundaries, etc. You’re just getting a more secure and robust version of it. [twitter]Consider implementing enterprise versions. FB is FB, but internal tools might be more appropriate.[/twitter]
  • At this point I’d be pleased to entertain your questions.
  • In conclusion, Web 2.0 is not something coming down the road or over the horizon – it’s here today and is probably in your organization, whether you know about it or not. It is all but impossible to effectively prohibit them – and the tools can significantly improve an organization’s collaboration and knowledge sharing, thereby adding value to the organization. It is incumbent on records management professionals to step up and lead your organizations in the effective use and management of these tools.
  • 20110720 fose 2011 sm governance

    1. 1. Social Media Governance in Federal Agencies<br />Jesse Wilkins, CRM<br />AIIM International<br />July 20, 2011<br />
    2. 2. International - Members in 146 countries<br />Independent - Unbiased and vendor neutral<br />Implementation Focused - Processes, not just technology <br />Industry Intermediary - users, suppliers, consultants, analysts, and the channel<br />http://www.aiim.org <br />http://www.aiimcommunities.org<br />About AIIM<br />
    3. 3. Director, Systems of Engagement, AIIM<br />Background in electronic records management, email management, ECM, and social technologies<br />Frequent industry speaker and author<br />AIIM ERM and Social Business Expert Blogger<br />Instructor for AIIM Certificate Programs<br />Jesse Wilkins, CRM, CDIA+, ERMM<br />
    4. 4. By the end of 2013, half of all companies will have been asked to produce material from social media websites for e-discovery. <br /> Source: “Social Media Governance: An Ounce of Prevention”, Gartner <br />It’s just a fad….<br />
    5. 5. Is a Facebook “like” a record?<br />
    6. 6. The social media governance framework<br />Structural elements of a comprehensive social media policy<br />Social media policy statements<br />Managing social media content as records<br />Agenda<br />
    7. 7. The social media governance framework<br />
    8. 8. Prohibition is not realistic<br />
    9. 9. “A new class of company is emerging—one that uses collaborative Web 2.0 technologies intensively to connect the internal efforts of employees and to extend the organization’s reach to customers, partners, and suppliers. <br />We call this new kind of company the networked enterprise.”<br />
    10. 10. Ensures that employees know what is expected of them<br />Provides guidelines for being more effective<br />Reduces risk of someone posting inappropriate content<br />Addresses legal and operational concerns<br />Why a governance framework?<br />
    11. 11. Management <br />Strategic roles and responsibilities <br />Organization <br />Groups and structures required to manage information<br />Policy and procedures<br />Processes and standards for managing information<br />The governance framework<br />
    12. 12. Determines overall strategic goals of organization<br />Provides support for social media initiative(s)<br />Determines need for policy guidance<br />Determines need for enterprise solutions<br />Supports – or doesn’t – transformation efforts<br />Management<br />
    13. 13. Governance roles required to ensure compliance with the framework<br />Includes usual suspects…<br />Also includes new roles<br />Social media strategist<br />Community managers<br />Moderators<br />Organization<br />
    14. 14. Social content is just another form of content<br />Policy should provide a framework applicable to most or all social media tools – and to other content/communication-related technologies as well<br />DON’T write a Facebook policy, a Twitter policy, etc.<br />The social media policy<br />
    15. 15. Be smart.<br />Be respectful.<br />Be human.<br />Best Buy Social Media Policy<br />
    16. 16. Be real and use your best judgment. <br />Zappos Twitter Policy<br />
    17. 17. Our Twitter policy: Be professional, kind, discreet, authentic. Represent us well. Remember that you can’t control it once you hit “update.”<br />Policy 2.0 – in 140 characters<br />
    18. 18. Structural elements of a social media policy<br />
    19. 19. Purpose<br />Scope <br />Responsibilities<br />Definitions<br />Policy statements<br />References<br />Policy elements<br />
    20. 20. This policy has three purposes:<br />Establish definitions relevant to social business technologies<br />Describe usage policies relating to social business technologies<br />Describe security and technology policies relating to social business technologies<br />Scope: This policy is applicable to the entire enterprise. <br />Purpose and scope<br />
    21. 21. Responsibilities for policy development and maintenance<br />Responsibilities for policy administration<br />Responsibilities for compliance with policy<br />Responsibilities<br />
    22. 22. Uncommon terms<br />Common terms used in an uncommon fashion<br />Acronyms and abbreviations<br />Definitions<br />
    23. 23. Many different elements available<br />Detailed in the next section<br />Policy statements<br />
    24. 24. List any references used to develop the policy<br />Internal strategic documents<br />Existing policies and procedures<br />Statutes and regulations<br />Publications <br />Examples and templates<br />References<br />
    25. 25. Social media policy statements<br />
    26. 26. Official vs. unofficial<br />Link to social media policy<br />
    27. 27. Creation of official accounts<br />
    28. 28. Account details<br />User name<br />Picture<br />Corporate logo usage<br />Bio<br />Contact information<br />Friends/buddies/contacts<br />Groups/fans/likes<br />Look & feel guidelines<br />
    29. 29. Whether posts will require approval<br />Pictures and video<br />By the organization<br />By third parties<br />Links (i.e. “sharing”)<br />Applications and widgets<br />Likes, retweets, etc. <br />Content guidelines<br />
    30. 30. Access to personal accounts using organizational resources (time, computers, network, etc.)<br />Access to sites using personal devices (iPhone, tablet, etc.)<br />Personal access and usage<br />
    31. 31. Affiliation<br />Acceptable and unacceptable groups<br />Perception of approval<br />
    32. 32. Offensive content<br />Disparagement of the organization – or of competitors or others<br />Slander or libel<br />Sexual content<br />Solicitations of commerce<br />Threats<br />Illegal activity<br />Violation of copyright<br />Inappropriate usage<br />
    33. 33. Personnel-related information<br />Financial information<br />Confidential information<br />Health information<br />If you wouldn’t post it to your website or send via email, don’t post to FB or send via Twitter. <br />Sensitive materials<br />
    34. 34. Whether comments are allowed<br />And monitored<br />Comments<br />
    35. 35. Official response to third-party sites<br />Response to comments<br />
    36. 36. Monitoring and reviewing comments<br />
    37. 37. Public records act notices<br />Public safety monitoring considerations<br />Other considerations<br />
    38. 38. Whether the account is monitored for actionable content (screenshot)<br />Public records<br />Monitoring for public safety<br />
    39. 39. Managing social content as records<br />
    40. 40. Is the information unique and not available anywhere else?<br />Does it contain evidence of an agency’s policies, business, mission, etc.?<br />Is the tool being used in relation to an agency’s work?<br />Is there a business need for the information?<br />Does it document a transaction or decision?<br />Is it a record?<br />
    41. 41. Check the service level agreement<br />
    42. 42. Blog post<br />Comments?<br />Updates?<br />Individual Tweet<br />Links and shortened URLS?<br />Wiki article<br />The article?<br />Its changes over time?<br />It depends….<br />What’s the record?<br />Prepare for production<br />
    43. 43. Address in policies<br />
    44. 44. Save content locally<br />Most sites store information outside the firewall<br />Little control over how it is stored<br />Little control over how long it is stored<br />Geographic and jurisdictional issues<br />First step is to save content locally <br />
    45. 45. Take a snapshot of record content<br />
    46. 46. Archive entire stream locally<br />
    47. 47. Archive selected items locally<br />Use search queries and monitoring<br />Records management in brief<br />Store selected items locally using search queries or RSS<br />
    48. 48. Use the native backup to store locally<br />Store locally using built-in tools<br />
    49. 49. Use a third-party service to store locally<br />Store locally using third-party service<br />
    50. 50. Store locally using API<br />Store locally using APIs<br />
    51. 51. Use Word or Notepad to draft content updates and save *that* as a record<br />Draft content locally<br />
    52. 52. Implement enterprise versions<br />
    53. 53. Implement a compliance solution<br /><ul><li> And many others</li></li></ul><li>Questions?<br />
    54. 54. Web 2.0 is here<br />Prohibition is not a realistic option<br />Web 2.0 tools can add significant value to the organization <br />Lead your organization to use them effectively<br />Conclusion<br />
    55. 55. Jesse Wilkins, CRM, CDIA+, ermm<br />Director, Systems of Engagement<br />AIIM International<br /> +1 (303) 574-0749 direct<br /> jwilkins@aiim.org <br /> http://www.twitter.com/jessewilkins<br /> http://www.linkedin.com/in/jessewilkins<br /> http://www.facebook.com/jessewilkins<br /> http://www.slideshare.net/jessewilkins<br /> http://www.govloop.com/profile/jessewilkins<br />For more information<br />
    56. 56. On September 8, 2011, AIIM will bring together leading industry experts in a Social Business Virtual Conference.<br />Attend this 1-day event to learn how your organization can use social technologies to engage staff or customers with the appropriate control and governance.<br />Running from 11am – 5pm EDT we have a packed program of 30 sessions, delivered in 3 tracks.<br />Social Business Virtual Conference<br />
    57. 57. Workshop Attendees: <br />Attend the Social Business Virtual Event for $50 – a savings of $45!<br />Register for the conference by July 31, 2011<br />Enter code FOSEATT85 at checkout<br />http://www.aiim.org/socialbusinessconference<br />Social Business Virtual Event<br />
    58. 58. Covers best practices in governance<br />Policy development<br />Governance processes for social media<br />Roles and responsibilities<br />Broadly applicable strategies – and solutions for specific tools and processes<br />Records management for social media<br />Currently in development<br />Some courses available now<br />Total of 30 courses available by end of September<br />Social Media Governance Training<br />

    ×