From The Archives
Software Equals Interactive Design Education?
“What might help in dealing with the problem of using software? Should we teach it ‘outside’ the class, i.e., done as workshops by techs, or as a totally separate ‘nuts and bolts’ unit?”
When it comes to learning software, students can be divided into two categories: self-reliant and instructor-dependent. The self-reliant student will dabble, toy, and experiment until they reach some level of mastery with the given tools; peers will rely on them for help either during or outside the class. Oftentimes the instructor even looks to these students for technical assistance, and moreover, the self-reliant student is the model teacher’s assistant. On the other hand, instructor-dependent students feel the teacher must direct them in times of need, and when instructors continue to help students with even the smallest problems, they will hinder the student’s growth because this prevents them from exploring and troubleshooting on their own. For designers, the willingness to discover and take risks is a valuable asset that mirrors the design process itself. Play yields inquiry, forcing one to ask questions about the matters at hand and then observe, act, and react in order to reach an objective. Whether the media is pencil or computer, instilling self-reliance and the play principle should always be the instructor’s objective when teaching computer media and technology. But changes occur so frequently that unlike a pencil or paintbrush, the Photoshop of today will be different within 1-2 years time. And with companies acquiring one another, or absorbing their competition, it is foolish to revolve a class (or curriculum) around software because institutions may find little or no support for that software in the near future.At an early level of development, students must learn to understand this so they may adapt to technology’s dynamism long after they leave school and then carry the habit of play and self-reliance into their interactive design practices. By having a media course at the foundation level, students would be exposed to the fundamentals, history, and usage of the computer as a creative tool from the outset. Said course would have weekly lectures about historical and technical data, with breakout sessions for studio work or lab sessions moving them through one piece of software to the next: bitmap and continuous-tone renderings; working with vectors and Post-Script data; and combining the aforementioned with motion. Only after passing this class, would students move into advanced instruction or their focus area, such as graphic design.
But merely creating a new course or changing the entire curriculum won’t guarantee a changeup in a student’s design process; they may invariably start with the computer and rely on software around the clock. And while such a process has its benefits, this technocentric method will close their creative process, and cut them off from valuable research methods and practices, so intervention must happen where the instructor will redirect the student to keep them fresh, motivated, and on the right track.
This intervention can happen in a number of ways, and sometimes teamwork will help bring about fresh results and foster each student’s communication and social skills. Brainstorming sessions are just one of many ways to get them to talk with one another instead of gazing at a screen in isolation, and brainstorming will have a valuable impact over the long term because it teaches students to work in broad terms at the outset, having a broad view of the problem and its context. Requiring students to perform other experiential tasks such as interviewing—where they can hit the ground running and get first hand information from reliable sources—teaches them that design and the work they do has social and cultural relevance, even though it can exist out of context on the users’ computer screens. From interviewing, the may learn that a kiosk will best serve the problem instead of a website. And heuristic evaluations (although a quick and efficient method of testing) challenge students to hold their designs against the barometer of real-world applications and experiences. Mapping will also yield favorable results, especially if the process involves the entire class: through mapping, students will source material that relates to the problem at hand. The visual or textual data builds up piece by piece on a wall, evolving and growing into something that early on, appears out of hand (first described by Robert Horn in 1966). However, through a macro viewing, where students can see large amounts of information and images, they will begin to draw relationships by grouping, fusing, or combining elements. This method of categorization is akin to having an outline prior to writing a paper—it gives you a structure. Nothing is more upsetting than when a student has either lost their storyboards or outline, or both; and it’s even more infuriating to learn about students ignoring that process entirely.
The argument has been made that students, who dwell on processes like those above, will fail to become productive and efficient designers when they enter the workforce. Some even believe that mastery of tools, software and technology is the privileged and ideal skill-set for interactive designers entering an agency. In fact, what most employers do want are designers who can hit the ground running in a number of domains: an understanding of software; a willingness to work in team environments; dedication; curiosity; and strong communication skills. In agency and studio environments, there is always a need for talented electronic production specialists, who dedicate their time and effort to final assembly and engineering of jobs using commercial software and technology; they ensure that a job is “tightly” rendered and that all parts are in place prior to final production and implementation. This would be similar to the 3D designer that generates Frank Gehry’s conceptual visualizations; any of Gehry’s gestures or drawings would be nothing without the 3D designer, but Gehry does not spend his own time rendering and wrestling with the computer because in the studio, generating that initial idea—even as the crudest napkin sketch—carries the most value.
In order for interactive design to move forward, we must generate thinkers, entrepreneurs and innovators in the classroom, so they will have the ability and ambition to do more than mediate between the idea and end product using code or commercial software. In order to prepare students to be thinkers as well as form givers, they should be surrounded by process-sensitive problems and interdisciplinary projects that put them in touch with culture, current events and social issues. Said educational goals would create a self-motivated student with a passion for life-long learning as engaged citizens. A new graphic design curriculum that focuses on principle, tools, complexity, and change would better prepare students for such endeavors. Principles would instruct students about the means of creating dynamic, expressive and communicative form; tools would sharpen hand and craft skills while introducing a wide variety of rendering methods including print and digital media; context would expose students to a range of problems, issues, and influences while fostering critical thinking and inquiry; and complexity would expose them to a range of difficult and dynamic problems needing intense examination and adaptability. Through this breadth of instruction, students would gain ambitions deeper than the supposed financial affluence that awaits them, and foster critical inquiry far beyond gazing at a computer screen for answers.
-
As a student in Graphic Design, i've learned the importance and relevancy of "playing" with your software on your own time if you are unfamiliar with most of its functions. If you do not understand something, research it (look it up in "help" instead of tagging down the instructor first, you will learn much faster if you are self reliant). You will grow exponentially as a result. After all, the profession we are studying about highly revolves around problem solving and a reverent understanding of the culture and environment around us. Learn to evolve with it now and in the future.
-
Jason, I wrote an article very similar to this some while back talking about the problem with software. One issue is the belief that there is some kind of mystery secret to a successful work life after studentdom.
I think that we need to educate students about the idea of continuous learning - there is always someone who knows the software better than you. One's point of different has to be what one can do with it. That is what defines a designer as different to a software hobbyist.
We're also caught in a fee-paying student trap (at least in the UK and Australia and I imagine the USA) where we're expect to provide a service. That's fine, we should be, but it's important that we help students recognise that our service might not be to show them software tricks but rather to show them how to think and that that may mean leaving them to work it out themselves. In the end, we want to teach our students to go beyond learning how to play the instruments and instead teach them to play the music. -
I see both of your points on this matter, and especially appreciate your statement, Andy, "...we want to teach our students to go beyond learning how to play the instruments and instead teach them to play the music." That's the most poetic way of framing the matter around education that I've ever read, and it is an ongoing challenge. Time's proven that this issue won't go away, so doesn't that tell us something? Either we're not doing it right in the classroom, or the client (student) will always have a propensity for the our spoon-feeding them. I do not fault the client for this inclination, because I was in that state at one time myself, but forced to learn by my own instructors and lack of exposure in the classroom. There's just not enough time in school to cover everything; and when they leave school, designers must get used to learning on their own.
-
**clap** **clap** **standing ovation**
I love this article. I may make it required reading for my students first day of class!
"...what most employers do want are designers who can hit the ground running in a number of domains: an understanding of software; a willingness to work in team environments; dedication; curiosity; and strong communication skills."
Could not have said it better myself.
Thanks for the great article! -
As an instructor, I am encouraged by this topic. However, there are some who need more assistance than others to master the concepts of software applications. Often this happens with older students.
Younger designers, often have no fear of the computer and dive right in. They often think of the computer as little more than a toaster. Older students (over 30) sometimes struggle with the changing environment that our culture has created with the magic computer that opens up our world to them.
I have had some who have never really worked with any kind of computer before. To them, surprisingly, they are still uneasy wandering around on the web, have never experienced blogs, don't know how to access Google or Yahoo or Youtube to find information or instruction. They seem to be the most needy.
I often find myself being ambushed by one of them between classes to figure out how to do some simple task in Illustrator or Indesign.
At the end of the day though, these students must be confronted with the realization that perhaps maybe this isn't the right career for them.
At our school, we struggle with the time spent (hundreds of hours) to master extensively, software packages and then have to retrain them and our staff every 24 months.
Employers in our neck of the woods, appreciate the thorough understanding of software that our students use, as they can dive into a job from day one. But I worry about some of them being able to transition as thinkers in the business over the long haul.
Finally, we all know that design education is only begun in college. Our education continues in the working environment. Some of us began as designers on the production side and became thinkers, and some of us started as problem solvers and later became adept at software.
After the Future 3 conference last week in Chicago, we are beginning to discuss this conundrum in our teaching curriculum. -
Interaction design and instructional design both rely on cognitive psychology theories to focus on how users will interact with software. They both take an in-depth approach to analyzing the user's needs and goals. A needs analysis is often performed in both disciplines.
Both, approach the design from the user's perspective. Both, involve gathering feedback from users, and making revisions until the product or service has been found to be effective. (Summative / formative evaluations) In many ways, instructional design can be considered a precursor to interaction design.

Comments