Showing posts with label BYOT. Show all posts
Showing posts with label BYOT. Show all posts
Wednesday, September 5, 2012
10 Things School Leaders Do to Kill a Teacher's Enthusiasm for Technology
Here's a list of ten things a school leader does to kill any teacher’s enthusiasm for using technology in their classrooms. An alternative title for this list might be, “10 Things a 21st Century School Leader Will Not Do to Discourage Teachers from Engaging in the Use of Technology.”
1. Mandate the use of technologies or specific programs. One of the fastest ways to kill an educator's enthusiasm for infusing technology is mandate a specific technology or specific program. We all have specific needs, tastes and desires, and a program that satisfies mine will not necessarily satisfy the next educators. For example, I like Evernote. I preach the use of Evernote. But, some educators despise it. It does not match their needs.It does not do the things they want to do with technology. Mandating the use of Evernote is counterproductive. The same goes for iPads, digital cameras, interactive boards, and any number of tech devices and software. Some teachers can use these technological devices because they fit their teaching style, their subject matter, and their students' needs. Others would rather get students using devices themselves. Mandating specific devices, technologies, and software will kill an educator's enthusiasm quickly.
2. Use inadequate, faulty or overzealous web filtering systems that block sites teachers want to use. This one is a teacher enthusiasm-killer of major proportions. While school districts are obligated under CIPA and common sense to provide some level of protection for young students, a filtering system is inadequate or faulty when it dictates what teachers can and can't do with the technology. For example, I am an advocate for blogging, and as a former English teacher, the potential of blogging for providing authentic writing experiences for our students is enormous. But then comes the web filters, that dictate that blogs are off limits because the manufacturer of that filter sees blogs as a greater threat to kids' safety than its potential to get students to engage in authentic writing. A web filtering system that dictates what teaching resources teachers can use is a quick way to stifle a teacher's enthusiasm and to force them back to using textbooks and other 20th century materials.
3. Provide inadequate or sloppy tech support systems. While teachers should always have plan B, even without technologically enhanced lessons, they should not have to have a plan b, a plan c, and even a plan d. If a school district has such shoddy tech support systems that using technology is like running an obstacle course, then expect your teachers to lose enthusiasm for using technology. Having technicians available is only one aspect of support. Too often administrators like to brag about the number of iPads or laptops they've added, but they failed to hire the support needed to keep those things operating. When adding technologies it is vital that school leaders factor in additional support systems and their costs as well.
4. Provide inadequate funding. There is a great deal of frustration when a classroom teacher wants to implement a project using a technology resource, only to be told there's no funding for that. It's not frustrating because of the lack of funding itself, it's frustrating because there's evidence all around of funded projects that were a waste, and that same money could have been used to pay for technology a teacher wanted. Sometimes I have to wonder whether some administrators get a trip to the Bahamas out of the purchases they made because they obviously could not have made the technology purchases with a teacher in mind.
5. Fail to provide adequate hardware and/or software. I've seen so many examples of this over the years. Teachers are encouraged to get students writing and engaging in online blogging, but they don't have access to computers. Another example is even more ludicrous; students being asked to create 21st century projects yet they aren't given anything but 20th century tools such a colored pencils and construction paper. It is the school leader's responsibility to ensure teachers have adequate hardware and software for implementing technology.
6. Purchase hardware or software after a sales pitch rather considering staff needs. Sometimes while attending a leadership conference or in a leadership meeting a school leader will see a demonstration of a new product like a smartboard or class response device. He becomes so impressed by the device that he forgets he's seeing a "sales presentation" and agrees to purchase 15 of them. Next thing anyone knows, these things are being installed in classrooms and no one has any idea about how they are going to be used. The devices become expensive dust collectors. Administrators should always bring in the end users when making these purchase considerations. School leaders would do well to remember that sales pitches don't always translate into effective classroom implementation when it comes to technology sales presentations too!
7. Fail to be enthusiastic about technology use themselves. This is self-explanatory in many ways. There are many a school leaders who communicate a total lack of enthusiasm or even disdain for technology by their reaction to it. They don't talk about it. They ignore it. They even change the subject when a teacher excitedly describes a technology-infused lesson that went well. Twenty-first century education is exciting. I find it very difficult to understand the school leader who is not excited about technology's potential, but there some school leaders out there who kill teacher enthusiasm by just their reactions.
8. Refuse to use technology yourself. This is related to number 7, but involves a total rejection by the school leader to use technology. You can't be a 21st century leader by refusing to be a tech consumer yourself. Your refusal to engage in its use demonstrates what you really feel about technology. School leaders shouldn't complain that their teachers fail to use technology innovatively when they keep sending out paper memos.
9. Fail to provide training and additional resources needed for tech implementation. Training with an expert user is always a plus, even when using someone on staff as that expert. Even more important is providing time for the teacher to explore, experiment, and "play" with the technology. As far as resources, school leaders need to make sure teachers have all they need to implement new technologies: everything from powerbars to tables. Nothing can be more frustrating than having your greatest tech plans foiled by a lack of power outlets.
10. Use test scores as the only measure of successful technology implementation. This is a real killer of anyone's enthusiasm for technology. Everything we do and do well cannot be connected to a "higher test score." Test scores provide valuable information but they are not the only measure of effectiveness. School leaders who always want to know, "Will it increase test scores" aren't really interested in successful technology infusion and tech implementation anyway. Their focus is pretty obvious.
There are, of course, many other ways for school leaders to "Kill the Passions any Teacher Has for Technology" but this has to be some of the most common I have encountered. I try to use this list as reminder daily in my own efforts to support teachers use of technology.
Monday, February 27, 2012
5 Areas of Consideration for Developing a BYOD Policy for Your School or District
While there is some debate about whether a BYOD (Bring Your Own Device) Policy perpetuates inequities and the technology gap, school districts in times of tightening budgets and limited resources are looking for cost-effective ways to increase student access to technology. While BYOD should not be a substitution for adequately funding access to technology for all students, it is a means by which we do not have to ask students to unplug when their walk through our school building doors. But in providing this increased level of access, there are areas of consideration before opening the WiFi to student use, and here’s a short list of 5 considerations for implementing a BYOD policy for your school district.
1. Be aware of the technical requirements needed for providing BYOD in your school or district. For example, make sure your hardware and software is prepared to handle things like the sudden increase of IP addresses with all the new devices logged on to your network. Also, how will the sudden increase in devices affect bandwidth? Taking stock of your network to see if BYOD is going to enhance access not degrade access is important.
2. Set up general guidelines for BYOD access. These guidelines are important. They let students know that using their own devices is welcome, but instruction and educational use is the primary reason for that access. Here are some key things to consider when setting up these guidelines for a BYOD policy:
4. Clear description of the procedures students must follow in order to optain access under the BYOD policy. This tells students clearly what they need to do in order to obtain their access.
5. Clear disclaimers regarding what the school is responsible for and not responsible for. For example:
1. Be aware of the technical requirements needed for providing BYOD in your school or district. For example, make sure your hardware and software is prepared to handle things like the sudden increase of IP addresses with all the new devices logged on to your network. Also, how will the sudden increase in devices affect bandwidth? Taking stock of your network to see if BYOD is going to enhance access not degrade access is important.
2. Set up general guidelines for BYOD access. These guidelines are important. They let students know that using their own devices is welcome, but instruction and educational use is the primary reason for that access. Here are some key things to consider when setting up these guidelines for a BYOD policy:
- Clear statement in policy that use of a device during the school day is clearly at the discretion of teachers and staff. They are to put the devices away when asked to do so.
- Clear instructions to students that using devices during the instructional day is in support of their educational activities. Personal access for personal reasons is secondary.
- Make clear to students that their use of a device must not disrupt the learning of others.
- Clear statement in policy that use of a device on the school WiFi might mean their device could be subject to search and/or seizure under certain circumstances.
- Clear statement that use of a device under the school or district’s BYOD policy requires the student's adherence to the school or district’s acceptable use policy.
- Clear statement regarding what kinds of resources students will have access to using their own devices under the BYOD policy.
4. Clear description of the procedures students must follow in order to optain access under the BYOD policy. This tells students clearly what they need to do in order to obtain their access.
5. Clear disclaimers regarding what the school is responsible for and not responsible for. For example:
- Access to the WiFi is for Internet access only. No access to other network resources is provided.
- School district IT department is not responsible for the maintenance and repair to personal devices used under the BYOD policy.
- The school district is not responsible to damaged, lost, or stolen devices used under the BYOD policy.
Thursday, January 19, 2012
Lessons from Our One-Year Experiment with BYOT
Schools can successfully implement the practice of allowing students to use their own technological devices on school networks. Early next month, our school will mark the one-year anniversary of our implementation of a policy that allows our students to use their own laptops, tablets, iPods, and smartphones on our school WiFi. Last February, I posted "Lessons in Providing Students Wireless Access in Our School Building." In that post I described what we learned early in that implementation after three weeks.
Now, after almost a year's implementation, I would still stand by those lessons we learned early in the implementation process. Now, a year later, here's my revised list of suggestions for those considering a BYOT (Bring Your Own Technology) initiative.
1. Educate your parents on the kind of access you're providing students. During the course of the past year, several times I've had to explain to parents that our school is still providing students with filtered access. Though they are using their own devices, our filter is set up to provide some level of protection. This meant a great deal for those parents who were afraid that students could access anything while at school. When you implement a BYOT initiative, it's important that parents understand what you mean by WiFi access and what actions will be taken should students access unacceptable content.
2. Educate students on responsible use of their WiFi access. Ethics and responsible use of technology should be part of what we teach students anyway. But as you implement a BYOT initiative, teaching ethical use of technology, even with their own devices becomes an integrated part of what the school does. Any new BYOT initiative should include an ongoing focus of ethical use of WiFi access and technology in general.
3. Be prepared for technology glitches, even after a year's implementation. Even though most kinks in the system work themselves out over time, there are going to be issues. For example, when we implemented the use of an iPad lab a couple of months ago, IP address assignments by the hardware and software was suddenly an issue. It's vital that school leadership and teachers work through these problems as they occur. Often all that's needed is a software adjustment, but be prepared for the need for additional hardware. As with any technology implementation program, expect problems and be prepared to deal with them.
4. Make sure students understand teachers control the classroom environment. Students need to know up front that when a teacher asks them to close their laptop or put away their iPod, they are to do so. While you want teachers to engage students in the use of technology, there are certainly times when students need to unplug. On the one hand, you want students engaged in technology use, but on the the other, technology-savvy teachers need to be able to guide that use. School leaders need to make it clear to students that teachers determine when use of their devices happens.
As I indicated a year ago, schools have no choice but become 21st century learning environments. A solid implementation of a BYOT (Bring Your Own Technology) initiative should not be optional, but standard practice. We have had a year of successful, mostly-trouble-free implementation. Twenty-first school leaders no longer have to ask students to unplug when they walk through the front doors if they effectively implement a BYOT initiative.
Now, after almost a year's implementation, I would still stand by those lessons we learned early in the implementation process. Now, a year later, here's my revised list of suggestions for those considering a BYOT (Bring Your Own Technology) initiative.
1. Educate your parents on the kind of access you're providing students. During the course of the past year, several times I've had to explain to parents that our school is still providing students with filtered access. Though they are using their own devices, our filter is set up to provide some level of protection. This meant a great deal for those parents who were afraid that students could access anything while at school. When you implement a BYOT initiative, it's important that parents understand what you mean by WiFi access and what actions will be taken should students access unacceptable content.
2. Educate students on responsible use of their WiFi access. Ethics and responsible use of technology should be part of what we teach students anyway. But as you implement a BYOT initiative, teaching ethical use of technology, even with their own devices becomes an integrated part of what the school does. Any new BYOT initiative should include an ongoing focus of ethical use of WiFi access and technology in general.
3. Be prepared for technology glitches, even after a year's implementation. Even though most kinks in the system work themselves out over time, there are going to be issues. For example, when we implemented the use of an iPad lab a couple of months ago, IP address assignments by the hardware and software was suddenly an issue. It's vital that school leadership and teachers work through these problems as they occur. Often all that's needed is a software adjustment, but be prepared for the need for additional hardware. As with any technology implementation program, expect problems and be prepared to deal with them.
4. Make sure students understand teachers control the classroom environment. Students need to know up front that when a teacher asks them to close their laptop or put away their iPod, they are to do so. While you want teachers to engage students in the use of technology, there are certainly times when students need to unplug. On the one hand, you want students engaged in technology use, but on the the other, technology-savvy teachers need to be able to guide that use. School leaders need to make it clear to students that teachers determine when use of their devices happens.
As I indicated a year ago, schools have no choice but become 21st century learning environments. A solid implementation of a BYOT (Bring Your Own Technology) initiative should not be optional, but standard practice. We have had a year of successful, mostly-trouble-free implementation. Twenty-first school leaders no longer have to ask students to unplug when they walk through the front doors if they effectively implement a BYOT initiative.
Subscribe to:
Posts (Atom)