I really like my job, but there’s one aspect that’s starting to getting me worked up. I’m the UI guy at work. I didn’t start that way, though. I moved into the position because I’ve grown tired of super heavy technical work (the honeymoon is over), and I’m moving myself to tasks that I enjoy more as well as find engaging while learning to improve myself. If I wasn’t doing this at work, I’d still be reading up and learning about it anyway.
The problem is that no one really sees me that way (or the key people have yet to fully acknowledge it), and I keep hearing about how the guys before me, who still work for the company, should have a look at what I’ve designed and critique it. No, even worse, design a piece within what’s already been started, without any knowledge of what’s been done, why it’s been done, where it’s all going, or what the application as a whole really does even from a business perspective (let alone a design perspective). AND! they aren’t actual designers on top of it.
This is definitely an angst post that’s built up a little over time. I still need to work on how others perceive me, and I have to change how that is from how it was. Never an easy task, but in the meantime, I get the group think problem.
The art critique is rarely an event that’s enjoyed by those being critiqued, especially in college sessions where the art professor doesn’t go easy on freshmen. However, at work, it becomes the group think that we all know and hate. Committees that turn out crap.
The meetings my company have are generally above average. We make good progress, and solve problems that take more than one person’s limited base of knowledge. On average, we’re not performing group think, and we do a good job at this outside of design. Design, however, never really had a champion. Someone to lead the way. I’ve finally picked up the reins, and I’m not about to let group think ruin the small progress I’m making at turning our decade old, flagship application, into a modern, slick-yet-comfortable tool.
Design is one of those areas you just can’t have a teams of people contributing. You have to have an executioner, a king, a monarch who calls the shots. You still have to remain open to ideas, and accept the critique for what it’s worth. I find more often, when dealing with non-designers, you really have to work at digging deeper to understand the underlying problem they’re incorrectly trying to solve through design terms.
People want to speak your language, and because art and design are so accessible to all, everyone thinks they’ve got a clue. But they don’t. They don’t know how to convey meaning through contrast and texture, typography and spacing. I certainly don’t think I’m perfect, but I’ve set a path, and I’m not about to let others change that path.
So, I’ll endure the near useless “design critique.” I know it will be useless, but the boss will still think the others A) have any time to actually do work on this product, and B) have any clue what they’re doing. They won’t speak up about what I’ve done with anything of value because they lack both basic design knowledge, specific business knowledge, and they lack the time to process anything from an outside point of view to say anything of meaning.
Yes, they know how to write HTML and CSS, and not enough of Java to be a real coder, but that doesn’t make a designer. So, I’ll cut the heads of any ideas that aren’t appropriate, and define myself in the new role I’m playing. They don’t realize they’re invading my territory, so I’ll be nice, but as time passes, I can’t let their group think hold me back from taking part in the art critique that should really happen. Since this is currently in house dev work (clients on the horizon the in next few months), my coworkers are my clients, so I must treat them similarly. But, as I don’t let clients bowl me over, I can’t give coworkers the easy out for being familiar to me. They’ll be happier in the end that I didn’t sacrifice the application for ideas they half thought through and half considered a valid idea.