512
edits
Changes
m
1 revision imported
{{CLFBreadCrumb|lang=eng|level1=[[Web_Standards|Web Standards]]|level2=[[User_experience_working_group|UXWG]]|level3=[[User_experience_working_group_/Project_plan|Projects]]|level4=0|level5=0}}
{{Good stuff}}
<div style="float:right; padding:0 40px;"><videoflash height="190" width="320">http://31591.vws.magma.ca/sct-tbs/ROT.mp4</videoflash></div>
<br>
The idea for a ''Reduce the ROT (Redundant, Outdated and Trivial)'' campaign (en français: RID (R: Redondant, I: Insignifiant, D: Dépassé)) was presented at the [[Web_Managers_Council_(WMC)_2010-09-16|Web Managers' Council meeting]] on September 14th, 2010. The impetus for this campaign was taken from content strategist Coleen Jones, based on her [http://www.uxmatters.com/mt/archives/2009/08/content-analysis-a-practical-approach.php 2007 blog post on content analysis].
With three [http://www.tbs-sct.gc.ca/clf2-nsi2/13msg-eng.asp Web Standards] replacing the [http://www.tbs-sct.gc.ca/clf2-nsi2/index-eng.asp Common Look and Feel Standards], departments are looking for implementation guidance. The UXWG would like to bring attention to best practices for managing content with a focus on evaluating and improving what's online now in order to keep costs as low as possible. <br>
There are about 10 million pages on the .gc.ca network - it's time to trim the fat. Our aim is to help departments implemente the Web standards and guidelines by reducing the amount of content to manage.
= Reduce the ROT Guidebook =
{{TOCright}}
*[[Media:ROT_FINALKIT.doc|Download the guidebook]]
== Appendices / Annexe ==
* '''Appendix A''' - '''Appendix F ''' included in the Guidebook
*'''Appendix G:'''[[Media:AppendixG_Guide_to_effective_web_writing_presentation.ppt| Guide to effective web writing presentation]]
*'''Appendix H'''[[Media:AppendixH_Web_Content_Accessibility_Guidelines_2.0_reference_guide.pdf| Web Content Accessibility Guidelines 2.0 reference guide]]
*'''Appendix I''':[[Media:AppendixI_ROT_overview_presentation.ppt|ROT overview presentation]]
*'''Appendix J''': [[Media:Sample_Process_Map.doc|Sample Process Map]]
::*[[Media:ROT_Sample_Process_Map_.VSD|Sample Process Map (Visio)]]
= Reduce the ROT Support Group =
ROT (Redundant, outdated, trivial content) Reduction sessions were held on July 20, July 28 and October 25th. Over 250 public servants attended from close to 50 departments. See who attended via the [[User experience working group (CLF)/Redundant Outdated Trivial Content Information Session/Registration Page|registration page]] (Previous session registration can be view via the history tab. <br>
Have you started to reduce the ROT? Found some tricks or roadblocks? We want to know how you're doing. Share your story in the [http://gcforums.gc.ca/default.aspx?g=topics&f=2767 Reducing the Redundant, Outdated and Trivial (ROT) Community on GCForums]
== Reduce the ROT.gc.ca Steps and Success Stories==
*[[Media:TC_presentation_-_eng.ppt|Overall Process / Processus global: Transport Canada]]
{| class="wikitable" cellspacing="0" cellpadding="3" width="100%" border="1"
|-
! scope="col" | <span style="color: rgb(0,128,128)">Step</span>
! scope="col" | <span style="color: rgb(0,128,128)">Detail</span>
|-
| '''Step 1: '''
Complete a Content Inventory
*[[TBS_Content_Review|TBS Presentation]]
| You have to know what you have in order to keep it current. Every page needs a content owner and a review date. How can departments create an inventory of all their web pages?
|-
| '''Step 2: '''
Evaluate and sort content
*[[Media:ROT_CanadaBusiness.ppt|Canada Business ROT Success Story Presentation]]
| Does content need to be removed just because it's old? How is 'relevant' defined? These are the kind of decisions that each department needs to determine in order to manage their content effectively.
<br>
|-
|
'''Step 3:''' Archive out-dated content
*[[2011-09-30_:_Information_management_community_/_IMSO_Day_September_30,_2011|Presentations from IMSO Day 2011]]
| Content that is no longer relevant should be '''archived, not deleted'''. Most departments will find it necessary to develop a Content Lifecycle policy or guidelines that describe how long documents are kept and how often they are reviewed.
|-
| '''Step 4:'''
Re-write, [[Web_information_architecture|Re-organize]] and Re-publish
| If content is still relevant, it may need to be re-written or re-coded to adhere to Web Standards. If it's okay, the review date should be updated. With reduced content, you may need to [[Web_information_architecture|re-organize what's left]]. [[Web_information_architecture|Find out how]].
|-
| '''Step 5:'''
Develop a [[Web operations and governance|governance framework]] and set editorial policies for your website.
| Needs your input...
Prevent future ROT by defining how decisions are made about their web presence and who has authority in order to ensure content remains relevant and up-to-date.
|}
== Benefits ==
*Easier for client to find what they're looking for - studies of [http://www.useit.com/papers/webwriting/ content usability] typically find that removing half of a website's words will double the amount of information that users actually get. [http://www.useit.com/alertbox/20030811.html Source]
*By reducing the amount of content on your website, you will reduce the time it takes and cost of updating your site to be compliant to the new web standards
*Fewer resources required to modify content to be compliant with updated web standards
*Less content to manage
*Improved service delivery
*Improved perception of the organization
<br>
== Measure Success of Reducing the ROT ==
Measure success by determining improved efficiency, effectiveness and/or client satisfaction of your site.<br>
'''Efficiency:''' Consider the percentage decrease in time (and therefore money) it will take to update your site to meet the new web standards. If you currently have 10,000 pages, and you reduce this number by half, you're also reducing the time and cost of changing it.
'''Effectiveness:''' Studies of [http://www.useit.com/papers/webwriting/ content usability] typically find that removing half of a website's words will double the amount of information that users actually get. [http://www.useit.com/alertbox/20030811.html Source]
'''Client satisfaction:''' Want to know if your site is better? Ask your clients. Let them know in advance that it'll be changing or make a link to email the webmaster prominent on your home page or feedback page.
The reduction of ROT content should be an ongoing activity in government departments. While this challenge will not be an official component of CLF reporting or evaluation for departments, we should nonetheless try to find some ways by which we could measure its uptake, success etc.
== Committed to Reducing the ROT? ==
Are you committed to reducing the ROT on your website? Add the userbox to your GCPEDIA profile page like [[User:Martha.mclean|Martha]]:
{{userbox2|DodgerBlue|LightSteelBlue|[[Image:zombie22.png|75px]]|'''This user is committed to [[User experience working group (CLF)/ROT Challenge|reducing the ROT!]]'''}}
== What are people saying about the Reduce the ROT.gc.ca challenge? ==
*[http://spaghettitesting.ca/2010/11/04/reduce-the-rot-or-not/ Reduce the ROT (or Not)] blog post by Peter Smith
*[http://aboutness.ca/2011/04/20/of-rot-and-puffery/ Of rot and puffery] by Jane Stewart
*[[Reducing the Redundant, Outdated and Trivial (ROT) Content project cycle|What your colleagues are saying about their ROT.gc.ca challenge experience...]]
<br>
{{Uxwg}}
[[Category:Usability]] [[Category:Content Strategy]]
[[Category:Information architecture]] [[fr:Defi sur la reduction du RID]]
[[Category:Web Renewal]]
{{Good stuff}}
<div style="float:right; padding:0 40px;"><videoflash height="190" width="320">http://31591.vws.magma.ca/sct-tbs/ROT.mp4</videoflash></div>
<br>
The idea for a ''Reduce the ROT (Redundant, Outdated and Trivial)'' campaign (en français: RID (R: Redondant, I: Insignifiant, D: Dépassé)) was presented at the [[Web_Managers_Council_(WMC)_2010-09-16|Web Managers' Council meeting]] on September 14th, 2010. The impetus for this campaign was taken from content strategist Coleen Jones, based on her [http://www.uxmatters.com/mt/archives/2009/08/content-analysis-a-practical-approach.php 2007 blog post on content analysis].
With three [http://www.tbs-sct.gc.ca/clf2-nsi2/13msg-eng.asp Web Standards] replacing the [http://www.tbs-sct.gc.ca/clf2-nsi2/index-eng.asp Common Look and Feel Standards], departments are looking for implementation guidance. The UXWG would like to bring attention to best practices for managing content with a focus on evaluating and improving what's online now in order to keep costs as low as possible. <br>
There are about 10 million pages on the .gc.ca network - it's time to trim the fat. Our aim is to help departments implemente the Web standards and guidelines by reducing the amount of content to manage.
= Reduce the ROT Guidebook =
{{TOCright}}
*[[Media:ROT_FINALKIT.doc|Download the guidebook]]
== Appendices / Annexe ==
* '''Appendix A''' - '''Appendix F ''' included in the Guidebook
*'''Appendix G:'''[[Media:AppendixG_Guide_to_effective_web_writing_presentation.ppt| Guide to effective web writing presentation]]
*'''Appendix H'''[[Media:AppendixH_Web_Content_Accessibility_Guidelines_2.0_reference_guide.pdf| Web Content Accessibility Guidelines 2.0 reference guide]]
*'''Appendix I''':[[Media:AppendixI_ROT_overview_presentation.ppt|ROT overview presentation]]
*'''Appendix J''': [[Media:Sample_Process_Map.doc|Sample Process Map]]
::*[[Media:ROT_Sample_Process_Map_.VSD|Sample Process Map (Visio)]]
= Reduce the ROT Support Group =
ROT (Redundant, outdated, trivial content) Reduction sessions were held on July 20, July 28 and October 25th. Over 250 public servants attended from close to 50 departments. See who attended via the [[User experience working group (CLF)/Redundant Outdated Trivial Content Information Session/Registration Page|registration page]] (Previous session registration can be view via the history tab. <br>
Have you started to reduce the ROT? Found some tricks or roadblocks? We want to know how you're doing. Share your story in the [http://gcforums.gc.ca/default.aspx?g=topics&f=2767 Reducing the Redundant, Outdated and Trivial (ROT) Community on GCForums]
== Reduce the ROT.gc.ca Steps and Success Stories==
*[[Media:TC_presentation_-_eng.ppt|Overall Process / Processus global: Transport Canada]]
{| class="wikitable" cellspacing="0" cellpadding="3" width="100%" border="1"
|-
! scope="col" | <span style="color: rgb(0,128,128)">Step</span>
! scope="col" | <span style="color: rgb(0,128,128)">Detail</span>
|-
| '''Step 1: '''
Complete a Content Inventory
*[[TBS_Content_Review|TBS Presentation]]
| You have to know what you have in order to keep it current. Every page needs a content owner and a review date. How can departments create an inventory of all their web pages?
|-
| '''Step 2: '''
Evaluate and sort content
*[[Media:ROT_CanadaBusiness.ppt|Canada Business ROT Success Story Presentation]]
| Does content need to be removed just because it's old? How is 'relevant' defined? These are the kind of decisions that each department needs to determine in order to manage their content effectively.
<br>
|-
|
'''Step 3:''' Archive out-dated content
*[[2011-09-30_:_Information_management_community_/_IMSO_Day_September_30,_2011|Presentations from IMSO Day 2011]]
| Content that is no longer relevant should be '''archived, not deleted'''. Most departments will find it necessary to develop a Content Lifecycle policy or guidelines that describe how long documents are kept and how often they are reviewed.
|-
| '''Step 4:'''
Re-write, [[Web_information_architecture|Re-organize]] and Re-publish
| If content is still relevant, it may need to be re-written or re-coded to adhere to Web Standards. If it's okay, the review date should be updated. With reduced content, you may need to [[Web_information_architecture|re-organize what's left]]. [[Web_information_architecture|Find out how]].
|-
| '''Step 5:'''
Develop a [[Web operations and governance|governance framework]] and set editorial policies for your website.
| Needs your input...
Prevent future ROT by defining how decisions are made about their web presence and who has authority in order to ensure content remains relevant and up-to-date.
|}
== Benefits ==
*Easier for client to find what they're looking for - studies of [http://www.useit.com/papers/webwriting/ content usability] typically find that removing half of a website's words will double the amount of information that users actually get. [http://www.useit.com/alertbox/20030811.html Source]
*By reducing the amount of content on your website, you will reduce the time it takes and cost of updating your site to be compliant to the new web standards
*Fewer resources required to modify content to be compliant with updated web standards
*Less content to manage
*Improved service delivery
*Improved perception of the organization
<br>
== Measure Success of Reducing the ROT ==
Measure success by determining improved efficiency, effectiveness and/or client satisfaction of your site.<br>
'''Efficiency:''' Consider the percentage decrease in time (and therefore money) it will take to update your site to meet the new web standards. If you currently have 10,000 pages, and you reduce this number by half, you're also reducing the time and cost of changing it.
'''Effectiveness:''' Studies of [http://www.useit.com/papers/webwriting/ content usability] typically find that removing half of a website's words will double the amount of information that users actually get. [http://www.useit.com/alertbox/20030811.html Source]
'''Client satisfaction:''' Want to know if your site is better? Ask your clients. Let them know in advance that it'll be changing or make a link to email the webmaster prominent on your home page or feedback page.
The reduction of ROT content should be an ongoing activity in government departments. While this challenge will not be an official component of CLF reporting or evaluation for departments, we should nonetheless try to find some ways by which we could measure its uptake, success etc.
== Committed to Reducing the ROT? ==
Are you committed to reducing the ROT on your website? Add the userbox to your GCPEDIA profile page like [[User:Martha.mclean|Martha]]:
{{userbox2|DodgerBlue|LightSteelBlue|[[Image:zombie22.png|75px]]|'''This user is committed to [[User experience working group (CLF)/ROT Challenge|reducing the ROT!]]'''}}
== What are people saying about the Reduce the ROT.gc.ca challenge? ==
*[http://spaghettitesting.ca/2010/11/04/reduce-the-rot-or-not/ Reduce the ROT (or Not)] blog post by Peter Smith
*[http://aboutness.ca/2011/04/20/of-rot-and-puffery/ Of rot and puffery] by Jane Stewart
*[[Reducing the Redundant, Outdated and Trivial (ROT) Content project cycle|What your colleagues are saying about their ROT.gc.ca challenge experience...]]
<br>
{{Uxwg}}
[[Category:Usability]] [[Category:Content Strategy]]
[[Category:Information architecture]] [[fr:Defi sur la reduction du RID]]
[[Category:Web Renewal]]