New Years Resolution: Conduct a Web Standards Audit
The start of a new year is a great time to conduct an audit of the web standards in your organization. Web standards are important since they allow for a decentralized group of people-- like contributors throughout various departments, a large in-house web team or external web design firms-- to work on the same sites, channels, etc. while maintaining digital quality. An audit will reveal how complete your set of standards may be and will reveal what standards are already documented, those that can be easily drafted and those that are wholly missing and need to be heavily defined.
The steps for doing an audit are below. For some motivation in getting started, check out Lisa Welchman talking about the importance of standards in this video.
Find Standards-Related Information You Already Have
Pulling together existing standards documentation is the first step to creating a comprehensive set of web standards. After all, if you don't know the standards you already have, you can't identify the ones that are missing and need to be created.
While your organization may not have formal web standards, written documentation about things that impact the web likely exists. Your task is to find it. Be a detective and look for it in all sorts of places. For instance, you may not have a formal standard (or policy) on web privacy, but privacy may be discussed in a memo from a division vice president. Similarly, you may not have formal standards related to web accessibility but you may find your organization has a style guide that mentions accessibility or a checklist of to-do items related to accessibility.
Create a Repository and Take Inventory
Once you've scoured your organization for documentation, create a repository of all the files so everything is in one place. Consider creating a wiki to house the documents or link out to the relevant information wherever it exists. Inventory what you've found so that you can identify what's missing. When I conduct an inventory for a client, I group topics into these four categories and you could do the same:
- Publishing and Development
- Network and Server
If you found information on allowable font colors, indicate that under Design and note the source. If you found statements related to your company's copyrights and trademarks, note that under Editorial and include the sources too. Keep in mind that a standard might be relevant to multiple categories.
Examine Your Inventory for Gaps
Once you've finished the inventory, you can see the gaps in topics. Standards gaps generally fall into two categories:
Gaps that can be easily shored up by documenting an as-is state
Server and Network infrastructure standards are usually good examples of standards that are in place but not formally documented. For example, what are the parameters for web hosting? What about load balancing? Your IT department likely has load balancing under control, but how it is done is not formally written down. Set up some meetings with the IT team and write things down like, "Our company website is hosted on two or more mirrored Web servers. These servers are mirrored every 5 minutes and are load balanced using DNS round robin. Load balancing is to be provided by Citrix Netscalers..."
Gaps that need to be heavily defined
There will be some web-specific standards topics that are wholly unaddressed at your organization. Common examples might be web records management, allowable files and their size limitations and metadata schema. Flag such topics to be addressed as a next step in your standards project-- a step that requires you to have time and resources to devote to gathering stakeholder input and defining.
Create a Standards Writing To-Do List
Once you've compiled the standards-related documentation and inventoried it, make a to-do list of standards you need to write so you can adequately plan your schedule and approach. These are the types of standards you'll need to add to your writing to-do list:
- The standards in the gaps as discussed above
- The standards that you found related documents for. For example, if you did find that privacy was discussed in a memo from a division vice president, use that as a starting point to write web-specific privacy standards.
I think you'll find that following these steps makes for a great start to creating a comprehensive set of web standards. You can make fast progress at the outset and be able to plan for creating standards you don't yet have formally documented. That should feel good!