Programme timelines

May 17th, 2012 by sheilmcn

As the Design projects come to and end and are compiling their final stories of their four year journeys, I’ve been thinking about timelines. So, in preparation for next week’s final programme meeting, here’s a timeline which pulls pictures and videos from youtube and twitter that have been tagged with #jisccdd (thanks to my colleague Martin Hawksey for creating the template to do this).

I also set up a couple of other timelines using the Diptiy timeline service way back in 2009:

This one pulls a feed from the CETIS Curriculum Design web site topic area 

This the #jisccdd twitter feed.

 And this one has various feeds relating to #jisccdd

Curriculum Design Technical Journeys: part 3

April 23rd, 2012 by sheilmcn

**NB this post has been amended from a post on my CETIS blog**

Continuing from my last post, the next part of the programme technical journey focuses on the Cluster B projects: Co-educate, SRC, P3 who had similar objectives in terms of organisational change.

SRC
*Project Prod entry

In terms of organisational change, SRC (Supporting Responsive Curricula) is part of larger set of project EQAL which is radically changing the way the MMU provides learning services (in the broadest sense) to its students. Other JISC funded initiatives e.g. the W2C project are connected to this major organisational change, of which SOA approaches is key. Professor Mark Stubbs’ keynote presentation at this years CETIS conference gives an overview of their overall technical approach.

MMU is in the processes “introducing a new curriculum framework, new administrative systems and processes, revised quality assurance processes and new learning systems to transform the student experience” and the SRC project has been at heart of the complete revision of all undergraduate courses, through developing a processes and workflows for a common curriculum database which feeds into a range of other learning services a part of their “corePlus” learning environment provision.

All course module and assessment structures have been completely revised (starting with first year and now extending to 2nd and 3rd). A new course database is now being populated using a common set of forms which provide a common set of tags (including competencies) and unique identifiers for courses which can be used a part of a wider set of “mash up” activities for students to access. When redesigning the course database, extensive stakeholder engagement and mapping was undertaking (using Archimate) in relation to QA processes which formed a key part of the project’s baseline report. A case study details this work and this blog post provides a summary of the new course documentation and QA processes including a map of the new peer review process.

A key part of the project has been to explore effective ways for students to showcase their experience and abilities to employers. A number of systems have been explored and an institutional e-porfolio strategy produced. A decision has now been taken to provide institutional support for Mahara, beginning in September 2013.

In terms of standards/specifications, this being MMU, XCRI is integral to their systems but hasn’t been a core part of the project. Like other projects, the institutional demand for xcri is still not widespread. However members of the team are key to developments around the integration (and thereby extension) of XCRI into other specifications such as MLO and various competency related initiatives.

Now the major technical implementations have been implemented, the team are now focussing on the wider cultural changes, engagement with staff e.g. the development of the Accrediation! Board game which I’ve written about before, and evaluation.

Coeducate
*Project Prod entry

“Coeducate is a cross institutional project that will focus our staff on a re-engineering of the professional curriculum. It will develop new processes and technical systems to support curriculum development and design that start with the needs of the learner and their organisation. This will be negotiated and delivered in partnership and with full recognition of in-work and experiential learning.”

Coeducate, has taken an the almost opposite approach to MMU in terms of a top down approach to creating and managing new courses. They have connected their SITS database with their new Moodle installation see this blog post for an overview, but unlike MMU do not have a set of course templates, or the same level of automatic course population. Instead, staff now have more flexibility in terms of creating courses suited to their specific needs, as this post and linked documentation describes. The IDIBL framework has also been developing as template for course creation, however the institution has developed an alternative undergraduate curriculum framework. The team have also produced a report on approaches to developing open courses, which again should provide a useful staff development resources.

Following this more bottom up approach, the team have also instigated an series of innovation support network seminars and produced a set of online resources (housed in Moodle) to support staff as new institution validation process are being introduced. Like so many of the projects being caught up in a sea of other institutional change initiatives that aren’t as tightly coupled as MMU, the project has focused effort on providing support to staff to guide them (and in turn the institution) through changes such as course revalidation. The project has been able to to influence and inform institutional strategy to initiatives such as course revalidation through some light weight data analysis of the VLE in terms of course structure, numbers and types of assessment etc.

Over the past year, the team have also been exploring the Business Model Canvas tool in terms of its suitability for learning design planning and/or conceptual modelling. The flexibility of the tool has been identified as a key strength. The team have found other more specific learning design tools such as the LDSE too prescriptive. This post outlines the approach of integrating this tool within Archi (which is being developed by colleagues at the University of Bolton). The tool is currently being trialled with PGCHE students, and again will hopefully provide another design tool for the University and the rest of the community. The team have been using the tool to support staff in course revalidation process, and are lobbying for its adoption into the formal revalidation process.

The team had hoped to do more work on integrating widgets into Moodle for course authoring. However staff issues and a refocus of project priorites has meant that not as much progress on this has been made as originally intended. However, over the last few months the team have been able to build a customisable 8LEM widget (more information and a link to a beta version is available here). The principles outlined in the 8LEM methodology are also the basis for the work of the Viewpoints project, and by the end of this June, it is hoped that there will be at least two versions of the widget available based on the approaches of the Viewpoints project as well as the “vanilla” version.

Bolton has also been successful in gaining funding for one of the JISC Course Data projects and this project will extend work started in Co-educate. The work done through the CoEducate project has help to articulate some of the key requirements for data reporting and practical uses of data collection, including key indicators for retention and drop out.

As with other projects, the challenge for the team is to ensure that the resources and approaches explored and advocated through the project continue to be embedded within institutional frameworks.

Enable
*Project Prod entry

“As a ‘hub’ initiative, the project aims to enable the University to join together its various change initiatives around curriculum development into a coherent and radical overall change process, which will ensure all stakeholder needs are understood, identify overlooked problems areas, and provide a sustainable solution . . .”

The Enable project started out with the vision of connecting and enhancing institutional processes. As with all the other projects, senior management buy-in was always a critical part of the project and a Senior Management Working Group was set up to ensure this buy-in. Part of the wider institutional story has been the relatively high number of changes at senior executive level which have impacted the project. The team have shared their experiences around managing change and information processes.

In terms of technologies, as well as being part of the Design Programme, the project has engaged with a number of other JISC funed initiatives. The team have been an early champion of EA approaches and have been involved with the JISC FSD EA practice group initiative. They have piloted TOGAF approaches in an Archimate pilot. Their experiences of using Archi in for their work in external examiners pilot are summarised in this blog post and embedded slides. Phil Beavouir, the developer of the Archi tool has also posted a thoughtful response to this post. If you are interested in EA approaches , I would recommend both these posts.

