As second semester 2004 is drawing to a close, I find myself experiencing (yet again) the frustration of “last-minute learning” in my Web Design class - and I want to do something about it for next semester.
The problem
The more I think about it, the complete process of designing and implementing a website for a client is really only learned during the last few weeks as the students race to get their Client site finished before the end of semester. It’s during these weeks that the first real Client Documentation is prepared, Information Architectures are designed for the first real situation, MS Project Plans are created for the first real project etc. I think this is due to the linear fashion with which we currently teach all the material (with practical assignments and workshops along the way of course!), until towards the end of the semester when students focus primarily on their client projects. But I’m wondering whether a more iterative learning cycle would be more effective and perhaps more student-centred… for example…
Gene, who teaches parts of the course with Jude and me, came up with the great idea at the end of last semester of using some of the modules that she facilitates (Instructional Design / communications) as a “mini” client project, giving students a small taste of the whole project cycle before their major assessment - their real client project. We tried this approach this semester and I think it worked well for the scope that we gave it: students got a taste of a mock client interview and both Gene and I were able to assess most students on their HTML/CSS/Instructional design skills early in the semester. Yet I think I missed the opportunity to use this mini project as an introduction to the complete web design lifecycle (for example, I could have also introduced information architecture, documenting the design, performance testing, accessibility testing etc.)
The idea
Jude and I had a chat the other day about the possibility of a more iterative (or cyclic?) learning process for the students, where they go through the complete lifecycle two or three times during the semester (this was probably Gene’s original idea!). For example,
- during the first 2-3 weeks while learning the fundamentals of XHTML and CSS, we could begin the first mini project: planning, designing and implementing our own website. This mini project would include everything from a small MS Project plan, a (brief) information architecture, design, documentation, implementation, performance and accessibility testing.
- During the implementation phase of the first mini project, we could begin the planning and interviews for the second mini project: the instructional design site. Again going through the complete lifecycle (perhaps in more depth or with more restrictions on accessibility/performance?)
- During the implementation phase of the second mini project, students could begin the planning/interviews for their actual client project - again going through the whole lifecycle (but this time, hopefully on their own).
Of course, as new skills are learned, students would be (hopefully) updating and maintaining their own websites.
But that’s too much work!
… I hear you saying! And perhaps it is impossible to do this without packing more work into an already bulging course - which I want to avoid at all costs. But perhaps it is possible to do without increasing the workload. For example, we could provide strong scaffolding (in the form of templates) for the documentation, project plan and testing cycle for the first mini project, so really students would be filling in the blanks while learning the ropes. Some of the scaffolding could then be removed for the second mini project and finally taken down completely for the final client project. Similarly, the first mini-project would just introduce many of the techniques/skills without going into much depth, the second could build on those and introduce more depth, while the client project would ideally contain little new learning (probably impossible in practice).
I think this structure would enable us to continue developing the self-paced learning strategies that we’ve used this semester and may even enable further flexibility in terms of blended delivery (once the scaffolding/templates and other resources for the mini-projects have been created/updated).
Any comments or criticisms? Can you see any other ways that this might be helpful or unhelpful for the modules that you teach? Or, if you are a student, does the problem description above fairly describe the situation you are now in and do you think this iterative structure would have been helpful or unhelpful for your learning?
Thanks in advance for any feedback!