Why I Get Paid II

I get paid to prevent what happened for most of you looking at the below web site.

1. You saw the picture.
2. Your eye didn't come to rest easily (other than possibly on the picture).

Though I don't know a lot about this site, I know I won't be going back. Why? It's not the writing. Honestly I didn't really read anything. So why? *BECAUSE* I didn't really read anything. I never found the focus, the main point for being there. I'm sure I wasn't alone.

The picture is a useless construct unless it's a celebrity and there's an associated story (for the most part). I personally have no idea what the headline was associated with the picture.

Web sites need to be designed so that you can easily identify your purpose for being there - and perform that purpose. This site isn't. It's a bad design. And that's the reason why I get paid - so that your site won't look like this one.

Class dismissed.

Why I Get Paid

Nope. This isn't going to be a long rant. I'm not providing a tutorial. Just a picture. And a question. (yes, I purposely used a period and I capitalized And at the beginning of a sentence).

First, the picture. (best if you view it full size)


Now the question (2 really)
1. Where did your eye rest? (or did it?)
2. If it did come to rest, where did it?

Thank you very much. Class dismissed.

The Corporate Process

I'm working a new gig right now (ok, new since the end of November) and it is a bit different than anything else that I've worked on.

I'm in at a large financial services company, which is really cool actually, because I love the industry, stocks, trading, everything. Of course, I get to do none of that. What I'm there for is to be an Information Architect. What I work on is how one of the company's institutional products looks and feels. Some of the stuff is pretty stodgy, but it is in process. I'm responsible for working on new designs, envisioning future designs and shepherding a team of designers (visual design, prototypers, usability experts, editorial, accessibility) through the process of getting a great design that allows the user to get what they want, when they want it quickly, easily and intuitively. If you think it sounds easy - you may or may not be right. For me, it is pretty "easy" but it's because of several reasons. It's actually not easy - and if you don't believe me, sit down with a visual designer (graphics guy) and a usability expert and see if you can get them to agree on something. And, then once I've got the design team to agree, we then have to sell the design (essentially) to the systems team (the developers}, providing of course we can get the business partners to agree on what we're doing too. Yes, if you're thinking that it sounds like it can be a three ring circus at times, you're right.

The worst of this is that during many of the meetings I can have ten people in the room - all with different opinions. Any change that we're attempting to make comes under brutal scrutiny because it all has to be signed off on by the business (which has one objective), systems (which has several other objectives) and the designers (who have five different opinions). Oh yes, then we have to run things by legal. So, there are lots of times when I'm in a meeting when we can burn up an hour just discussing the placement of a label, the name of a label. Yes, ONE.

Part of that reason is because the company is so huge and all of its systems seem to interact. Therefore, anything we change needs to pass muster across almost all systems. It needs to be consistent across several different style guides (one company, several brands that are all a theme of the primary company brand), it needs to be language that is meaningful not only for my product, but several others as well.

The result? I spend much of my day dissecting and analyzing pocket lint.