Like David Danielson did in the paper Victor referenced, the best bet is to test the headers with users, in as quantitatively representative a manner as is feasible for your team.
If there's no budget / time / interest in researching this topic with users, then it's a question of the relative weight you would assign to the factors you listed above: branding, consistent context, convenience of quick access points, and the relative quantity of useful content that fits above the fold. I wasn't able to access the link you provided (forbidden) so I wasn't able to get a feeling for your goals, audience, content, etc. So, in general I'd say that if the header is providing useful context about the information hierarchy and is surfacing often used links and functionality, then it makes sense to keep it for all applicable pages. If it only serves as a branding tool, then a visually consistent but less obtrusive brand voice would probably have more impact. /pb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=45003 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
