Author: Gerolf Nauwerck

Some notes from EUNIS 2017

In the SISU project we study a major system implementation in a university context. This year we got accepted for the EUNIS 2017 Conference, which is an excellent opportunity to present our results outside the academic community (no pun intended).

My presentation was one of the last but we had a full seminar room and the response was positive. (The presentation will ba available from the EUNIS web site.) Many universities all over Europe are in the same stage, transitioning from old student information systems to new, so many shared the same concerns. One example was this year’s host Münster who presented their transition to a new student management system, a project which felt quite familiar to us studying Ladok.

Of course, for me it was really interesting to listen to the other presentations and to get a feel for what is important for the community and what is on the agenda.

The three largest conference tracks were e-learning, infrastructure and management respectivly. Reocurring themes were mobility and analytics. The new EU regulations on privacy were given special attention.

The conference ended with a brilliant presentation by Nikolas Guggenberger on trust in blockchains. Guggenberger discussed the relation between blockchain and law. He concluded by pointing out how reliance on blockchain will invert the field of data protection. Not by solving the problem but rather by switching focus from known individuals with secure transactions to anonymous users with open transactions. A main point was also how the lack of a central authority is misaligned with most jurisdiction as the idea of someone ultimately responsible is often critical.

To me, the keynote on open education by Sheila Macneill was nevertheless the most inspiering. Macneill is a long term advocate for open education and made a convincing case for openness being a core value of higher education. (Her presentation is available on her web site as a recording.)

Taking a somewhat longer perspective she also noted how hard it is to make reliable predictions. Just some years ago MOOCs were seen as the next big thing, ready to make all but a few HEIs obsolete. Now they are just a part of life but instead alternate facts are shaking the wery foundation of education. “That’s just an expert, what does s/he know?”. Sheila’s answer was a plea that universities must create their own strong narratives to remain relevant.

This year all but one member of the Ladok consortium were absent due to heavy workload. Pray next year’s conference will be dominated by lessons learnt from the Ladok project.

A View from the Top

Recently I had the opportunity to listen to a full day of presentations from what could possibly be Swedens largest software development project, the New Ladok project. The New Ladok is Sweden’s new national student information system, which will serve about half a million users when fully implemented.

In the SISU project we follow the preparations for the implementation of the new system, from what could be called a bottom up perspective. It was thus very interesting to hear about this huge project from a top down perspective–from the actual development project.

Project Leader Johan Sjödin stated that the initial development backlog was estimated to have started at 60000 hours of pure coding/development. While one major effort has been the prioritizing of the backlog a project of this size is not just coding. Adding requirements elicitation, testing, validation, documentation, learning material etc. the project so far amounts to over 400000 hours of work. That is the equivalent to more than 50 PhDs.

The presentations included high level perspectives from Mauritz Danielsson and Johan Sjödin. There were also more in depth presentations: Catherine Zetterqvist commented on backlog, the technical setup was described by Staffan Ekstedt and Anna Åhnberg talked about the concepts behind the learning material being developed. Malin Zingmark said a few words about success factors for local implementations and the new web site was presented by Rebecka Guzman.

Interesting were also Jan Winkle’s presentation from Malmö University, which has formed the avant-garde by being the first larger university to implement the new system. This was nicely contrasted with the presentation by Karim Andersson from Lund University, which will form the derrière-grade and implement the system in 2018. So far the implementation at Malmö University seems to have been successful and that must indeed have been very positive for the project as a whole.

Still this huge project no doubt has many challenges ahead, both on the project level but also on the level of local implementations. Starting with the latter there is a huge undertaking at each university relating to the conversion of legacy data and the adoption of routines.

On a project level, there are of course the usual challenges related to running huge IT-development projects. I could note two principal challenges that the project has to deal with. One is the fragmented customer base. There are many differences between universities and colleges, but also within institution there are many structural differences. As the new Ladok will have a monopoly there will have to be a one size fits all for the end product, and no doubt this will be better for some then for others.

A more intricate problem relates to the overall orchestration. The project is now in a critical phase where it is simultaneously implementing the system, keeping implementations stable and developing new versions to meet the more complex requirements that have to be supported. At the same time the higher education system is very cyclic, and the project has to adapt to the academic year leaving little room for quick adjustments.

