Several years ago, Astrid Klein and Mark Dytham invented the Pecha Kucha presentation format in response to two significant problems in presentations: people tend to talk too long and people tend to use PowerPoint slides in mind-numbingly horrible ways. I’m sure you all know what I mean. Klein and Dytham’s solution: add constraints to the presentation format:
They held a conference. It was a success. And the Pecha Kucha format spread around the globe, landing, now in #tfw1 at Rowan University.
Since the first conferences others have added additional constraints to the format, notably limiting the number of images on a slide, limiting how often an image can be used, and how many words may appear on each slide. These are often written in rules that look like this:
Because of the limited time, Pecha Kuchas are wonderfully devoid of fluff and filler. Presenters using such a format get to the point and explicate their points. The presentations are idea-and narrative-driven. That is, they take a single idea or issue (for example, bullying in a cyber world or the impact of gaming on writing) and over the course of the presentation explicate on that idea, the implications of that idea, and offer unique (not cliched) takes on what we are to do with this idea or issue. The presentations, when done well, are fascinating and gripping. They are funny when they need to be. And they leave the audience wanting to know and understand more. That is what you are going to try to do in your project.
Here is an example of a Pecha Kucha by Dan Pink of Wired Magazine in which he explains and provides an example of the format (and mispronounces the name):
For this assignment, each blog group is going to collaboratively compose a Pecha Kucha that considers the impact that Web 2.0 technologies’ affordances and constraints are having on the issue discussed in their blog
That is, I’d like you to look in-depth at the many complex and varied ways that Web 2.0 technologies are transforming how people understand your issue, writing, how they all intersect, and what the implications are for the future, and to present those ideas in a seamless narrative.
Each group will present their Pecha Kucha to the class on the last day of the module. Each group member will also compose a reflection that is due on the Sunday following the end of the module. The reflection will contextualize the work the student completed on the Pecha Kucha. Though this is a group project, students will be assessed in terms of their individual work. If a group members does not fulfill their obligations, the other members will not be penalized.
The Structure of the Pecha Kucha
Each Pecha Kucha must conform to the following constraints:
Though students are creating their own slides and composing their own parts of the narrative, each blog group must collaborate when determining the overall goals of their Pecha Kucha. This is because the presentation must be seamless. That is, it should appear as if it was collaboratively written or written by one person. Here is a suggested work flow for getting started:
I suggest setting strict due dates for when work is going to be completed. If a blog member is not doing their work, the rest of the group should move on and not get held up.
I also suggest composing the final PowerPoint on a Mac so there are no presentation issues when moving from a PC to the classroom Mac.
Setting up PowerPoint, Keynote, for a Pecha Kucha
Students must set up PowerPoint or Keynote to advance automatically from slide to slide every 20 seconds. This takes a few easy steps.
Setting Up PowerPoint
These steps can be taken before you start adding slides or after all the slides are completed.
Setting up Keynote (Mac only)
These steps should be taken after all the slides are completed (or during the process if you want to test things out)
You are to compose TWO reflections in ONE .doc, or .docx document, which you will also post as a TWO part final blog (700-800 words total). Write this in response to the following prompts:
Your reflections should be written in Times New Rowan font size 12 and be presented double-spaced. Be sure to put your name at the top of your document.
Submit your reflections in two ways:
2/17: All group members should know what their section of the presentation will be about
2/19: Rough Draft of slides and narrative due by class time in Dropbox
2/24: Final Draft presented to class; your blog group is to create one blog post in which you upload a copy of the PowerPoint and paste in the narratives for each blog member. Attribute the narratives to the blog member by firstname and last initial.
2/27: Add your Reflection to your Dropbox folder by 11pm
3/12: All group members should know what their section of the presentation will be about
3/26: Rough Draft of slides and narrative due by class time in Dropbox
3/31: Final Draft presented to class; your blog group is to create one blog post in which you upload a copy of the PowerPoint and paste in the narratives for each blog member. Attribute the narratives to the blog member by firstname and last initial.
4/2: Add your Reflection to your Dropbox folder by 11pm
4/21: All group members should know what their section of the presentation will be about
4/28: Rough Draft of slides and narrative due by class time in Dropbox
4/30: Final Draft presented to class; your blog group is to create one blog post in which you upload a copy of the PowerPoint and paste in the narratives for each blog member. Attribute the narratives to the blog member by firstname and last initial.
5/3: Add your Reflection to your Dropbox folder and create blog post by 11pm
Beyond creating and delivering this collaborative presentation, each person will provide a substantial reflection (700-800 words) in a two-part blog post (and Word doc uploaded to your portfolio). This will be your final assignment for the module.