Immediate opening for a Flash Prototyper in NYC

We have the immediate need for a Flash Prototyper here in midtown Manhattan. You will be onsite and working with me everyday… and you even get paid well, ;) Email me your resume with lots of amazing flash interfaces that you have built.

(Reader question) Why do you dislike design patterns so much?

I’ve been so busy at Bloomberg I haven’t had the chance to write anything new, even though I have a few things cooking already. I got this email from a reader and asked her permission to post. Enjoy.

Jocelyn writes

Hello,
I’ve been reading your articles about OCGM and found them quite interesting, thanks for sharing your thoughts. I was intrigued by your statement, saying that you were

“not a fan of UI DESIGN PATTERNS”.

“When designers could and should be thinking outside of the typical experience, they rely on a “crutch” called a UI pattern.” Say you are to implement a login feature to your application/site, couldn’t you rely, at least partially, on what’s already been done ? And so on for search, breadcrumbs etc.

“Those patterns were developed by City Engineers because there were only so many different ways you can put 3 buildings on a city block.”

Are there many more possible solutions in HCI? Isn’t one of those solutions better than the other (id “the pattern for this problem”) ?

In my opinions design patterns are like having an HCI expert team at your side (don’t remember where I read that). You are not compelled to use them everytime, but it’s nice having them for some tasks.

I’m genuinely interested in hearing your opinion on the matter. I hope my bad English doesn’t sound angry, I assure you that’s not the feeling.

Regards,

Jocelyn

Ron writes…

The problem with patterns are they do not exercise the mind or further the experience. Having a book of patterns at your side is very unlike having an HCI Expert on your team, because those are just cookie cutter solutions. HCI is not math. There is not one simple solution to every problem. My main point is to reach further than what has been seen so far. Just because its the most popular, or most successful at the time, does not mean its correct.

The primary difference between math and HCI is that HCI contains people, and people change in expectations, considerations, and needs, among other things.

Design patterns will never substitute a person that has been trained in the field and is willing to challenge the norm to find something unique and innovative. Design patterns are the antithesis of innovation.

If it’s ok with you, I would like to post this on my blog with my answer. Ive been meaning to write something new. :)

Jocelyn writes…

“The problem with patterns are they do not exercise the mind or further the experience.”

This is a very valid concern.

“Just because its the most popular, or most successful at the time, does not mean its correct.”

So very true (isn’t it even called “the Smashing Magazine Effect”?).

Yet I cannot help but notice that conventions people are used to, physiological stability of the user, recurrence of problems (again, a login form) make for a quite repeteable set of constraints, thus theremust be some repeatable solutions, be it patterns or another artifact.

You say that patterns are numbing creativity. After reading your answer, I agree, but partially : pattern overuse (eg relying on others work to solve every problem) is nefarious. But it doesn’t mean you shouldn’t have a look at whats currently the best practice ; you cannot push the enveloppe on every component on a given project. Or maybe sometimes you just have to get it done for yesterday. Or you need an overview of available solutions before diving in. Or you need to share knowledge. In those case, patterns are well suited (imho).

After a bit of pondering on your message, I’ll keep that: there’s a place and time to use patterns, it’s not a solution ex machina. But it doesn’t mean knowledge reuse is never appropriate. What’s your opinion? Is there any form of reuse that fits you better, or do you take them all for dumbing practices?

In any case, thank you very much for taking the time to answer, it is much appreciated. It’s totally ok to post the whole thing as you wish. Last of all and on a totally unrelated matter : would you recommend any resource pertaining to touch/multi-touch interfaces (I’m talking rugged tablet PC rather than iPad)? Thanks in advance!

Regards,
Jocelyn.

Thanks so much for writing in Jocelyn!

Goodbye Microsoft (sorta) and Hello *********

Well it’s been a chaotic few weeks here in wonderful Microsoft Land. I have been getting tons of questions about some things I said at CHI. Apparently, unknown to me, a few people overheard me talking to some SOFTie colleagues and telling them that I was planning an external move soon. What that means is I was planning on getting another job, but not at Microsoft.

ProTip: A “move” just means you are shifting teams, an “external move” means I was going back into the world. Its rare that a Microsoftie goes back out into the world. It really is an incredible place to work.

Here is a small “guide” to Ron.

  1. I have Asperger’s Syndrome. It is clinically significant, but not so much that I freak out or am crazy awkward in public situations. I consider it an amazing gift to be honest. There are a few things about the “syndrome” that really come out in me. I am very honest and upfront, and I am incredibly gifted in some things (mainly design and using logic to break down and solve problems) and am very bad at other things (remembering dates, balancing a checkbook, etc).
  2. I am obsessive about finding solutions to problems. (see #1) The more difficult the problem, the more obsessive I get. The real challenge to this is that in design, you rarely find a “solution” rather than finding a better than what you have now option. That does suffice for me, but usually I will obsess about a problem until I make a giant leap in the space. Good enough isn’t enough.
  3. I LOVE a good challenge. These are what make me get up in the morning and clap my hands.
  4. When it comes to work, I rarely choose the “easy” route. Which means if I have the choice between a difficult job and an easy job, with both being the same amount of money… I always choose the difficult job because it will cause me to grow.

So where does that leave us? Well, I’m trying to lead up to where I am going to next. My last day at Microsoft was Friday and I am busy preparing to move across the country.

So what is my next challenge? I think it is the most complex problem in the User Experience world at the present time and just thinking about it gets my brain pumping.

Bloomberg.

The article at UX Mag.

This interface is complex, rich, and mind-blowing in size and scope. I think this article really sums up a few of the problems, but also makes some wrong assertions as well.

http://uxmag.com/design/the-impossible-bloomberg-makeover

I think the best line in the article is this,

“Redesigning the Bloomberg Terminal would be any interface designer’s dream.”

You are correct, and if I have said it once, I’ll say it again… I am living the dream. See you in New York!

Further Reading:

Wikipedia Article

Google image search of examples of the terminal.

An interesting visual history/lineup of past terminals on display at Bloomberg

An example of a typical Terminal in use

Looking for a Senior User Experience Designer (contract)

Currently looking for a full-time/on-site Senior Interaction Designer to work at Microsoft. You will be working on a product team on a new product offering going into the Office Suite. Your impact could be substantial, to say the least. The product is a Silverlight Product, so your knowledge of Silverlight should be high, including capabilities, application experience, and pushing the limits.

  • Silverlight application experience (not marketing)
  • Interaction design experience in Microsoft Expression Blend
  • Rapid prototyping
  • Knowledge of Server UI and Design Patterns
  • Help bridge gap between Win32 UI and Silverlight capabilities
Strong User Experience Background. The ability to make rationale judgement calls based on sound principles and the ability to advocate those decisions to other stakeholders and product owners when challenged.
The challenge to this role is also having a strong technical background. The ability to discuss with developers and program managers, the ability to write, edit, and possibly own specs.
The need is immediate and the first step would be to send me a Resume and Portfolio. The next step would be to schedule an  interview with you, here at Microsoft.
Page 1 of 912345...Last »