Once again I fall into the role of the fervent defender of the blighted IT Support teams in schools. As much as I enjoyed a good argument (oh no you don’t!) there are times when I feel that the word compromise is missing from the vocabulary of some people.
In a short break from the course I am on at the moment I picked up a tweet to a blog post from our friend Spannerman2.
It makes for good reading and raises an important points about IT and ICT & Computing as subjects, about the lack of subject specialism in teachers of these subjects and about the amount of effort which goes into running (& locking down) a school network.
It does, however, throw stones. I don’t think stone throwing is any good at the moment in education. It just generates a lot of people pointing their fingers and saying, “you are doing it wrong!” without any ideas or support for getting it right.
In conversations on EduGeek.net there have been ideas shared about how you can make things more manageable and flexible on a school network, about how you can give freedom to staff and students, about how to manage situations better and stop the ‘them & us’ perception which can be the stimulus to things getting out of hand when there is the slightest problem.
So here are a few ideas. First we will have the objectives … the school needs computers systems. It needs three types of systems really.
Let us cover the easy one first. We want a system that allows for the running of a school, the day-to-day stuff of administration, the ordering of toilet roll for the toilets, the paying of staff, keeping records on students … you know the sort I mean. It used to be that this network was kept as separate as possible from everything else. It had to be … it holds sensitive data, it needs to have careful controls over who can do what with it … both legally (DPA) and for audit reasons. However, more and more senior leaders have realised that this network holds some really valuable and vital information. Stuff that can make a difference in the way teachers operate in the classroom … and teachers also need to add to this information too. So that means it has to overlap with the other systems in the school. Problem number 1 arises, but we will come back to this one.
System number two is the one used by teaching staff to deliver what they do, day in, day out. Teaching. I don’t want to turn this into a ‘them & us’ post … I never do … and sometimes people have to remember that those most likely to read my blog from the teaching community are those most likely to understand and want to push what tech they have … in fact, the people who are the cream, those who have risen to the top … but try to remember that there are those who can do *some* of the things that you do and are learning fast … but there are also those who struggle … not just with tech, but with classroom management, with change in general … and I am thinking about *all* staff in schools. A single solution is not always the best thing … having one setup for all staff … only giving limited access to doing stuff … but the problem is that at the moment it takes time and investment to give a more flexible system for staff. There are little things which can be done, like giving rights to install software on their laptops, giving more relaxed filtering … perhaps not even ‘filtering’ as such, but just logging what is used on the internet (remember folks … audit trails!) But what happens when a laptop is brought back in to the IT team to be fixed because something they downloaded at home seems to have broken stuff (after they have turned off the anti-virus or stopped it from downloading updates or running scans) … and that is if you are lucky and they don’t just plug it into the network and infect other computers where teachers have also turned off the antivirus too … and so you have to fix their machine. You might need a spare laptop or two so that they still have a machine to use in the classroom (back to investment again) and then there is the time and staff to fix it. Problem 2 appears … planning for the inevitable workload that comes with either building systems to deal with having to fix problems like this or having to do it on a case by case basis.
And so we go on to system 3 … the most problematic because you are having to cover three conflicting needs. The student workstations / laptops. Here you have to think about what software is needed, who gets to choose that software, pay for it, develop resources for teaching using it or even for teaching the software itself (either the skills / concepts or the specific software … that argument is for another day) … and then let us think about that touchy area of classroom management. I don’t like people blaming technology when it is being used as substitute for classroom management … I’ve spoken about how filtering gets abused this way before and the same applies to locking down the desktop, turning off the ability to right-click, where things can be saved … it all boils down to how much disruption in the classroom the teachers can handle, the amount of effort which is needed to fix problems that arise and so on … So we get to Problem 3 … and this *is* aimed at the teachers who might read this blog. COMPROMISE. Oh, that was also aimed at the Techs too.
So what happens when we need these 3 systems to overlap … or even be the same system?
I would love to say that this is a perfect solution out there … but there isn’t. It will *have* to vary from school to school purely due to the nature of each school, the emphasis each school might choose to put on classroom control, on how much investment the school puts into different aspects of IT, what technology gets used, the strength of things like Web 2.0 tools, of VLEs, of email, of using data straight from the MIS … so many factors that *no-one* can give a single system that will suit everyone.
Instead … how about thinking a little more about how you are going to get to where you want to go. I can guarantee that the end system you want cannot be delivered overnight and be usable by everyone without considerable pain … so you are likely to have to do things in steps. These steps have to be done with compromise and I’m going to say my usual mantra … Change Management!
So … let us think about something that gets raised a lot at the moment. The introduction of student owned devices (yes … I know I have avoided mentioning the learners themselves … more below) can be considered in a few stages, some technical, some pedagogical. If you are going to introduce this sort of system then yes, you will have to segregate it from system 1 … the stuff you have to legally protect. A typical way of doing this would be by having a ‘dirty’ wireless network … a separate WLAN that is only used by students, *may* have some restrictions on it … but will give them access to the internet at the bare minimum (even if you choose not to filter then at least log it). You then have to consider how it will be used in the classroom. Will it be used in conjunction with a VLE? Online stuff such as [email protected] or Google Apps? How will you ensure that the iPad is being used for work and not just to watch stuff on iPlayer? GameCentre? The netbook is not being used to just hog the school internet connection to pull down pirated video or software? Or the laptop used for chatting on IRC, tweeting about what they got up to last night or on facebook poking their mate in the class next door? The same way that it used to be notes on pieces of paper, or ‘interesting’ magazines shared by some of the boys (actually, both of those still happen too) now there is a new range of things to distract the learner …
One way of dealing with this is by using the student wireless network to force the student to log into the school terminal server system (various solutions are available to do this via a website) and so that they can use their own device in the school but with some element of control by the teacher / techie / school.
There is still another way … the idea of privilege, of use versus abuse. And this is where we talk to the learner. They can make some of the best and worst suggestions and decisions you can come across. It might be that they want the system to allow them to do nearly everything, but on the understanding that if it is abused that they get locked down. Hmm … that might even work in conjunction with other polices the school has? Wow … revolutionary concept?
It might be that the desktops are set to be rebuilt each night … so that if the students do mess things up then it is not a problem. It might be that you have systems that go back to a baseline after each log-off. you can do almost anything … but there has to be a reason to do it, it has to be a balance between what is possible, what is practical and what delivers some sort of benefit.
So … there we go … a start … I’ve already prodded a few of the detractors to techies locking things down or wanting to drop working systems to go to Open Source based purely on ethical principle rather than education need or practicality … if they want to change then I want to see a range of options and some sort of roadmap about how to adopt it, both technically and pedagogically. “Just because…” is not a suitable answer. I might want to put studded tyres on my little Smart car just because … you never know, we might get heavy snow tonight … it might become fashionable … it might mean I can drive over an ice rink to drop off James Bond to do a bit of bomb disposal and save the world … or it might tear up a recently resurfaced road … cost me a fortune to buy and get fitted the new tyres.
So … a start … let us see how it goes from here.