...
| About us | Purpose and role of faculty. Strategic objectives. Strengths and features. Org chart. Link to faculty handbook. |
| Location | Link to Our campuses. Include faculty-specific info about facilities if necessary. |
| Staff / Faculty staff | People finder tool? All staff associated with the school. Not presented in a table. Student and Academic Services - who, what, when (counter hours), where. |
| Forms | As on faculty sites now - large number of downloads. (May move to 'Current students' in the future.) |
| Mission, vision and values | If required |
| Committees and boards | If required. Complex information needs to be simplified or 'flattened' out - not nested too deeply. |
| Affiliations | If relevant at faculty level (rather than school level) |
Dean's list | Dean's list, Dean's award. |
...
Summary of approach
- Sections/areas, not separate sites.
- Much smaller and simpler - audience focused, clearly defined purpose.
- Content much more integrated with mainsite. Content exposed in key areas of site where visitors are looking at related material.
- No content duplication.
- Flexible approach - 'local' content that has no logical home on mainsite remains on school site.
- Aligned with mainsite approach for content being organised by task, topic or user group - not by organisational structure.
- Encourage people to think about F&S content (rather than F&S 'sites').
...
Risks
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Faculty and school staff may not support the approach; or may support it on face value, but not really understand how it works. | H | H Approval for the approach may be obtained, but when work starts there could be repeated rounds of negotiation required, putting stress on relationships and timeframes. F&Ss could go along with the approach, but build their own sites, wikis (etc) independently. | See the consultation on the approach as a process of change and education. In particular, staff in faculties and schools (who? the decision makers? administrators? managers?) need to understand and buy in to the user-centred approach to IA (rather than organisational unit-centred) and plain language. This may mean having more mini-workshops and meetings with groups of staff. Showing built examples of key deliverables will help stakeholders visualise where they need to get to (eg, topic page, UG degree page (if changed), F&S area). |