The team have also been experimenting with a number of different ways to automate their code build, acceptance, testing and deployment processes. These tools and techniques are being adopted and used in other areas now too. Again the team have promised to share more via the blog, in the meantime a summary of the technologies they are using are detailed in the project Project prod entry.

The team have been looking at Sharepoint and, another example of cross JISC programme fertilisation, were able to gain some of the benefits realisation funding for the Pineapple project to experiment with its software. An overview presentation is available here. The pilot was successful, but, at this point in time, no institutional decision on an institutional wide document management system has been made, so no further developments are being introduced in respect of this work.

The team feel that the EA approaches have “enabled” them to define with stakeholders the key areas to be addressed in terms of developing effective processes. And, have found that having “just enough backing” for developments has been effective. Particularly in gaining senior management buy-in whilst Executive decisions are not possible. The project has been able to illustrate potential working solutions to recognised problem areas. They have also been sharing their experiences of EA extensively with the rest of the sector, through presentations at various institutions.

PC3
*Project Prod entry

“The Personalised Curriculum Creation through Coaching (PC3) project is developing a framework that places coaching at the heart of the personalised curriculum design. Learners will be able to select provision suitable to their needs, construct an award (or module set), access resources and learning support, and negotiate assessment, with structured support from a personal coach. The PC3 Framework will facilitate this process by developing the necessary processes, documentation, training and technological support, within the context of Leeds Met’s flexible learning regulations and systems.”

Again the PC3 project has been on quite a journey over the past three and and a half years. Changes at senior management level have meant that, whilst not changing the underlying principles of the project of using coaching (as explained in its curriculum model ), the project team have had to adapt some of their anticipated approaches and have experienced delays in decisions around key institutional wide provision of technologies.

A major milestone for the project has been decision to adopt PebblePad as the institutional portfolio system. The team acknowledge that there is still work to be done around the integration of resources in the VLE and in Pepplepad, in terms of the user experience of switching between systems. Perhaps Pepplepad’s planned LTI adoption will help mitigate some of these issues.

The project is now reaping the rewards of their early work in staff development and are now working increasingly to support students, and their use of technology whilst implementing the PC3 coaching methodology. The approach is now embedded into the Sport Business Management Degree programme (see this post for more information) and students are playing an increasingly important role as coaching ambassadors.

Earlier in the project the team had created a number of video based resources around coaching. Now they are supporting students in the creation and sharing of videos as part of their course work and as coaching ambassadors. The team are working with institutional AV staff around developing approaches to creating video resources with students. The project is also planning a conference, where students will be key contributers, and plan to video sessions and make the recordings available as a set of resources.

The team are also seeing increasing use of social media sites such as Facebook for communication and even for running coaching sessions. This has very much been student driven and developments are being monitored with interest.

The team have also been using a number of google products (forms and documents) for sharing of project information and for part of their evaluation by using google forms to collect session feedback.

Where possible, the project are releasing resources as OER. To this end have they have benefited from the experiences of the Streamline project which was funded through the JISC/HEA Academy OER programme. Institutionally there has been a significant development around workflow of OERs with the institutional repository and the JORUM national repository that the project has benefited from. Again another example of cross programme sharing of experience.

So, another set of projects with common aims but very different approaches to organisational change. In many ways, a top down approach as exemplified by MMU may well be the most effective way to gain widespread adoption. However, MMU have benefited from a more stable senior management perspective and have not had to re-articulate their vision to a different set (or sets) of stakeholders during the project lifecycle as some of the other projects have. Engaging staff and students at different levels, as Bolton and Leeds, have done may well be just as effective in terms of seeing real pedagogical change in the longer term. But whatever approach, the importance of modelling and being able to visualise, and develop conversations and engagement has been central.

Curriculum Design Technical Journeys: Part 2

April 4th, 2012 by sheilmcn

**NB this post has been amended from a post on my CETIS blog**

Continuing from my last post, the next part of the programme technical journey focuses on Cluster B projects: T-Sparc, PALET, UG-Flex and PREDICT who all had a broad common theme of organizational change.

In many ways this cluster represents the ‘business end’ of the programme. With Cardiff, Greenwich and City Universities all having pretty robust institutional system integrations in place before the programme started. The programme was a way to develop these existing systems to allow more effective and pedagogically driven processes to be developed and incorporated.

T-SPARC
*Project Prod Entry

Unlike the other 3 projects in this cluster, T-Sparc didn’t have as robust an infrastructural starting point, however providing a means for organizational change around curriculum design was a key driver.

The project had four key aims;

“• To inform programme design activity through the improved provision of relevant information to those stakeholders engaged in curriculum design.
• To redesign the ICT infrastructure which supports the workflow of curriculum design and programme approval processes.
• To develop and pilot mechanisms for supporting, through electronic means, course team discussion during their programme design activity.
• To develop and pilot the electronic representation of programmes and underpinning evidence for the purposes of approval.”

One of the key findings from previous technical conversations with the programme was the number of instances of Sharepoint, and its central role for a number of projects. As I commented then, that probably wasn’t that surprising given the that over 90% of UK universities have an installation. The T-SPARC project initially were looking towards utilizing Sharepoint as a definitive document repository and take advantage of its document version control abilities. However as the project has progressed, it has evolved to become the central part of their curriculum design system. A number of workflows were created from their stakeholder enagement and baselining processes using combination of modeling techniques including experiments with BPMN, UML and Visio as outlined in these blog posts.

The team were also able to negotiate dedicated time from an specialist Sharepoint developer in the institution to work with them using an agile development process. A dedicated area in the project blog documents their experiences in working with Sharepoint, and agile project methodology. The posts in this area are particularly useful in sharing real experiences of a project working with agile methods, as well as with corporate IT services – worth a look if you are new or going to be working with others new to this type of approach. Their prototype PADS (programme design and approval system) system is now being trialed by eight programme teams. A key challenge in terms of sustainability and embedding is how to ensure that the system is integrated into wider institutional initiatives such as the recent implementation of SITS. However, as with many other projects, cultural interoperability is perhaps more of a challenge than its technical counterpart.

