The reason for that is simple: You have to develop your eye.
Let me explain. One of the first major pursuits I took up was music - playing AND writing. Ever heard the phrase "develop your ear"? Basically, the more you do it, and the more you can hear the difference between the crap coming out of your instrument or computer sequencing program (in my case) and something professional, the better you'll be at finding those subtle things that make it that much better. When I got into recording engineering, I didn't know the difference between electric guitar sounds besides "distorted" and "not distorted." After getting feedback on my early mixes ("That sounds like shit."), I can now guess amp manufacturers and guitar brands with pretty good accuracy just by listening.
Now that I'm learning to code, I've discovered that it's similar. When I started, the difference between bad complex code and good complex code was not obvious to me. After having MY code refactored by my boss/mentor, I saw the difference unfold before my very eyes. Now I get compliments for writing clever, efficient code instead of "Um... can I sit down here? I'd like to go over that with you..."
So basically, aside from practice, it's about learning what to look for. Learn to identify what's good and what's bad about any design, and eventually, with practice, your own designs will improve. You HAVE to have both components, though, or you'll be stuck in an endless loop of making stuff that is different without actually being better. (Personal experience.)
That said, go get a book on typography from the library. Make sure it's one with lots and lots of pictures, diagrams, and full pages focusing on one or two typefaces. You don't have to read it cover to cover, but get the basics.
Once you've started, identify a few friends who are either great designers or at least who really know what they're talking about. Don't show it to random people who will say "yeah I guess that's good." That means "I don't know much about design, but that doesn't offend me so I guess it's okay." That's not helpful.
Also, http://kuler.adobe.com is pretty cool for picking color schemes.
Before and after articles on redesigns of web sites and print materials are really helpful as well.
Lastly, find some computer programs (NOT web apps) that look really good and stare at them until your eyes hurt. Safari is one of my favorites - it looks great, but everything that makes it look great is incredibly subtle - The font rendering on the bookmark bar has a nearly invisible bevel, which inverts on mouseover (for instance).
EDIT: After an hour or so, I realized that parts of this came off kind of arrogant. I am not an amazing hacker or the best audio engineer - I just wanted to relate growth in those disciplines to growth in design skills as well.
And then there's just giving my mixes to people and listening when they tell me what's wrong.
1) Be Simple. 2) Be Sparse.
You don't need drop shadows, shiny buttons, gradients, rounded corners, animation, or complex imagery to make a good site. As any good musician will tell you, music is about what you do with the space in between the notes; graphic design is about what you do with the space around the content (and if your content is good, the less crap you need to put around it!)
If you use a simple layout, a very small palette of 4-8 colors, 1 font, and only a few font sizes, you'll find that your designs will improve automatically. If you lack even the basic ability to coordinate colors, use a tool (http://www.colorschemer.com/schemes/ is a good source), and never deviate from the scheme that you choose.
Remember: think Google, not Microsoft.
Good design is also about layering, which sometimes means rounded corners, gradients and complex imagery. Done right it won't distract the user from the essential functions.
Also, I recently designed an interface for a .NET application, first version was Google-ish, sparse design, content front and center, just a logo and some very basic design elements. Client HATED it, wanted shiny buttons, gradients and more "bling". Second version was designed to look exactly like an MS Office online app and the client was in love.
Just remember, most design is dictated by the client, whereas your programming functions aren't inspected by the client and you aren't forced to re-code something to add more "bling".
Pick a grid. Stick to it...no matter what. As with anything, once you master it you can deviate from the rules. But if you want to create something nice, try your best to stick to the design standards you set for yourself.
I agree. Google is a good model. It's clear that even now they don't really get design. Their rule is just to make everything simple and functional. This means that even though they never manage to do anything inspired (Google has never made anything people would compare to the iPod) they at least avoid a lot of design mistakes. You can probably get 85th percentile design merely by avoiding mistakes.
Some people have natural talent with design. If you find you aren't one of these people, just get someone else to do it. I've had great experience with crowdspring and it is very good value for money. The best part about these two sites is, you get to choose the best design and give the designers feedback for further iterations.
It's working for spec on the off-chance your designs might get chosen. THe odds are stacked against you and the competition devalues your work. It's the type of thing that is historically rampant with IP theft, abuse, underhanded tactics etc.
Designers should not be working on spec; ever, especially college educated designers. It's tempting to get these projects under your belt for the experience and the portfolio but once you go down that path, it can be hard to raise your rates up to a liveable wage when everyone else is working for free or cheap.
If you're good and can market yourself you can always find people to pay the rates you want. If you are missing one of those things you wouldn't be getting the rates you want anyhow. Your work is worth exactly what someone is willing to pay for it. If you can't find people to pay what you want then you are overvaluing your abilities.
Some day I hope to start up a bunch of huge computer labs throughout SE Asia and Africa so that kids can come in and do custom programming and graphic design, undercutting all of us Westerners. I'd rather have disadvantaged teenagers drawing little icons for $5 a hour than working as hookers to get $10 a night--even if it means that designers in the US won't be able to afford to live in downtown S.F., drinking $6 cups of coffee, and buying $5K of gadgets every year.
We'll definitely be doing more there. There's a lot of talented people doing this work for fun and/or on the side to build up their portfolio. Not sure how long this will last for these low prices, but I definitely recommend taking advantage of it while it lasts.
We paid for logo work at about the same price from an online company and got something passable, but had worries the whole time that we wouldn't get anything good at all.
In the end the 99designer winner even sent us the raw Adobe illustrator files, etc. The pro firms I saw were only sending the SVG for artwork, but the raw source is even more useful if we need to transform things down the line (and helps confirm it's an original work).
Not sure what the quality will be for website design, but the logo design side seemed to "crowdsource" amazingly well. YMMV.
Elance/Outsource your programming for less pretentious clients, it's more profitable.
It goes both ways my friend ;)
I can slice the layout in Photoshop, markup the HTML and code the CSS--so I don't have the designer do any of these things.
I have them focus on things I'm not good at--colors, typography, general look and feel, etc...
This saves some money and let's me maintain control over the code base (which I like).
While an average designer probably does make less than an average developer, often people are quick to assume design isn't important--and therefore not worth paying for.
Sure it's easy to throw a design together and make something look decent.
But to have a designer that understands color theory, spacing, typography, usability/accessability, being able to "lead your eye" along with many other important skills--you have to be willing to pay.
Just like you can get a programmer that can technically program--but has no experience, no understanding of design patterns and has barely heard of this SQL thing--but they can still program your site, and that's good enough for you.
I think it's a mistake to penny pinch when choosing a designer. It will come back to bite you in ways you don't expect.
Like causing confusion among customers, increasing your bounce rate and ultimately affecting sales.
I recently went through the process of finding a designer and had enormous success using freelance sites such as getafreelancer.com (not affiliated).
I received about 30/40 replies. While I only need 1 designer, I now have 4-7 quality designers that I can go to for quality work in the future.
The short answer: You get what you pay for. Just like in every other profession.
Well that is not what I said.
So what do you pay your freelancer designers? I highly doubt they earn 100$ per hour?
What I meant is that if you can earn 100$ as a developer, you can afford to pay a designer for 50$. If I thought that design was worthless, I would have recommended do-it-yourself design.
$100 is very reasonable for a quality designer--personally I find $75/hr to be a good rate for the type of work I'm looking for.
My whole post wasn't geared towards your comment--so I apologize if it came off that way.
Did not mean to imply this was your view.
My point was, many people assume design is the least important part of a web site.
This mind-set is flawed, because design is very important. Not the most important part--but still very important.
There is a reason some designers charge $25/hr and some charge $100/hr, and the $75 you save today may (or may not) cost you $1,000 tomorrow.
I was lucky to find some affordable designers, but I am all for giving them their money's worth. I can't design at all, so I respect good designers for their work.
Yes given time a designer can program an entire software program by keeping things simple and not getting fancy. I'm a designer and have programmed a good deal, however like designs from my programmer, you'd laugh at what I've coded.
However, I don't care. I focus on what I am good at in order to get even better. Don't try to diversify. Specialize. There is more money in it.
With respect to the topic.. good design studios get involved in a project from day one and have a tremendous impact on the outcome of the final project. It's not simply a "skin" over a technology. It's should be a critical part of your operation.
I find it bizarre that many people assume anything "artistic" requires innate talent and you either have it or you don't. Design requires constant practice and dedication to be good and ten years (or more) of experience to be truly great, just like any other discipline.
My designs from 15 years ago are laughably bad but now I can whip up some decent fairly quickly. On the other hand... I haven't programmed anything in 10 years and have a long learning curve ahead of me.
I'd recommend looking for some good designers on one of the freelance sites.. there's no shortage of choice. If you decide to go it alone, or even if you don't, I recommend picking up the book "Design Elements" by Timothy Samara. It's the best, most concise, book on the general principles of design I have yet to find. It will give you a good overview and some talking points with any designers you hire.
Good luck!
I worked with many talented designers in pre-Internet-Crash 1.0 days. They were very good at telling me where to add some whitespace - almost invisible tweaks that made great differences.
They all studied at design college. Of course in those days, their training was in print, and didn't enjoy working with the limitations of the web.
You could do some traditional artistic study?
Of course, if you just want your website to look great - hire someone. An advantage you have over someone hiring you to do programming work is that you can look at a piece of artistic design work and make a value judgement about whether it is any good.
As a web designer and user interface expert, when a client asks me for a brochure or business card design I dutifully refer them to a print expert and don't tell them "yeah I can do that" just because I can.
Being artistic is a natural talent to some degree but you don't need to be a Picasso to create effective web designs. However, you probably don't want to waste the time to become a good designer when you could be working on skills which are closer to your core expertise.
Thanks again, I have never gotten so much helpfull feedback!
I argue here that they are not for the proof of concept stages.
http://thenextweb.org/2008/05/30/the-power-of-elegance-in-de...
That's a big difference from "is a designer really necessary?"
Same argument but for programming; Do you really need a team of 20 programmers? My conclusion from that argument would not be "are programmers really necessary?" Would you hire a web designer to program your software?