Based on what is known about Glow today – it is clear that Glow as we know it will be replaced by some other service in the near future. There is currently no hard information around about what the new Glow will consist of, but we do know that the current contract will come to an end in September 2011 – that is less than 12 months from the time I am writing this post. We also know that the Glow re-procurement exercise, which was started some time ago, has been stopped by the Scottish Government. So currently there is a real possibility that there will be no Glow after the end of this school session.
I want to use this post to exercise my own thinking about how this will affect the current Glow user base.
Let me preface my comments by making a comparison between Glow and a traditional school. Glow is a learning platform with the capacity to support up to 1.5 Million unique users with adoption increasing on a year on year basis. I prefer to deal with the facts as I know them as opposed to speculating on the basis of information rumor. Glow also provides a national focus for online learning which not as some seem to think completely closed down and exclusive of the web as a whole. Many discussions seem to confuse the impact of Local Authority internet filtering as synonymous with Glow – nothing could be further from the truth.
Pupils and teachers attend school each day and school is traditionally taken to be a place of learning. Lots of resources are collected there which both teachers and pupils can use to deliver and enhance the learning experience. What an outcry there would be if the government was to announce that it was stopping its involvement in curriculum development, or worst still closing down all schools in a years time and leaving the process of Education to the “free” sector. Scotland makes a significant investment in its education system and although it’s not perfect it has certainly served Scotland’s learners well. Of course the education system does need to evolve to remain relevant so change is inevitable. I would assert that the government has a key role and responsibility to ensure that the education system is protected and developed in a caring and sensitive manner. The use and development of ICT today is now embedded in our education system in my view – but I do recognize that we have some way to go before ICT is universally adopted as part of daily practice in schools.
Scotland took a very brave decision early in the last decade to establish Glow as a country wide service at a time when this was unprecedented. The technology landscape at the time was very different to the way it is today and to some extent the context did influence what could be achieved.
The cost of the Glow initiative was also very small in the context of overall spending in Education. With an overall burget of £37.5M. This cost was spread over the initial 5 years with payments being made only when the contractor achieved clearly defined milestones according to user account provision and service performance. There may well be a case for altering the commercial model of Glow to recognize actual service usage. This would lead to a situation where cost of the service would of course increase as user adoption increases. This idea is complex and probably warrants another post dedicated to considering how this may make better sense.
Early in the Glow (SSDN) project words of Alan Kay were often quoted as follows
“The best way to predict the future is to invent it”
I believe that the Glow project was one of a number of initiatives by the Scottish Government aimed at trying to “invent” the future IT landscape for Scottish education. This was always set against a backdrop of continuous change and evolution in the world or IT at large. We have certainly seen a number of unexpected developments taking place which have altered peoples expectations – these include the advent of Web2.0 and the social networking revolution which were just beginning to emerge when Glow was initially being specified.
Glow is based on a national directory of users including pupils, teachers, school support workers and parents. Establishing this directory has been possible by designing and implementing a data transfer system which allows existing school MIS data to be first cleaned up and then used to trigger the setup and alteration of user accounts in Glow. Although this process was very difficult and complex one could argue that getting user accounts setup in the Glow directory is the easy part. Much more difficult is getting teachers to take the opportunity to use Glow and embed it into their daily teaching practice. There is always a group early adopters but I think that in reality the majority of teachers are overwhelmed with their current workload and for some technology adoption is a step too far.
A critical issue here is the type of support that teachers are given – it is useful to note that the majority of the Glow budget was apportioned to teacher support – not the platform systems. It was always recognized that helping the teaching profession to adapt their attitude towards and knowledge of using technology in the context of classroom practice was a key element. This goes much further than just giving instruction of how to operate and application and is also about how the application can be used effectively to improve the learner experience.
For me it is critical that any transition from the current position to the next must be managed in a way that brings existing users onboard. The move to the next system should be perceived as an evolution where users can easily adapt in easy stages. I believe that a fundamental requirement here should be that existing users should be able to continue to access the platform using their existing user identifier (UID) and password (PWD). Things like email address should be preserved as they currently are and of course the current investment in content – both nationally provide and user created – must also be preserved.
In closing I should also state that I recognize that some elements of Glow need to change but on the following basis.
- It is essential that the move forward takes into account any lessons learned from the experience of deploying and using Glow to date.
- We should develop the good and remove/replace/enhance the elements which are judged to be weak in a planned and staged manner.
Evolution not Revolution is the way forward.