Perhaps the leading light in terms the use of video narratives, the T-Sparc team have invested time and money into capturing the stories and experiences of their key stakeholders (staff and students) included a very innovative video baseline report. The team have used a mix of video caputure methods including flipcams and the ipad based MiiTuu sytesm. The later is a relatively new development which the team have been using with students and employers. The allows exporting and sharing of questionnaires across devices and allow for time reductions in the setting up and gathering of data. The system utilizes i-Tunes, BCU has an institutional wide itunes provision, so again sharing is simplified. The use of video for personal reflection is fairly mainstream within the institution now too. The team have made extensive use of free editions of video editing/compression packages (Handbrake, Microsoft Expression), however they are still searching for a real time video compressor. Ideally one which would compress on the fly and have an automagic deposit to repository feature to suit their needs – and budget. Again storage for video is an issue (as highlighted in this post) – is this where cloud storage could play a useful institutional role?

The team are also developing a Rough Guide to Curriculum Design which is outlined in this post which will synthesis all aspects of the project.

PALET
*Project Prod Entry

In contrast to T-Sparc, the PALET project was working within the context of a fairly robust internal technical infrastructure based largely on IBM websphere and Lotus tools. Institutionally, the Lean methodology was also being widely supported. Cardiff also had previous experience of Enterprise Architeture and, as the project developed, through other institutional projects, links to the JISC FSD programme.

The PALET project’s aims were to:

“Utilising the Lean Thinking methodology for process improvements, the PALET project will develop revised procedures for the approval of new programmes to create a more agile, efficient and flexible approach to the design of new curricula and the subsequent programme approval process. In the context of the University’s Modern IT Working Environment (MWE) project, a service-oriented approach will be utilised to develop a toolset to support academic and support staff through each stage of the new programme approval process, which will also ensure that the resulting programme and module information is clearly defined and can be seamlessly utilised by other business applications.”

Key to the project has been the creation of a single data source which contains all relevant curriculum design and approval information which can be easily re-purposed and accessed by various stakeholders. Interestingly the project has ended up taking a scaled down approach and building their own webservices and not using IBM tools.

They have moved away from using websphere as their main data source and SITS is now core for the storage of course related information. This has allowed the team to write their own webservices using Grails, and taking restful approaches and the Groovy programming language. This was quite a sea change for all involved as outlined in this blog post. As highlighted in the post, the team have found this experience very useful, and this generic web services approach/architecture is now being rolled out in other parts of data provision in the University. This should help with sustainability and the embedding of more data services/ provision as and when needed. Again the successful managing of change during the lifecycle of the project has been key for everyone. Sometimes a simple approach is best.

Parts of the their larger infrastructure remain and there are now better connections with for example Lotusnotes and bringing feeds and topics into one overarching portal for end users. However, the team have developed a dedicated portlet for course information which links to the main websphere portal. Details of which are outlined in their portlet technical specification. The work done on the underlying technical infrastructure ensures that the progress in terms of redesigning course and module templates can be fully utilised.

Like T-Sparc, the team are still analyzing the need for XCRI, and are confident that they could easily create a feed if need, however there still aren’t key internal drivers for this as yet.

A full technical specification for the project is also available.

UG –FLEX
*Project Prod Entry

Like PALET, UG-Flex also had a robust infrastructure (based largely on SunGard Banner ) in place which they planned to build on.

“We envisage that our technical outputs will be of use to other institutions using SunGard’s Banner system and we plan to feed these outputs into the European and international Banner community. The project also intends to share the lessons learned about the challenges of working with a proprietoriaml product based applications with the wider education community.”

Although the institution did have dedicated business analysts the experience of the project has had an impact on approaches to business processes in general and the use of and techniques applied for modelling. For example although their Business Analyst were conversant with various visual modeling techniques and languages (BPMM, BPEL, UML) to illustrate and developed technical infrastructures, having resource dedicated to the project allowed them to work at a far greater level of detail. This experience has allowed the for the processes used in the project be incorporated into day to day techniques in other large scale projects throughout the University. Exploration of TOGAF methodologies is ongoing and staff are undertaking accreditation training..

In previous conversations with the team, they had expressed an interest in XCRI. Greenwich has been successful in gaining one of the JISC Course Data projects and it is now embarking on their xcri-cap production stage. A nice example a synergistic relationship with the outcomes and findings of UG-Flex, and future institutional planning e.g. KIS returns.

Through Banner, there is use of IMS enterprise compliant tools, but there has never been a plan to develop anything at the enterprise level. However, in terms of future developments there are some major changes for the IT team. The new versions of Banner are now component based as opposed to Oracle based. Whilst on the one hand this does allow for greater flexibility and more agile approaches, as well as an improved UI; on the other this is a major change for some more traditional database developers, and so an issue for staff skills and development.

Again we had talked about Sharepoint in previous discussions, and concerns had been raised about its suitability for managing data as opposed to documents which it has undoubted strengths in. Now there is a fully supported installation in their Business School. Preparatory work is been undertaken around implementing some automated workflows, in particular around QA processes which have been developed through UG-Flex. As an adjunct to this work, and UG-Flex, a personalized timetabling service is being developed and trialled in the Business School. The team have also kindly agreed to write this up as a guest post in the CETIS other voices blog.

During the project lifecycle the institution has also migrated to Moodle (more details of some of their approaches and the lesson learnt about stakeholder involvement and process mapping have been included in this summary post from Lou McGill )

Overall the team have found that the UG-Flex project has been exemplary in terms of academic needs driving developments, and not the IT department. Particularly with the VLE migration, there is a strong sense of ownership from the academic community as they feel they have been fully part of the decision and migration process.

PREDICT
*Project Prod Entry

PREDICT was again a project with a pretty robust architecture and like UG-Flex, they have noticed a perceptible change in attitude during the lifecycle of the programme. The use, and understanding of the term, Curriculum Design is now far more commonplace in conversations within the IT department, and the core business of the University – teaching and learning – is being considered more at the start of discussions about new IT developments.

“The project focus is to develop a new curriculum design process that is efficient, flexible, focuses on enhancing educational development and the student experience and, is supported with responsive technology to accommodate our curriculum models. It is essential that the design process takes account of our diverse stakeholders – whether learners, staff or employers.”

In terms of use and standards, the project haven’t really deviated from their original plans. One of the few institutions to be have an implementation of xcri before the programme started, they actually haven’t done much more. They have looked at xcri-cap but, largely due to the current lack of vendor buy-in and wider external drivers, they haven’t felt the need to implement it.

In light of the KIS requirements they are reviewing their current data provision and in particular their local course information database (Prism). They are considering some re-engineering and simplification of the UI, taking a more component/SOA approach. They have also been in discussions with other institutions about building similar tools in SITS. SITS and in particular StuTalk has proved to be central for developing more business processes, and they have “service enabled” their installation for wider business processes. Like Cardiff they use IBM Websphere and it provides their key middleware stack. In conjunction with these back-end developments, the project has also made progress in the redesign of their course and module documentation for staff.

