Sorry about the Hot Fuzz start to this blog, but it matches the out comes quite nicely for the programme meeting we had yesterday.
Last week has been interesting for the project. In discussions with one spoke it was clear that some changes had been made to the processes around course design with little expectation of making a large impact on the creation of more flexible awards. This matched discussions at the programme meeting about whether changing processes and documentation alone will make the desired changes we need within institutions. There is hope that the changes made as part of the spoke will support more responsive curriculum design and a slicker curriculum portfolio. Discussions then turned to how these expectations would be evaluated, there is some difficulty in this a much of the baseline for the spoke was based on perceptions. The spoke will be using the expectation spreadsheet it completed at the start of the project along with the JISC Evaluation workshop notes, to support the evaluation process. The spoke is also reviewing the usefulness of recording date information against each stage of the process for faculties to measure responsiveness.
The JISC programme meeting raised an interesting discussion around institutions expectations of learner and staff cultural attitudes to technology and how this differs between institutions. As we, in the project, talk a lot about culture being a barrier to change is there a practical way of addressing this? Bolton spoke briefly on training they are providing for staff around supporting using technology for learning. Does Enable need to think about putting together training for staff to help manage these cultural attitudes, using faculties who we have identified as already making those changes? I’m not sure we would be the right people to do this but we can try talking about it to the right people. Some projects in the programme have created tools to help staff identify their teaching approaches and what others are doing in their institution.
The final part of the day was a discussion summarising the work projects have been doing and how it can be used to help others, stopping duplication of effort at a higher level than simply within an institution. The projects discussed whether it would be possible for them to bring together the combined effort using design studio or whether it was something that needed to be organised centrally with everyone in a room. The idea of an information roadmap was seen to be useful and projects were happy to provide information to support it, although what information was needed and in what form was difficult to determine. Some felt that information needed a context within a process map (or in a model) and Bolton demonstrated the work they were doing with the FSD programme. I personally feel that a generic model to support staff with a starting point for discussion would be useful, and that validation documents themselves would be of little value. Perhaps a quick model/map with each stage a clickable link to a list of information collected/used would be best. It will be interesting to see the out come of this session will be.
Further relevant blogs: