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. The house is on fire and the C-Suite has got a garden hose.
To address this strategic deficit, there’s been a lot of discussion about the placement of a senior Web-savvy person in the C-Suite to drive the creation of a sensible Web content and information strategy. I’ve thought about this potential new role in the C-suite a lot and think that it’s not required.
My philosophy background always makes me apply Occam’s Razor to any solution, and thus I don’t see that real long-term value can be added by increasing the number of bodies at the executive level. That doesn’t mean I don’t believe there is a lack of Internet smarts in the C-Suite—my experience shows that the C-Suite in most organizations is not “Web-enabled” and frequently to the detriment of the business.
So, I’d like to illustrate how I see the problem and offer a suggestion about how the situation can be improved without creating a new role.
There are three players acting in this dynamic: The C-Suite, Middle Management, and Web Experts. Here’s how I see the existing interaction:
And here’s my explanation of the dynamics behind this scenario:
The C-Suite’s Lack of Web Understanding
Down-side: At the executive level there is an element of conservatism, resistance to change, or just general ennui about the Web, depending on the individuals involved. Organizations, led by executives that grew their careers prior to the advent of the business Web, have frequently segregated their organization’s Web efforts because these pre-Web executives view both the strategy behind the use of the Internet and the business process of building the Web presence as tactical. Their personal experience of business success did not include the World Wide Web. So, despite the Web’s growing operational primacy and the ever-growing opportunity for creating business, the Web, strategy and execution, is frequently off in a corner, an after-thought in business-process.
Therefore, middle management and the Web Team are forced to manage a sophisticated Web presence with inappropriate human and fiscal assets (often riding piggy-back on Marketing Communications or IT budgets) and with little or no organizational strategic guidance.
Up-side: These executives are super smart and the most strategic thinkers in your business. They steer the ship and step up to the plate daily to make the big and difficult decisions that impact thousands.They just don’t “get” the Web.
Middle Management Pulled in Two Directions
Down-side: Organizational middle managers are not taking any risks.They are doing what their superiors tell them. From time to time, if there is a Web Expert below them who is able to make a cogent business case for resources or change, they may shop that idea up to the C-suite. But, the middle manager is not swayed by the lure of a cool technology, as a Web Expert might be. They’re looking for business value and alignment with business strategy and objectives. And, what is core to the failure in this area is that they frequently lack the specialized expertise and understanding of the strategic and technical capabilities of the Web required to translate the “give me more” arguments of the Web Expert into a serious business case. So, a lot of business opportunity dies on the vine at this level.
Up-side: If you give them something to manage, they’ll manage it well. They know how to build consensus and get the resources to make things happen. In the rare case, when this manager is also a Web Expert, the positive impact on the quality of Web Execution, and therefore the quality of the Web presence, can be staggering.
Frustrated Web Experts
Down-side: Those who work on the Web day-to-day, from the most junior individual practitioners to the most senior gurus, are frequently weak in the area of business strategy and management. Often they lack the skill and authority to effect real change in the enterprise, but, due to the disconnect with the top of the organization, are frequently put in the position to make strategic decisions about the use of the Web channel which impact the bottom line.
Saddled with the task of operating without strategic business guidance and appropriate support from middle management, Web Experts frequently thrash about, executing on project after project, in quest of the magic bullet that will solve the Web problem. Consequently, resources are wasted or misdirected.
Up-side: Real Web execution maturity is coming into play 15 years after the advent of the commercial Web. In almost every organization we’ve worked with, the amount of real Web talent related to the strategic and tactical development of content, data and applications for the Web is staggering. The fact that, without guidance and resources, these people create and maintain what is probably the first (and sometime only) point of contact for a business, is admirable and deserves more recognition than it receives.
Web-enabling the C-Suite
So, what can be done about this?
I think the solution is simple—or certainly a lot simpler than creating a new role at the executive level. The answer lies in the education of the C-Suite. There are a few ways this could get done. For instance, an organization could use outside coaching by an Internet Strategist or, more drastically, replace some personnel in your executive suite. But I think that, for most organizations, change can be most effectively and less disruptively achieved through active collaboration by Web experts and middle managers.
Within an organization, there are usually a few Web experts with some strategic DNA and a few middle managers who understand the missed business opportunities that have occurred as a result of lack of integration of the Web function at the executive level. If middle managers and Web experts join forces, they can combine managerial courage and skill and Web expertise and vision to build a sound business case for strategic use of the Web. Be prepared for push back and have your facts and figures straight. This cannot be an emotional or “because it’s the right way to do it” appeal. It has to make business sense, not Web sense.
Business Value = "Instant On"
My experience has been that when shown business opportunity supported by quantitatively expressed value that benefits the mission or bottom-line of the business, most executives sit up and listen AND learn, AND integrate the larger lesson instantly when the actuality meets the projection. Showing how use of the Web will make the organization more effective or profitable should act as an "instant on" button for the C-Suite. If it doesn't, then the organization truly is in trouble from the top down. And no Chief Content Officer, or Chief Web Officer is going to fix that. You simply need a better CEO.
Yes, if you are a Web expert when you help make this translation, it might mean for an instant you might be doing part of the job of the C-Suite, but that doesn’t mean you belong in the C-Suite. At least not at this juncture for most. The function of the C-Suite is beyond the capabilities of even the most senior Web practitioners we have worked with—and we’ve worked with some genius-level Web folks. It’s just a different skill set.
For those Web experts that do have the constitutional make-up and the desire to reach the C-Suite, they need to educate themselves about the business, holistically, and make the natural progression to the executive roles--carrying with them their Web intelligence. It doesn’t make good business sense to promote a relatively junior resource to the executive level because of a temporary knowledge deficit at the top.
With a Web-enabled C-suite, all players should be more comfortable and effective in their roles:

