Blog proposal

From Wiki.gc20.ca

Jump to: navigation, search


Image:File edit.png This template was cited on the GC20.ca blog here. Feel free to edit!

Blog prototype links:

Legend:
{{{Department}}} Department submitting the proposal
{{{Directorate}}} Directorate submitting the proposal
{{{Division}}} Division submitting the proposal
{{{Purpose}}} Department-specific purpose for the blog
{{{Quote}}} Relevant quote cited from documentation
LL: "Lesson Learned", source for the insight.

This document is a listing of pertinent information related to the discussion of the feasibility of developing and implementing a {{{Department}}} blog.

Overview

The {{{Directorate}}} is supportive of the development of Web 2.0 and collaborative tools. In the interests of better communicating the work of {{{Directorate}}} with the public service of Canada, the development and implementation of a blog is proposed. At this stage, the purpose, principles and policies guiding a {{{Department}}} Blog are being evaluated and considered for further revision.

A discussion meeting is proposed with the following outline:

Contents


The blog is an external site, meaning it is intended for access as a public website by the public. As such, various policy requirements are applicable, and have been included in the development of this proposal.

Purpose

The {{{Department}}} is not part of the discussions happening online on the blogosphere. Bloggers are discussing the {{{Department}}}, without any discussions stimulated by or from the {{{Department}}}.

A blog from the {{{Department}}}, on a more refined topic such as best practices across the federal government, can significantly improve visibility of the {{{Department}}} among citizens, fellow federal public servants and allow us to disseminate information about {{{Purpose}}} to promote dissemination, stimulate discussion and get valuable feedback from our target audience without minimal added resources. (Reference)


Departmental level:

In line with the {{{Department}}} policy:
{{{Quote}}}

Directorate level:

In line with the Key Accountabilities of the {{{Directorate}}} Director General, {{{Directorate}}}:
{{{Quote}}}

Division level:

In line with the Key Accountabilities of the {{{Division}}} Director, {{{Directorate}}}:
{{{Quote}}}

Principles

Blog mission {{{Purpose}}}

i.e.: To support the sharing of emerging practices in Web 2.0 across the government and make them accessible to Public Servants across the government of Canada, and to stimulate and support discussion of these emerging practices among public servants interested about emerging and accepted best practices across the government.

This blog will make a special effort to identify and highlight discussion and review of emerging practices in Web 2.0 that may help Canadian federal public servants, while identifying and explaining emerging practices in Web 2.0 across a wide range of topics of interest.

This blog is supported by a group effort by employees working with the {{{Department}}}, either from the {{{Department}}}, or the rest of federal government, or from the public working with the {{{Department}}} exposed to an emerging Web 2.0 practice.

What the blog is A medium to engage the target audience to the discussion of emerging practices in Web 2.0 across the Federal Government, and if pertinent, how they are tied to the projects and programs of {{{Directorate}}}, to generate interest and to solicit pertinent feedback. They are discussed in a context relevant to public servants and to begin a discussion.
What the blog is not A marketing or promotions outlet to passively disseminate information from a one-way channel. Information is not provided to inform, but to engage. Topics are not discussed from the viewpoint of what the {{{Department}}} wants to communicate, but in a way that is of interest to the public servant. (see " Risks: Litmus test criteria")
Blog audience Federal public servants of the Government of Canada, past, present and future, and academics interested in Public Administration issues and the learning programs and projects of in progress by the {{{Department}}}.

Policies

External to {{{Department}}}

MAF: "Citizen-focused Service" Point 3: "Extent to which public/client views/needs are considered when developing new services/programs/policies"

The Governor General blog was assessed as "Strong":

The creation and use of the Citizens Voices blog ensures that the views and concerns of the public can be gathered; it also promotes dialogue and understanding of the issues that policy must address now and in the future. (source)
Content All information is public, accessible publicly and subject to ATIP. Retention/disposition of records in accordance with IM policy.
CLF The site works off a CLF theme in circulation among other Government of Canada departments, on the same WordPress blog platform used by the Privacy Commission blog.
Official Languages (bilingualism) Following on the practice of the Privacy Commission blog, the site is built for parallel language blog postings on a dual install with cross-linking between the English and French language sites.

Internal to {{{Department}}}

Posting policy (suggested)
  • Blog posting at least weekly (>52/year)
  • Bank of 10 postings ready in the queue for publishing
  • Published simultaneously in English and French
  • Posting policy defined
Comment policy (suggested)
  • Readers are encouraged to leave a comment, which are moderated. They may leave their name and email, but are not required.
    • Public postings, including Anonymous postings, will be moderated, and unapproved if they violate any one of the criteria set out for comment approval. (LL: TSA blog)
  • Comments do not need to translated. Comments on the French blog remain there, comments on the English blog remain there. Comments may be posted in the language of choice of the blog reader. (LL: PrivCom Blog)
  • After 3 months, comments are closed after 2 weeks of the blog posting (applicable to past postings). This keeps the task of moderating comments to past blog postings to a minimum, to focus on the moderation of current relevant blog postings. (LL: TSA blog)

