Ironically, the thing that will likely make the least improvement in the ease of use of software-based products is new technology. There is little difference technically between a complicated, confusing program and a simple, fun, and powerful product.

Past dreams of bliss our lives contain, And slight the chords that still retain A heart estranged to joys again, To scenes by memory's silver chain Close-linked, and ever yet apart, That like the vine, whose tendrils young Around some fostering branch have clung, Grown with its growth, as tho' it sprung From one united heart.

Just how do I design if not with prototyping? An excellent question. The short answer is 'on paper.'

Keep it simple: In general, interfaces should use simple geometric forms, minimal contours, and a restricted color palette comprised primarily of less-saturated or neutral colors balanced with a few high contrast accent colors that emphasize important information. Typography should not vary widely in an interface.

There's only one thing you can use against pure logic, and that's common sense.

A powerful tool in the early stages of developing scenarios is to pretend the interface is magic. If your persona has goals and the product has magical powers to meet them, how simple could the interaction be? This kind of thinking is useful to help designers look outside the box.

Because computers have memories, we imagine that they must be something like our human memories, but that is simply not true. Computer memories work in a manner alien to human memories. My memory lets me recognize the faces of my friends, whereas my own computer never even recognizes me. My computer's memory stores a million phone numbers with perfect accuracy, but I have to stop and think to recall my own.