All of that said, I’ll allow that some businesses might need a chief Content Officer or Chief Web Officer at the C-level because of their particular business model. If that’s the case, then so be it. But I don’t think there is a need for a new standard role in line with the CEO, CFO and CIO. You just need web-enabled versions of CEOs, CFOs and CIOs. Those in this role in a legacy capacity need to be educated. In a few years, I think much of this will be a moot point as the digital immigrant and digital native populations naturally progress to the executive level bringing with them all their Web savvy.
Maybe one of them will be you!

29 weeks ago
The concept of Business Value = "Instant On" is very well understood at the CxO level. It tends to be less well understood at other levels down the chain, and I'm not sure why that is, although you've given some clues. "We're here to make money and increase shareholder value" is a mantra every C-level exec lives every day. Somehow that message doesn't propagate well, going down the food chain. But as you say, messages involving the value of Web and SoCo likewise don't propagate very efficiently in the other direction, either. It may be partly generational. But clearly, when both messages meet, the potential exists to integrate a Web strategy into the overall business strategy *without* the involvement of a new species of C-level expert. The Web is now part of the fabric of business, and all of us, at all levels in the organization, have to understand that. It shouldn't take a new type of C-level position to "inject" that knowledge into the organization. If it does, we're in trouble.
Thanks for a great post.
29 weeks ago
My guess is that someone probably wrote an article very similar to this in the early 70's (what the Wikipedia IBM entry calls the "System/370 Era") only where this post uses the word "Web" that article in its place had something like "computer" or "mainframe" or "information services".
There are many parallels. Certainly the advent of mainframe computing and related forms of business automation had just as revolutionary of an impact on business and had a similar lack of knowledge and insights in the C-Suite then.
Yet--most likely because of the ever-changing nature of technology--existing C-level folks then never quite caught up or added information services to their overall skill set at a needed level, so somewhere along the line a new roll was championed and eventually added to the C-Suite called Chief Information Officer and/or Chief Technology Officer.
So while I agree completely that (1) current C-level executives need more education and (2) that one potential career path for some of today’s Web Executives is to move into traditional C-level slots, I think it is too early to dismiss the idea of a C-Suite position such as Chief Web Officer or Chief Internet Strategist as another need and career path. If history is any indication, that is a definite possibility as long as we find champions for it within the ranks of corporate Web experts.
28 weeks ago
Thanks for the comment Steve. Yes, I've read a lot of those articles from the late 60s and early 70s and agree that there are extremely relevant parallels. I find the lessons learned educational. It is relatively early, but, I'm asserting my view in an effort to move the conversation along.
I think that there is a difference between an "Internet Strategist" and a "Chief Web Officer" as I hear the debate in the Web community and as we discussed it last month at the Internet Executive Career Path Symposium at the ISF Summit. And it became even more clear to me that there is a real difference when Gregory Miller gave his description of what an Internet Strategist was. The skills he listed included, amongst others, computer science background, MBA-level business knowledge background, and a formal legal background.
I don't think I'm arguing semantics here. We all know there is a fundamental (and technical) difference between the Internet and the World Wide Web. So I think there should be a difference between strategizing for the Internet and strategizing for the Web. Just as there is a difference between Internet Governance and Web Governance.
When Gregory Miller offered his definition of an Internet Strategist I nodded and said to myself, "that makes sense for an organizational Internet Strategist. BUT this is not what people who want to be a Chief Web Officer want or are arguing for." When someone says we need a "Chief Web Officer" in the C-suite because an organization can't strategize about or properly manage their Web channel (which is what I hear a lot), I can't buy that argument. If someone says we need an Internet Strategist at the C-level because our organization doesn't include the capabilities of Internet as part of its business strategy so we need an Internet Strategist at the C-level, I'd say "maybe I'll buy that argument but explain to me first why you can't get a better CIO and have the Internet Strategist report to them."
So, my point is that there is some compression of language and roles when we talk about the "Internet" and the "Web" and its associated strategy or execution tactics-- and the roles that make support these new business realities. Maybe a first step and one that colleagues at conferences have discussed for years, is to get our terminology straight. So, we can have our debate on even terrain. What are (or would be) these roles?
Chief Information Officer
Internet Strategist
Chief Web Officer
What do they do? Where might they be seated in the organization and why?
We spend a lot of time looking at the structure of Web Teams in organizations and right-sizing and restructuring them. It's amazing to me that it just used to be "webmaster" and the IT server folks and now there are a dozen or more necessary functions and a slew of outsourced services required to keep a sophisticated Web presence running. At the end though, the Web is just one of many information channels that might be used to support business objectives. We need a really strong argument why that particular channel needs representation at the C-level.
28 weeks ago
As per usual, I'm impressed with your firm's ability to channel the progressive thoughts of creative web professionals. The effects of irresponsible planning, arbitrary spending, and inefficient staffing have aided to drown a retreating economy. However, prior to recession, and since its inception, web technicians have been criticized, unappreciated, misdirected, and marginalized. Despite this, the emergence of Agile / Lean methodologies, and subsequent adaptation by industry have optimized the decisions executives make, however the potential benefits and unexpected risks of technology are still only rarely quantified during planning.
A company's web site represents their unique ability to adapt to a market place with competing customer demands, diverse technology options, and almost complete customer attention. Why does the C-Suite ignore the moving web, and focus on artifacts that are merely vain monuments to their reign?
Could it be, that its harder to create an effective, usable, and relevant site without qualified customer input? I think so, but it's not just clients wanting tacky and trendy features. It could be the designer/developer compensating for being confused, isolated, under payed, or under qualified.
-Ryan Gensel
28 weeks ago
Hi Ryan - you raise a valid point about designers and developers. At the end of the day, the quality of the Web presence is the responsibility of senior management.
Designers and developers are tacticians whose job it is to execute a Web strategy. Granted, there are many designers and developers who are strategic thinkers and have the vision and foresight to provide managers with good guidance. For example, they may say smart things like, "If you implement a blog on the homepage you should have policy in place to cover third-party content..." but to assume they are always going to go to that level of detail is naive.
The job of senior management is to communicate a vision, establish objectives and mitigate risks. These basic functions need to extend to the Web. But what we see instead is the expectation that Web practitioners are going to be able to implement tactics AND have the insight to address management functions as well. Talk about the tail wagging the dog.
What's more, if design and development is outsourced, there's even more reason for managers to play their part. Why? Because even the best vendors are, at the end of the day, vendors. If the content quality starts to erode or the software needs to be re-configured...guess what, it's an opportunity to sell more services.
Senior managers need to listen to the input of Web vendors and staff, but then use that input to provide strategic direction. To your point, when senior managers are not involved with Web planning, it's not fair to blame the design and development team for poor results.
28 weeks ago
Christine,
You are quickly becoming my professional hero, complimenting the ranks of David Maister and Richard Feynman. I applaud your logic, and look forward to more.
-Ryan Gensel
28 weeks ago
Thanks. You flatter me, but I really credit Lisa Welchman for having this insight more than ten years ago (http://www.welchmanpierpoint.com/blog/call-action-web-managers-blow-whis...). I'm just glad to see it's finally starting to resonate.
28 weeks ago
I think it took a recession to almost eliminate non-essential expenses. Vanity web sites are no longer considered a logical investment, even if web professionals are adept at creating the most with the least. Infinite recursion and socially adaptive programming conventions are phenomena that will remain consistent with technology development, and hence complicate the progression of any standards. However, concurrency and portability will represent the management of information for at least two more years. (Maturation of Semantic Web, DITA, and GRDDL.)
-Ryan Gensel
7 weeks ago
Agree. It's a process, education, governance and steering committee challenge, rather than more "suites". Great post!
Post new comment