La la Ladok

Our research group has a long tradition of doing action research. Action
Research has been defined as having dual aims, research as well as involvement. The latter implies things happening, action, change–a bit like agile development if you wish. At the same time, this is relative to scale. In a small project, things are happening fast and various actions by practitioner and researcher alike have direct consequences. In large projects, this is not always so. In retrospect it will be easier to see the change and trace a trajectory. In real time, especially in the periphery of a large project, it can be hard to experience any action.

One of ongoing action research projects we are following the local preparations for a major new system implementation. Deadlines have been pushed forward on numerous occasions–by years.

The system in question is the nationwide Swedish Student Information System (SIS) – better known by the name Ladok. The system holds all student records for students in Swedish higher education and is critical from a legal perspective but it is also the backbone for most other student related ICT as it is used to generate directory information that is used by learning management systems (LMS), campus cards etc. The system is long overdue for an upgrade and a completely new version is just in its early phase of implementation. This is a 50 million Euro project with an estimated user base of 400 000 students and 50 000 staff in higher education.

We have been following the local preparations at one university, rather than the development as such. The collaboration has included activities such as:

  • coaching,
  • seminars,
  • participation in information efforts and
  • surveys.

The major effort though, were the vision seminars that were conducted with students and staff (users that is) in order to establish high level goals. Thus, our focus has been on local preparations for a huge change in work processes that the new system will require.

While the constraints and uncertainties can be at times frustrating this is also the reality behind many large system implementations. In the next few posts we will further discuss some of our experiences from the project – so far.