A chief web officer (CWO) is the highest-ranking corporate officer (executive) in charge of an organisation’s Web presence, including all internet and intranet sites. As a corporate officer position, the CWO reports directly to the CEO.
Genesis of the CWO Role 
A 1999 CIO magazine cover story asked the question: Is it time for corporations to create a new executive position—Chief Web Officer—to “oversee the strategies of company intranets, extranets and Web sites?” The six experts interviewed for the article were split in their viewpoints. Some argued that the tasks associated with any new position should be handled by IT staff already within the company or guided directly by the CEO. Others said that, because a typical CIO was too focused on technology issues, there should be a new position created “to coordinate all Web-based activities and to put resources, both people and capital, into his or her organisation.”
The article “Chief Web Officers Take Charge” in the March 20, 2000 issue of ‘Inter@ctive Week’ explored the roles and responsibilities of CWOs through interviews and a survey of Web professionals.
Beginning around 2005, more writers began calling attention to the need to create a CWO position. These authors pointed to the need for an organization to have an executive at the C-level focused on coordinating and directing all Web-related activities. Cherian posed the need for the CWO position within an enterprise with the simple question: “Do you have a central internet group (CIG) directed by a chief Web officer and composed of dedicated staff for each business function?”
Contrast with CIO and CTO 
The position of CWO has emerged distinctly from the positions of Chief Information Officer (CIO) and Chief Technology Officer (CTO) because of the need to focus on and coordinate an organisation’s entire Web environment and presence. A CIO typically focuses on IT planning, procurement, and architecture for the enterprise; a CTO “is principally overseeing development of new technologies.”
Responsibilities of the CWO position vary among enterprises, depending on the needs and goals of the business. A CWO should have a deep and broad understanding of the Web and website governance issues. Some of the issues within the CWO jurisdiction could include online strategy, budgeting, systems & software administration, hosting, online marketing & communications, e-commerce, customer service, business development, online community & social media, web content development & workflows, website graphic design, user experience (analysis/design), information/data architecture, website analytics, security, archiving, accessibility, legal issues (for example, copyright, DRM, trademark, and privacy), and training, among others.
See also 
- Jahnke, Art (1 April 1999). "The Powers That May Be: Executive Offices: Some CIOs think it's time for corporate America to anoint the Chief Web Officer". CIO, Section 2, WebBusiness (USA: CIO) 12 (12): 28–37. ISSN 0894-9301.
- Thompson, Bina (August 1999). "Colgate-Palmolive Names Jack Haber Chief Web Officer". Retrieved 22 May 2010.
- Sprangler, Todd (2000-03-20). "Chief Web Officers Take Charge". Inter@ctive Week 7 (11): 70–76.
- Cherian, Abe (September 2005). "One Simple Strategy to Organize Your Online Business". Retrieved 22 May 2010.
- Tingmon, Chris (April 2006). "It’s Time for a Chief Web Officer". Retrieved 22 May 2010.
- Stopforth, Mike (November 2006). "Where Does the Web Fit?". Retrieved 22 May 2010.
- Berlind, David (November 2006). "Does your company need a Chief Web Officer?". Retrieved 22 May 2010.