Non-Authoritative "Expert Plan"
0This is perhaps one of those midrashim that strive to unnecessarily explain the inexplicable…
It is, perhaps, worth noting — in my endless struggle towards internal consistency — that I’m still on board with what I wrote about striving to be less authoritative in my own classroom (as a means of pushing my students to be more active and independent learners).
The term “Expert Plan” that I was throwing around last weekend (and that, in fact, has become a whole category unto itself on this blog) is not of my devising. And is, in fact, my department head’s effort to do exactly as I aimed to do in being less authoritative: distribute leadership, push the folks doing the learning to take control of their learning, and generally promote active, independent learning… among faculty in preparation for going 1:1.
I am working on an “Expert Plan” for using laptops in education wearing my classroom teacher hat, not my educational technologist hat (although, perhaps, documenting with the educational technologist hat in the vicinity).
Short Focused Screencasts
0A week or so ago, I recorded a long screencast for my computer animation class, explaining — soup to nuts — the process of constructing an armature for a model in Blender. It’s got a lot of tricky steps, and you have to do it just so: an ideal candidate for screencasting. You can see it. You get it narrated. You can pause and rewind. It’s great.
Except.
It’s not so great if your idiot teacher gives you a fifteen minute video that explains the whole process, without bookmarking key moments in the process. This is one of those wonderful learning moments, when teaching material helps you understand how to teach that material better. Which doesn’t do your (well, my) students a lot of good if they’re trying to figure out a particular step.
Screencast-O-Matic offers some bookmarking potential that I need to play with on my long video. But, in the short term, it’s been just as easy — maybe even easier — to just record 1-2 minute videos of specific key steps. We’ll see if this works better for my poor, confused students. None of what they see in these videos is new. But they need to be able to pull up the instruction á là carte, rather than as the prix fixe seven course meal.
So, a playlist of the short videos:
And, for comparison’s sake, the original long video (broken into two pieces on YouTube below):
Blogs as Portfolios
0This post is part of a series that are components of my “Expert Plan” at my school, looking to create a shared resource for my colleagues as the school moves towards greater adoption of laptops and technology in our pedagogy.
The Model
One goal of [my media design class] and [my computer animation class] is for the students to develop a portfolio of completed work that demonstrates their skills and creativity in digital design and presentation. In both classes, I have been collecting projects and final products on the [local network shares] and (in the case of [media design]), on Flickr (more on the Flickr experience specifically under Social Media).
At the end of the digital photography unit in [media design], I asked my students to draw on their body of work to present a portfolio of the 5-7 most representative pieces, and to post these pieces, with some annotation, to our class blog. The students each created a category on the blog for their portfolio (so that we could bring up everything related to their portfolio on a single page). I posted my (public) feedback to the students into these portfolios, and asked the students to provide feedback to each other (in public) on the blog as well.
A major part of my rationale for asking the students to publish their portfolio to the blog was to provide them with a public arena for “publishing” their work, hopefully pushing them to take pride in their presentation (and allow them to share with their friends, family, etc.).
In Practice
Thus far, one unit (digital photography) has been posted to the blog. I anticipate that we will post videos shortly, although this may be a more restricted process (I don’t feel good about publishing interviews with students to the world without some pretty clear and explicit permission from the families involved). We may end up having conversations about the videos on the blog without embedding the video (instead, we will probably link to the videos posted on a Ning).
I would like to get my computer animation class to the same point of presenting their work in a portfolio, but the lion’s share of the file collection and organization has been mine. The students in that class have had far more problems losing their files, misnaming them, forgetting to turn them in, and so forth. In fact, on Parent’s Night, I realized that, although I had required a JPEG of each model that that they had constructed, such a vanishingly small minority of the students had turned those files in (and had, therefore, taken a full grade hit on their scores), I didn’t really have enough to put together a slide show for parents.
Reflections
One unanticipated issue (on my part), was the difficulty the students had in distinguishing between when I wanted them to create a new post of their own, and when I wanted them to comment on someone else’s post. I think (based on their most recent performance), that this is a confusion that is dissipating, but that a good clear explanation of the structure of a blog might have been a good place to start.
I fell into the classic trap: I believed that my students were more technologically able than they are, based simply on their appearance as “digital natives” — particularly embarrassing, as I have spent the last few years railing against this assumption! (Students know how to do something better than teachers — play video games, watch YouTube, IM — but are vastly deficient in the critical and analytical skills related to thinking and learning, which we have learned through years of education (and so will they, albeit moderated through more extensive use of technology).
Blogging Reflections
0This post is part of a series that are components of my “Expert Plan” at my school, looking to create a shared resource for my colleagues as the school moves towards greater adoption of laptops and technology in our pedagogy.
The Model
Particularly in my [media design] class, which is fundamentally more process-driven, but also in my more application-driven computer animation class, I want to push my students to think critically about their own work and the work of their peers, and to reflect on that feedback (and, potentially, my feedback) in a constructive, forward-looking, “lessons learned” manner. To this end, as we reach the end of a project or unit, and we critique work presented, I ask students to respond the criticism that their work has received (while simultaneously providing similar criticism to their peers). I have them post their responses to our class blog, and then ask them to review each other’s responses, posting comments on ideas or insights that are particularly interesting or challenging to them.
In the interest of “pre-thinking” big questions before students arrive in class, I may also present them with a big question and a list of resources as a starting point for beginning to think about that question. I ask them to post their response to the question to the blog as a way of ensuring some level of thought and reflection prior to class, and ensuring that our class discussion can go further and deeper, rather than getting bogged down in background material.
In Practice
This is definitely something that works better the more you do it. And initial forays will be deeply disappointing. The best advice I’ve ever received about asking students to be reflective (especially in public) is that you have to have one or two “throw away” assignments where the focus is on getting the process under their belt, without regard to the quality of the outcomes.
By the middle of November, I have really asked my students in [media design] class to critique and reflect on our class blog only a couple of times, at the ends of units. This is, perhaps, not frequent enough for them to develop real facility. I have interspersed the feedback reflections with the big questions, so that they stay in the habit of posting to the blog every couple of weeks.
I have found, however, that the process of pre-thinking (first espoused to me by my colleague Anna Reid at [my previous school]), is very effective. Particularly when done regularly (I have also used online reading quizzes in a similar way, asking open-ended questions based on the reading to focus their thought while providing mandatory accountability.) I found, for example, that when we sat down to discuss issues of copyright and Fair Use in class, the students who had posted had already developed much more nuanced and thoughtful perspectives on the issues, and that we had a much deeper and more informed class discussion than we had had on the introduction of the assignment before the weekend. (In fact, when presented with optional reading assignments, most of the students read them as well.)
The process of developing an online conversation, in which students are actively commenting on and discussing each other’s ideas and work also requires more development. I have assigned a couple of rounds of online commenting, asking students to post n responses to each other’s work, but have not had in depth discussions of those comments. I have modeled this commenting, particularly early on, although the process of commenting on every student’s work quickly begins to (at least) feel prohibitive in terms of time.
Reflection
This is actually an area that I want to really hammer away at over the rest of the year. I think that the payoff — not potential, but actual payoff — is huge, in terms of helping students both learn to think critically about their own and other people’s work, and to develop their own perspectives based in evidence rather than hearsay. The big challenge for me, is to really embed this in the routine of my class. (I have mentioned this elsewhere, but the adjustment from 4-5 class meetings per week to just 2-3, is really messing with my rhythm… and I didn’t have terribly reliable rhythm before this.)
Wikis for Notetaking
0This post is part of a series that are components of my “Expert Plan” at my school, looking to create a shared resource for my colleagues as the school moves towards greater adoption of laptops and technology in our pedagogy.
The Model
For the last few years, I have found that, when appropriate, I get far more use out of my notes if I take them on a computer. Using the computer allows me to keep my notes organized, to instantly create links to related information (either within my notes or on the web), to flag my own questions as they arise (and unflag them as they are answered), to find ideas in my notes later (search is way faster than flipping through my notebooks and legal pads), to share my notes with colleagues and students, and to link to as references and resources in later iterations of documents.
In Practice
It’s not always kosher to have your laptop open in a conversation. If I take notes in a one-on-one meeting in my laptop, there is a real danger that I will be talking to my computer rather than the person I am meeting with. (Simultaneously, if I take the notes on my laptop, I am able to refer back to them more easily than in handwriting.) Personally, I have found that if I feel compelled to take notes by hand, that those notes are not going to make it into my computer except in extraordinary circumstances, and that the only service that paper notes have for me is as a memory aid (“the information has passed from at least one neuron to at least one other neuron, crossing at least one synapse in the process, giving you a faint hope of remembering the information.” — Duane Bailey).
If there are network connectivity problems (or battery power level issues), my notes may either not be available or may disappear entirely (as happened at one point this fall, taking notes on [a major collaborative project] presentation). This doesn’t happen with notebooks. However, referring back to the last paragraph… those notes would have gone into the ether anyway (for me at least) if I had taken them on paper.
I find that I am much more willing to share my digital notes than I would hand-written notes — not just because of legibility issues, although those are real, but also because when I share my notes, I share it with an expectation that the recipient will be adding some input to those notes, adding value for me as well.
I have also found that using the tagging feature of the wiki gives me a tool for taking attendance at a meeting — who was there, so that I can find notes based not just on content, but on the makeup of the meeting: “I know we discussed this in EdTech, I think Scott said something about it…”
Reflection
As someone who spent years not taking notes on anything, simply remembering what was said to the best of my ability, I find that taking notes on my computer is a massive advantage: it allows me to empty my brain and forget things with confidence. And taking my notes in a wiki makes them instantly shareable and referable from any computer, anywhere. I love it.
Wikis for Documentation
2This post is part of a series that are components of my “Expert Plan” at my school, looking to create a shared resource for my colleagues as the school moves towards greater adoption of laptops and technology in our pedagogy.
The Model
This is actually a classic use of wikis — the one for which they were developed, in fact — and one that I have found very useful in the past. By documenting my work on a project in a public, shared space, I am both sharing information that needs to be known and inviting other participants to contribute their knowledge as well. I use wikis both for shared projects with my colleagues (as a way to guarantee that only the most current documentation is available, rather than distributing instantly out-dated paper handouts) and as a way of pushing my students to document their own work so that I can grade them on process. Additionally, wikis are a way for me to document my own thought process for both professional development and future planning purposes.
In Practice
Shared Projects with Colleagues
I have found that many of my colleagues (both at [my current school] and [at previous schools]) are hesitant to edit existing documents. The most reliable contribution that I have found my colleagues make is on meeting minutes, when I invite those who did not attend a meeting to insert their contributions to the meeting as comments on the page.
When working on a project with a similarly technically-inclined colleague (say, in the Education Technology department), the process is more likely to be more collaborative, as we edit each other’s work more liberally (although even this is not a guarantee).
Student Documentation of Process
Students don’t document their working voluntarily. I have only had success in asking students to document their work when I have both assigned the documentation for a grade (usually a grade separate from the end product of their work, so that I can distinguish between process and outcome not just in narratives but also in my gradebook).
The closest that I have come to developing a true classroom culture of collaborative documentation was last spring at [my previous school] in my Application Design classroom. In this case, I worked with the students to help them select and design an open-ended project for which they had to do immense amounts of research (they were creating a computer-controlled CNC lathe). I found that there was an inverse relationship between the amount of expertise that I demonstrated and the amount of work and thought that my students contributed: when they could rely on me for answers, they were lazy about documenting their work and finding their own solutions. When I professed no knowledge (often truthfully), students were far more likely to both do much more exhaustive research and to present their findings more clearly.
Professional Development
One challenge of creating a truly collaborative wiki environment (whether with colleagues or with students) is to get all of the participants to read, respond, revise and/or react to each other’s contributions. For example, I am doing a miserable job, on this page, of linking to the work of others in the Laptop Leaders program. I suspect that a major part of this is simply the “drinking from the fire hose” feeling incurred by the stream of data as everyone contributes simultaneously. In a classroom, I have had some success dividing students into groups around a shared research interest. To that end, I need to sift through the other Laptop Leader documentation that refers to, say wikis.
Reflection
At the basic level, my sense is that wikis represent such a shocking change in paradigm for how the web is used that the average user is either befuddled or intimidated by them. I found that I was explaining how wikis work to my classes and the students were fascinated and mildly horrified at both the ease with which they could make changes and the ease with which I could track their use of the wiki. I don’t know for certain, but I wonder if my colleague’s reluctance to update wikis is a combination of fear of the unfamiliar (editing the wiki) and fear of speaking out (publishing their words/ideas to a broader arena in a way that feels more permanent than, say, an email — more on par with a faculty meeting).
Wikis for Class Notes
0This post is part of a series that are components of my “Expert Plan” at my school, looking to create a shared resource for my colleagues as the school moves towards greater adoption of laptops and technology in our pedagogy.
The Model
I started off using this model in both my [high school] classes. I post an outline of the class to the wiki before class. At the start of class, as I discuss the agenda for the day with the students, I project the outline on the board. After discussing the agenda (my plan, their questions, etc.), I ask for three volunteers: one to take notes into the outline during class, one to review those notes for content before the next class, and one to review those notes for clarity before the next class. The content reviewer is responsible for correcting any mistakes (or omissions) that the original notetaker made. The clarity reviewer is responsible for proofreading and correcting the notes into a readable, standard English format.
In Practice
I found, almost immediately, that while the [media design] class was (grudgingly) willing to do the notetaking, the [computer animation] class revolted against it. The revolt in computer animation had a lot to do with the difficulty of simultaneously following along with the processes that we were learning in a computer modeling application and also keeping a browser window open and taking notes into the wiki. Theoretically, a dual display setup might have ameliorated some of those concerns (screen real estate was demonstrably at a premium as they were trying to use both applications, the browser and the 3D modeling tool). However, the real issue lay in the division of attention.
I have stopped asking the computer animation class to take notes into the wiki, but continue to encourage them to take their own notes (a practice that none of them engages in voluntarily — and their difficulty grasping new concepts reflects real difficulty storing the concepts for reflection, whether in their heads, their notebooks or their computers).
I have substituted somewhat more detailed notes of my own in the outlines for computer animation, or links to more detailed tutorials online covering the same concepts that we are learning in class, or links to screencasts demonstrating the concepts and processes we are learning in class. (One challenge that I have run into is that, using Blender, many of the tutorials and screencasts assume a great deal of prior familiarity with the materials, if not the tool, so I have been working on recording more basic level screencasts for that class).
On the flip side, we have settled into a routine in [media design] in which I ask for a notetaking team only on days when I know that we will be having a concept-based discussion/critique/lecture (as opposed to process or application-based lessons). A core of students have stepped up as fairly reliable notetakers, although I am working to spread the responsibility out across all students in the class — although I have set up no formal system of rotation (this lack of a formal system is actually based on previous experience with rigid rotations on what is, essentially, a creative task: it’s lousy. It works far better to set up an expectation that everyone will do it, and then ask for volunteers in the moment, while creating a (public) tracking system to ensure that no one is left out.
One issue that I have run into, particularly over a span of project-based lessons which are not discrete lessons but actually the continuation of a single idea (editing a video, for example), is that I lose track of time and forget to keep the wiki up-to-date. I focus my attention on the process occurring in class, rather than in documenting the process. Since my rationale for documenting the process is provide a resource for the students, this is deeply problematic and something that I need to address.
Reflections
Early on, I realized that I should have made more of an effort to distinguish between concept-based and practice-based classes, and to create different models for collaborative notetaking in each of those environments. My computer animation class did well in articulating their frustration (mostly) respectfully, and speaking up for their own needs and learning styles.
I have not incorporated the notetaking into the students’ grades (which was, really, something that slipped my mind), framing the notetaking not as an assignment, but as a collaborative study tool. I’m not sure that this is a winning motivator for students. I think it works in my [media design] class because they are a) intrinsically interested in the material at a more conceptual level and b) generally a year or two older on average than my computer animation class. That maturity is reflected across the board — preparation, classroom demeanor, participation, actual product. It would, of course, be easy to connect a grade to participation in the notetaking (do some math, figure out how many times everyone needs to do it to cover the semester or quarter and assign it that many times).
The other missing component, and this has much to do with my teaching style, is adequate review of the student notes, to provide feedback on quality (and quantity). Early(er) in the year, I should have dedicated much more of a class period to going over the previous period’s notes and pushing each of the members of the notetaking team to be more accountable. To be honest, the switch from meeting my classes 4-5 times a week to 2-3 meetings (yay for changing schools!) left me running ragged trying to keep up with material, and process fell by the wayside.



