Perhaps they knew darn right-well about their school's firewall.
See, a Spanish teacher wanted her upper-level students to work on their oral and written communication skills. She wanted them to refine and practice their use of the preterite and imperfect tenses. And she really, really wished that their stories could survive beyond the two minute space in time that they would tell them in class. Oh, and she wanted to afford them with opportunities beyond class to communicate / share in the target language.
Enter wonderful idea: Voice Thread.
- Pick a memorable event from their lives
- Acquire a picture from selected memorable event
- Compose a two-minute script in the target language telling a personal story about selected event, replete with preterite and imperfect verb tenses
- Conference with teacher to receive feedback, revision ideas, and suggestions
- Rehearse, rehearse, rehearse
- Sit in a cozy office with script, laptop , and microphone and, deep breath, record their story into Voice Thread
- Meet well in advance and plan.
- Develop the assignment sheet and rubric
- Upload student pictures to Voice Thread
- Create a test 'thread' to insure smooth instructional transfer to students
- Secure a location for students to record their Voice Threads
- Celebrate the amazingly smooth integration of technology into a pre-existing lesson! Ew, yeah!
For three glorious days, YouTube had been accessible to one and all. On one of those days, well, that's when the Spanish Teacher tested Voice Thread and, tah-dah!, it worked. She uploaded her own picture, recorded her story, and shared it with some of the staff.
But the day students went to record, YouTube had been demoted backed to blocked / evil status and when this happened, our Firewall settings changed, making communication with Voice Thread's site a 30-second opening.
No more than 30-seconds.
So every kid that recorded a diligently crafted, well-rehearsed story, found themselves listening to the first 30-seconds.
Damn you, Firewall! Curse the heavens!I filled out the mandated / friendly "District Tech Request" and held my cherubic breath for a quick and timely (1)response AND (2)solution.
Okay, how 'bout one outta two?
I received a response, immediate and timely. However, a solution took over TWO WEEKS to appear.
That TWO WEEK delay is dangerous for someone like me. But for teachers, well, that time is open season for reaffirming techno-skeptic words and phrases like 'nope', 'told you', and 'that's why I wouldn't do it'.
Ya see, that's plenty of time for word to get out that attempting to integrate technology can be an exercise in futility and stupidity. I mean, why would any teacher willingly make the effort to modify an existing lesson to include technology when doing so runs the all-too-real risk of derailment?
Anyhow, tomorrow, over TWO WEEKS since the students first recorded their Voice Threads, they are going to give it another go. I tested it today.
It worked like a charm!