Friday, November 9, 2007

Design Language

One session that caught my attention at AECT was how to teach design language in the filed of ID. If we examine closely in our field, we have hundreds of models, tens of theories, but what is lacking is a set of systematic design language; consequently, we ended up perform badly in describing projects and in demonstrating our ideas.

I totally agree on this. See the storyboards we created for our two YouTube project, you will know what I mean.

However, these poor storyboards helped us film the scenes one after one, and we are finally done.

1 comments:

wave said...

That's what I like most, the process of conducting the product rahter than the product itself. Just like your comment in the previous post, we ignore the learning iteself. Which is more important? process or product? Brainstorming, discussing, exploring, arguing, drafting, agreeing, disageeing, etc. all these process are more important for me, by camparing to the final product.

Learning and Teching become more interesting when you see the improvment little by little. my 2 cents