Why I’m Disgusted with Web Teams

5 minute read
Brice Dunwoodie avatar
What’s it gonna take to get organizations to take their web sites seriously? By seriously I mean staff them, fund them and manage them?I’m beginning to believe that some newsworthy misinformation-on-the-Web or ecommerce-related revenue losing incident may be the only way that some organizations, both public and private, are going pay attention to the fact that their Web products are an embarrassment and, sometimes, a liability. Is that what it’s going to take? Some unlucky organization’s got to get caught with their Web pants down?

Web People and Web Management

In 1997 I was working on the Web team at Cisco Systems. The public website was serviced by several different groups within the organization and we were constantly battling about who was in charge (sound familiar?). I only mention Cisco by name not to name drop but because it’s significant to my gripe: Cisco Systems, the first big retailers of multiprotocol routers. Cisco gets the internet. Cisco gets the Web. Cisco has a vested business interest in having the Web work for every breathing human on the planet. Cisco would be the first to put the internet on Mars (if it’s not already there). But, Cisco still had a lot problems managing their website. Why? Because managing a large Web presence is less about understanding the potential and possibility of technology and more about sound operations and management practices -- creating an environment where people work together to create a quality product.Web People (this is a special breed of people who were drawn to work with Web technologies during the Web’s commercial proliferation in the 1990s) have many strengths. But establishing sound operating practices and sound management principles don’t seem to be among them. Web people are good at flying by the seat of their pants, doing the impossible overnight for demanding and technologically clueless managers, inventing new products out of new technologies, and complaining about being under appreciated and overworked… but not great about clearly explaining to managers why the organization is at risk because of the low quality of the organization’s Web products. In short, Web People are not good managers. It hurts me to say this because I feel like I’m dissing my own people. But, I think it’s for the greater good.

Web Management Demands Technical Literacy

The Web needs to be managed and it needs to be managed by people who understand not just the Web but also business operations and product quality. Unfortunately, this is not a description of many of the plain old vanilla business school manager types we see in organizations. A lot of managers we work with have an aversion to any knowledge that might be construed as specialized. I’m generalizing to make a point. There’s a general view that mangers don’t actually need to *do* anything (particularly anything technical)… that would be for subject experts and individual practitioners -- not managers. But not doing something is a lot different than not understanding what you’re managing. Not understanding what you’re managing is bad management. And there is a lot of bad management happening around websites.So, on the one hand you have technically-literate but managerially-illiterate individual contributors who know that the organization’s website is a ticking time bomb. And, on the other hand, you have technically-illiterate but managerially-literate managers who just want to be able to report up that everything is “just fine” with the site. The result is that organizations are stymied by big, unwieldy, and messed-up websites, largely created by a lot of smart, technology-focused Web People who don’t know how to manage their way out of the mess they have unwittingly created. Above them is typically an administrative structure that might know how to manage but won’t take the time to understand the basic technical underpinnings of the Web (“I’m not technical”); so, they can’t manage effectively and make bad, mostly tactical, reactionary choices for their Web products based upon the complaint of the moment from the Web People who report them.These things combined lead to what I consider to be a “deer in the headlights” Web syndrome: where lots of smart people in an organization are standing around stunned and up to their waists in bad Web product -- and they just stand there knowing that something bad is going to happen but unable to move. It’s a sad sight.

The Way Forward

What’s to be done, for all my complaining? Here’s a few suggestions:# Admit Defeat -- Admit that you are powerless over your website and that your website has become unmanageable.# Figure Out Who is In Charge -- Establish some basic organizational norms around the management of your websites. Make sure the definition of these norms includes Web People and Good Managers.# Make an Operational Plan -- Figure out how to get out of the mess that you’re in and how you will work in the future to create a higher quality, strategically-focused Web product.# Get a Sponsor -- I say this a lot but I also mean it a lot. Find the most senior person that you can in your organization and get them to support you with management mandates and human and financial resources.# Be a Copy Cat -- Most organizations have at least one thing that they do really well. Figure out what that is and then figure out why it works. Then apply those principles to your Web Operations plan. While the Web may be new, sound management principles are not.

About the Author

Welchman Consulting founder and principal consultant, Lisa Welchman, is recognized as a thought leader in the Web operations management arena and among the first to develop proven methodologies around Web governance. Lisa will be presenting at the cmf2007 conference in Denmark this November. Her talk entitled Web Governance: Figuring Out Who is in Charge will be presented on November 6th at 13:00. This article was originally published on the Gilbane Group Blog.