2. challenges to implementing CMS systems Selling concept to users Selling project to senior management and financial controllers What to use?

3. Selling concept to users Get them involved and find out what’s needed Take the best from the past Pilot scheme - allay their fears Map their workflows and present to them how it can be accomplished or improved Tell them it will help with technical challenges they may meet (scare them with accessibility) Sell end product - actual benefits:  "Don't need to know HTML" - empowers them to publish  Aids accuracy and timeliness

4. Selling concept to management Cost Benefit Analysis, and threat of legislation Real issues (FOI, - removing bottlenecks - better use of resources - efficiency) Tie to current, major issues (e.g. student recruitment) - quote their own strategy documents back at them Use - what is the impact of not doing it? Warwick have got one External consultant - believed over and above own staff - invite colleagues from other places Makes branding easier Tying web to institutional information systems

5. What to use? Network like crazy by attending workshops and events, consulting with peers at other institutions and joining mailing lists and newsgroups Compile your top ten questions and send to current practitioners for honest answers Be thorough in your requirements document Consider local factors - your technological infrastructure and in-house experience available Look at other public sector experience

6. Point for the panel… Is there a “Resource gap”? Do we need: HE Community publications such as “good practice guides” more regional groups perhaps a UK HE CMS Wiki!