http://www.aeca.es/pub/on_line/comunicaciones_xvicongresoaeca/cd/18f.pdf
My research focuses on the adoption of social technologies in the public sector. I am specifically interested in how government agencies decide to adopt new technologies, what adoption pathways they chose, what the organizational, cultural and managerial challenges are and how other government agencies’ actions influence adoption decision processes.
For this project, I interviewed the social media director in the executive branch of the U.S. Government who received the mandate via the Transparency and Open Government memo to “harness new technologies” to become more transparent, collaborative and participatory. I conduct ongoing participatory observations of government agencies’ online behavior since 2009.
In preparation for my research, I prepared my outlook on how Web 2.0 will change the public sector for the 2008 Minnowbrook III conference, (published in 2011).
In 2011, I wrote a piece together with my colleague Stuart Bretschneider defining Government 2.0 as the fifth wave of e-Government.
In the same year, I received the George Frederickson PA Times Best Paper award for my paper on social media strategies in the public sector.
Together with my co-authors, I published a piece on how PA scholarship can adopt social media applications to fascinate knowledge sharing in form of Open Public Administration Scholarship in J-Part (2011).
In 2012, I wrote two books based on my research: Social media in the public sector: A guide to participation, collaboration and transparency in the networked world and together with my co-author Bill Greeves, CIO of Wake County: Social media in the public sector field guide: Designing and implementing strategies and policies.
IBM’s Center for the Business of Government published a special report in June 2012: A manager’s guide to designing a social media strategy.
- Measuring social media impact in the public sector: I received a grant to study the managerial and administrative processes of impact measurement of social media use among government agencies. My previous research has shown that government actors are mainly focusing on quantitative measures, such as number of followers, number of retweets, number of likes, etc. as an indicator for a successful social media presence. Existing rules and regulations hinder a deeper and more appropriate analysis of social impact, awareness creation, and networking. While some of the regulations, such as the cookie policy were recently abandoned, use of metrics is in its infancy. I am planning to design metrics and performance indicators that help government agencies understand if their use of social media is truly making their work more transparent, participatory, and collaborative.
- Open innovation platforms in the public sector: In this project I am looking at innovative ideation processes and open innovation platforms to understand knowledge incubation in the public sector. Among them is Challenge.gov – an ideation platform launched by GSA to help agencies run their own contests and prizes. I recently published a PA Times paper on the topic and am preparing my research for journal publication.
- Wikis in the public sector: The goal of this project is to understand how agencies are adopting collaborative technologies for intra- and inter-organizational collaboration as well as how they use them to include citizens into content co-creation processes. The research includes 10 cases on the federal, state and local level. A first report was published by IBM – The Center for the Business of Government.
Like this:
Be the first to like this.
Ines Mergel, D.B.A. | Assistant Professor
The Department of Public Administration and International Affairs
Syracuse University| Maxwell School of Citizenship & Public Affairs
(T) @inesmergel | (Blog) Social Media in the Public Sector
Three related courses are offered as part of the Master of Public Administration program:
Spring semester
PPA 730 - Government 2.0
PPA 730 - Networked Governance
Fall semester
PPA730 - New Media Management
Syllabus
Government 2.0 Course outline
Week 1: Government 2.0: How'd we get here? • Government 2.0: A new mandate in the public sector • Course schedule, readings, expectations
Suggested readings:
• Bretschneider, S. I., Mergel, I. (2010): Technology and Public Management Information Systems: Where have we been and where are we going, in: Menzel, D.C., White, H. J.: The State of Public Administration: Issues, Problems and Challenges, M.E. Sharpe Inc., New York, pp. 187-203. • Carr, N. G. (2008): Is Google Making us Stoopid?, in: The Atlantic Monthly, July/August 2008. • Coleman, C. (2009): Managing technology - Commentary: The Web 2.0 revolution, published online on August 24, 2009.
• Mergel, I. Web 2.0 in the Public Sector, with Schweik, C., in: Public Service, and Web 2.0 Technologies: Future Trends in Social Media (accepted for publications) • O’Reilly, T. (2009): Gov 2.0: A Promise of Innovation, in: State of the eUnion: Government 2.0 and Onwards, by Goetze, J. and Pedersen, C. B., AuthorHouse, Bloomington, IN, pp. 29-32. • O'Reilly, T. (2005): What Is Web 2.0: Design Patterns and Business Models for the Next Generation of Software, published online: 09/30/2005 • Thomson, C. (2008): Brave New World of Digital Intimacy, in: The New York Times, 09/07/2008.
Week 2: Introduction to social media applications
=> Guest speaker: Kara Capelli, USGS: Twitter business case at USGS <=
1. Blogging & RSS feeds 2. Microblogging
3. Online social networks: Facebook, LinkedIn, GovLoop 4. Content sharing: Photo sharing sites, YouTube 5. Student presentations: International practices
Required readings:
• David C. Wyld (2007): "The Blogging Revolution: Government in the Age of Web 2.0”, Report, IBM - The Center for the Business of Government • Netherland, W., and McCroskey (2010): Case Study: Tweet Congress, in: Lathrop, D. & Ruma, L. (Eds). Open Government – Collaboration, Transparency, and Participation in Practice, O’Reilly Media Inc., Sebastopol, pp. 177-182. • Twitter.com: Science for a Changing World, USGS Twitter business case
Twitter agreggator: “GovTwit: Twitter & microblogging in the public sector” (previous guest speaker: Guest speaker: Steve Lunceford, founder of GovTwit)
Required readings: • Boyd, D. M., & Ellison, N. B. (2007). Social network sites: Definition, history, and scholarship. Journal of Computer-Mediated Communication, 13(1), article 11. • Samuel, A. (2009): Waiting for Government 2.0: Why Do Public Agenices Take so long to Embrace Social media?, in: State of the eUnion: Government 2.0 and Onwards, by Goetze, J. and Pedersen, C. B., AuthorHouse, Bloomington, IN, pp. 111-124.
Week 3: Transparency 2.0
=> Guest speaker: David Fletcher, CIO, State of Utah <=
Required readings:
• GSA newsletter (2008): Transparency, available online
• Suzanne J. Piotrowski and Gregg G. Van Ryzin (2007): Citizen Attitudes Toward Transparency in Local Government, in: The American Review of Public Administration, pp. 306-323.
• President Obama (2009): Transparency and Open GovernmentTools:
- Data.gov
- USASpending.gov
- IT Dashboard
- Recovery.gov
Week 4: “It’s no longer the campaign” • Social media use in grassroots organizations • … and beyond
Required readings:
• Peter Wallsten (2009): Retooling Obama's campaign machine for the long haul, in: LA Times, January 14, 2009 • Andy Barr (2008): 2008 turnout shatters all records, in: Politico, , November 5, 2008 • Jennifer Senior (2009): The Message Is the Message: Barack Obama’s ubiquitous appearances as professor-in-chief, preacher-in-chief, father-in-chief, may turn out to be the most salient feature of his presidency, in: New York Magazine, August 2, 2009, • Sifry, M. (2010): “You can be the eyes and ears”: Barack Obama and the Wisdom of the Crowds, in: Lathrop, D. & Ruma, L. (Eds). Open Government – Collaboration, Transparency, and Participation in Practice, O’Reilly Media Inc., Sebastopol, pp. 115-122 • Mikolaj Jan Piskorski, Laura Winig (2009): Barack Obama: Organizing for America 2.0, HBS case study
Week 5: Participation 2.0
=> Guest speaker: Dustin Haisler, Spigit.com, former CIO Manor (TX) <=
Required readings:
• Nabatchi, T. & Mergel, I. (2010). Participation 2.0: Using Internet and Social Media Technologies to Promote Distributed Democracy and Create Digital Neighborhoods. In: James H. Svara and Janet V. Denhardt (eds.), White Paper: Promoting Citizen Engagement and Community Building. Phoenix, AZ: Alliance for Innovation, pp. 80-87.
• Noveck, B. (2010): Single Point of Failure, in: Lathrop, D. & Ruma, L. (Eds). Open Government – Collaboration, Transparency, and Participation in Practice, O’Reilly Media Inc., Sebastopol, pp. 49-69. • Luehrs, R., Feil, B., Rathmann, H. (2009): e-Participatory Planning: Necessity and Advantage, in: State of the eUnion: Government 2.0 and Onwards, by Goetze, J. and Pedersen, C. B., AuthorHouse, Bloomington, IN, pp. 223-237. • Bryant, L. (2009): People Power can Reboot the Nation, in: State of the eUnion: Government 2.0 and Onwards, by Goetze, J. and Pedersen, C. B., AuthorHouse, Bloomington, IN, pp. 247-256.
• Max Chafkin (2010): Why the High-Tech Industry Loves Manor, Texas, Inc.com magazine.
Week 6: Distributed Democracy 2.0
=> Guest speaker Ben Berkowitz, SeeClickFix.com <=
Required readings:
• Stephen F. King and Paul Brown (2007): Fix My Street or Else: Using the Internet to Voice Local Public Service Concerns, CEGOV2007, December 10-13, 2007, Macao
• Friis, M. (2009): Democracy 2.0, ?, in: State of the eUnion: Government 2.0 and Onwards, by Goetze, J. and Pedersen, C. B., AuthorHouse, Bloomington, IN, pp. 203-209.
• Caddy, J. (2009): Focusing on Citizens, in: State of the eUnion: Government 2.0 and Onwards, by Goetze, J. and Pedersen, C. B., AuthorHouse, Bloomington, IN, pp. 213-222.
• Bovaird, T., Loeffler, E., Downe, J. (2009): Co-Production of Public Services and Policies: The Role of Emerging Technologies, in: State of the eUnion: Government 2.0 and Onwards, by Goetze, J. and Pedersen, C. B., AuthorHouse, Bloomington, IN, pp. 263-280.
Week 7: Wiki-Government
=> Guest speaker: Nick Charney, Government of Canada (GCPedia) <=
Required readings:
• Mergel, I. (2011): Using Wikis in the Public Sector: A Guide for Public Managers, IBM – The Center for the Business of Government, report. • Carafano, J. J. (2011): Mastering the art of wiki, in: JFQ, Issue 60, 1st quarter 2011, pp. 73-78. • McAffee, A. (2005): Will web services really transform collaboration?, in: MIT Sloan Management Review, pp.78-84.
Week 8: Diplomacy 2.0: Diplopedia
=> Guest speaker: Tiffany Smith Licciardi, U.S. Department of State <=
• Intraorganizational wikis • Collaboration • Social sharing
Required readings:
• Bronk, C. & T. Smith (2010): Diplopedia Imagined: Building State’s Diplomacy Wiki • Bronk, C. (2007, Aug) "May a Thousand Wikis Bloom: The Politics of Ubiquitous Web Publishing in the U.S. Federal Bureaucracy", Paper presented at the annual meeting of the APSA, Chicago. Online Retrieved 2008-05-20 • Shirky, C. (2011): The Political Power of Social Media: Technology, the Public Sphere, and Political Change, in: Foreign Affairs, January/February 2011, available online: • Lord, K. M. and Fontaine, R. (2010): Managing 21st-Century Diplomacy: Lessons from Gloabal Corporations, Center for a New American Security.
Week 9: Civil Society 2.0
=> Guest speaker Noel Dickover, U.S. Department of State: Civil Society 2.0 project <=
Required readings:
• U.S. Department of State (2009): Secretary Clinton Announces Civil Society 2.0 Initiative to Build Capacity of Grassroots Organizations.
• Tech@State (2010): What is Civil Society 2.0?.
• Civil Society 2.0 & State Department White Paper (2010)
• Hamel, Michael P., and Charles M. Schweik. 2009. Open source collaboration: Two cases in the U.S. public sector. First Monday 14, no. 1 (January 5, 2009).
Week 10: Collaboration 2.0
=> Guest speaker Bill Greeves, Co-founder MuniGov2.0: Second life: “Virtual Worlds in the Public Sector” <=
Required readings:
• Bruce Damer (2008): Meeting in the Ether: A brief history of virtual worlds as a medium for user-created events, in: Journal of Virtual Worlds Research, Vol.1. No. 1, “Virtual Worlds Research: Past, Present & Future” July 2008.
• Mergel, I. (2010): The use of social media to dissolve knowledge silos in government, in: O'Leary, R., Kim, S. and Van Slyke, D. M. (Editors): The Future of Public Administration, Public Management and Public Service Around the World: The Minnowbrook Perspective, Georgetown University Press, pp. 177-187.
Instructions:
• Familiarize yourself with MuniGov2.0: https://sites.google.com/site/munigov20/ .
• Download Second Life desktop application, create and dress your avatar and familiarize yourself with islands on Second Life. Bring your favorite destinations to class.
Week 11: Information security
Distributed Denial of Service attacks (DDoS) Online censorship vs. transparency and openness
Required readings:
• Shirky, C. (2008): Forethought Security: Next online Cons, in: HBR: Reprint F0806D.
• Davis, J. (2008): Secret Geek A-Team Hacks Back, Defends Worldwide Web, WIRED MAGAZINE: 16.12.
• David Drummond, SVP, Corporate Development and Chief Legal Officer (2010): A new approach to China, Google Public Policy Blog, accessed Tuesday, January 12, 2010 at 6:53 PM ET
CASE: Mueller, P. (2008): Security 2.0: The Estonian-Russian Cyber war of 2007, Erfurt School of Public Policy (free).
Week 12: Access, digital divide, new media literacy
Required readings:
• Thompson, Clive (2008): Brave New World of Digital Intimacy, NYT, September 5, 2008.
• Sipior J. and Ward B. (2005) Bridging the Digital Divide for e-Government inclusion: A United States Case Study. The Electronic Journal of e-Government, 3(3): 137-146.
• Pew Foundation: “The Ever-Shifting Internet Population”.
• Gillmor, D. (2008): Principles for New Media Literacy.
• Anderson, J. & Rainie, L. (2010): Millenials will make online sharing in networks a lifelong habit, published July 9, 2010.
• Familiarize yourself with the 508 compliance website: http://www.section508.gov
Week 13: Bringing it all togher: Social media policies and strategies in the public sector
Required readings:
• Mergel, I.: Measuring the effectiveness of social media tools in the public sector, in: Public Service, and Web 2.0 Technologies: Future Trends in Social Media (accepted for publication) • Mergel, I. (2010): Government 2.0 Revisited: Social Media Strategies in the Public Sector, in: PA Times, American Society for Public Administration, Vol. 33, No. 3, p. 7 & 10, available online. • Brian, J. Dunn (2010): How I did it: Best Buy’s CEO on Learning to Love Social Media, in: Harvard Business Review.
• Harvard Business Review Analytic Service Report: The New Conversation: Taking Social Media from Talk to Action, HBR.
Week 14: Looking beyond Government: What can the public sector learn from successful social media practices in the corporate and non-profit sector?
Week 15: Student presentations of Government 2.0 implementation projects
http://www.aeca.es/pub/on_line/comunicaciones_xvicongresoaeca/cd/18f.pdf
Guideline for External Use of Web 2.01. Publication Date
The publication date of this guideline is November 18th, 2011, and it will be reviewed and updated on an ongoing basis as appropriate.
2. Purpose
This guideline is designed to provide specific guidance to Government of Canada departments on the use of externally facing Web 2.0 tools and services.
This guideline does not alter or replace any existing legislation or policy instrument. When interacting with external audiences through Web 2.0 tools and services for official purposes, departments must comply with existing legislative and policy requirements. This guideline includes practical advice to help departments make informed decisions about how to meet these requirements when using externally facing Web 2.0 tools and services. In addition, the guideline encourages departments to:
- Designate clear accountability for the coordination of departmental Web 2.0 initiatives; and
- Develop guidance for personnel on the use of Web 2.0 that addresses expected behaviours, benefits, risks and consequences for all types of potential use (official use, professional networking use and personal use).
This guidance may not cover every situation, but it will help departments make good choices that mitigate risks while maximizing benefits of these tools and services.
2.1 Application
This guideline was released by the Treasury Board Secretariat (TBS) Chief Information Officer Branch. It supports and should be read in conjunction with the Policy Framework for Information and Technology, including the Policy on Management of Information Technology and the Policy on Information Management, as well as the Communications Policy of the Government of Canada. Unless explicitly stated otherwise, the guidance provided applies to the use of Web 2.0 tools and services developed by the Government of Canada and/or hosted on Government of Canada networks, as well as to those developed and/or hosted by a third party.
This guideline applies to departments as defined in section 2 of the Financial Administration Act, unless excluded by specific acts, regulations, or Orders in Council. Other Government of Canada institutions may make use of this guideline as appropriate for their operational needs. Some of the policy instruments referenced in this guideline, including those relating to official languages, values and ethics, and political activities, have specific applications that may be broader or narrower than the intended audience of this guideline, therefore each department should accordingly give consideration to its specific obligations. All Government of Canada departments are encouraged to draw on this guideline to complement and support their existing obligations.
3. Background
3.1 What is Web 2.0?
Web 2.0 refers to Internet-based tools and services that allow for participatory multi-way information sharing, dialogue, and user-generated content. This can include social media, which allow participants with distinct social/user profiles to create, share and interact with user-generated content, including text, images, video and audio (e.g. Facebook, Twitter, YouTube, Linked-In, blogs) as well as collaborative technologies that allow multiple users to collaboratively create content (e.g. Wikis, Google Docs).
3.2 Benefits of Use
Government of Canada departments are encouraged to use Web 2.0 tools and services as an efficient and effective additional channel to interact with the public. A large number of Canadians are now regularly using Web 2.0 tools and services to find information about, and interact with, individuals and organizations. For many Canadians, Web 2.0 is increasingly becoming a primary channel for sending, receiving and generating information. Because of the participatory nature of Web 2.0, it can help facilitate interactive and rapid communication and engagement between government departments, their partners and their clients, with some common uses including:
- Recruitment;
- Risk and emergency communications;
- Services to the public;
- Stakeholder outreach and education;
- As a collaborative tool; and
- Consultation.
3.3 Risks of Use
Though the use of Web 2.0 is encouraged because of the many potential benefits, departments should remain aware of the risks and challenges that the use of Web 2.0 can sometimes present, including:
- Difficulty reconciling existing constitutional, statutory, regulatory and policy obligations with the technological constraints and usage patterns of these tools and services (e.g. reconciling Official Languages requirements with a Web 2.0 tool that has per-message characters limits);
- Potential misuse of Government of Canada content that is shared through Web 2.0 tools and services, particularly when subject to the terms of service of third-party Web 2.0 service providers (e.g. profile information being reused by a third-party service for advertising);
- Negative perceptions resulting from Web 2.0 initiatives associated with the Government of Canada, including users posting offensive or abusive comments, attempts to engage in dialogue about political decisions or direction, on-line vandalism, and inability to fulfill reasonable expectations of timely two-way communication;
- Misinterpretation of online activity and/or comments as the official position of the Government of Canada rather than that of an individual;
- Challenges in protecting the privacy of both personnel and the public who are interacting through Web 2.0 tools and services; and
- Extensive and legally binding terms of service that can, if not sufficiently understood and respected, present legal risks for the Government of Canada and individuals.
4. Key Considerations for Web 2.0 Initiatives
This section provides advice and guidance on key considerations for departments when developing and executing externally facing Web 2.0 initiatives. Specifically, it provides key considerations for the following phases of the life-cycle of a Web 2.0 initiative:
- Governance and Oversight;
- Planning and Design;
- Rules of Engagement; and
- Evaluation and Measurement,
Departments should ensure that their use of Web 2.0 is consistent with their mandate. Management of Web 2.0 initiatives should be included in regular departmental planning exercises to address business value, governance, resources, costs, communications, policy and legislative requirements, as well as risks and challenges of use.
4.1 Governance and Oversight
- Departments should designate a senior official accountable and responsible for the coordination of all Web 2.0 activities as well as an appropriate governance structure. It is recommended that the Head of Communications be the designated official. This designate should collaborate with departmental personnel who have expertise in using and executing Web 2.0 initiatives, as well as with representatives from the following fields in their governance structure: information management, information technology, communications, official languages, the Federal Identity Program, legal services, access to information and privacy, security, values and ethics, programs and services, human resources, the user community, as well as the Senior Departmental Official as established by the Standard on Web Accessibility. A multidisciplinary team is particularly important so that policy interpretations are appropriately made and followed when managing information resources through Web 2.0 tools and services.
- Governance of Web 2.0 initiatives should be clear, succinct and well communicated so that all departmental personnel are aware of their responsibilities and how decisions are made. The governance of Web 2.0 initiatives should be integrated with existing departmental governance structures to reduce duplication of effort, information and repositories, as well as to help ensure that engagement is consistent.
- When it is likely that a Web 2.0 initiative will require a Treasury Board submission (e.g. a requested modification under the Federal Identify Program (FIP) for a unique departmental or program identifier), the appropriate TBS analyst should be engaged early in the planning process.
- The designated departmental accountability centre for Web 2.0 initiatives should be the coordination point for creating and managing official departmental Web 2.0 accounts and profiles. It should also ensure that when creating these accounts and profiles the department uses customized terms of service for third-party Web 2.0 tools and services (see Appendix H for further information on customized terms of service).
- Approaches that reflect the participatory nature of Web 2.0 platforms should be encouraged and supported within the governance structure. These approaches may include developing or leveraging communities of practice and communities of interest, as well as processes to integrate these communities' input into current governance structures. Where multiple departments collaborate through Web 2.0 tools and services, cross-departmental governance is recommended.
- An overall departmental strategy (and policies, where required) for using Web 2.0 tools and services should be developed, which takes into account:
- Existing mandate and business value for the department;
- Policy and legislative obligations;
- Departmental governance structures;
- Operational requirements, including resources and costs;
- Risks and challenges of use;
- Assessing and granting access to Web 2.0 tools and services on departmental networks;
- Expected and recommended behaviours and procedures for personnel;
- Monitoring and consequences; and
- Lessons learned and shared by other departments.
4.2 Planning and Design
- Have a plan: For each Web 2.0 initiative, departments should develop a plan with input from departmental communications advisors that follows departmental policy and procedures with respect to external communications activities. This plan should outline:
- The business drivers for the use of Web 2.0 tools and services;
- How this use is aligned with overall governmental, departmental, program and/or project objectives to ensure that it is aligned with overall outcomes;
- Delineation of roles, responsibilities and accountabilities;
- Considerations of the target audiences (Internet behaviours, language preference, persons with disabilities, mobile technologies, literacy levels, knowledge and understanding of the issues, positions on issues, etc.) to help identify which are the most appropriate Web 2.0 tools and services for the department to be using, and how to manage interactions;
- The authorities for project ownership and approval, competition and contracting, intellectual property, and licences;
- A risk assessment and management plan;
- A communications plan to:
- Help outline the expected nature of the interactions;
- Respond to stakeholders, including when responses are critical, political, off-topic or abusive; and
- Ensure that messaging on Web 2.0 tools and services aligns with Government of Canada themes and messages on other channels.
- Allocation of appropriate resources (human, technical and financial), including the resources needed to manage the accounts in both official languages;
- The training required to ensure that personnel understand how to use Web 2.0 tools and services within the legislative and policy framework of the Government of Canada and the department;
- An approach for program evaluation including what metrics are available and what defines success;
- A proposed timeline for evaluation;
- A continuous improvement process to learn and improve the initiative; and
- How it will be phased out or transitioned if necessary.
- Comply with policies: When using Web 2.0 tools and services for official purposes, departments must ensure compliance with legislation and Treasury Board and departmental policies. Information about certain specific legislative and policy obligations is provided in the Appendix of this guideline, which should be referred to for more detailed guidance. As a summary of the Appendixes, the key policy considerations when developing a Web 2.0 initiative are as follows (in alphabetical order):
- Accessibility
- Government of Canada public facing Web pages (including Web applications) must comply with the accessibility requirements outlined in the Standard on Web Accessibility. Web 2.0 tools and services integrated into those Web pages (including Web applications) must also comply with the requirements outlined in the Standard on Web Accessibility; and
- Government of Canada Web content hosted on external third-party Web 2.0 tools and services (including Web sites) should conform to the Web accessibility best practices for those tools and services, and should include links to equivalent content on Government of Canada Web sites, which are required to meet the Standard on Web Accessibility.
- Communications
- Verify that the planned Web 2.0 initiative is congruent with Government of Canada themes and messages, as well as departmental communications' and consultations' objectives and requirements. Privy Council Office should be engaged early in the process to ensure alignment of Web 2.0 activities with Government of Canada communication and consultation priorities;
- Confirm that if the planned gathering of opinions or views through public interaction falls within the definition of public opinion research, that it complies with mandatory requirements under the Communications Policy of the Government of Canada and related Procedures for Planning and Contracting Public Opinion Research;
- Web 2.0 advertising activities must comply with mandatory requirements under the Communications Policy of the Government of Canada and related Procedures for Planning, Contracting and Evaluating Advertising; and
- Ensure that advertising from sources outside of government is not displayed alongside the department's Web 2.0 presence where possible to avoid perception of endorsement.
- Federal Identity Program
- Ensure that the Government of Canada or department is appropriately identified as required under the Federal Identity Program Policy; and
- Web 2.0 initiatives undertaken jointly with another government, company, organization, group or individual must clearly and equitably identify the participation of all parties.
- Information Management
- Review planned Web 2.0 initiatives for the ability to save or capture information of business value to ensure that relevant content can be stored and retrieved and to ensure that recordkeeping requirements and procedures are followed; and
- Departmental information management specialists can assist with determining ways to identify information of business value and to integrate Web 2.0 tools and services with recordkeeping and document management systems where necessary.
- Official Languages
- Ensure that each Web 2.0 tool or service under consideration supports content in both official languages, according to the Official Languages Act, the Policy on the Use of Official Languages for Communications with and Services to the Public and associated directives;
- Actively encourage participation in both official languages, including informing the public that there is an equal "activity" that they can access in the other official language;
- Ensure that terms of reference, conditions of use, departmental positions and disclaimers are available in both official languages;
- Ensure that management and editing tools, help sections, pop-up messages, site navigation, as well as user interfaces (including use of accents for French and equal access from initial points of entry) are available in each official language and are of equal quality. This is required when a Web 2.0 tool or service is being provided by the Government of Canada; when using a third-party Web 2.0 tool or service, departments should strive to meet these obligations and assess whether the platform should in fact be used;
- Ensure that if using two separate single-language accounts, that both versions have equal status (i.e. both versions considered to be official);
- Put in place a strategy to deal with comments from the public in both official languages. This strategy must include carefully monitoring both language versions of Web 2.0 tools or services being used so that when it appears that the department is receiving more public questions/comments in one language that require a general and public response, it ensures that it provides the same information to the public in both official languages. Departments should consider providing regular summaries of comments which are posted in both official languages simultaneously; and
- Plan ahead for translation at key milestones to ensure equality of services and quality in both official languages.
- Privacy and Access to Information
- Engage your departmental Access to Information and Privacy (ATIP) office at a sufficiently early stage to assist in reviewing the privacy implications of the planned use of Web 2.0 tools and services. ATIP officials will help ensure that:
- The requirements of the Privacy Act are respected;
- TBS policy instruments, in particular that Privacy Impact Assessment (PIA) requirements, are addressed where appropriate;
- In cases where personal information is used for non-administrative purposes only, that a privacy protocol addresses any personal information concerns;
- An appropriate privacy notice is developed for the site; and
- Procedures are in place to ensure any requirements under the Privacy Act or Access to Information Act are addressed
- Privacy, legal and security concerns related to sites hosted or owned by third parties are addressed; and
- Institutions should monitor Web 2.0 sites to ensure that any inappropriate, unsolicited or confidential information is removed.
- Procurement and Contracting
- If the acquisition of the Web 2.0 tool or service has costs associated with it, consult your departmental procurement and contracting experts for guidance;
- A contracting risk assessment must be undertaken for each of the Government of Canada's Web 2.0 initiatives that have a cost associated with the use of the respective tool or service. Conducting a risk assessment remains a good practice in the case of using no cost Web 2.0 tools and services; and
- Whenever possible, departments should use custom terms of service that have been negotiated by PWGSC for some third-party Web 2.0 tools and services. For more information on how to do so, please refer to the "Social media procurement process" page on GCpedia.
- Security
- Evaluate any unique security risks (e.g. identity theft, viruses, worms, phishing and Trojan Horses) associated with the Web 2.0 tools or services under consideration and identify approaches for information and technology security.
- Legal review: Prior to using Web 2.0 tools and services, departments should engage their legal services unit for advice on associated legal issues. In seeking advice, departments should provide legal counsel with information about the proposed use(s) including information about the Web 2.0 initiative's oversight plan, the particular Web 2.0 tool or service under consideration and the relevant terms of use. Key legal issues related to Web 2.0 initiatives will include:
- Canadian Charter of Rights and Freedoms and Canadian Human Rights Act;
- The Values and Ethics Code for the Public Service;
- Privacy and Access to Information;
- Official Languages;
- Intellectual Property (including copyright);
- Procurement;
- Crown Liability; and
- Governing law.
4.3 Rules of Engagement
Departments should develop rules of engagement for the public whenever using external Web 2.0 tools or services. The rules of engagement should be clearly posted on or linked from the Web 2.0 tool or service at an appropriate location, such as the departmental account profile or the main navigation page. The rules of engagement should, at a minimum, provide the following:
- Moderation criteria for:
- Topical posts or comments;
- Personal information and other protected or classified information;
- Political posts;
- Advertising, solicitation or spam;
- Profanity;
- Attacks; and
- Discrimination on the basis of, for example, race, national or ethnic origin, colour, religion, sex, age, mental or physical disability, or sexual orientation;
- Response time expectations;
- Intellectual property (including copyright), privacy, accessibility and official languages notices which include links to the corresponding legislation, Treasury Board or departmental policies; and
- Consequences for violation of the rules of engagement.
4.4 Evaluation and Measurement
It is recommended that departments conduct evaluations of all Web 2.0 initiatives at regular intervals appropriate to the pace and nature of interactions, that:
- Measure to what extent the use of the Web 2.0 tool or service is meeting expected outcomes and providing business value;
- Ensure that the use of the Web 2.0 tool or service is reaching the desired target audiences;
- Evaluate compliance with policies, procedures and legal obligations;
- Establish processes to leverage outcomes of evaluation to improve the initiative, including updating personnel and managers' training needs.
Through the participation in cross-departmental working groups and by sharing the results of evaluation and measurement of Web 2.0 initiatives, departments should actively contribute to developing and maintaining Government of Canada best practices and procedures for using Web 2.0. Since Web 2.0 tools and services are ever-changing, this will allow the Government of Canada to keep current and assist all departments with governance and risk management.
5. Establishing Guidance for Personnel
It is recommended that departments provide personnel with guidance for their use of Web 2.0 that addresses expected behaviours, benefits, risks and consequences for all potential types of use. This guidance should be based on the principle that personnel are trusted in their use of Web 2.0 tools and services just as they are trusted in every other aspect of their work. When possible, existing guidance for personnel on the use of Web 2.0 that has been developed by other Government of Canada departments should be leveraged.
Government of Canada personnel may seek to use Web 2.0 tools and services in one or more of the following ways:
- Official Use:
- Use of an official departmental Web 2.0 account for departmental communication purposes, including as a spokesperson for the department or within the scope of an individual's duties in the course of their employment.
- Professional Networking Use:
- Use of an individual's personal Web 2.0 account for non-official communication purposes that are related to their employment, including participating in professional associations, knowledge sharing and career development.
- Personal Use:
- Use of an individual's personal Web 2.0 account for purposes unrelated to their employment.
1. In the development of guidance for their personnel on the use of Web 2.0 tools and services in official, professional networking, and personal use situations, departments may consider basing their guidance on the following statements which are broadly applicable to all Government of Canada personnel:
For Official Use:
- All Web 2.0 activities for Official Use should be undertaken with the support and under the direction of the department's designated official responsible for Web 2.0.
- When using Web 2.0 tools and services as part of your official duties, you may be acting as a designated departmental spokesperson in accordance with the Communications Policy of the Government of Canada. Your manager and communications advisors will provide you the guidance and permissions needed and help you put together a plan for engaging the public.
- Ensure that you have the proper authority prior to creating a profile on a Web 2.0 tool or service on behalf of your department.
- Whenever possible, you should use customized terms of service when creating a profile on a third-party Web 2.0 tool or service. For more information on how to do so, please refer to the "Social media procurement process" page on GCpedia.
- When using Web 2.0 tools or services for official use, compliance with relevant legislation and Treasury Board and departmental policies is required. The appendixes of the TBS Guideline for External Use of Web 2.0 provides specific advice as to how to comply with existing legislative and policy requirements governing interactions with external audiences through Web 2.0 tools and services and should be followed at all times.
For Professional Networking & Personal Use:
- Your obligations as outlined in the Values and Ethics Code for the Public Service apply at all times, particularly if your employer could be identified through your use of Web 2.0 tools and services.
- By virtue of your employment, information shared through Web 2.0 tools and services may be perceived as an official Government of Canada position rather than your own opinion. You should therefore clearly state in your account profile that the views expressed are your own and not those of your employer. However, it is important to note that such a disclaimer does not absolve you of your obligations as a public servant, including your duty of loyalty to the Government of Canada.
- Forward all requests for statements or interviews from the media to your departmental communications advisor and/or provide a contact to your departmental media relations advisor as you may not be the authorized spokesperson on these matters for your department.
- Only publicly available information may be shared externally, unless you are specifically authorized otherwise. Always check permissions required to reproduce or distribute any information, including Government of Canada content such as illustrations, photographs, videos, audio, logos, trade-marks or wordmarks. Wherever possible, provide links to original source material and attribute as required to respect copyright and intellectual property rights.
- Personal information about others should not be posted through Web 2.0 tools and services, unless you have the explicit consent of the individual(s) to whom the information relates to do so.
- Divert work-related conversations to official channels (e.g. a Government of Canada e-mail account) as appropriate so that there is a record of any guidance provided or decisions taken.
- Do not use any Government of Canada corporate symbols or signatures in your use of Web 2.0 for professional networking or personal use. They are for use in official communication only.
- Remember that Web 2.0 interactions can be easily republished or repurposed without the original context, and may be permanently accessible. Be sure to understand the Web 2.0 environment and its associated risks.
- When creating an account on a Web 2.0 tool or service, if it is linked to your Government of Canada e-mail address it should only be used for professional networking purposes.
- If you have questions about an on-line activity that you want to or have engaged in, you should speak to your manager or Values and Ethics advisor.
- You must not engage in any activity that might put at risk the non-partisanship and impartiality of the public service. If you have questions about political expression through the use of Web 2.0 tools and services, you should speak to your manager or contact your department's designated political activities representative.
- If you are accessing Web 2.0 tools and services through Government of Canada networks, you must be aware of the terms of your department's policy regarding the use of electronic networks, including its monitoring, investigation and disciplinary provisions.
2. Departments are encouraged to provide training to assist personnel in understanding their obligations when using Web 2.0 tools and services in any capacity, under both the Values and Ethics Code for the Public Service as a term and condition of employment, as well as the rights and legal obligations for personnel subject to Part 7 (political activities) of the Public Service Employment Act (PSEA).
Fulfillment of these obligations is expected at all times as follows:
- Public servants owe a duty of loyalty to the Government of Canada;
- Do no harm to the reputation of your employer;
- Maintain integrity and impartiality; and
- Uphold the tradition of political neutrality of the Public Service.
An explanation of what, if any, employment consequences exist when contravening these obligations should be explicitly provided.
6. Additional Guidance Sources
Additional guidance on the use of Web 2.0 tools and services is in various stages of development by communities of expertise and Web 2.0 practitioners within the Government of Canada. Many of these resources are available to public servants on the Government of Canada's internal wiki, GCpedia. While these resources are not official Government of Canada policies or guidelines, they are valuable sources of information in this rapidly evolving environment. As a companion to this guideline, a GCpedia page listing additional sources of guidance on the use of Web 2.0 is available.
7. Related Legislation and Policy Instruments
Legislation
Policy Instruments
8. Definitions
- Collaborative technologies
- Internet-based technologies that allow multiple users to collaboratively create content.
- Communications
- A management function that ensures that the public - internal or external to the government - receives government information, and that the views and concerns of the public are taken into account in the planning, management and evaluation of policies, programs, services, and initiatives.
- Department
- A federal entity as defined in section 2 of the Financial Administration Act unless excluded by specific acts, regulations, or Orders in Council.
- External
- For the purposes of this guideline, "external" or "externally facing" means available to members of the public as opposed to available only to personnel of the Government of Canada.
- Guidelines
- Information, usually in the form of best practices, intended to help departments carry out government policy efficiently and effectively. Guidelines are not mandatory policy instruments.
- Information management (IM)
- A discipline that directs and supports effective and efficient management of information in a department, from planning and systems development to disposal or long-term preservation.
- Information resources of business value
- Published and unpublished materials, irrespective of medium or form, that are created or acquired because they enable and document decision making in support of programs, services and ongoing operations, and support departmental reporting, performance and accountability requirements.
- Information technology (IT)
- Any equipment or system that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission or reception of data or information. Information technology includes all matters concerned with the design, development, installation and implementation of information systems and applications to meet business requirements.
- Personal information
Information about an identifiable individual that is recorded in any form. The Privacy Act provides a non-exhaustive list of examples of personal information, including the following:
- Information relating to the race, national or ethnic origin, colour, religion, age, or marital status of the individual;
- Information relating to the education or employment history of the individual, such as found in a résumé;
- Information relating to the medical or criminal history of the individual;
- Information relating to financial transactions in which the individual has been involved;
- Any identifying number, symbol or other particular assigned to the individual, such as a Social Insurance Number or Personal Record Identifier;
- The address, fingerprints or blood type of the individual;
- Correspondence sent to a government department by the individual that is implicitly or explicitly of a private or confidential nature, and replies to such correspondence that would reveal the contents of the original correspondence;
- The views or opinions of another individual about the individual; and
- The name of the individual where it appears with other personal information relating to the individual or where the disclosure of the name itself would reveal information about the individual.
The Privacy Act also provides examples of what does not constitute personal information, which include:
- Selected information about government personnel, including their titles, business addresses and phone numbers;
- Information about individuals acting under contract for government institutions; and
- Information about an individual who has been dead for more than twenty years.
- Personnel
- Full- or part-time employees of the Government of Canada (e.g. indeterminate, seasonal, specified-period/term, student or casual).
- Public consultations:
- Processes whereby information is provided to the public in order to seek their views/concerns relating to the planning, management or evaluation of government policies, programs and services. As a best practice, the results of a consultation are always made public.
- Public opinion research
- The planned gathering, by or for a government department, of opinions, attitudes, perceptions, judgments, feelings, ideas, reactions or views that are intended to be used for any government purpose, whether that information is collected from persons (including personnel of government departments), businesses, departments or other entities, through quantitative or qualitative methods, irrespective of size or cost.
- Social media
- On-line platforms that allow for participants with distinct social/user profiles to create, share and interact with user-generated content, which can include text, images, video and audio.
- Spokesperson
- For the purposes of this guideline, "spokesperson" is understood as a function outlined in the Communications Policy of the Government of Canada.
- Web 2.0
- Internet-based tools and services that allow for participatory multi-way information sharing, dialogue, and user-generated content. This can include social media and collaborative technologies.
Appendix: Specific Policy Guidance (in alphabetical order)
A. Accessibility
Government of Canada public facing Web pages (including Web applications) must comply with the accessibility requirements outlined in the Standard on Web Accessibility. Web 2.0 tools and services integrated into those Web pages (including Web applications) must also comply with the requirements outlined in the Standard on Web Accessibility.
Government of Canada Web content hosted on external third-party Web 2.0 tools and services (including Web sites) should conform to the Web accessibility best practices for those tools and services, and should include links to equivalent content on Government of Canada Web sites, which are required to meet the Standard on Web Accessibility.
Some additional information resources about accessibility are as follows:
For more information about Government of Canada Web Standards, please contact your department's Web Centre of Expertise.
B. Communications
When using Web 2.0 tools or services to communicate or consult with the public as the department's representative, public servants are acting as designated spokespersons, according to the Communications Policy of the Government of Canada. Public servants are therefore required to consult their head of communications or his or her delegate before communicating with the public in an official capacity. The head of communications is responsible for overseeing and advising on content that informs the public of government priorities, policies, programs, services and initiatives.
According to the Communications Policy of the Government of Canada, the head of communications for each department is responsible for ensuring that:
When public servants use Web 2.0 as designated spokespersons, they are to:
- Confine their remarks to factual information concerning the priorities, policies, programs, services or initiatives of their department. Discussions on political matters are the exclusive domain of ministers and their offices;
- Respect privacy rights, security requirements, the confidentially of matters before the courts, government policies, third parties' intellectual property rights, Cabinet confidences and ministerial responsibility; and
- Identity themselves by name and department and, when feasible, position title.
C. Federal Identity Program
Web 2.0 tools and services can present a challenge to the clear identification of official government content and accounts in accordance with the visual identity of the Government of Canada. On some Web 2.0 tools and services, the available visual space, page layouts and proprietary design controls limit the size and display of elements as well as the length of account names and official titles. Because of these constraints and the evolving nature of government's use of Web 2.0, the Federal Identity Program (FIP) has tailored its advice for identifying government content on Web 2.0 tools and services. The practical tips below provide general direction on basic identity considerations. It does not supersede the general requirements of FIP policy and standards and is to be read in conjunction with any templates produced for government-wide use.
Practical Tips for Complying with FIP Requirements:
- Use the "Canada" wordmark and the appropriate government signature where sufficient space is available. Where space is insufficient to display both symbols, the "Canada" wordmark may be used alone.
- Treasury Board approval must be received before using any unique identifying marks (logos, logotypes, marks, emblems, identifiers, etc.) to identify a department or its programs or services.
- When the terms of use of a Web 2.0 tool or service include suspending the government's exclusive right to its official symbols, or authorizes use of the symbols by the service provider or other parties, departments should discuss the terms with their legal counsel. The TBS Federal Identity Program, in consultation with legal counsel, will determine the appropriate form of government identification in these specific instances.
- When presenting official government symbols within a page format controlled by a Web 2.0 tool or service provider, carefully consider any visual elements, non-government corporate or brand elements, and the proximity of any proprietary advertising features to ensure that the official symbol(s) of government are free from any unintended association or distracting information.
- Where avatars are insufficient for incorporating the "Canada" wordmark, the national flag of Canada is to be used as the primary element, rendered in its entirety as a two-dimensional image.
- The official symbols of government may not be altered, presented vertically, obscured in any way, or integrated into text or designs. They must be free from distracting or interfering elements, with optimal contrast, and in accordance with the general principles of the Federal Identity Program.
- All video clips must end with the "Canada" wordmark. Video advertisements and presentations must include the standard audio end credit "A message brought to you by the Government of Canada." Video clips that are presented individually or as a series, or that serve to animate data or present other information, may include the appropriate government signature rather than the standard audio end credit as appropriate.
- Logos or corporate symbols of non-government organizations or private sector enterprises may not be incorporated into a department's content except when a) the elements form part of the Web 2.0 tool or service and are entirely outside the control of the department, or b) when the information pertains to a collaborative arrangement, in which case the official symbol of the partnering organization may be used.
- Account names or "handles" should be clearly based on principal elements from a department's official title or acronym where possible and use functional and service-based words or terms otherwise. When establishing a Web 2.0 presence, consideration of official languages must be given to account names or handles.
- Widgets and downloadable information or code developed by departments and made available to the general public for re-posting on non-government sites may not include the official symbol of the Government of Canada. The information source or author attributions in these cases must be text only.
- Consideration must be given to photographs to ensure that author attribution and copyright information are embedded into those images offered as (or are likely to be used as) information re-posted on third-party sites.
- The use of the official symbols of the government is limited to the official activities and communications of the Government of Canada. Use of these symbols in personal Web 2.0 activities is strictly prohibited.
Enquiries about these requirements may be directed to your department's Federal Identity Program Coordinator or to the Treasury Board of Canada Secretariat policy centre at: information@fip-pcim.gc.ca
D. Information Management
As the Government of Canada increasingly makes use of Web 2.0 to support the development of policy and to meet operational requirements, the integration of information management requirements is essential to ensure that digital information of business value is accessible, shareable, and usable over time and through technological change.
The relevant policies that dictate which information created and maintained through Web 2.0 tools and services needs to be retained, and how this should be accomplished, are:
- The Policy on Information Management which specifies that all decisions and decision-making processes must be documented to account for and support the continuity of departmental operations;
- The Directive on Information Management Roles and Responsibilities which stipulates that all personnel of the Government of Canada are responsible for managing the information they collect, create and use in carrying out their work, including information published through Web 2.0 tools and services; and
- The Directive on Recordkeeping which requires that all information be identified, documented and protected when it relates to decisions and decision-making processes, regardless of format.
Under the Directive on Recordkeeping, the following information resources associated with Web 2.0 tools and services are required to be captured in a departmental information repository as a record:
- Official program information made available through external Web 2.0 tools and services that has not otherwise been recorded through official documentation such as departmental externally-facing web sites, briefing notes, project or communication plans, etc.
- Information received from the public in response to requests for Government of Canada departments for information via external Web 2.0 tools and services.
Responses from the public received to a request for information sent out via Web 2.0 tools and services may form the basis of a report on a public consultation. These responses need to be captured as evidence of the consultation and the rationale for the decisions taken.
If the information needs to be kept, it is the responsibility of the government personnel who is posting on the Web 2.0 tool or service to capture the information by storing it in a departmental information repository as an official record. Departmental information repositories include physical or electronic storage space (e.g. shared drives, electronic documents and records management systems, records rooms, etc.). Web 2.0 tools and services are not considered to be approved information repositories for housing Government of Canada information.
The following resources are not required to be captured in departmental information repositories as a record as they are already recorded elsewhere:
- New information, messages, or official pages posted on Web 2.0 tools and services that have already been captured in official documentation (e.g. externally-facing web sites, briefing notes, project or communications plans, etc.) that relate to decisions and decision-making processes or announcements regarding federal programs and services; and
- Information in the form of electronic conversations that have taken place through the direct messaging components of external Web 2.0 tools and services.
Not all electronic conversations need to be kept. They only need to be captured when the conversation affects a decision being made or an action being taken by the government.
In a Web 2.0 environment, information created is often required only for a limited time to support the completion of a routine action, the preparation of a subsequent record, or casual communications.
In the same way as personnel treat a telephone conversation, if a decision is made, action taken, or the reason for a decision or action is discussed via an electronic conversation, the personnel is responsible for documenting that decision, action or rationale, and ensuring that the information is captured within the department's information repository.
Federal program information posted to Web 2.0 tools and services needs to be captured in departmental information repository as a record of the information on the program that has been distributed to Canadians.
E. Official Languages
Relevant Policy and Legislative Requirements
When determining departmental practices for the use of external Web 2.0 tools and services, departments are encouraged to seek the advice and participation of persons responsible for official languages and legal services within their organization.
Departments need to ensure that the use of Web 2.0 tools and services complies with the Canadian Charter of Rights and Freedoms (ss.16-20) and the Official Languages Act, including Part IV of the Official Languages Act and, consequently, the Policy on the Use of Official Languages for Communications with and Services to the Public, the Directive on the Use of Official Languages in Electronic Communications and the Directive on the Use of Official Languages on Web Sites. See the Treasury Board of Canada Secretariat website for current versions.
Federal departments must also comply with Part VII of the Official Languages Act in their use of Web 2.0 tools and services. This deals with the advancement of English and French, enhancing the vitality of linguistic minority communities as well as fostering the full recognition and use of both English and French in Canadian society.
Use of Official Languages and Web 2.0
For online communications, one of the vehicles for official dissemination of a department's information is its website. The application of Web 2.0 tools and services should be consistent with the Government of Canada's approach to Web sites. The department's terms of use for social media should be posted on their website to which users are referred through a link or web address.
Recommended Practices
Whether provided by Government of Canada or third-party Web 2.0 tools and services, departments must ensure that all profile content through all forms of communication originating from federal departments is made available simultaneously in both official languages and is of equal quality. This includes terms of reference, rules of engagement, and departmental positions and disclaimers. When the Web 2.0 tool or service is being provided by the Government of Canada, management and editing tools, help sections, pop-up messages, site navigation, as well as user interfaces (separate interfaces for each official language of equal quality) must be available in both official languages and be of equal quality. When using a third-party Web 2.0 tool or service, departments should strive to meet these obligations and assess whether the platform should in fact be used.
Users should be advised that by participating in Web 2.0 activities, they are consenting to the possibility that their comments could be summarized and translated by departments.
Where third-party Web 2.0 tools and services (e.g. Twitter, Facebook, YouTube) are used, the department should reference through profile information, the rules of engagement located on the department's website, including the official languages component.
Departments, as well as personnel communicating on behalf of their department when using Web 2.0 tools and services, must respect the concept of active offer of services by ensuring that the user knows communication is available in both official languages and can access the equivalent services in the other official language.
In all Web 2.0 initiatives aimed at the public, departments must:
- Encourage users to contribute in the official language of their choice;
- Use Web 2.0 tools and services that are conducive to the use of both official languages.
When considering using Web 2.0 tools and services being developed by the Government of Canada and/or hosted on Government of Canada networks, departments need to evaluate the extent to which these tools and services allow the department to comply with its official languages obligations. If these tools and services are not offered in both official languages, federal departments should opt for ones that allow them to comply with their obligations and that allow users to switch from one language to the other.
A department that posts information using Web 2.0 tools and services on the site of an entity or third party not subject to the Official Languages Act must ensure that:
- Information originating from the department is in both official languages;
- A notice precedes the information to indicate clearly that the information originates from that department.
Departments that re-disseminate third-party information should look for sources that release information in both official languages.
In order to foster the full use of English and French in Canadian society and to meet its obligations in relation to communications to the public, departments should carefully monitor both official language versions of the application used. When it appears that the department is receiving more public questions/comments in one language that require a general and public response, it should ensure that it provides the same information to the public in both official languages. Responses should be formulated in a way that allows all users to understand the nature of the initial query and are available in both official languages simultaneously. This can be done by summaries of discussions/questions that have taken place on both accounts or by referring the public to the information on its website. The summary should include discussions that have taken place on both language accounts and the sum total of the discussions posted in both languages.
Practical Tips for Complying with Official Languages Requirements:
- For most Web 2.0 tools and services, a single-language version (two accounts) is the recommended best practice. Departments should take measures to ensure, as much as possible, that users of both accounts have an equally profitable experience.
- All content (text, audio, video, etc.) should be posted simultaneously in both official languages through the respective departmental accounts.
- The equivalent account in the other official language should be clearly referenced with the appropriate link.
- Departments actively engaging in providing responses through Web 2.0 tools and services should do so in the language in which contact was initiated, unless it is a question of general public interest that requires a response in both official languages. If information is referenced pertaining to the department, it should direct users to their website where content is available in both official languages.
- Departments should carefully monitor both official language accounts of the Web 2.0 tool or service being used. When it appears that the department is receiving more public questions/comments in one language that require a general and public response, it should ensure that it provides the same information to the public in both official languages. Responses should be formulated in a way that allows all users to understand the nature of the initial query and are available in both official languages simultaneously. Departments should consider providing regular summaries of comments/questions which are posted in both official languages simultaneously.
- As a way of promoting linguistic duality, departments that re-disseminate third-party information should look for sources which release information in both official languages.
- The re-dissemination of unilingual third-party information items should not be a frequent and predominant method of disseminating information. If third-party information is circulated, the department informs the public through the rules of engagement located on its website that the information was obtained from an external source and that is not subject to the Official Languages Act.
- For collaborative technologies such as Wikis, the following practices should be followed:
- Departments should make content pages available in both official languages, and provide links between the English-language and French-language pages;
- When users are asked to edit pages they can do so in their preferred official language;
- Once the content is finalized and approved, it is posted in both official languages or a link to the final document where there are English and French versions is provided. Both versions are posted simultaneously and are of equal quality. The appropriate links are established between the English and French versions;
- In the case where the content does not reach a final version but continues to change as new events take place, the department determines at which point a significant version is attained. Significant versions are made available simultaneously in both official languages. A significant version represents an important step in the development of the content, one which allows the discussion or consultation to move on to a new phase in its progression. If the steps are not clearly defined, the project leader determines when a significant version is attained;
- Departments decide whether it is best to have one bilingual discussion page or two separate pages, one for each official language. Departments base this decision on consideration of different factors such as their objective, the intended public audience, relevance and the extent to which this Web 2.0 tool or service allows departments to fulfill their official languages obligations in conducting their particular consultation; and
- Departments should provide links between the English-language and French-language discussion pages when two discussions are being held concurrently.
- For media/file sharing tools and services, the following practices should be followed:
- In the production of video and audio, content should be made available in both official languages. The English-language and French-language versions should be equivalent in content and be of equal quality using identical formats.
- In cases where the media file is in one language only, departments should provide voice-over or subtitles or transcriptions for the version in the other language.
- Bilingual video that is posted on both sites should contain voice-over, where applicable, sub-titles or transcriptions in the other official language. Departments should plan videos to ensure that they are not creating a situation where one language is always a language of translation.
- For instant messaging/chat sessions, departments should determine whether it is best to hold a bilingual session or two separate sessions in each official language. If one bilingual session is held, the session organizers should actively encourage participants to use the language of their choice. Responses from the department should be formulated in a way that allows all users to understand the nature of the initial query and should be available in both official languages simultaneously.
Translation Software
The use of translation software or automated translations offered on web sites is not recommended for use in an official communications context given their current limitations and given the Translation Bureau's advice against their use. Departments are responsible for the content of the information they provide, even when the information is housed on third-party platforms, and would therefore also be responsible for the quality of translations generated by automated software.
F. Political Activities
Part 7 of the Public Service Employment Act (PSEA) governs the political activities of employees subject to its provisions, recognizing the need to balance the rights of employees to engage in political activities with the principle of a non-partisan and politically impartial public service. The PSEA also defines "political activity"; using Web 2.0 tools or services to express personal views in support of, or in opposition to, a political party or candidate is one example of a political activity. Employees must assess their own circumstances and make reasonable decisions about their involvement in political activities and determine whether a given activity would impair or could be perceived by others as impairing their ability to perform their duties in a non-partisan and politically impartial manner. They are encouraged to discuss their specific circumstances with their manager or with their organization's Designated Political Activities Representative.
It is important to know that anyone may put forward an allegation of improper political activity against employees subject to Part 7 of the PSEA. The Public Service Commission (PSC) may investigate these allegations and if it concludes, following an investigation, that an allegation is substantiated, it may take any corrective action it considers appropriate, up to and including dismissal.
It should be noted that activities that do not fit the above-mentioned definition may be subject to the Values and Ethics Code for the Public Service or, in cases where Treasury Board is not the employer, to the organization's applicable values and ethics code.
Any questions on Part 7 of the PSEA should be referred to the PSC or additional information found on its website.
G. Privacy and Access to Information
Before a government department initiates the use of an externally facing Web 2.0 tool or service, the Treasury Board of Canada Secretariat (TBS) strongly advises government officials to consult with their department's Access to Information and Privacy (ATIP) Office, Legal Services and security experts to ensure that all privacy risks are identified and addressed. ATIP officials can help to determine if it is necessary to notify the Office of the Privacy Commissioner of Canada and if a Privacy Impact Assessment (PIA) should be undertaken.
Personal information is information about an identifiable individual and includes names and occupations or contact information. If any personal information is collected, used and disclosed through government use of Web 2.0 tools and services, departments should be aware that such collection, use and disclosure is subject to the Privacy Act and may, in certain circumstances, engage section 8 of the Canadian Charter of Rights and Freedom. Under the Privacy Act, the Privacy Commissioner has the authority to receive and investigate privacy complaints against departments and can conduct audits of personal information practices, including those involving Web 2.0 tools or services, at government departments.
Requirements of the Privacy Act concerning the Collection, Use and Disclosure of Personal Information
Section 4 of the Privacy Act states that "no personal information shall be collected by a government institution unless it relates directly to an operating program or activity of the institution." This has been interpreted to mean that a department must have parliamentary authority in an Act or Regulation, or authority provided by an Order in Council, for the collection of personal information related to the program or activity that will be administered through the Web 2.0 tool or service. The authority for collection is a requirement of the Privacy Act whether the Web 2.0 tool or service is hosted by the department or by a third party.
Departments should use and disclose personal information posted through a Web 2.0 tool or service only for the purposes for which it was collected unless an individual posts inappropriate comments or where the department suspects that a law has or will be been broken. In such a case, the personal information disclosed would have to be retained in accordance with section 6 of the Privacy Act. Unsolicited information will be deleted, except where action is required to protect a public or private interest (e.g. someone reports a crime or threat to security).
Privacy Impact Assessment Requirements
Under the TBS Directive on Privacy Impact Assessment, departments are required to conduct a PIA for any new or substantially modified program or service that collects and uses personal information, including those involving Web 2.0 tools and services. A PIA will help to ensure that the Web 2.0 initiative complies with the Privacy Act and that measures are implemented to mitigate any potential privacy risks.
A PIA may be required even when the Web 2.0 initiative involves a minimal collection of personal information (e.g., names and passwords to authenticate individuals to give them access to a wiki or blog).
Furthermore, the PIA requirement may apply whether a Web 2.0 tool or service is hosted by the department or a third party. A PIA will help identify the intended uses and disclosures of personal information that should be described in a Privacy Notice.
Under the Directive on Privacy Impact Assessment, departments must provide a copy of the completed PIA to TBS and the Office of the Privacy Commissioner of Canada. For more information about PIA requirements, refer to the Directive on Privacy Impact Assessment.
Privacy Protocol
The Policy on Privacy Protection requires that departments establish a privacy protocol which may be used in place of a PIA in instances where a department collects and uses personal information for non-administrative purposes only, i.e., where no decisions will be made that affect the individuals. For example, surveys may be conducted on an external Web 2.0 tool or service, where no follow-up will take place with the individuals and no decisions will be made by the department that directly affect the individuals.
Privacy Notice
Once the department confirms that it has the authority to collect or use personal information for the purposes of the Web 2.0 initiative, and has addressed or mitigated any privacy risks, it must then post an appropriate Privacy Notice to inform users of their rights under the Privacy Act.
The requirement is based on subsection 5(2) of the Privacy Act, which specifies that a government department must inform any individual from whom the department collects personal information about the purpose for which the information is being collected.
The Directive on Privacy Practices requires that a Privacy Notice be provided to individuals. A sample Privacy Notice is available on GCpedia for Government of Canada personnel to consult.
Access to Information and Privacy (ATIP) Requests
The Access to Information Act gives rights of access to records and the Privacy Act give rights of access to information under the control of a government department. Any request to a government department that is made under either Act for access to information posted on a Web 2.0 tool or service must be addressed by the department. For further guidance, government officials are directed to consult with their department's ATIP Office.
Web 2.0 Tools or Services Hosted or Owned by Third Parties
Departments may choose to use third-party Web 2.0 tools or services to communicate on behalf of the department. In such cases, the department should establish specific terms and conditions with the provider to ensure the protection of personal or other sensitive information. It is strongly recommended that, before negotiating any such contractual arrangement, the department should consult its ATIP, Legal Services and security experts. Whenever possible, departments should use custom terms of service that have been negotiated by PWGSC for some third-party Web 2.0 tools and services. For more information on how to do so, please refer to the "Social media procurement process" page on GCpedia.
Departments should consider the ATIP implications of using sites that are hosted or owned by third parties, particularly if such sites are based in foreign countries or accessible by companies located in foreign countries. It may be necessary to conduct a PIA or Threat Risk Assessment to ensure privacy risks are identified and mitigated. When information is stored or accessible outside of Canada, it can be subject not only to Canadian laws, but also to the laws of the hosting country. For more information, refer to the TBS guidance document Taking Privacy into Account Before Making Contracting Decisions.
H. Procurement and Contracting
If the acquisition of a Web 2.0 tool or service has costs associated with it, consult your departmental procurement and contracting experts for guidance. These costs include either the upfront procurement cost or the requirement for non-competitive maintenance and operations of the platform. The principles underlying the procurement framework are openness, fairness and transparency for suppliers and effectiveness and efficiency in meeting government needs. Full costs of the Web 2.0 tools and services need to be assessed up front to ensure that the appropriate acquisition steps are followed.
Departments must determine if they will accept the terms of service for the Web 2.0 tool or service being considered for use. In making this determination, departments are encouraged to seek the advice and participation of persons responsible for procurement and legal services. For information on accessing custom terms of service that have been negotiated by PWGSC for some no-cost Web 2.0 tools and services, please refer to the "Social media procurement process" page on GCpedia.
Responsibilities of Government Organizations
This section identifies the responsibilities of government organizations regarding procurement as set out in various Acts of Parliament, regulations and policies. This section does not confer any authority or responsibility on any organization.
Treasury Board Secretariat
The Secretariat supports the Treasury Board in its role as the government's management board. The Secretariat is responsible for maintaining an ongoing relationship with departments to address management issues and to ensure compliance with the Contracting Policy and related policy instruments through management reviews, evaluations, Auditor General audits, internal audits and transactions. The Secretariat also develops federal government administrative policies for procurement and for a broad range of areas that have an impact on procurement, such as financial management, materiel management, communications, delegation of authority, project management and investment planning. In addition, the Secretariat manages a certification program for federal procurement and materiel management personnel.
Public Works and Government Services Canada
The mandate of the Minister of Public Works and Government Services includes planning and organizing the provision of materiel and related services to departments and the acquisition of goods, services and construction services for departments. The Department of Public Works and Government Services Act states that the Minister shall investigate and develop services for increasing the efficiency and economy of the federal public administration and for enhancing integrity and efficiency in the contracting process.
Section 9 of the Department of Public Works and Government Services Act gives the Minister of Public Works and Government Services exclusive responsibility for the procurement of all goods as described in the Act. Other departments may procure goods only when their own legislation specifically permits or when an appropriate delegation of authority has been made by the Minister of Public Works and Government Services.
Risk
As a general principle, risks should be borne by the party best placed to manage them, that is, departments should generally not accept risks that another party is better placed to manage. In accordance with the Policy on Decision Making in Limiting Contractor Liability in Crown Procurement Contracts, procurement specialists should strive to achieve a balance among the protection required by the Crown when entering into Crown procurement contracts, marketplace conditions, and conditions important for assuring program and service delivery results. Note that there must be an individual risk assessment for each of the Government of Canada's Web 2.0 initiatives that have a cost associated with the use of the respective tool or service. Conducting a risk assessment remains a good practice in the case of using no cost Web 2.0 tools and services.
Documentation
Documentation is critical to accountability and transparency. It provides a record of procurement activities and how they have been conducted, and it facilitates management oversight and scrutiny of these activities.
Government Contracts Regulations
The Government Contracts Regulations (GCRs) were approved pursuant to subsection 41(1) of the Financial Administration Act. It is not always possible, practical or cost-effective to seek bids for every proposed contract. Section 6 of the GCRs permits certain exceptions that provide contracting authorities with the flexibility to negotiate a contract with a particular supplier on a non-competitive (sole-source) basis. Section 6 of the GCRs addresses the more compelling cases where exceptions to competition are warranted, as in the case of Web 2.0 tools and services when the estimated expenditure does not exceed $25,000.
Control of Assets
The Policy Framework for the Management of Assets and Acquired Services states that the following:
Deputy Heads are accountable to their respective Ministers and to Treasury Board for the management of assets and acquired services in departments. They are responsible for implementing an effective management framework, including departmental procedures, processes and systems, that demonstrates how the department is managing based on the principles identified above. The framework must demonstrate how the management of assets and acquired services is effectively integrated with program, expenditure, financial and human resources related considerations to promote value for money.
Related Policies, Regulations and Directives
I. Security
A number of the requirements of the Operational Security Standard: Management of Information Technology Security (MITS) pertain to the use of external Web 2.0 tools and services. Departments that choose to make use of externally facing Web 2.0 tools and services for conducting official Government of Canada business should undertake the following actions:
- Assess and document the sensitivity of information that will be transmitted, stored and processed using Web 2.0 tools and services (in accordance with MITS, section 12.2);
- Ensure that any unique risks to information, Information Technology (IT) assets and service delivery associated with the use of Web 2.0 tools and services are assessed, documented and understood, and that residual risks are accepted by program or service delivery managers (in accordance with MITS, section 12.3);
- Formally document roles and responsibilities of personnel who will engage in the use of Web 2.0 tools and services;
- If the Web 2.0 tool or service is hosted by the department, ensure that it is located in an appropriate network zone, that it is regularly monitored for vulnerabilities and configuration weaknesses, and that an appropriate patch management schedule is maintained;
- Ensure that appropriate authentication and integrity controls are in place for Web 2.0 tools and services to prevent impersonation of Government of Canada entities;
- Ensure that, where applicable and appropriate, information-sharing agreements are established and respected;
- Ensure that, where applicable, incident management procedures have provisions to address incidents relating to, or resulting from, the use of Web 2.0 tools and services; and
- Ensure that personnel who will be using Web 2.0 tools and services are provided with appropriate IT security and information classification training (in accordance with MITS, section 12.12).
Departments should also consult SPIN 2010-01: Security Considerations when Allowing Connections to Public Social Networking Sites, which states that: "From an IT Security stand point, connections to social networking sites are not substantially different than other connections to the Internet and will not normally require a new Threat and Risk assessment by each department".
For further information, departments should contact their departmental security officials, CSEC client service representative or visit CSEC's website.
J. Values and Ethics
A public servant's public activity is subject to the Values and Ethics Code for the Public Service. Web 2.0 activity is considered public activity and as such is subject to the Values and Ethics Code for the Public Service. The following excerpts from the Code help to illustrate how public service values can be applied to the use of Web 2.0 tools and services:
Democratic Values
Public servants shall loyally implement ministerial decisions, lawfully taken.
In Canada's system of parliamentary democracy, public servants owe a duty of loyalty to their employer, the Government of Canada. This includes refraining from any activity that could compromise the efforts of Government organizations to deliver on their mandate.
An employee's public commentary (including online activity on blogs and other social media platforms) about an organization, including its minister, is subject to scrutiny under the duty of loyalty requirement.
Only those employees specifically designated as spokespersons are to publicly comment on government operations.
Professional Values
Public servants must work within the laws of Canada and maintain the tradition of the political neutrality of the Public Service. Public servants should also strive to ensure that the value of transparency in government is upheld while respecting their duties of confidentiality under the law.
The Public Service Employment Act states that a public servant can engage in any political activity as long as it does not impair or is not perceived by others as impairing his/her ability to perform his/her duties in a politically impartial manner.
Promoting political ideas online may appear to compromise an employee's ability to maintain impartiality. Before engaging in online political activity, an employee should subject him/herself to the Political Activity Self-Assessment Tool, provided by the Public Service Commission to assess his/her particular circumstances for risk.
Ethical Values
Public servants may take part in outside activities unless the activities are likely to give rise to a conflict of interest or in any way undermine the neutrality of the Public Service. The Deputy Head may require that the outside activities be curtailed, modified or terminated if it is determined that real, apparent or potential conflict of interest exists.
Avoiding and preventing situations that could give rise to a conflict of interest, or the appearance of a conflict of interest, is one of the primary means by which a public servant maintains public confidence in the impartiality and objectivity of the Public Service. Employees should review their online presence and associations regularly and report any potential areas of concern with their manager.
People Values
People values should reinforce the wider range of Public Service values. Public servants should demonstrate respect, fairness and courtesy in their dealings with both citizens and fellow public servants.
Making a comment about a colleague or client online may be subject to scrutiny, just as making that same comment in the workplace would be. Employees should familiarize themselves with the Policy on the Prevention of Harassment in the Workplace and act towards other individuals professionally and respectfully.
For further information concerning the interpretation or application of the Values and Ethics Code for the Public Service, employees should talk to their supervisor or contact the senior official for values and ethics in their organization.
How Italian Public Bodies make use of Twitter by giovanniarata in Internet & Technology, Research, and administration
Analysing the actual deployment of e-Gov practices by Italian Public Bodies [Survey]
This Report provides a snapshot and an analysis of the state of progress of the application of e-Gov in Italy and at the level of the local communities. The aim of this “atlas” is to reconstruct and map the changes which are underway in order to gather, measure and make visible the results (that are at times scattered or insufficiently known) and the innovation processes accomplished by the whole of the public administration, especially the local administration.
Contributions to this Report, realized by the Department for Digitization of the Public Administration and Technological Innovation (DDI) and by DigitPA upon specific request by the Standing Committee for the Technological Innovation of Regions and Local Authorities, have been made by the Central Administrations, the Regions and representatives of the Provinces and Municipalities.The e-Gov Plan clearly sets out the priorities to be pursued at the various levels of government and defines a set of digital innovation projects designed to modernize, make more transparent and more efficient the entire public administration (in both the North and South, in the central and peripheral areas of the Country), improving the quality of services delivered to citizens and businesses and cutting costs for the community.
The encouraging results obtained during these years suggest that the direction we are moving in is right. However, we don’t have a precise picture of the changes under way. And this is all the more negative if one considers that the Country – especially in this area – presents major inequalities which often go beyond the traditional classifications by macro-areas, by region and in general by geographic categories.
It is therefore necessary to take a magnifying glass, go down to the community level and analyze and classify the various experiences, local solutions and best practices. And this should not (or not only) be done because we want to offer models capable of being inclusive, but in order to take into account and give visibility to the many local experiences, sensitivities and innovative cultures that the Country is expressing in the North as in the South, at the centre as in the periphery.At the heart of this “atlas” therefore there is the local dimension of e-Government: a snapshot of the solutions that the PA has achieved at the local level, in the local administrations, and in the decentralized offices of the central PA. This explains why, in this first Report, albeit being aware of the importance of the systems related to the great platforms for taxes, social security and business demographics, it was decided to focus on analyzing the other themes to which the e-Government plan attaches priority.
The method is based on taking pictures at the “local level” in order to understand what can be expected – immediately and by everyone – thanks to an accountable administration which, by going against the traditional idea of bureaucracy, puts itself actively at the service of citizens and businesses. An analysis is made of the components that make up the local level in order to learn from local success stories, understand how and where to get value for money, and focus commitment on all those actions that are capable of ensuring, from North to South, a convergent and unifying development.
Only in this way, and only thanks to the contribution of all the players who operate locally, is it possible to imagine a transparent, dynamic and credible administration that is worthy of a leading democracy, the ideal place for an exchange of ideas and innovative solutions, interpreter of the needs of a society that urges its governors to respond more effectively to the challenges posed by current changes.
The Report consists of two parts. By retracing the priority actions for developing e-Gov in Italy, the first part gives a snapshot of the changes under way, describing the renewal process that is involving the PA across the Country. The second part contains 21 fact sheets or progress reports of the Country’s 21 Regions showing the progress achieved in each thematic area.
You can download the entire report using the link below
(Download free but registration required)
2010 e-Gov Report Italy
An important role of technology journalists in the 21st century is to explain how broader trends that are changing technology, government and civic society relate to average citizens. Some have called this broader trend towards smarter, more agile government that leverage technology “Gov 2.0.” (Readers of this blog are no doubt familiar with the term.) When you dig into the topic, you can get stuck in a lot of buzzwords and jargon quickly. Most people don’t care about how a satellite gets into orbit, the release of community health data or the standards of an API for product recalls. They care quite a bit, however, about whether their GPS receiver enables them to get to a job interview, if a search engine can show them ER waiting room times and quality statistics, or if a cradle for their baby is safe. Those wonky policies can lead to better outcomes for citizens.
If you follow Mashable, you might have read about the ways that social media promotes good health or how government works better with social media.
The following stories have little to do with technology buzzwords and everything to do with impact. Following are five stories about government 2.0 that matter to citizens, with issues that literally come home to everyone.
1) The Consumer Product Safety Commission has launched a public complaints database at SaferProducts.gov. You could think of it as a Yelp for government, or simply as a place where consumers could go to see what was safe. Add that to the mobile recalls application that people can already use to see whether a product has been recalled.
2) The new Consumer Financial Protection Bureau will use technology to listen to citizens online to detect fraud. If you haven’t heard, DC has a new startup agency. That hasn’t happened in a long time. Your could think of it as Mint.gov mashed up with HealthCare.gov. The CFPB plans to use technology in a number of unprecedented ways for fraud detection, including crowdsourcing consumer complaints and trends analysis. Given how much financial fraud has affected citizens in recent years,and how much of the anger that the public holds for the bailouts of banks remains, whether this agency leveraging technology well will matter to many citizens.
3) Social data and geospatial mapping join the crisis response toolset. Historic floods in Australia caused serious damage and deaths. Government workers used next-generation technology that pulled in social media in Australia and mapped the instances using geospatial tools so that first responders could help citizens faster, more efficiently and more effectively. It’s an excellent example of how an enterprise software provider (ESRI) partnered with an open source platform (Ushahidi) to help government workers use social media to help people.
4) New geolocation app connects first responders to heart attack victims.The average citizen will never need to know what Web 2.0 or Gov 2.0 means. Tens of thousands, however, will have heart attacks every year. With a new geolocation mobile application that connects citizen first responders to heart attack victims, connected citizens trained in CPR now have a new tool to help them save lives.
Better access to information about food safety, product recalls and financial fraud will help citizens around the country. Improvements to the ability of government workers to direct help in a disastrous flood or for citizens to receive immediate help from a trained first responder in an emergency are important developments. As 2011 takes shape, the need for government to use social media well has become more important than ever. That’s why the perspective of government officials like FEMA administrator Craig Fugate matter.
“We work for the people, so why can’t they be part of the solution? “ said Fugate, speaking to delegates from the distributed chapters of Crisis Commons assembled at FEMA headquarters. “The public is a resource, not a liability.”
For example, Fugate said that FEMA used reporters’ tweets during Hurricane Ike for situational awareness. “We’ve seen mashups providing better info than the government.” Listening and acting upon those digital cries for help on social media during crisis could literally be a matter of life and death.
Whether government can adapt to a disrupted media landscape and the new realities of information consumption is of substantial interest to many observers, both inside and out of government. Whether government can be smarter, agile and more effective is a great interest to all.
How are Governments worldwide dealing with Social Media [via @Elena2020]
This is all part of a historic continuum, as Adam Conner, Facebook's first staffer in Washington, D.C., reflected in an essay shared with this correspondent.
When the use of the telephone became widespread, the ability to establish instantaneous audio communication between two separate points was a game-changer for government agencies. They no longer needed to rely solely on in-person meetings or written correspondence for communication and operations and service became many times faster, more efficient and more personal.
We believe that social media can be similarly transformative to the way government and constituents interact. While it is possible in the first years of a new communication technology to delegate responsibility and knowledge to a few individuals, as adoption grows, it becomes impossible, impractical, and inefficient to silo that knowledge in one place. This was definitely true of the telephone.
The telephone shifted the way that everyone in the government conducted business on a daily basis. It didn't just affect GS-8 level "Telephone Specialist" government employees. Inevitably, everyone had to have a phone and know how to use one. Understanding how to use phones, email, social media, and the next big thing won't be a requirement -- it'll be so expected that to encounter someone who doesn't will give you genuine pause.
Today, there are still people who install and repair phones but there's no one around who teaches you to pick up the phone when it makes a noise and say hello. In the same way, the duties of "Online Communication Specialist" and "New Media Director" are important and their work will continue for years to come. But these specialized jobs related to using a new technology will eventually fade away as they are integrated into the broader areas they fill. And the title "New Media Director" may become as commonplace as "Director of Two-Way Wirebound Audio Communication."
By Alexander B. Howard, The Atlantic
Editor's Note: For good or for ill, governments have to deal with social media. In Cairo and London and Washington, the way people organize themselves is changing -- and governments are struggling to adapt, adopt, co-opt, or disable the technologies that enable these changes. Here, O'Reilly Media's Government 2.0 correspondent takes a step back and surveys the landscape at the crossroads of social media and political power in the summer of 2011.
In the 1990s, the Internet changed communication and commerce forever. A decade later, the Web 2.0 revolution created a new disruption, enabling hundreds of millions of citizens to publish, share, mix, comment, and upload media to a more dynamic online environment. That two-way communication, enabled by new, highly accessible and scalable Web technologies, is generally called "social media." In the years since the first social networks went online, the disruption has spread to government, creating shifts in power structures as large as those enabled by the introduction of the printing press centuries ago.
"Connection technologies, including social media, tend to devolve power from the nation state and large institutions to individuals and small institutions," Alec J. Ross, senior innovation adviser to Secretary of State Hillary Clinton, said in an interview. "Nothing demonstrated that more than the power to publish and distribute at great scale by historically disempowered individuals with inexpensive devices."
For a recent example, consider the role of social media in revolutions in Tunisia and Egypt, where YouTube, Facebook, and Twitter acted in combination with Al Jazeera and mobile phones to catalyze reactions to deep-seated repression. "If governments are not engaging in social media, they are essentially ceding influence and power," said Ross.
It also provides new capabilities and opportunities to work with the public in collaboration, co-creation or oversight. Social media is changing how state and local government elections are covered, including fraud or corruption reporting. In California, social media is connecting citizens to e-services, and it is an elemental component of New York's bid to be the nation's premier digital city. In Washington and other capitals around the world, legislatures and executive offices now operate in a 24-hour stream of live updates and discussion. This January, the Congressional transition was streamed live online, as well as on Twitter and Facebook. After President Obama's historic speech on Middle East policy, the White House turned to Twitter to discuss it.
"Social media allows for more distributed communication and collaboration when natural or man-made crises occur," said Ross. "This allows for faster and more inclusive, broadly participatory responses to life and death situations." For example, in Australia, social media and geospatial mapping helped crisis responders deal with historic floods. In San Francisco, city services, 311 and Facebook are enabling new ways of solving civic issues.
Latest Politics Posts:
Loading feed...Mainstream media is increasingly merging with social media. Last year, more citizens experienced "Twitter TV" during sporting events like the World Cup. This fall, Facebook and NBC will co-host the Republican primary debate. (Don't get lost in the glitz of social media, though: Election 2012 will be about the data.) In June 2011, Google launched YouTube for Government, offering civic leaders around the world a platform to reach all connected citizens.
Social media does present novel risks and rewards for government beyond the changes wrought by telegraph, telephone, and television. Social media creates new online privacy challenges for citizens and government alike. It presents a real headache for the government employees entrusted with records management. A recent GAO report highlighted the need for consistent social media policies that address security, privacy, and records keeping.
Under repressive governments and autocracies, social media can act as a tool of oppression as well as freedom. Congress faces challenges in identifying constituents using social media. That said, the Internet has become the public arena for our time. One challenge is that third-party platforms control this 21st-century public square, creating novel issues for government's relationship with the technology companies that host civic dialogue.
After the president and House speaker addressed the nation on the debt crisis and called for public support, House and Senate websites were swamped with electronic interest. Many citizens turned to Facebook and Twitter to contact congressional staffers on social media expecting to be heard.
The White House has turned to social media to advocate for #compromise, starting with a tweet from the president himself on his campaign account. The subsequent ripple of feedback suggested the influence of political communication over social networks. Statistics provided via e-mail by Twitter government liaison Adam Sharp offer more data about Twitter : "Tweets regarding #debt & related keywords peaked two times" during the last week of the debt ceiling debate, according to Sharp, driven by Monday's primetime speeches and Friday's "Call to Tweet." Further, Sharp wrote that @mentions of members of Congress increased three times from Friday over Thursday, a five-fold increase over the previous week's average. White House communications director Dan Pfeiffer affirmed to New York Times reporter Brian Stelter that e-mail and tweets from constituents influenced Sunday's debt ceiling deal, along with phone calls. Fittingly, perhaps, the interaction between the two men happened over social media.
During these dog days of summer, we've also seen massive dissatisfaction with elected representatives expressed by citizens using social media, including the anti-Washington hashtag Jeff Jarvis started during the debt-ceiling debate. Social media platforms will continue to reflect both that tension and a reality. While technology empowers citizens to have a real-time conversation with their governments, the men and women entrusted with making laws and policies will find better ways to govern amid the tumult. Congressional staffers are on social media but, as Nick Clark Judd pointed out, "it bears mentioning that the conversation that congressional staffers are listening to on social media is the same one they've been in for years."
Whether or not social media played a critical role in the debt ceiling debate, Middle East revolutions or the 2008 and 2010 elections, one truth has become even more clear in the summer of 2011: these channels now complement the use of phone, email, txts and television in the business of government, and they're not going away.
Alexander B. Howard is the Government 2.0 Correspondent for O’Reilly Media and a technology writer focused on open government, innovation, and online civics.
Want to stay ahead of the curve? Sign up for National Journal’s AM & PM Must Reads. News and analysis to ensure you don’t miss a thing.
What does the Community Manager of a municipality social space actually do? [Italian]
Nell'attuale vuoto normativo per i ruoli della comunicazione 2.0 (che ci rimanda solo alla legge 150/2000) molti enti hanno attivato di propria iniziativa le pagine ufficiali sui Social Media.
Il più frequentato dalla PA è sicuramente Facebook, seguito da YouTube e poi Twitter che, essendo un sito di microblogging in 140 caratteri, funge spesso solo da volano alle notizie che appaiono altrove.Le ricerche pubblicate finora sull’uso di questi canali, alternativi al sito ufficiale, non danno risultati incoraggianti: nel maggio 2011, secondo la ricerca di Francesco Pavan, solo 4 regioni su 20 hanno un account Facebook, mentre i comuni capoluogo di provincia con una pagina ufficiale sono 21 su 117. Youtube invece è scelta da 11 regioni su 20, e da 22 comuni capoluogo su 117. Secondo la ricerca di Giovanni Arata (#TwitterPA) 7 regioni su 20 hanno un loro account Twitter, ma il trend di crescita non è cosi alto cosi come lo è per i privati, che negli ultimi mesi hanno più che raddoppiato le iscrizioni.
Questi dati si riferiscono sopratutto al 2010 e siamo in attesa di nuove ricerche, ma al momento non si può certo dire che il trend sia in rapida ascesa.Eppure i tagli alla comunicazione e alla pubblicità (L. 122/2010) potevano far lanciare le pagine sui Social Media in modo definitivo essendo a costo zero e molto frequentate; anche per rinnovare URP desueti e per rilanciare in modo diverso le notizie dai i portali istituzionali, ormai veicoli di pubblicità legale e vincolati dal CAD e dalle linee guida (per i siti web PA e per l’accessibilità).
Per questo credo che sia giunta l'ora di inserire nella PA anche profili che abbiano le competenze digitali giuste per questi settori.Il community manager
Cominciamo con il Community Manager. E cominciamo dicendo subito che non ci si improvvisa CM, ci sono manuali che spiegano molto bene quali sono le abilità che devono essere acquisite e il ruolo che hanno all'interno di una strategia aziendale.
Molte PA si sono affidate a servizi esterni perfetti per lo Startup, ma perché non provare a farlo direttamente in house? D'altronde la stessa manovra sopracitata esorta gli enti a valorizzare le professionalità interne ed evitare il più possibile l'affidamento a specialisti e consulenti...Prendendo spunto dagli skill profiles elaborati dall’IWA, esistono delle abilità di base specifiche:
- Saper lavorare con la gente;
- Saper Lavorare in gruppo;
- Conoscere il linguaggio HTML;
- Conoscere il marketing non convenzionale;
- Conoscere il linguaggio di scrittura del web;
- Conoscere la normativa che presiede sia la PA che il diritto d’autore;
- Avere buona padronanza della lingua (almeno quella madre).
Non essendoci alcuna normativa che vieti o obblighi la PA ad avere un CM saranno sicuramente competenze e servizi che si vanno a sommare agli altri offerti dalle URP e, dunque, potranno solo migliorare l'immagine e la comunicazione dell'ente.
Le competenze qualificanti (di secondo livello) sono invece:
- Pubbliche relazioni;
- Promozione di eventi;
- Pianificazione di eventi.
Tutte già prerogative del front office e dei responsabili URP ( L.150/2000).
Competenze e comportamento in rete
Dunque proviamo ad elaborare e definire meglio le competenze di un buon Community Manager della PA.
Prima di tutto conoscere le norme e le leggi che regolano la pubblica amministrazione. Un CM deve saper rispondere alle esigenze dei cittadini nei tempi e nei modi che la legge prevede.
Senza la conoscenza del diritto amministrativo e delle leggi che regolano i procedimenti e gli atti non è possibile poter stabilire un dialogo costruttivo coi cittadini che chiedono informazioni via web. (Le conoscenze tecniche di informatica devono ovviamente esserci. Le diamo per scontate).Il CM della PA deve essere flessibile e creativo, abile e convincente. Calmo e riflessivo. Assertivo e mai polemico.
Deve sempre rispondere a nome dell’amministrazione. Dunque non deve mai porsi in prima persona né utilizzare la pagina per rispondere con toni troppo amichevoli o “pressapochisti”.
Non c’è cosa che da sempre irrita di più il cittadino dell’impiegato pubblico maleducato o incompetente. Far finta di sapere è sempre sbagliato, conviene sempre e comunque rispondere con una frase del tipo :“giro subito la domanda al funzionario competente così da darle una risposta certa”.
La professionalità non si lede certo con le ammissioni di ignoranza e comunque si conferma con l'impegno a dare una risposta tempestiva.Non prendere mai iniziative da solo. Discutere di ogni “lancio” di evento sia nei modi e nei tempi col responsabile della comunicazione e con i promotori soprattutto con gli amministratori quando si tratta di eventi politici e organizzati direttamente da loro.
Si parla di cose che riguardano direttamente l’ente e solo di queste. Non si promuovono iniziative di privati. Non si condividono eventi non promossi e patrocinati dall’Ente e, invece, per questi non si fanno distinzioni di sorta. Tutti devono essere condivisi e promossi.
Si deve seguire ogni discussione 24h. (un flame può scoppiare in qualunque momento per cui il monitoring periodico è importante).
Devono essere condivise solo le notizie uscite dall’agenzia di stampa o quelle pubblicate sul portale dell’Ente. No a link a quotidiani, agenzie, blog che non siano di proprietà dell'ente.
Gli aggiornamenti in bacheca devono essere scritti con poche parole, chiare e precise. Linkare l'evento al portale riportando luogo data e titolo dell’evento nello status. Nessun commento o giudizio di valore sul contenuto né descrizioni prolisse. Evitare il copia e incolla di interi comunicati stampa nello status .
Mai cancellare i commenti o moderarne i contenuti. Tanto qualcun altro li segnalerà e saranno direttamente gli amministratori di Facebook (o Youtube o altro) a rimuovere i contenuti inopportuni.
Qualche consiglio per l’utilizzo dei principali social network
- Per quel che riguarda Youtube dà molta visibilità e offre un ottimo servizio gratuito di SEO (ottimizzazione del posizionamento sui motori di ricerca). Ricordiamo che i video visti su Facebook non implementano i numeri di visualizzazioni dunque in questi casi conviene anche farli embeddare dai giornali online e TV.
L'uso di Youtube serve anche a liberare dati dal server. Niente più FTP o chiavette USB. Questo risponde anche ad uno dei principi della pubblica amministrazione: l’economicità.- Twitter è ancora in mano a pochi enti, ma alcuni comuni sono riusciti ad utilizzarlo al meglio.
L’esempio del Comune di Genova durante l'alluvione che la colpito il territorio è quello di aver reso un servizio davvero utile ai cittadini in quei momenti di panico e disagio (aiuto che avrebbe potuto essere più efficace se fosse stato accompagnato da alcuni accorgimenti da utente esperto, come l’uso degli hashtag). Calcolando anche che per diverse ore molte zone erano senza elettricità l’unico modo che molti hanno avuto per tenersi aggiornati era collegarsi con lo smartphone.- Non dimentichiamo Flickr per l'hosting fotografico. Oltre a liberare i server mantiene la proprietà sulle foto. Dunque prima caricare le foto su Flickr poi linkarle su Facebook (i due siti hanno politiche sulla gestione dei contenuti molto diverse, ed occorre controllarle sempre - anche per la privacy policy - prima di utilizzare qualunque nuovo servizio on line).
- Altro servizio che può essere usato è Tumblr, un servizio di blogging gratuito. Utile per un grande evento, per una manifestazione, per un progetto da condividere. Ha template gratuiti e applicazioni specifiche per i singoli dispositivi (pc, smarphone, tablet etc).
- Non parlo di come utilizzare Google+ perché avendo Google cambiato totalmente la sua privacy policy non ci sono ancora sufficienti analisi per verificare la compatibilità con la nostra normativa, solo esempi diametralmente opposti: il garante della privacy norvegese che vieta l'uso dei servizi di Google apps per dubbi sulla conservazione dei dati e il Presidente Obama che risponde ai cittadini in diretta via web con servizi di Google (con oltre 130.000 domande inviate dai suoi cittadini). Attendiamo dunque analisi accurate anche da noi per capire come poter usare i tanti servizi che Google oggi offre.
Un Community Manager dentro la PA può solo contribuire a migliorare la comunicazione avendo a disposizione anche una grande risorsa altrimenti indisponibile: il feedback del pubblico in tempo reale. L'esempio della conferenza via web di Obama ne è una conferma e in campagna elettorale si può immaginare quanto siano utili questi "sondaggi popolari" a costo zero.
* Francesca Sensini è Web Content Editor al Comune di Città di Castello
Strategies and tactics for Municipalities aiming at going social [presentation]
Social media strategies, tactics and policies for governments.
The British Government has launched a beta of its GOV.UK platform, testing a single domain for that could be used throughout government. The new single government domain will eventually replace Directgov, the UK government portal which launched back in 2004. GOV.UK is aimed squarely as delivering faster digital services to citizens through a much improved user interface at decreased cost.
Unfortunately, far too often .gov websites cost millions and don't deliver as needed. GOV.UK is open source, mobile-friendly, platform agnostic, uses HTML5, scalable, hosted in the cloud and open for feedback. Those criteria collectively embody the default for how government should approach their online efforts in the 21st century.
“Digital public services should be easy to find and simple to use - they must also be cost effective and SME-friendly," said Francis Maude, the British Minister for the Cabinet Office, in a prepared statement. "The beta release of a single domain takes us one step closer to this goal."
Tom Loosemore, deputy director of government digital service at UK Government, introduced the beta of GOV.UK at the Government Digital Service blog, including a great deal of context on its development and history. Over at the Financial Times Tech blog, Tim Bradshaw has published an excellent review of the GOV.UK beta.
As Bradshaw highlights, what's notable about the new beta is not just the site itself but the team and culture behind it: that of a large startup, not the more ponderous bureaucracy of Whitehall, the traditional "analogue" institution..
GOV.UK is a watershed in how government approaches Web design, both in terms of what you see online and how it was developed. The British team of developers, designers and managers behind the platform collaboratively built GOV.UK in-house using agile development and the kind of iterative processes one generally only sees in modern Web design shops. Given that this platform is designed to serve as a common online architecture for the government of the United Kingdom, that's meaningful.
“Our approach is changing," said Maude. "IT needs to be commissioned or rented, rather than procured in huge, expensive contracts of long duration. We are embracing new, cloud-based start-ups and enterprise companies and this will bring benefits for small and medium sized enterprises here in the UK and so contribute to growth.”
The designers of GOV.UK, in fact, specifically describe it as "government as a platform." It's code that others can build upon. It was open from the start, given that the new site was built using open source tools. The code behind GOV.UK was released as open source code on GitHub.
Things like code for @govuk being on github is a pretty big deal. Proper bold statement of a new kind of culture. Respect #gov20
— Dominic Campbell (@dominiccampbell) January 31, 2012"For me, this platform is all about putting the user needs first in the delivery of public services online in the UK," said Mike Bracken, executive director of government digital services. Bracken is the former director of digital development at the Guardian News and Media and was involved in setting up MySociety. "For too long, user need has been trumped by internal demands, existing technology choices and restrictive procurement practices. GOV.UK puts user need firmly in charge of all our digital thinking, and about time too."
The Gov.UK stack
Reached via email, Bracken explained more about the technology choices that have went into GOV.UK, including a platform diagram, below.
Why create an open source stack? "Why not?" asked Bracken."It's a government platform, and as such it belongs to us all and we want people to contribute and share in its development."
While many local, state and federal sites in the United States have chosen to adapt and use Wordpress or Drupal as open government platforms, the UK team started afresh.
"Much of the code is based on our earlier alpha, which we launched in May last year as an early prototype for a single platform," said Bracken. "We learnt from the journey, and rewrote some key components recently, one key element of the prototype in scale."
According to Bracken, the budget for the beta is £1.7 million pounds, which they are running under at present. (By way of contrast, the open government reboot of FCC.gov was estimated to cost 1.35 million dollars.) There are about 40 developers coding on GOV.UK, said Bracken, but the entire Government Digital Service has around 120 staff, with up to 1800 external testers. They also used several external development houses to complement their team, some for only two weeks at a time.
Why build an entirely new open government platform? "It works," said Bracken. "It's inherently flexible, best of breed and completely modular. And it doesn't require any software licenses."
Bracken believes that the GOV.UK will give the British government agility, flexibility and freedom to change as they go, which are, as he noted, not characteristics aligned with the usual technology build in the UK -- or elsewhere, for that matter.
Given the British government's ambitious plans for open data, the GOV.UK platform also will need to be act as, well, a platform. On that count, they're still planning, not implementing.
"With regard to API's, our long term plan is to 'go wholesale,' by which we mean expose data and services via API's," said Bracken. "We are at the early stages of mapping out key attributes, particularly around identity services, so to be fair it's early days yet. The inherent flexibility does allow for us to accommodate future changes, but it would be premature to make substantial claims to back up API delivery at this point."
The GOV.UK platform will be adaptable for the purposes of city government as well, over time. "We aim to migrate key department sites onto it in the first period of migration, and then look at government agencies," said Bracken. "The migration, with over 400 domains to review, will take more than a year. We aim to offer various platform services which meet the needs of all Government service providers."
Making GOV.UK citizen-centric
The GOV.UK platform was also designed to be citizen-centric, keeping the tasks that people come to a government site to accomplish in mind. Its designers, apparently amply supplied with classic British humor, dubbed the engine that tracks them the "Needotron."
"We didn't just identify top needs," said Loosemore, via email. "We built a machine to manage them for us now and in the future. Currently there are 667!" Loosemore said that they've open sourced the Needotron code, for those interested in tracking needs of their own.
"There are some of the Top needs we've not got to properly yet," said Loosemore. "For example, job search is still sub-optimal, as is the stuff to do with losing your passport."
According to Loosemore, some the top needs that citizens have when they come to a site in the UK are determining the minimum wage, learning when the public and bank holidays are or when the clocks change for British Summer Time. They also come to central government to pay their council tax, which is actually a local function, but GOV.UK is designed to route those users to the correct site using geolocation.
This beta will have the top 1000 things you would need to do government, said Maude, speaking at the Sunlight Foundation this week. (If that's so, there's over 300 more yet to go.)
"There's massive change needed in our approach to how to digitize what we do," he said. "Instead of locking in with a massive supplier, we need to be thinking of it the other way around. What do people need from government? Work from the outside in and redesign processes."
In his comments, Maude emphasized the importance of citizen-centricity, with respect to interfaces. We don't need to educate people on how to use a service, he said. We need to educate government on how to serve the citizen.
"Like U.S., the U.K. has a huge budget deficit," he said. "The public expects to be able to transact with government in a cheap, easy way. This enables them to do it in a cheaper, easier way, with choices. It's not about cutting 10 or 20% from the cost but how to do it for 10 or 20% of the total cost."
The tech behind Gov.UK
James Stewart, who was the tech lead on the beta of GOV.UK, recently blogged about and browser support. He emailed me the following breakdown of the rest of the technology behind GOV.UK.
Hosting and Infrastructure:
- DNS hosted by Dyn.com
- Servers are Amazon EC2 instances running Ubuntu 10.04LTS
- Email (internal alerts) sending via Amazon SES and Gmail
- Miscellaneous file storage on Amazon S3
- Jetty application server
- Nginx, Apache and mod_passenger
- Jenkins continuous integration server
- Caching by Varnish
- Configuration management using Puppet
Front end
- Javascript uses jQuery, jQuery UI, Chosen, and a variety of other plugins
- Gill Sans, provided by fonts.com
- Google web font loader
Languages, Frameworks and Plugins
"Most of the application code is written in Ruby, running on a mixture of Rails and Sinatra," said Stewart. "Rails and Sinatra gave us the right balance of productivity and clean code, and were well known to the team we've assembled. We've used a range of gems along with these, full details of which can be found in the Gemfiles at Github.com/alphagov."
The router for GOV.UK is written in Scala and uses Scalatra for its internal API, said Stewart. "The router distributes requests to the appropriate backend apps, allowing us to keep individual apps very focused on a particular problem without exposing that to visitors," said Stewart. "We did a bake-off between a ruby implementation and a Scala implementation and were convinced that the Scala version was better able to handle the high level of concurrency this app will require."
Databases
- MongoDB. "We started out building everything using MySQL but moved to MongoDB as we realised how much of our content fitted its document-centric approach," said Stewart. "Over time we've been more and more impressed with it and expect to increase our usage of it in the future."
- MySQL, hosted using Amazon's RDS platform. "Some of the data we need to store is still essentially relational and we use MySQL to store that," said Stewart. "Amazon RDS takes away many of the scaling and resilience concerns we had with that, without requiring changes to our application code."
- MaPit geocoding and information service from mySociety. "MaPit not only does conventional geocoding, " said Stewart, in terms of determining what the given the longitude or latitude is for a postcode, but " italso gives us details of all the local government areas a postcode is in, which lets us point visitors to relevant local services."
Collaboration tools
- Campfire for team chat
- Google Apps
- MediaWiki
- Pivotal Tracker
- Many, many index cards.
Related: