Web Strategies

1
Web Strategies

• Chair Andrew Aird, KCL
• Reporter William Mackintosh, University of York

2
Session 1 Overview

• Ice breaker
• How many institutions have a web strategy?
• gt 20 institutions represented
• Only 4 had a web strategy
• Lengthy discussion about the need for a strategy
• Questions to be addressed in Session 2

3
Web strategy Why bother? (1)

• A strategy is redundant
• An institution already has a number of high level
  strategies.
• Web is only a delivery mechanism
• Web will be implicit in the strategies anyway

4
Web strategy Why bother? (2)

• Middle ground
• Institution has several high-level strategies
  which refer to the web and address business
  needs.
• A web strategy should refer to the other
  strategies and pull strands together.

5
Web strategy Why bother? (3)

• Strategy is essential
• Web is all-pervasive, omnipresent, and driving
  the institution
• MLE

6
Questions to be answered

1. What is a web strategy?
2. Identify what should be included in a strategy
   and what should not be addressed.
3. Who are the stakeholders?
4. Who should own the strategy?

7
Q1 What is a web strategy?

• Strategy is distinct from an operational document
  e.g. rules and guidelines
• A document which can be consulted
• Set out aims and objectives
• A need for regular review and updating of the
  strategy
• Implementation plan could form part of strategy

8
Q2 What should be included in the strategy?

• Define the scope of the strategy
• Centralisation vs. decentralisation
• Scalability
• Who decides what
• Refer to other strategies

9
What should not be included in the strategy?

• Technical details

10
Q3 Who are the stakeholders?

• Strategy needs to address all audiences
  potential applicantsalumni, staff, etc.
• gt Stakeholders are everybody

11
Q4 Who should own the strategy?

• Implementer is owner
• gt Web Team

12
End of Presentation

• Thank you for your attention.