The PREDICT project, and other internal projects relating to blended learning have been useful in terms of developments in their Moodle deployment, and getting people to engage more about using it, and not just using it as a defacto course notes repository.

One area the PREDICT project has highlighted is a gap in up to date information on staff in the HR system. There is basic employment/payroll information but not an awful lot on what they actually do day to day. Creating more personalised timetables is something they (and many others) are currently investigating. The potential for joining up curriculum information, student information with staff information so, for example, a student would see which lecturer was taking each class, and have links to the staff members research interests; publications etc is very attractive. But again, requires more work on the sharing of the appropriate information between systems.

Overall the project has shown that it is worthwhile to allow staff and students and the IT department time to think through their IT service provision together. Enhancing business processes alone can’t make a poorly designed course better (the supporting pedagogically guidance the project has produced will help with that!), but they can make some tasks easier/less time consuming. Like UG-Flex there is now more IT provision planning being done in conjunction with educational development staff which wouldn’t have happened before the project.

So from this cluster, agility and greater communication between central IT provision has been key. Agile approaches can allow for more rapid development of light-weight, but effective web services as highlighted by PALET. However, this change of approach can bring with it issues of staff skills and development. Effective communication is always central to the success of any change process, and maintaining the links fostered through these projects will be key for future sustainability and embedding.

Curriculum Design Technical Journeys: Part 1

March 21st, 2012 by sheilmcn

**NB this post has been amended from a post on my CETIS blog**

This is the first of a series of posts summarizing the technical aspects of the JISC
Curriculum Design Programme, based on a series of discussions between CETIS and the projects. These yearly discussions have been annotated and recorded in our PROD database.

The programme is well into its final year with projects due to finish at the end of July 2012. Instead of a final report, the projects are being asked to submit a more narrative institutional story of their experiences. Rachel’s recent post gives a great overview of this approach. As with any long running programme, in this instance, four years, a lot has changed since the projects started both within institutions themselves and in the wider political context the UK HE sector now finds itself.

At the beginning of the programme, the projects were put into clusters based on three high level concepts they (and indeed the programme) were trying to address

• Business processes – Cluster A
• Organisational change – Cluster B
• Educational principles/curriculum design practices – Cluster C

I felt that it would be useful to summarize my final thoughts or my view of overall technical journey of the programme – this maybe a mini epic! This post will focus on the Cluster C projects, OULDI (OU), PiP (University of Strathclyde) and Viewpoints (University of Ulster). These projects all started with explicit drivers based on educational principles and curriculum design practices.

OULDI (Open University Learning Design Initiative)
*Project Prod Entry
The OULDI project, has been working towards “ . . .develop and implement a methodology for learning design composed of tools, practice and other innovation that both builds upon, and contributes to, existing academic and practioner research.”

The team have built up an extensive toolkit around the design process for practitioners, including: Course Map template, Pedagogical Features Card Sort, Pedagogy Profiler and Information Literacies Facilitation Cards.

The main technical developments for the project have been the creation of the Cloudworks site and the continued development of theCompendium LD learning design tool.

Cloudworks, and its open source version CloudEngine is one of the major technical outputs for the programme. Originally envisioned as a kind of flickr for learning designs, the site has evolved into something slightly different “a place to share, find and discuss learning and teaching ideas and experiences.” In fact this evolution to a more discursive space has perhaps made it a far more flexible and richer resource. Over the course of the programme we have seen the development from the desire to preview learning designs to last year LAMS sequences being fully embedded in the site; as well as other embedded resources such as video diaries from the teams partners.

The site was originally built in Drupal, however the team made a decision to switch to using Codeigniter. This has given them the flexibility and level control they felt they needed. Juliette Culver has written an excellent blog post about their decision process and experiences.

Making the code open source has also been quite a learning curve for the team which they have been documenting and they plan to produce at least one more post aimed at developers around some of the practical lessons they have learned. Use of Cloudworks has been growing, however take up of the open-source version hasn’t been quite as popular an option. I speculated with the team that perhaps it was simply because the original site is so user-friendly that people don’t really see the need to host their own version. However I think that having the code available as open source can only be a “good thing”, particularly for a JISC funded project. Perhaps some more work on showing examples of what can be done with the API (e.g. building on the experiments CETIS did for our 2010 Design Bash ) might be a way to encourage more experimentation and integration of parts of the site in other areas, which in turn might led to the bigger step of implementing a stand alone version. That said, sustaining the evolution of Cloudworks is a key issue for the team. In terms of internal institutional sustainability there is now commitment to it and it has being highlighted in various strategy papers particularly around enhancing staff capability.

Compendium LD has also developed over the programme life-cyle. Now PC, Mac and Linux versions are available to download. There is also additional help built into the tool linking to Cloudworks, and a prototype areas for sharing design maps . The source code is also available under a GNU licence. The team have created a set of useful resources including a useful video introduction, and a set of user guides. It’s probably fair to say that Compendium LD is really for “expert designers”, however the team have found the icon set used in the tool really useful in f2f activities around developing design literacies and using them as part of a separate paper-based output.

Viewpoints
*Project Prod Entry

The project focus has focused on the development and facilitation of its set of curriculum re-design workshops. “We aim to create a series of user-friendly reflective tools for staff, promoting and enhancing good curriculum design.”

The Viewpoints process is now formally embedded the institutional course re-validation process. The team are embarking on a round of ‘train the trainer’ workshops to create a network of Viewpoints Champions to cascade throughout the University. A set of workshop resource packs are being developed which will be available via a booking system (for monitoring purposes) through the library for the champions. The team have also shared a number of outputs openly through a variety of channels including delicious , flickr and slideshare.

The project has focused on f2f interactions, and are using now creating video case studies from participants which will be available online over the coming months. The team had originally planned on building an online narration tool to complement (or perhaps even replace) the f2f workshops. However they now feel that the richness of the workshops could not be replaced with an online version. But as luck would have it, the Co-Educate project is developing a widget based on the 8-LEM model, which underpins much of the original work on which Viewpoints evolved, and so the project is discussing ways to input and utilize this development which should be available by June.

Early in the project, the team explored some formal modelling approaches, but found that a lighter weight approach using Balsamiq particularly useful for their needs. It proved to be effective both in terms of rapid prototyping and reducing development time, and getting useful engagement from end users. Balsamiq, and the rapid prototyping approach developed through Viewpoints is now being used widely by the developers in other projects for the institution.

