A Web Policy is a Policy, Not a Standard

I've been spending a lot time lately crafting a solid list of Web policies and standards that organizations should consider. After all, the benefits of codifying and enforcing policies and standards are significant as they serve to limit risk and increase Web site quality and consistency. 

So I've noticed recently that people (and organizations) often interchange the policies and standards labels as if there is no difference between them... like those who insist the Web and the Internet are the same. 

I'm not one for splitting hairs, but in this case, policies are truly not the same as standards and it's important to be clear about the distinction.

Let's Define the Terms:

Web Policy: Basic set of legal, compliance-related, editorial and technical constraints for Web development.  

Web Standards: Web standards describe specific parameters and limits and exceptions for development of Web products.

Simply put, policies and standards compliment each other but are indeed distinct. Policy specifies the "what" and standards respond with "how."

Here's A Quick Example of Each:

Web Policy for Business Language: The organization's Web properties shall utilize English as the official business language but account for cultural and location specific terminology.

Web Standard for Business Language: Utilize postal code instead of zip code as zip code is specific to the US.

So, there is a distinction between the two but people and organizations continue to meld them together. Even the Department of Health and Human Services which has extensive and solid standards is known to label them as policies. Take a look.

Understanding the distinction is one step, understanding how policies and standards align with Web governance and the categories they should cover should not be ignored. Be sure to read Lisa Welchman's Web Governance definition for a comprehensive explanation of policies and standards and what they mean to an organization.