2. Making it fail … A user guide to getting eportfolio implementation wrong.

3. Your task … In this session you will pretend to implement an eportfolio system in the least sensible way. In other words, what things will you do to make the project most likely to fail.

4. Think about … What things will make life difficult for the project? Which are most detrimental to success? Which are easiest to resolve (given the will)?

5. How others got it wrong … 1. Not getting key people on board 2. No academic leadership 3. Not emerging beyond the champions 4. System too complicated, unusable, inaccessible 5. Insufficient training for staff and students – poor internal support (technical and pedagogical) 6. Getting the levels of ownership wrong 7. Lack of long term strategic commitment 8. Technical infrastructure not suitable 9. Don’t have (or articulate) an understandable and acceptable purpose 10. Insufficient time for planning and preparation 11. No planning for growth 12. Poor support from the supplier 13. No back-up strategy 14. Product costs escalate 15. Poor introduction, induction. Bad messages 16. Bringing in too many new tools at once 17. Relying on good will 18. Not having a common understanding of eportfolio 19. Have no link to strategic initiatives 20. No communication or sharing between users, implementers, stakeholders... 21. It’s the cure for all your ills 22. Don’t embed use in the curriculum … Layer it on top. 23. Do a ‘short’ trial or use the word Pilot 24. Ignore and exclude the middle managers 25. Ignore the needs of the academics 26. Tell everyone that it’s easy “it will reduce your workload” Honest!! 27. Don’t articulate the differences between the LMS and the PLS 28. Train, expose or promote all aspects at once 29. Don’t have a project champion, leader or manager. No focal point. 30. Make it optional 31. Introduce it at the end of a course or programme 32. Don’t value (or even view) the work of the learners 33. Choose a tool that isn’t fit for purpose 34. Provide no support – technical or pedagogic 35. No single sign on 36. No clear learning purpose 37. Make sure you have no central support (no budget, no training, no resources...) 38. Design your curriculum around the features of the tool 39. (Regular) Institutional change 40. Poor admin procedures

6. We’re clear in our purpose. Are you?