Due to the focus on developing the workshop methodology there hasn’t been as much technical integration as originally envisaged. However, the team has been cognisant of institutional processes and workflows. Throughout the project the team have been keen to enable and build on structured data driven approaches allowing data to be easily re-purposed.

The team are now involved in the restructuring of a default course template area for all courses in their VLE. The template will pull in a variety of information sources from the library, NSS, assignment dates as well as a number of the frameworks and principles (e.g. assessment) developed through the project. So there is a logical progression from the f2f workshop, to course validation documentation, to what the student is presented with. Although the project hasn’t formally used XCRI they are noting growing institutional interest in it and data collection in general.

The team would like to continue with a data driven approach and see the development of their timetabling provision to make it more personalised for students.

PiP (Principles in Patterns)
*Project Prod Entry
The aims of the PiP project are:
(i) develop and test a prototype on-line expert system and linked set of educational resources that, if adopted, would:
· improve the efficiency of course and class approval processes at the University of Strathclyde
· help stimulate reflection about the educational design of classes and courses and about the student experiences they would promote
· support the alignment of course and class provision with institutional policies and strategies

(ii) use the findings from (i) to share lessons learned and to produce a set of recommendations to the University of Strathclyde and to the HE sector about ways of improving class and course approval processes

Unlike OULDI and Viewpoints, this project was less about f2f engagement supporting staff development in terms of course design, and focused on designing and building a system built on educationally proven methodology (e.g. The Reap Project). In terms of technical outputs, in some ways the outputs and experiences of the team actually mirrored more of those from the projects in Cluster B as PiP, like T-SPARC has developed a system based on Sharepoint, and like PALET has used Six Sigma and Lean methodologies.

The team have experimented extensively with a variety of modelling approaches, from UML and BPMN via a quick detour exploring Archi, for their base-lining models to now adopting Visio and the Six Sigma methodology. The real value of modelling is nearly always the conversations the process stimulates, and the team have noticed a perceptible change within the institution around attitudes towards, and the recognition of the importance of understanding and sharing core business processes. The project process workflow diagram is one I know I have found very useful to represent the complexity of course design and approval systems.

The team now have a prototype system, C-CAP, built on Sharepoint which is being trialled at the moment. The team are currently reflecting on the feedback so far via the project blog. This recent post outlines some of the divergent information needs within the course design and approval process. I’m sure many institutions could draw parallels with these thoughts and I’m sure the team would welcome feedback.

In terms of the development of the expert system, they team has had to deal with a number of challenges in terms of the lack of institutional integration between systems. Sharepoint was a common denominator, and so an obvious place to start. However, over the course of the past few years, there has been a re-think about development strategies. Originally it was planned to build the system using a .Net framework approach. Over the past year the decision was made to change to take an InfoPath approach. In terms of sustainability the team see this as being far more effective and hope to see a growing number of power users as apposed to specialist developers, which the .Net approach would have required. The team will be producing a blog post sharing the developers experience of building the system through the InfoPath approach.

Although the team feel they have made inroads around many issues, they do still see issues institutionally particularly around data collection. There is still ambiguity about use of terms such as course, module, programme between faculties. Although there is more interest in data collection in 2012 than in 2008 from senior management, there is still some work to be done around the importance and need for consistency of use.

So from this cluster, a robust set of tools for engaging practitioners with resources to help kick start the (re) design process and a working prototype to move from the paper based resources into formal course approval documentation.

From Steptoe and Son to Monsoon Wedding

March 19th, 2012 by Rachel Harris

Everyone attending last week’s Telling the story webinar was asked to suggest films that their project’s reminded them of. Hence the title of this post! Suggestions ranged widely, from Steptoe and Son, which I guess might be a tale of partnership, careful reuse, some deception along the way, and the value of insurance (or JISC funding?) To Monsoon Wedding, which picked up on the experience of “many interweaving stories and different (design) languages being spoken that (hopefully) all come together at the end“. While the programme was seen as something of an epic, it is perhaps not surprising that many people also talked about personal transformations, the influence of changing contexts, and cultural change within organisations.

Capturing the story of cultural or organisational change was, however, seen as no easy task. A number of approaches were discussed. For example, some projects are interviewing stakeholders to capture individual’s perceptions of change. This was seen as useful as it provided a space for individuals to stop and reflect, something that often isn’t possible when everyone is busy working on the project. During the webinar, suggestions were made as to the kinds of questions it would be interesting to discuss with stakeholders.

This included background questions on the individual’s role, how he or she became involved, and the amount of effort put in to the project. Stakeholders could also be encouraged to reflect on local contextual factors that were important to the project, including those factors that acted as drivers, and any barriers they had encountered. Questions about how life within the institution had changed since the start of the project could pick up on a number of themes including changes to cultural norms, access to information, or the language used regarding curriculum design. Stakeholders’ perceptions of projects’ main achievements, and the impact they think projects will have in the longer-term would also be part of the story of the change. Thinking about the future, Paul Bartholomew suggested it would also be valuable to consider what “opportunities have been missed, or remain unexploited“.

If a number of projects take this kind of approach, it will be interesting to see whether there are any commonalities from these individual stories, within projects and across the programme.

A number of attendees saw changes in language as a particularly interesting facet of cultural change. Rebecca Galley felt “shifts in language and focus in strategy and curriculum design documentation … and stories of individual’s transformation” should both be captured.

Other options for capturing organisational change included looking at working practices, awareness of curriculum design processes and procedures, the level of discussion of curriculum design at all levels, evidence of joined up working, and whether issues or barriers identified at the baseline stage had shifted.

There was a recognition that sometimes changes to the system can make people feel a bit uncomfortable possibly because, as intended, the system is delivering a greater level of  scrutiny. These kinds of negative positive outcomes can be more difficult to sell. Highlighting that ‘satisfaction’ measures can sometimes mask the real outcome.

Making these cultural shifts visible and telling the story of change in an appealing manner is a challenge. Projects within the curriculum design programme have already made good use of video to bring in different voices, and no doubt there will be more voices shared in this way. The institutional narratives that form part of projects’ final reports will also be valuable in enabling projects to reflect on their role within the development of their institutions over the last three and a half years.

Just to show that some things don’t change, Steptoe and Son, or at least the Rag and bone man, is still alive and well in Croydon. Photo by Peter G Trimming, May 2011.
Rag & Bone Man

Enhanced programme maps

February 3rd, 2012 by sheilmcn

