Visual design will not fix your broken business
micrypt.com
micrypt.com
As a designer, I get tons of requests to work with startups only to later find out that they want an aesthetic layer slapped on top. Is this possible? Certainly. But it doesn't address major problems with your experience, content structure, or the most important thing: the message you're trying to convey.
The thing missing in this article is that, for a good designer, it's quite the thinking man's game. For example, I'm working on a design now where the original menu system wasn't 100% clear and by trying a couple of different approaches, we came to something great. This is key: hire someone who thinks about the problems, not the aesthetics. A solid designer will address the problems and then devise an aesthetic strategy.
Most importantly: show respect for designers. The good ones can help you immensely.
What type of startup? Is it a native app-focused endeavor or will it be browser-based? What if it requires NO developers and can run on some out of the box solution or SaaS/PaaS? What if you use Twitter bootstrap and outsource/contract your minimal design needs??
There is no secret sauce, people -- success is a highly-variable mix of hard work and luck. Period. You could do everything right and still fail. And vice versa. Just look around a your local brick and mortars. How many establishments have been making a go of it for years, even decades, with subpar products and services?
This has been, is, and will be the case for every type of business for a long time.
Get over yourself, get out there, and fucking do it anyway.
Conversely, a bad design on a good product can hinder a project in the long run.
Designers are an important part of the mix, but you'd be a fool to concentrate on design alone. In my own experience, we successfully bootstrapped a startup with no designer, winging it based on user feedback and our own intuition. But when we got funding, the first person we hired was a designer - and the popularity of the product rose accordingly.
See how silly that sounds when you turn it around? Author seems to think that all it takes it a couple of books a bit of practice to become competent at design.
Sadly typical for engineers to hand-wave everything that isn't engineering away as a job easy enough for monkeys.
It's almost like saying "Buy a bunch of books, learn Autocad and you'll be an architect in no time"
A designer who reads a couple books about programming is somewhat less likely to generate a lot of value for customers than a developer who reads a couple books about design. Success or failure in many (maybe most?) markets is much more sensitive to engineering talent than design talent.
"success...is much more sensitive to engineering talent" - again, is that a fact? what is that assertion based on?
Part of it is long-term experience. My field is dominated by products that sell to businesses; they have universally terrible UIs, many of which wouldn't have passed muster in 1999.
Part of it is direct, current, ongoing experience: we sell security engineering services to application providers, and so my working weeks consist of looking at other people's applications --- in fact, of looking at successful applications, because nobody spends 5 figures on security assessment if their app isn't doing well. Most of the applications we see look worse and are less useable than Themeforest templates.
Part of it is friends, who have launched products on templates instead of professional designs, who have done fine and not observed any objection to their application's lack of a vertical baseline typographic grid or the correct noise texture in the background or the color-theoretic implications of their button colors. Again: launched on templates, did fine.
HN overvalues design expertise. For most of the businesses started by people on HN, from weather tracking to fraud prediction to appointment reminding to credit card processing, a unique design tailored to the company's exact business is not a real requirement. In many cases, custom designs are mostly about vanity.
I'm not bagging on designers. My sense is that for the subset of designers who are actually both talented and competent consultants, there is too much work, not too little. I admire and can geek out about graphic design and UX. I wish designers the best.
But: design is one of those things that keeps people from shipping their apps, or sometimes even from starting on it. The belief that a poorly designed rev1 app will destroy the prospects of a new business has harmed more startups than inadequate design ever will. Unrealistic and frankly pointless expectations about bespoke design are a mental obstacle to getting shit done. So I think it's worth pointing out how overvalued design is, repeatedly and at length.
Visual aesthetics is about optimizing not about fundamentally solving business problems.
Of course you need something that is not completely impossible to look at but obviously the world is filled with less than pleasing visual solutions on very successful businesses.
If you are dealing with designers as customers you obviously need to prioritize the visual aspect. And visual design can be used in saturated markets to become the preffered choice but it can also work against you.
All businesses must figure out to what extent design is important for their success not just assume that it will help.
Designing the actual interface/service/functionality/product is a different problem all together.
Knowing how a colour wheel works doesn't solve problems like a custom-designed, ticked-out über-awesome CSS -based drop-down list that doesn't respond to keypresses.
Knowing when to use search, and when to use tags, or how to group search results in a way that makes sense to the use context is worth paying a lot more for than just coming up with a cool UI concept.
TLDR - this blog post is bang on the bucks.
The only point I am trying to make is that there are many many great webdesigners out there that can make beautiful websites that communicate well. But it it's often the same guys that design something like an interface or a mobile app.
The creative agency world is filled with people able to do artistically stunning websites but they are approaching it from a communication/advertising point of view where you might be exposed to the site once or twice. This is very different than doing something like say hipmunk.
A more useful topic would have been that design alone will not guarantee the success of your business.
The reality of the matter is that both design and engineering are critical aspects of your business in different ways.
Design IS important. Like it or not, the design of your website and your product screen-caps are the first thing any potential customer is going to see. A well designed brand does influence buying decisions, that's a fact.
Furthermore, users don't care about how well your code is written. The only contact they have with your code is through your UI. If the experience is not well designed, you're not really doing your job. Everything else being equal, a consumer is always going to choose software that is pleasant to use over software that is merely "functional".
That being said, once you entice users to try your product, the engineering better be solid.
So there you go, two important skills- both of which add to the value that you're (hopefully) offering to your customers.
Engineers are, in general, bad at two things:
- Designing a product that people want to use. By this I mean focusing the idea, cutting off the extra bits, refining the workflow, making it simple enough for people to understand, pivoting it slightly to solve a different need, and designing the basic methods of interaction.
- Making it look pretty.
"Designer" could mean either (or both! or neither!) of these tasks. The first is what a co-founder should be. The second is someone you hire.
Industrial design always matters, but your startup doesn't need a Dreyfuss or a Loewy.
A period where they did lose their elegance was when Jobs was in exile, they started looking like pretty ordinary (though still decent) PC systems.
>> Esslinger convinced Jobs that zero-draft tooling was essential. As well as gaining a subtle but powerful precision to the shape of Apple's cases, it decreased their actual size. A zero-draft enclosure could fit more tightly around the components within, and, despite the tooling expense, the resulting decrease in plastic could eventually decrease costs. Moreover, zero-draft molding, being an unusual, complex and expensive technology, helped prevent a growing problem for Apple: unauthorized clones.
It was the same beige as everything else and had the same square corners. It was aesthetically equivalent to a C64 or a PET 16 or any one of a large number of name brands.
That's not to say it wasn't sound industrial design, only that it's aesthetics didn't differentiate it in the way the first iMac's aesthetics differentiated it.
Design, like coding, takes absolute determination and vigilance in perfecting. It not something you just 'learn to do' over a night or even a few months. The quote by Dieter (a design hero of mine) was also taken out of context. Everyone in the company needs to be adept in their role, and have a bit of say as to how the product should be. He didn't say you only need engineers who can read design books.
So how about you focus on doing what you do best, and let the designers continue focusing on what they do best. Perhaps start a company with 3 instead of two. A designer, an engineer, and a business minded individual. Imagine that.
These articles are written in a situation where the balance is not right and depending on the situation, the author recommends the other side.
I am in a situation where the design is too much in lead and technical aspects are forgotten. The psd's are often all worked out in detail without considering if it is technically possible or there are far more better approaches to solve the problems then in the visual designs. Also the visual designs are inconsistent and cause confusion because there is not a idea how it really should work.
But this doesn't mean I'll have to preach that development is more important. The right balance needs to be found. But this advice is to nuanced to get any attention.
The problem here is that 6 or 8 years ago, building a basic product was a lot harder than it is today. I'm a designer and I used to spend a huge amount of time coding a product I wanted to build and less time designing it. Back then the differentiator was essentially launching a product.
These days you can get hold of a decent framework that does most of what you need so the rest of the time can be spent on design (or whatever else is important to you). As a result, launching a product is no longer impressive and good styling / usability are important differentiators.
Out-of-the-box software is getting so good / complete that products need to look elsewhere to stand out.
The entire purpose of a startup is to redesign some aspect of the user's life. A startup takes some experience in the world that has low usability, and makes that aspect of your life more usable. Having a founder with a design background, meaning someone who actually understands usability and how to simplify experiences CAN fix your broken business, assuming that the purpose of your business is to simplify some experience and make it more usable, which is what pretty much all businesses are. Additionally, the UI is not "just pixels" any more than a song is just "a C and a D chord" or a table is "just wood". The interface is the means through which the user problem is solved. From the user's perspective, the interface is the app -- the entirety of the app -- nothing other than the interface exists. And the user's perspective is the only one that matters.
Now, does this mean you can have a founding team without a developer? No, of course not. You need a technical founder. You should have a designer, a developer, and a hustler/biz person, but those don't need to be three separate people; one person can embody several of those qualities.
This is not exactly what you're looking for, but here are two studies concerned with the aesthetic-usability effect. The summary is that aesthetically-pleasing interfaces are judged by users to be easier to use, regardless of their actual usability.
"Apparent Usability vs. Inherent Usability Experimental analysis on the determinants of the apparent usability" - CHI '95 Proceedings - http://www.sigchi.org/chi95/proceedings/shortppr/mk_bdy.htm
"Aesthetics and Apparent Usability: Empirically Assessing Cultural and Methodological Issues" - CHI '97 Proceedings - http://www.sigchi.org/chi97/proceedings/paper/nt.htm
You could also test this yourself on your own software with an A/B test. Use two designs with the same feature set. Use a plain interface for one and a nice interface on the other. Whichever one brings better results according to your business needs is the one you should use.
Personally, I believe context is just as important as beauty in design. If an interface is plain but helps me get the job done faster because my brain is able to concentrate better, I would consider that better design.
But in general, given two designs of equal features, I prefer the one that looks better, however that is defined. I'm not a social psychologist, but one would probably tell you most people have the same preference.
In the second study listed above, the reference section lists this 1980 study: "Defendant's Attractiveness as a Factor in the Outcome of Criminal Trials". Search the web for an abstract. As you might guess from the title, the study found "the more attractive the defendant, the less severe the sentence imposed."
Universal Principle Design calls this "aesthetic-usability" effect.
This is essentially what the article boils down to and I think the fear is unfounded. Even the greenest wantrepreneur realizes that you need an engineer to build their awesome idea. The fact that some might focus on designer as well is just one of a million suboptimal decisions a founder might make.
At the end of the day, it's just like everything else in early-stage life: you need to make the most of the resources you have. If you can get an amazing designer on board then by all means go for it, if not grab a copy of bootstrap, try to develop a modicum of taste and take a look at archive.org to remind yourself that successful startups that had bangin visuals off the gate are the exception not the rule.
There are plenty of designer who can design beautifully illustrated landing pages but that can't design a product to save their lives.
If treated without some sort of caution all you will increase the risk of producing beautiful products that don't work.
Updating for security or real bug fixes is one thing. Running the treadmill of always trying to have the "latest and greatest" of everything wastes a lot of time.
With that said, I agree that if the core product isn't well engineered then no amount of lipstick on the pig is going to make it usable. You can paint rust any color you like but it's still rust.
Not that I think design should be ignored, but sadly some of the giants have ignored it and done remarkably well regardless.
In 1997, Yahoo offered real value (it made sense of the Web). Even in the early 2000s, ditto. The problem with the real value proposition is that if someone succeeds in providing realer value, so to speak, you're sunk.
CL is a very interesting exceptional case. I'll note that they've had a designer position open recently.
However it really depends on WHAT your product is, before you decide on how important the designers role will be.
Is this article focused on in-house/high end designer partner VS hiring a designer? Or is the other option sourcing to a design firm/agency?
"Good execution will not fix your broken business".
If you are solving the wrong problem, targeting the wrong market or building the wrong product, good execution will not save your business. Both the strategy ('what') and the execution ('how') have to be right for the business to succeed.
People loved it. Today, the design is unchanged, but the engineering has been entirely redone.
Good design can buy you time.
- Nobody cares how anything looks - any two things that are functionally equivalent are guaranteed to have equivalent conversions
- Looks have no impact on usability - anything that is functionally equivalent is guaranteed to be equally usable
- Usability does not translate to users - no correlation with whether a user has a preference for some look and feel with the number of such users you will get
In short, if visual design has no correlation with any part of the business, and, notably, people are as likely to pay, and will pay the same amount, for any two things that are functionally equivalent, then I can guarantee you that visual design will not fix anyone's broken business. If any of the above are not true - well, all bets are off.
Basically, I'm saying "it just might."
Only a fool would pretend to be blissfully unaware of what he's talking about and then offer you advice on the very subject of his ignorance.
Let me clarify this for those not in the know:
Unless you're in the business of selling design services, under no circumstances should you ever hire a full-time staff designer, never mind considering them for an equity-sharing position at the outset of your enterprise.
If one doesn't know what should and shouldn't be hired for in the early stage startup, one shouldn't be wasting their time pontificating about it. OP is a moron.