It’s a widely-held belief among various Web practitioners (from content strategists and information architects to Web infrastructure tool builders and application developers) that senior executives don’t understand the real power and capability of the Internet. And, that this lack of understanding has left Web Teams executing in a vacuum, with inappropriate funding and inadequate headcount. More importantly, it has left organizations exposed, as new Internet-enabled businesses sneak up and shut down the slower-to-react belle-weathers.
One of the challenges around creating social media policy is whether or not it is appropriate to constrain an employee’s social media activities when performed in a professional and personal capacity. There are a few key considerations to talk through when crafting a social media policy: what is unacceptable; what can be prescribed ; and, what can be reasonably enforced?
A lack of cross-functional representation is a surefire way to undermine your Web governance framework. Often organizations will default to the Web team as the group responsible for policies and standards; after all, they are the experts on Web technologies and best practices. However, having only "Web people" seated on the governing bodies means you may lose the perspective from the lines of business.
There's been lots of chatter online recently about Web governance... particularly when it comes to SharePoint. Just do a Twitter search on "governance sharepoint" and you'll see what I mean. Even sharepointgovernance.org launched recently. Can you tell it's a hot topic?
Definition of back channel communication: "'Grapevine' or informal communications that travels parallel to (and sometimes ahead of) official channels in an organization or society" from BusinessDictionary.com.
Of course, the "real work" of organizations is usually done informally, so unofficial communication is extremely important. That said, if you run a large Web site, you have probably encountered these types of internal issues:
The WelchmanPierpoint offices are located in Baltimore, MD. So what, you ask? Well, Baltimore is about 40 minutes by train from Washington, DC, so, we have a lot of federal government clients. We didn't plan it that way, it just worked out like that. As it turns out, that's not a bad thing. Federal government agencies for the most part have pretty messed up Web sites. And that's what we like: big, super-bad, un-navigable Web site atrocities.