Part of the programme support role for CETIS is to record and monitor the use and development of technologies across the programmes. This information is primarily stored in our PROD database, and then I contextualise the data primarily through blog posts like this one.

We now have an openly available linked data store of our PROD data, which means we can mash up data from with data for other sources. (See this post for more information). An example of this is that we now have integrated geo-locations for every institution in the UK in the triple store, allowing us to create enhanced google maps. As an illustration of this I’ve created maps for both the Design and Delivery programmes. Clicking on the screenshots below will take you to the interactive version of each map which includes a link to each projects PROD entry and Design Studio page.

Design Projects

Delivery Projects

More information how the maps were made is available here.

In conversation with Dawn Wood – an organic approach to evaluation

January 9th, 2012 by Rachel Harris

Just before Christmas I spoke with Dawn Wood from the PC3 (Personalised Curriculum through Coaching) project. Dawn gave me an update on what is happening with the project, but we also talked about how their evaluation has moved away from the traditional research approach.

PC3 has been exploring ways in which the principles of development coaching can be used to give students a more personalised experience throughout their university course. The project’s initial focus was at a course level, looking at how to enable students to design a personalised course from having developed a deeper understanding of their learning needs via coaching. This did not prove as fruitful as hoped, so the project was refocused on embedding coaching directly within existing modules/courses and enabling students to develop self and peer coaching. This is used to help students focus on their immediate and long-term development needs.

As the PC3 Research Officer, Dawn undertakes the day-to-day administration of the project as well as working with the team to develop, implement and disseminate the project’s research and evaluation activities. At the moment, Dawn’s main focus is on providing coaching to students and running workshops on coaching practice for staff and students. She also spends a lot of time networking and having conversations about what coaching can provide. As the project moves into the final stages, Dawn tells me she’ll be concentrating more on data analysis and writing the final reports!

How would you describe the approach to evaluation that the PC3 project adopted initially?

The project started by focusing on the PLC (Personalised Learning through Coaching) module as a means for students to identify the direction they wanted their studies to take. As part of planning the evaluation of the PLC module, detailed ethics documentation was prepared. This included an outline of the demographics of the target population, how data would be captured and revisited over the remaining three years of the project, details of how consent would be sought, and so forth. Overall, it was a very traditional research approach with a clear structure for specific data capture points.

At that time, the students would only know me as a relatively distant ‘researcher’, even though I was involved in writing some of the module materials.

What happened to change that approach?

Mainly, it came down to structural changes within the institution, such that some of the pilot cohorts we had identified would no longer exist.

Another strong influence was the lack of success with the original module. Twelve individuals had agreed to take part, but the data we were able to collect was very scattered, with only two complete sets. There was a real lack of engagement with the evaluation process. Essentially the 12 students were committed to enhancing their own learning via the PC3 coaching process, but were not so committed to the underlying research evaluation process. As we had originally planned to encourage uptake to the PC3 process using the evidence gathered from this first pilot, this compounded the problems created by the changes in the institution.

So this was the impetus to move to a more organic, flexible research approach?

Absolutely. We changed from being primarily researcher led and instead ask students ‘What can you commit to for the purposes of evaluating the impact of PC3?’ We negotiate this with students, and agree the data capture method they will use, such as written or video reflections. The details are then added in an appendix to our now considerably thinner ethical documentation!

We have also been more flexible and creative in terms of the evidence that we are using. For example, we repurpose assessed reflections as a source of evidence. This has meant we aren’t always able to design our own instruments, and we also have to engage our stakeholders in the process of identifying possible sources of evidence and negotiating with them what they are prepared to share. However, this kind of approach has meant we are much more aware of the resources available to us, we are better placed to pick up on the unexpected, and we identify issues sooner.

How would you describe this revised approach and what does it mean for your own role?

We now have an approach that is based in action research. As part of that I am more involved in the coaching process, rather than just looking in on it. Having direct experience of coaching students has meant that I have been able to identify issues that had not emerged from other sources. For example, it became clear there was a conflict between what tutors wanted to achieve in tutorials and what was possible within the coaching process. This had not come out in our interviews with staff, but now we are looking at this more deeply and working on improving embedding of the coaching process.

I feel this approach gives me a greater understanding of the student perspective. We have also worked with tutors to capture their views on how successful they have found the coaching process. Findings from interviews with one tutor team have been collated, anonymised and fed back to the team to help further improve how coaching works within their course.

Can you tell us some more about how students are more directly involved in designing the evaluation process, and the implications of this?

Yes, we now also have a group of student coaching ambassadors. Drawing on their experiences of coaching, the student ambassadors are looking at how best to promote the benefits of coaching to other students and staff. They have recently completed the same training the project provides for staff, and are in the process of developing a plan for promotional activities.

As for the implications, with the student ambassadors we had to balance our need to be able to document their activities, with our desire to hand over to them genuine responsibility for the project. After all, if this was to be their project, how could we impose a particular evidence gathering approach on them? We resolved this by engaging them in the process of designing the evaluation plan for the student ambassador project and asking them to propose ways in which they could provide the evidence we need. We hope that this will lead to greater buy in to the process.

Finally, are there any words of wisdom you’d like to pass on to other projects undertaking their own evaluations?

We’ve learned along the way, and part of that has been a realisation that a broader vision is sometimes better. Be prepared to change your approach and willing to look at alternatives. The traditional approach to research may not provide the evidence you had hoped for, so keep alert to opportunities.

The team are currently preparing additional coaching materials that will be made available on the Design Studio. In the meantime, there are various coaching resources on the PC3 blog, including videos demonstrating coaching conversations and coaching workshop resources.

Enhanced by Zemanta

Feature article on Dynamic Learning Maps project

December 9th, 2011 by sheilmcn

The latest installment of Lou McGill’s series of posts highlighting the work of the Design and Delivery programmes takes an in-depth look at the Dynamic Learning Maps project, from the University of Newcastle. DLM was funded through the Curriculum Delivery Programme. It’s focus was on creating dynamic visualisatons of the medical curriculum.

“The DLM project aimed to make visible the complex medical ‘spiral curriculum’ where topics are revisited with increasing depth over a 5 year programme, and to reveal connections across curricula to support modular learning. High level goals included a desire to promote lifelong learning, enhance employability and enable personalisation for students. The diverse nature of stakeholders with unique views of the curricula increased the complexity of the project and led to some interesting paths and choices as the team developed the maps. Simply getting agreement on what constitutes a curriculum map proved challenging and required a highly flexible approach and agile development. Like many technical development projects DLM had to balance the need to develop a common understanding with the need to reflect different stakeholder requirements. Agreeing on what elements to include and the level of detail was important as well as the fundamental issues around how they might be used by both staff and students.”

