A List Apart
Alex Wright
Antenna
blackbeltjones
bLoug
Brad Lauster
Brightly Colored Food
CamWorld
City of Sound
Croc o' Lyle
Curious Lee
Designweenie
DesignWritings
Digital Web Magazine
Dive Into Mark
DonnaM
Elegant Hack
Holovaty
Guide to ease
Heyotwell
IA Wiki
InfoDesign
Joel on Software
Kaliber10000
KM Pings
kottke
memekitchen
Meryl's Notes
Lucdesk
NetDiver
Noise Between Stations
Off the top
Other Blog
pixelcharmer
peterme
Rogue Librarian
Semantic Studios
Shifted Librarian
Signal vs. Noise
squaresines
Suppose
sylloge
v-2
webgraphics
WebWord
xBlog
Zeldman Presents
Reduce Redundancy: Decrease Duplicated Design Decisions
Hmmm. I'm not so sure about this one. His first example talks about footnotes and endnotes in Microsoft Word and how there are too many options. I agree that there are a lot of features and it can be confusing to some people, but I don't understand how it relates to the topic. This feature is presented in one way; there is one way to get to this dialogue box, and the features that are available are indeed necessary. (I know many professors and academic journals are very specific about how they would like their footnotes and endnotes to be presented.)Summary: User interface complexity increases when a single feature or hypertext link is presented in multiple ways. Users rarely understand duplicates as such, and often waste time repeating efforts or visiting the same page twice by mistake.
Now, I could be wrong, but I thought redundancy is good. To copy text, for example, you highlight it and then can go to Edit --> Copy, or right-click (or option-click) and select Copy, or Control-C (or Apple-C). Yes, in a way, the complexity increases for programmers because you have multiple ways to perform the same task, but for the user, this redundancy is easier. Some people like using keyboard commands, some like right-clicking, and some use the menu bar for everything.
He does say that “one of the few cases where users actually benefit from a small amount of redundancy is in the navigational paths through an information architecture,” but then adds, “too many cross-references will create an overly complex interface and prevent users from understanding where they are and what options they have at that location.” How many is too many? Is an interface with lots of cross-references — like Flamenco or Wine.com — bad or effective?