Reference: see older post
I know I said I'll do the notes there too, but they grew too much, so I'm putting them in a new home. Note that I plan
to edit this post too :)
( Read more... )
First. I think it's a fine talk. I’m sorry I wont be there (actually, you are the one who’ll be sorry, for reasons I’ve made public before)
I have a few things to say, they may not be that important - and I may be wrong (after all - the talk will be given in Hebrew, not English - so things that I find problematic may be non-issues, anyway)
I have a fealing you are covering too much for a 2-3 hour talk to people who don't know a lot about this field. you should try to give the talk to a few people before (or give it to yourself - to see how long it takes).
I think you should treat it as an exercise in Interaction design, which it is - you're giving a talk to people, most of them you know as people who do not understand the reality of designing software/hardware. About half of the people you are coming from the "madaey haruach" type of world. Know your users. I think you should tone it down a notch
My guess is that you won't manage to get through half of what you propose for your talk. This is not because it can't be done, but because you aren’t laying the background for understanding many key concepts you assume that all your audience will know in advance.
I'll give you a few examples:
a blackbox, Occam's Razor, industrial design, marketing - all of these seem like obvious concepts to you - but I’m not sure they are obvious as you think they are to the people who will attend the lecture (and I’ll ignore the fact that even you over-symplified what industrial design is..)
The really good parts in the lecture are those that the people will feel smart when they hear them (for example the SMS example is a wonderful example - this is something everyone with a nokia will agree with). Those that are not as good (like the teapot example, or the email example, which I found difficult to understand - without an actual graphic representation) will make your audience drift, and they might feel a bit stupid.
Another thing - Graphic representation of the issues you disscuss could be very helpful.
" * This principle can be violated in these cases."
It really shouldn't - unless you REALLY know what your doing (and most software companies don't). I can think of only a handfull of situation when non-standard UI elements (for software) made sense and were not annoying and some of the companies who did that are no longer with us, anyway (for example metacreations who did some very cool graphical apps and had non-standard interfaces that made sense).
First. I think it's a fine talk. I’m sorry I wont be there (actually, you are the one who’ll be sorry, for reasons I’ve made public before)
I have a few things to say, they may not be that important - and I may be wrong (after all - the talk will be given in Hebrew, not English - so things that I find problematic may be non-issues, anyway)
I have a fealing you are covering too much for a 2-3 hour talk to people who don't know a lot about this field. you should try to give the talk to a few people before (or give it to yourself - to see how long it takes).
I think you should treat it as an exercise in Interaction design, which it is - you're giving a talk to people, most of them you know as people who do not understand the reality of designing software/hardware. About half of the people you are coming from the "madaey haruach" type of world. Know your users. I think you should tone it down a notch
My guess is that you won't manage to get through half of what you propose for your talk. This is not because it can't be done, but because you aren’t laying the background for understanding many key concepts you assume that all your audience will know in advance.
I'll give you a few examples:
a blackbox, Occam's Razor, industrial design, marketing - all of these seem like obvious concepts to you - but I’m not sure they are obvious as you think they are to the people who will attend the lecture (and I’ll ignore the fact that even you over-symplified what industrial design is..)
The really good parts in the lecture are those that the people will feel smart when they hear them (for example the SMS example is a wonderful example - this is something everyone with a nokia will agree with). Those that are not as good (like the teapot example, or the email example, which I found difficult to understand - without an actual graphic representation) will make your audience drift, and they might feel a bit stupid.
Another thing - Graphic representation of the issues you disscuss could be very helpful.
" * This principle can be violated in these cases."
It really shouldn't - unless you REALLY know what your doing (and most software companies don't). I can think of only a handfull of situation when non-standard UI elements (for software) made sense and were not annoying and some of the companies who did that are no longer with us, anyway (for example metacreations who did some very cool graphical apps and had non-standard interfaces that made sense).
Reply
Leave a comment