You can read the full article full article on the JISC CETIS Other Voices blog.

Tracks in the snow: finding and making sense of the evidence for institutional transformation

November 9th, 2011 by Gill Ferrell

The title ‘Tracks in the snow’ was designed to fit with the ALT-C 2011 conference theme (Thriving in a colder more challenging climate)

The kinds of evaluation we often do to show the impact of our work has a lot of parallels with following tracks in the snow. We are trying to identify a specific footprint relating to our activity and looking back at the impression it has made. A very focused evaluation plan might serve us very well for small-scale interventions, however …

… in a long-term project aimed at achieving major institutional change, things become a lot more complicated because other people start trampling their wellies all over the same space!

This paper stems from work with a range of institutions including some JISC activities (particularly the four year Curriculum Design projects) and also a review of Enhancing Learning Through Technology in Wales. Almost without exception, the people who were working to enhance or transform learning were doing so against a backdrop of significant structural change that makes it all the more difficult to know which factors are having the most impact.

Despite the external pressures, our institutions still have a core mission and are working towards a vision for where they want to be. The extent to which this vision is as dependent on external stimuli as you might think is something we’ll come back to later. 

I would argue that in this kind of situation it is fairly pointless to try to separate out all of the tracks on this journey. What we are really interested in is whether the institution as a whole has moved closer to its goals. We often talk about significant enhancement projects as change projects and we need to think about what it is we are actually trying to change.

I think what we are trying to change is institutional culture and I define culture as ‘the way things are done around here.’

What this post tries to do is:

•Look at a few models that have influenced the way I think about these issues

•Look at the experiences of some major change projects in the light of these models and

•Make some suggestions for things we could be trying to capture and measure that may bring us a little closer to understanding whether we are actually changing culture.

I don’t claim to have the answers but I hope the suggestions may lead to some interesting discussions on this blog or perhaps form the basis for an online session.

These notes represent a lightning run through models I find interesting to do with people and change and there is a list of references at the end of the post.

The image isn’t really to do with people or change at all but Chaos Theory makes a nice backdrop for the other models. The underlying premise here is of course that even in systems where you might expect quite deterministic cause and effect relationships, small variations in initial conditions can cause quite major fluctuations in outcomes. As human behaviour is the ultimate in non-linear systems, let’s not start out with any hope that patterns of change are going to be readily predictable.

The first group are models that concern the adoption of innovation.

The work of Malcolm Gladwell is very well known: the idea that once an innovation reaches a ‘Tipping Point’ continued adoption is self-sustaining. I’ve also been influenced a lot by the work of Albert Angehrn from INSEAD (and also Conner and Patterson’s eight stage model of the adoption of innovation). Angehrn has created an excellent simulation tool which is used in the JISC infoNet change management training courses and without giving too much away for those who may be interested in trying it, you very quickly learn that you need to understand both the formal and informal networks that exist in the organization in order to successfully influence enough people to get a change embedded (to reach that Tipping Point).

The second set of influences is work on social networks. By this I don’t mean Facebook and Twitter but rather how social ties in general operate. Some interesting work on the subject by Christakis and Fowler explains all sorts of social phenomena in terms of how social networks operate – one example is clusters of obesity affecting people who are at some social distance from one another. They suggest there is no simple cause and effect but it is to do with people adopting behaviours that spread to others and individuals making changes that affect other people’s perception of what is the norm.

The final influence is some work, by Gerry Johnson of Manchester University, on how institutions evolve their strategic direction. His diagram of the cultural web is used a lot but is often separated from its original context which looked at the ways in which strategy, often perceived to be a very logical planning process taking account of external factors, is actually much more heavily influenced by the institutional paradigm.

The paradigm is a generalized set of beliefs about the way the organization is and how it operates and it encompasses the politics, the rituals and the myths that make up organizational culture. External facts that don’t fit the paradigms can often be ignored in quite a surprising fashion. Johnson found strategy development was best understood by undertaking cognitive maps of key stakeholder’s views and triangulating these against events. He based his work in the retail industry but it is interesting to reflect on the extent to which views about a university’s core market and strengths and its response to the current climate are based on the institutional paradigm rather than the facts.

The common thread in a lot of these models is that it is the connections between people and the shared beliefs and behaviours that are particularly important. A critical mass of connections can create traits in networks that persist over time whilst individuals come and go. This for me is institutional culture.

Which brings me back to how we undertake change projects using technology. The traditional way used to be: bid for some funding from JISC, think of an acronym for your project (the sillier the better) and get out there and evangelise about what you were doing.

A lot of recent projects have approached change quite differently:

Many of the JISC curriculum design projects have deliberately not branded and marketed their activities, instead they have concentrated very hard on showing how what they are doing aligns with broader institutional goals.

Welsh universities, when they reviewed their progress with technology enhanced learning, felt that ‘branded’ projects simply created new silos within the organization and that real change was effected by plugging into existing networks.

A number of projects in the JISC Flexible Service Delivery programme adopted what they termed a ‘guerilla’ approach to change and

A very successful JISC Curriculum Delivery project at Exeter University, that is already having considerable impact in terms of its work on Students as agents of Change, realised that ‘change happens one conversation at a time’.

It might seem as if operating within the paradigm rather than explicitly setting out to challenge it is achieving considerable success in terms of stakeholder engagement but making it even more difficult for these projects to demonstrate their impact on institutional culture because they are so embedded. However, by looking at the bigger picture and by focusing on the glue rather than the building blocks, they seem to be coming up with a mixture of qualitative and quantitative ways of achieving this.

Finally, a run through some of the techniques that have been effective and highlight tips for measuring transformational and cultural change.

The first tip is to start from a baseline. You can’t measure the distance travelled unless you have some idea where you started. It was a requirement of funding that the curriculum design projects had to do this and many of them were initially very sceptical about the value of trying to take a snapshot of such a moving target. They took various approaches to determining the baseline and these are summed up in a report by Helen Beetham (see references)

Suffice it to say that the process mattered more than the specific techniques and within a very short space of time the project teams were convinced of the value of this work.

Some projects undertook quantitative analysis. The OU created a set of profiles looking at its courses from a range of perspectives including financial and pedagogic perspectives. Bolton did some basic but powerful analytics after finding that many discussions relating to course approval and validation were based on assumptions rather than facts.

