Why is there a hierarchy of importance?

Written by Yaron Schoen August 05, 2013

Read Now Read Later

I stumbled upon this paragraph while reading an article about Dribble today:

Design is paramount to the success of any new or developing startup. While the original idea and core functionality should always take precedence, there’s a growing demand for attractive services that offer a beautiful user experience.

I'm sure the author had great intentions, and is a really nice guy, but…

Hmmm.

Can we please stop?

Does this imply that, as a designer, my job is just to make things beautiful?

Does this imply that my job isn't as important as the person that came up with the idea or whoever is in charge of “core functionality” (what ever that is).

Wait, if “core functionality” isn’t “design”, then what is it?

Does core functionality mean making sure that the thing works purely on a technical aspect?

Why is that more important than making sure it’s easy to use?

Or better yet, usable at all...?

So it's more important to have something purely working, but super confusing to use?

How will you retain users?

Oh I see, because of the original idea!

Ah ha.

Makes sense.

Wait a second, why is there a hierarchy of importance?

Shouldn’t it be: “creating a great product is paramount to the success of any new developing startup”?

Creating a great product takes all of the disciplines combined, no?

Design, engineering, original idea, content management, customer support, sales, you name it!

One big happy family.

Where everyone is equal.

Dancing in harmony.

Designing a great product.

Okay, Yaron, stop. It was an article about Dribbble. We have to talk about the way things look. Right?

Right!?

I’m confused.


Written in New York. © 2013