System specs

Preview of the test install and setup of the {{{Department}}} blog
Preview of the test install and setup of the {{{Department}}} blog
The proposed system is built on Wordpress software, an "open source blog publishing application";
  • Free, open source: no cost, no licenses, on standard server;
  • Completely customizable, built on a free and open source platform LAMP stack common for website servers;
  • Very common software, the most common blog publishing platform for server-hosted blogs;
  • Completely administratable; admin interface with full controls;
  • Same system in use externally by the Privacy Commissioner of Canada.


Implementation

Discussion points

Strategy for content development.

Is this for communications and/or marketing? Blogs run by communications and/or marketing become a repository of desired Press Releases, without stimulating discussion, unless the required mindset change occurs within the organization. (Please refer to various posts by Mike Kujawski who blogs on this exact topic.)

  • Who writes?
    • {{{Department}}}-{{{Directorate}}}, with insight sought from others.
    • Capacity issue
  • About what?
    • Best Practices across the government.
    • Not too restrictive in scope?
    • What if other branches are interested in having their programs and activities covered?
      • Mission and perspective of the blog can change. Larger problem is having approved quality content up. A narrow focus (on {{{Directorate}}}) may be better in the interim until a strategy is developed elsewhere in the {{{Department}}}.
    • Risk of sprouting up other blogs? ADM blog? DM blog?
      • There is no {{{Department}}} Intranet development to do anything collaborative/web 2.0/government 2.0/anything helpful
  • Who approves posts?
    • ADM? Marketing? Not marketing? Endless cycle of approves and re-writes?
    • Need support from the President.
  • Workflow
    • Ideally the development server is on the Intranet.

Schedule

Site is developed as a pilot for 2 months, at launch having a bank of 8 posts already published, (2 months @ 1 per week = 8 posts).

Month 0:

  • Launch blog internally for commenting by {{{Department}}} employees and designated visitors under exclusive URL access.
  • Work with Marketing to assess CLF 2.0 theme for the {{{Department}}} (banner colour, top level links)
  • Work with TBS, PrivCom and other partners (LL: NRCan wiki)
  • Test out functions, operations, pages, English and French sites. (LL: TBS GCpedia)

Month 1:

  • Development of a bank of 10 posts. Translated.
  • Translate all pages and interface of the blog site.
  • Synchronise English and French sites.

Month 2:

  • Hosting of site/DNS subdomain pointer setup for blog site.
  • Continue to get content weekly.
    • Maintain a queue of 10 postings.

Risks

Not enough content to go up

  • Top priority must be to have content out at least weekly. Bank of 10 pre-approved translated posts in queue.
  • Recognise and praise those who submit content.
  • Eliminate barriers with principles: Litmus-test criteria:
    • Is it relevant to public servants?
    • Is it from a perspective of {{{Department}}}?
    • Is it content that would being a dialogue, incite reaction or stimulate response?
    • Is it accurate?

Too much content to go up

  • Problem: challenge to choose, select.
  • Develop roll-out schedule. Up the posting frequency (2x/week).
  • Develop thematic areas, try to cover them all.

Wrong information goes up

  • Need clear lines of authority, approval, moderation
  • Need to dedicate and maintain capacity to attend to the blog
    • Need understanding and elaboration of the blog as a medium and enabler.

Aim: The blog is an opportunity for the {{{Department}}} and {{{Directorate}}}to get in touch with the target audience, and not a repository or marketing engine like the local Intranet or the Internet site.

Challenge Areas

  1. Lack of awareness of the issues; purpose, system, medium, impetus;
    1. (Need to follow precedent and best practices from others);
  2. Breaking Status Quo and the associated barriers:
  3. Red Tape;
  4. Bureaucracy;
  5. Security;
  6. Gag orders.

Need to:

  1. Clearly define benefits
    Make the case;
  2. Mitigate the risks
    External server, keep content timely and up-to-date;
  3. Work as a team
    Identify partners and enablers;
  4. Develop a plan
    Content & Comment policy, evaluation;
  5. Don't re-invent the wheel
    Open source common tool;
  6. Always be learning
    Keep up-to-date of the emerging tools, modules.

(Source)

Other considerations

Policy
  • CLF 2.0 compliance is fully possible using CLF 2.0 themes freely available for install into the Blogging software proposed (Wordpress)
Technical
  • Blogs need to be at a %.gc.ca URL, for credibility in demonstrating it is a {{{Department}}}-supported blog.
    • Suggested url: http://blog.'{{{Department}}}.gc.ca & http://blogue.'{{{Department}}}.gc.ca, this involves the set up of a "subdomain"
    • If {{{Department}}} servers cannot host the blog, the {{{Department}}} servers should point requests to the blog.{{{Department}}}.gc.ca subdomain point to of an external site, hosted by non-GOC servers. (Note: Privacy Commission blog is hosted by Magma).
  • Requires Attestation that no privacy or privileged information is stored on the server, and that the server is Canadian.
Evaluation
  • Full stats should be collected on the use of the blog, the audience profile, etc.

See Also

Personal tools