All in all, it would seem that the new Ladok would be a perfect example for the hype curve. At the beginning there seems to have been rather unrealistic expectations. The project has since worked hard creating a focus and in a sense lowering the expectations (at least for the first version). There will no doubt be a rise towards the plateau of productivity. The question that remains is whether the project already has hit rock bottom and is working towards that or if the large scale implementations ahead will be a cause of concern. It will definitely be interesting to follow this huge project as it proceeds and I hope we could gain further insight into the development project as such.

Vitalis 2017 and the case for coordination

With 180 exhibitors and a huge number of presenters Vitalis 2017 was indeed vital. For a first time visitor such as myself it really made the impact of e-health on society tangible.

The exhibitions gave an understanding of the actors in the field, raging from service designers to robotics. (Plus more espresso than a man could drink, though I tried.) The presentations showcased how the same technology was introduced and effected health care on a many different levels. The combination of exhibition and presentation also created a nice tension between the promises of technology and the sometimes more complicated implementations of the same technology.

Given the sheer number of parallell sessions it was impossible to cover more than a few select presentations. The DOME consortium, of which we are a part, had great visibility with a track of its own. Jonas Moll of the HTO-group has written more on this topic. Quite impressive was also the fact that our students had been invited to give their view on the future of health care. Given how professional they were, I would say it looks promising. I also enjoyed the presentation made by Carl Johan Orre from Malmö University on the topic of person centered technology.

I might be a bit biased but what I found really inspiring was the presentations made by our colleagues from Uppsala University Hospital with whom we are collaborating in a number of projects.

  • Birgitta Wallgren discussed the complexities of large scale implementations in a setting with other ongoing large scale implementations.
  • Annemieke Ålenius and her colleague presented lessons learned from the unplanned and almost week long downtime for the hospital’s patient journal system. While interesting in itself–for instance the comment that soon staff will have no experience of paper based back up routines–they also managed to convey some of the drama from behind the scenes. Still, it was a good thing that the crisis had a happy ending–thanks to a strong group effort from the whole hospital staff.
  • Finally Morten Kildal discussed the various strategic paradigms that have succeeded each other as the solution for health care, including the current concept of value centered care. While no doubt new paradigms will come, Morten Kildal did make a solid case for the benefits of the current strategy–as well as the need for relevant data.

In summary all of the three presentations  stressed the importance of coordination–between implementations, in crisis or in the patient journey. Yet, what I really found positive for our ongoing collaboration was not only the fact that the presentations were analytical and reflective but that the presenters had a strong humanistic outlook.

This also, is promising for the future of eHealth.

Hooked on the J-curve

Anticipating exactly what will resonate with your audience is not always easy. During the last couple of weeks I have been presenting some results from a study on the healthy digital workplace, as a part of the SISU-project. The presentations were part of the studied organisations change effort and my presentation was one part, embedded in the information from the organisations project leaders. The overall message was thus one of progress. The study I presented created a baseline for measuring the effects of the coming changes. It also indicated some strategic areas to observe during the change.

The one thing that really seemed to catch everyones attention was not so much the results as one of the slides I used to frame my message. In this slide I contrasted the idea of a linear progression from the current state to the next with the classic J-curve or change curve as it might be called (originally the Kübler-Ross model describing grief). The J-curve in this context is mainly a rhetoric tool, it presents a generic path through change, the big difference to the simple linear progression is the understanding that things will get worse, before they get better. As basic as this concept might seem, it did however seem to catch the interest of both managers and employees. It did seem as if it created a common ground for discussing the upcoming challenges.

The J-curve illustrated.

As time was limited I did not expand on the concept however. Taken at face value it might be misunderstood as support for the idea of simple linear progression (A->B), just with a more bumpy road. In practice there are at least two waypoints that should be noted. The first is that there is a worst case scenario where there is no recovery and the change not only fails but even fails miserably (C). The second is that if the organisation navigates the turmoil it might still end up in some kind of status quo or rather same same but different (D). The promise of actual progress still needs to be fulfilled. Taking a note from Festinger’s theory of cognitive dissonance one might suspect that we might be tempted to rationalize our new position as an improvement without this actually being the case. Thus, we need to be careful to measure the right aspects during a change effort.

Finally, I didn’t use my favorite take on the change curve, namely the hype curve (hype cycle) made famous by Gartner. The inclusion of the hype is interesting as it puts focus on the rhetoric behind the change. Getting the boards interest and approval might well include some mild exaggerations regarding the benefits of the change. As is obvious from the hype curve the discrepancy between these promises and the coming turmoil might turn out rather dramatic. Thus, it is–as we all should know–important to manage expectations during change so as to avoid a roller coaster experience of change.

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.