Purpose and authority
The University Enterprise Web Advisory Council (EWAC) is entrusted with raising, hearing and discussing issues that affect University web properties, its online ecosystem and web visitors. The EWAC is expected to make recommendations to the President’s Executive Leadership Team (ELT) in the best interests of the University of Utah as a whole, based on consensus of the major campus web property service providers: marketing and communication leaders for academic and administrative units partnered with technologists. The EWAC will coordinate recommendations as needed with other oversight committees, such as the Senate Advisory Committee on IT, Strategic IT Committee, Architecture and New Technology Committee, etc.
Mission, scope and key goals
The EWAC considers the holistic view of the web visitors’ experience, addressing issues raised by University stakeholders and visitors related to the ecosystem underlying the web experience, such as content, presentation, infrastructure, policies, funding, tools and technologies. University Home Page Suite, templates and enterprise tools will also be considered. The EWAC has a fiduciary responsibility to identify solutions that align with the University’s strategic goals and represent what is best for the University at large.
EWAC considers programs, policy and initiatives surrounding all University web properties and the ecosystem, such as:
- University home page suite interactions, content, infrastructure, tools and template support to campus units
- Information architecture and common elements to provide a high-quality experience and seamless navigation for visitors
- Campus-wide Web policies and best practices
- Website accessibility, security and privacy
- Recommendations for funding and strategic purchases benefiting web property owners or presentation of our content and image
- Strategic, enterprise programs affecting University web presence
- Online and face-to-face communities of practice for sharing information and resources
- Holistic Web strategic planning such as:
- Coordination of UIT, ITS, UMC strategic initiatives with local campus units
- UIT UMC Strategic Plans
- Special enterprise project planning
- Accessibility, security plans and issues
Out of scope issues include, but are not limited to:
- Web applications
- Functional group priorities and projects (student, finance, HR, colleges and other campus-wide applications)
- Content on individual administrative and academic web properties
- Scheduling and managing UIT or UMC resources and operational decisions
- Functional and technical specifications for specific projects (applications)
- Analyze, vet and obtain consensus on recommendations for the president’s executive leadership team (ELT)
- Manage, approve, and recommend campus Web properties support services and university architecture (content, tools, data, infrastructure, process, accessibility)
- Obtain campus-wide input using task force groups to explore and propose solutions
- Develop, approve and update the Holistic Web strategic plan
- Analyze and make recommendations regarding overall spending on web properties
- Identify risks and take appropriate action
- Develop unified plans among web property managers on campus
- Update web policy
- Develop and administer the community of practice for web/content managers and web property owners
Membership and voting structure
The Chief Information Officer (CIO) and Chief Marketing Communication Officer (CMCO) will invite members to serve on the committee, representing the various functional and system perspectives, such as content, marketing, public relations, communications, tools, infrastructure, architecture, web managers, cyber security, Web accessibility, visitors and consumers of Web content (students, faculty, staff), etc. Representatives will be the associate dean or senior director with strategic responsibilities for the unit’s web site suites, funding and marketing and communication strategies. The council will also include a member from the Senate Advisory Committee on IT and the Communication Council.
A council chair and executive committee will be appointed by the CIO and CMCO to serve at least two years. After the original appointment, the executive committee will elect a chair every two years and recommend individuals to fill empty positions on the council as needed.
All council members will have full voting rights for matters on council meeting agendas.
|Paul Burrows||Information architect, Teaching and Learning Technologies|
|Holly Christmas||Web developer, College of Fine Arts|
|James Elder||IT associate director, Continuing Education and Community Engagement|
|Jodi Emery||Director of marketing & sales, Continuing Education and Community Engagement|
|Matt Gauthier||Web software developer, College of Engineering|
|Pat Hanna||Professor, Linguistics|
|Barb Iannucci||Associate director for content mgmt. & usability, University Information Technology|
|Thad Kelling||Director of marketing & sales, Lassonde Entrepreneur Institute|
|Mike Martineau||Director of institutional analysis, Budget and Analysis|
|Scott McAward||Director, Center for Disability & Access|
|Lori McDonald||Dean of Students|
|Elizabeth Bandy||Marketing manager, School of Business|
|Dean McGovern||Director, Bennion Community Center|
|Aretha Minor||Director, Enrollment Management|
|Corey Roach||IT manager, Information Security Office|
|Kim Tanner||Associate director for software platform services, University Information Technology|
|Nathan Tanner||Director of marketing & sales, Interactive Marketing & Web|
Associate director of communication, CON Advanacement
|David White||Senior web developer, University Marketing & Communications|
Ex Officio members:
|Mark Beekhuizen||IT director, Quinney College of Law|
|Tim Ebner||University registrar|
|Steve Hess||Chief Information Officer, U of U Campus & USHE|
|Peter Jensen||Associate professor, School of Computing|
|Paula Millington||Director, Strategic Planning & Process Team|
|Chris Nelson||Director of PR/communications, University Marketing & Communications|
|Ken Pink||Deputy CIO|
|Scott Sherman||Special assistant to the CIO|
|Cory Stokes||UOnline Director and Associate Dean for Undergraduate Studies|
|Scott Troxel||Director of digital strategy, University Marketing & Communications|
|Jim Turnbull||Chief Information Officer, U of U Hospitals & Clinics|
|Bill Warren||Chief Communications & Marketing Officer|
|Amy Wildermuth||Professor, Quinney College of Law & associate vice president for faculty|
Responsibilities, roles and duties
Council members are expected to review governance documents and participate in the evaluation and recommendation phases of the process. Council members are also asked to act as the first line of communication regarding campus web governance to other marketing and communication, academic or administrative units. Representatives will contact functional experts and other knowledgeable stakeholders to gather input for making the best decisions for the university. Voting members are expected to attend all EWAC meetings and vet issues in their communities (marketing, public relations, communications, technology) to help make the best decisions for the university. Members also may be asked to serve on ad hoc committees or to find suitable stakeholders to serve on ad hoc committees.
Representatives serve on the EWAC at the discretion of his or her dean or vice president. Members of the executive team will serve a minimum of two years; there is no specified minimum requirement or maximum term limit for council members.
Agenda and meetings
The EWAC agenda is gathered and prepared by a governance liaison (Deputy CIO and CMCO) and approved by the council chair. The council meets once a quarter, but may meet more frequently or hold virtual meetings and votes if necessary. The executive committee may meet more frequently in preparation for the quarterly meetings. The EWAC council meetings are open and welcome all stakeholders, but physical meeting space may limit the number of attendees.
Written agendas and meeting minutes are prepared by a governance liaison within University Information Technology and posted publicly.
Additional information related to ongoing governance council operations can be found in the operating guidelines.
Changes to this charter must be approved by the Executive Committee and the President’s Executive Leadership Team.
Questions or Comments?
Contact Scott Sherman, special assistant to the CIO.