A List Apart
Brightly Colored Food
City of Sound
Croc o' Lyle
Digital Web Magazine
Dive Into Mark
Guide to ease
Joel on Software
Noise Between Stations
Off the top
Signal vs. Noise
I pretty much agree with Jakob's April Alertbox Paper Prototyping: Getting User Data Before You Code: paper prototyping is not used as often as it should be.
I think the reasons center on fear factors -
While losing context does happen with paper, it is generally OK to lose that for initial designs. With paper, people do see it as a more informal design and give better feedback overall.
And when you use the paper format to your advantage and let users really get creative, creating parts of the own designs on the fly, then you really get to see the benefits. You can do so many more things with paper designs - so much more than just measuring completion times and gathering opinions.
I have not read Carolyn's book yet - but I did scan it at CHI. I hope that one of her messages goes beyond Jakob's "earlier is better" article - for some design tasks, paper is just plain better than building anything with code.
This is a first in a new series for ia/ - "beat reporters" who watch an area and blog it. I volunteered to "beat Alertbox" so I will be adding my own comments to Jakob's articles.
PS I have very little association with Morgan Kaufmann - I have reviewed some proposals for them, and I eat their desserts at CHI every year, but that is all.