Producing statistics about learning outcomes and assessment types helped show where some modules appeared to be over assessed or where the same learning outcome was assessed multiple times. Quite simply it changed the conversation. Snapshots of these types of analytics will show changes in practice in particular disciplines over time.

Every bit as important as having some kind of quantitative evidence is capturing what Birmingham City University has termed the ‘lived experience’ of curriculum design.

This is similar to Johnson’s work on cognitive mapping. Regardless of what the facts may actually be, it is people’s perceptions and assumptions that affect day-to-day practice.

BCU has made extensive use of video to capture and analyse stakeholder experiences. Greenwich University has used techniques such as Rich Pictures very effectively to identify certain myths that needed to be exploded before the institution could make progress in changing some of its processes.

Finally, what is needed in terms of looking at culture change is finding ways to look at how the individuals who make up the organization (and hence the culture) are connected and communicate. The most significant changes tend to happen when you get linkup and collaboration between parts of the organization that didn’t previously talk to one another.

This idea that it is the connections rather than the entities that really create the structure doesn’t just apply to social networks. You will find that architects looking to innovate also look not so much at the structures as at the linkages, the connections, the spaces between them.

Some of this is actually quite easy to measure in the Web 2.0 connected world. As a very small example this diagram shows the interconnectedness of people who were tweeting using a particular hash tag at a meeting. It would be interesting to look at a series of snapshots like this over time to track how the network expands or contracts and the frequency with which particular tags are used -  in other words who is talking to who and what they talking about. In some institutions there may only be a very small percentage of staff who are actually using tools like this at the moment and a growth in this type of communication would represent a significant cultural change.

In other cases it may be appropriate to track the formal networks in the institution i.e. the committees that exist and the parts of the organisation that are represented on the committees.

Many projects are finding that changes in the language used within the organisation reflect changes in perception and understanding of curriculum design and other processes. This language is manifest in policy and procedural documents and guidance used for staff development purposes. Again identifying phrases and descriptions that are key at the baselining stage and mapping how this changes over time can give an important perspective on institutional transformation.

Tips for evaluating Culutre Change

•Start from a Baseline

 •Capture the ‘Lived Experience’

 •Look at the Connections rather than the silos

•Find out about how others are doing this via the Design Studio
http://jiscdesignstudio.pbworks.com

References

Angehrn, A. Schönwald, I. Euler, D. and Seufert, S., (2005). Behind EduChallenge: An Overview of Models Underlying the Dynamics of a Simulation on Change Management in Higher Education. SCIL-Universität St Gallen, SCIL Report 7, December 2005. Retrieved 1 Sept 2011 from: http://www.scil.ch/fileadmin/Container/Leistungen/Veroeffentlichungen/2006-01-euler-seufert-behind-educhallenge.pdf

Bartholomew, P. (2010) TechnologySupported Processes for Agile and Responsive Curricula Project Interim Report. Retrieved 1 Sept 2011 from: http://www.jisc.ac.uk/media/documents/programmes/curriculumdesign/tsparcinterimreportoct2010.pdf

Beetham, H. (2009) Synthesis Report: Baselining the Institutional Processes of Curriculum Design. Retrieved 1 Sept 2011 from: http://www.jisc.ac.uk/whatwedo/programmes/elearning/curriculumdesign.aspx

Christakis, N. and Fowler, J. (2010) Connected: The Amazing Power of Social Networks and How They Shape Our Lives. Harper Collins.

Conner, D. R. & Patterson, R. B. (1982). Building Commitment to Organisational Change. Training and Development Journal, 36(4), 18-30.

Gladwell, M. (2000). The tipping point: how little things can make a big difference. Boston: Little Brown.

Johnson, G. (1988). Rethinking incrementalism. Strategic Management Journal, 9(1), 75-91. Retrieved 1 Sept 2011 from: http://onlinelibrary.wiley.com/doi/10.1002/smj.4250090107/abstract

Leslie, K. Dunne, E. Newcombe, M. Taylor, L. and Potter, D. (2010) Integrative Technologies Project, Final Report. Retrieved 1 Sept 2011 from: http://www.jisc.ac.uk/media/documents/programmes/curriculumdelivery/integrate_FinalReport.pdf

Debating our achievements

November 9th, 2011 by Gill Ferrell

One of the activities that took place at the last programme meeting was a debate on the topic:

This house believes that this programme will not actually change the pedagogic practice of curriculum design’’

The debate took place under the Chatham House Rule but, by popular demand, we have been persuaded to bend the rules slightly and summarise some of the points made for and against the motion.

The debate took a slightly different slant to that which might have been expected and concentrated more on the value of undertaking these activities as part of a formal programme as well as looking at whether the changes made to institutional processes did or did not change pedagogy. It was an interesting and heated discussion and these are just a few of the key points.

Points for the motion:

  • Change only happens when real pressure builds up and this has little to do with either institutional strategy or funded initiatives.
  • The changes so far have been organisational and structural but we are not yet seeing systemic and transformational change that leads through into a different student experience.
  • The ‘engine room’ for curriculum change is not in the formal policy making bodies that exist in the sector.
  • We can’t really tell how many of these changes would have happened anyway and what extra the programme added.
  • Projects who started from a principled pedagogic stance have had more disappointments than those who started by looking at institutional processes.
  • Better forms filled in online are not enough to improve pedagogy in themselves – we still need to address poor course design.
  • We started with some naïve assumptions about institutional change.

Points against the motion:

  • Turmoil presents open doors that we can push against. Everyone now accepts that the status quo cannot go on so the external environment offers fertile ground in which to effect real change.
  • It was a masterstroke that the requirements of the programme obliged us to spend a long time in reviewing the existing baseline. This meant we arrived at solutions people were already signed up to.
  • The timing was exactly right – had we started any later we would have been too far into the problem zone and less ready with solutions.
  • We had a situation where people wanted to change and needed to change and the programme provided the opportunity to change.
  • The programme has impacted 25% of HEIs and about 20% of the overall student body and we are seeing some real cultural shifts such as academics ranking learning design tools in the top five things they wanted to learn about.
  • Changing process isn’t enough but it changes the rules and people have to respond to that.
  • The programme offered more than money – it was a licence to work in ways that weren’t just bottom up. The intervention speeded the process up and amplified the results.
  • Better designed processes can lead to better courses.
  • We may not have had a credible theory of institutional change at the start but what JISC set up was a fantastic living laboratory.

The result:

The motion was defeated by a significant majority although a slight shift in opinion shows that the team in favour of the motion did make their case very well and raised some important points that need to be considered when communicating the work of the programme.