For a few years, I hosted a fun annual scavenger hunt in the Adams Morgan / Dupont Circle area of Washington, DC. Before everyone raced out with the clue list, I would go over the rules -- everyone would roll their eyes and groan at this point. A few hours later, after everyone got back with ginko leaves, strangers' phone numbers, religious group brochures, and obscure cooking ingredients, there would be quite vocal disputes over who got points for what. Of course, at that point, the rules would help move things along so that the prizes could be given out.
Posted by David Hobbs 2 years ago
Many technical groups within organizations feel that they own all things technical and therefore should define requirements (for example, CMS requirements) and technical standards (for example, the Web Tools and Applications standards team that we recommend groups have). On the one hand, I totally sympathize with these groups (I come from the technical side of things) since they often end up getting burned by tools acquired by other groups that they must then support. Also, many non-technical groups feel out of place and overwhelmed by the idea of helping with technical sta
Posted by Anonymous 3 years ago
We call them standards. Some people call them guidelines, some people call them standard operating procedures, but they are all nearly the same thing: they are the rules of the web site. And they come in all colors, shapes and sizes. But what’s in a standard?
