Meanwhile, other people will somehow manage to create value, ostensibly the goal of both bloggers, without writing confrontational screeds, perhaps even writing insightful blog posts intended to inspire and challenge rather than stir up conflict.
Maybe it's writing polemics that is horseshit.
It's pretty specific and clear: it argues that plenty of startups are successful with virtually no design at all, with interfaces as clunky as "clients call us on the phone" or "emailing spreadsheets back and forth". It implicitly argues, "early stage startups are continuously faced with a choice of spending energy on design† or on customer discovery", and "early stage startups should virtually always opt for customer discovery".
I can see how a reasonable person might disagree with that.
I don't see how a reasonable person could say that the question isn't a reasonable one to pose.
† Admittedly a synecdoche for lots of other things, like scalability, code quality, test coverage, &c
Android vs. iPhone. Devs vs. Designers. Tech founders vs. Non-tech founders. MBAs vs. CS. Instead of just arguing the merits of whatever point one has, it's become all too common to just lob ad hominem insults, call each other self-indulgent assholes, declare each others' views to be "horseshit", etc etc. It's grandiose posteuring and "witty" jabs disguised under a thin veneer of "legitimate discussion". It's like watching a pro wrestling match.
This is what I enjoy least about the startup community - and it certainly and obviously isn't contained to just HN. There's so much venom being spewed around for no good reason whatsoever. All of this mud-slinging is about as mature and informative as Kim Kardashian on TV.
It's like we can't communicate an opinion or belief without wrapping our entire egos into and making a spectacle out of it. Shit, I think I'd rather watch reality TV - they're about as nasty to each other as we are, but at least there's the off chance of ladies mud-wrestling.
But most of the post is spent venting against a perceived popular bias in favor of visual designers over "real value creators." The problem with that is that everyone who contributes to a product or service can create value—a particular startup may not need design early on, or it may not need developers early on, but it depends on the market it's tackling. The wrong omissions can spell disaster; the right omissions can spell success.
Design is not graphical embellishment. Design is decision making of appearance and functionality.
It ignores the special nature of the customer.
To talk about these successful startups, or design in general, as if there is one true answer is like talking about price. You can't have price without value, you can't have value without the exact customer in mind, so gabbling on about it in the abstract is an utter waste of time.
SOME customers are totally insensitive to good user interface, good flow, good product education, etc. They don't care if there are features which are pleasantly surprising. They don't care if they have to wade through poorly laid out, confusing forms, or configure things when smart assumptions could be made for them instead, etc., etc., etc. They are so desperate, or otherwise so used to using crap, that they just don't care. These people are also insensitive to visual design.
And ALL those things distinctly fall under "design."
MOST customers do not act like that. They crave software which is a pleasure to use, that anticipates their needs and provides them with things they never would have thought to ask for but later cannot live without, software that saves them massive amounts of time, software which prevents or eliminates anxiety & stress, software that doesn't make them do shit work, etc.
Software, in other words, which is well-designed.
The visual styling on top is a bonus -- these customers like pretty things -- but as long as it's not butt ugly, software with all those other features will do well with the majority of potential customers.
If it's pretty, the effect is multiplied. Some customers don't care or even actively dislike attractive things, but they are not the majority.
Whether or not total crap design will work for you wholly depends on who you're trying to get to give you money.
This is just a topic that bugged me.
Why the flamebait?
Maybe it's posting on HN that is horseshit.
> Design enhances value, it does not create it. Stop creating shitty startups that look amazing.
> It is to a massive degree much, much easier to spend a week pushing pixels to create something beautiful
> If there’s one thing you can rely on everyone having an opinion on, it’s how something should look.
(my emphasis)
The author's conniption would appear to be around graphic design. Graphic design is a subset of design, and covers nothing close to the full scope of what goes into the design of a new product. Design is about how things work and, often, what feelings they evoke in the process. How they look can be a part of that, but it needn't always be.
For example: how delightful is it to work with a great API? Something straightforward, well-documented, but nonetheless powerful? It's such a joy. But it requires effort: planning, understanding, experimentation, adjustment, refining, etc. In a word, design.
As a test, consider the following:
Is it first engine design or is it engine making? Airframe design or airframe building? Circuit design or circuit assembly? You can't make the engine until someone designs it first. How it looks doesn't much matter – how it works is non-negotiably essential.
Something that works well is said to be well-designed. Something that merely looks nice can be pretty – and terribly designed.
So a startup can't have something be both shitty and well-designed at the same time.
The notion that design is a differentiating characteristic for startups comes from the fact that many incumbent products simply do not work well. By designing a product that addresses a given workflow faster, with greater convenience, with greater fun, you're making something that works better.
We're past the point where you can build technology that fits requirements and stop there. Everyone else has done that already. Now success comes in making things that are satisfying, not obnoxious, that are easily learned, that make users excited to show their friends.
tl;dr: Someone doesn't grasp the difference between design and making nice graphics, throws a tantrum of a non-sequitur.
In any case, what you go to say hardly contradicts what the author is saying ... except if you redefine what he's saying as being about you think "design" ought mean instead of how he's clearly using it.
Words mean things.
If I cry out, at the top of my lungs, that "Pizza is fucking bullshit!", then go on to say that I hate how pizza kills people, tears countries apart, and delivers atrocities, people will narrow their eyes and say "Actually, I think you're thinking of war." And then they're going to be a little weirded out that I said something so simultaneously bizarre and incorrect just to get their attention.
The thing is, when someone says "design is a differentiator," they're not really talking about how it looks, either. Because appearance is very rarely a lasting means of differentiation.
My criticism is not that he's using the word wrong. It's that he's invested a lot of flaming in the process of misunderstanding people who aren't.
Don't believe me? Name me one design award that awards aesthetics alone. You won't find one, unless you're looking for an arts medal (edit: even graphics design awards have some sort of form and function criteria).
Who cares 1) how well something looks, and 2) how usable something is, if that thing provides no value to him?
Had you merely disagreed with his terminology, and left at that - it would be more forgivable. But you're trying to use it to discount what he said by deliberately misreading it, and thereby you're not actually addressing his argument.
I, for example, think this has nothing to do with "pet peeves" or deliberate misunderstandings. I think that the broader discussion of the role of design is very important and powerful, and calling design "bullshit" is a profoundly ignorant position to take. I think that building a cute little straw man and then burning him adds very little of the vaunted value the author has described.
One of the beauties of thoughts is that you get to have yours and I get to have mine. The meta stuff, here, eh, not so useful.
True, but this definition is a bit vague. Even if we think that this is not vague, then people with graphics design background should stop calling themselves designers, and engineers (who have years of training on some aspect of how some things should work) could call themselves designers. There will always be a debate on what exactly 'design' is, and who exactly a 'designer' is, because this is a bit artifical terminology in my opinion. (Long years ago, when engineers created mostly buildings engineers were also meant to be designers.)
I am an engineer/programmer, but I would feel extremely sad, uncreative, and a worthless biorobot if I could not see myself a 'designer' if we take the meaning of design very broadly.
Graphic design essentially concerns itself with how information is presented and consumed. This information can be presented in many different ways; ink on paper as an example or pixels on a screen. Part of the designers job is to solve the problem of how best to present the information, which may take the form of a call to action on a website or a tear-off in a magazine or what weight and style the fonts should be right down to the basic structure of the arrangements of elements on the screen/page/advertising hoarding. I know that most people think of this as a trivial task, but it isn't. It is the fundamental difference between good and great.
Engineers are designers, if one ever tells you otherwise, they don't have an understanding of what it is that they do.
Fun question - is emacs well designed ? What would a reviewer on engadget etc say if they came across it. Would they concede it has a better design than say - Textmate?
When Apple fans talk about the product being well designed its inevitably about the physical manifestation of the product - how it looks, what its battery life is, its weight etc. I fully concede that apple products are well designed in their own right and have a fantastical attention to detail, but the only details that get covered in the press and by evangelists are the ones that have to do with cosmetics or physical attributes.
Lastly - someone on this thread mentioned craigslist as having bad design. I think that is the classic example of equating cosmetics with design. I have yet to find another website that allows me to finish the task at hand with as little fuss and as few clicks. There are flaws to craigslist - like their ability to curate content in realtime - but their design to me is unobtrusive and efficient.
Along with terms like "It's really easy to use". The physical manifestation of any product, be it a torch, a pizza or a web based app, is part of it's design, as is the why and how of it's workings.
I just looked at the Designer Fund thing for a second, but I noticed a headshot of Luke Wroblewski on there. He co-founded the IxDA, wrote the books Mobile First and Web Form Design (both awesome), and then was co-founder and chief product officer at Bagcheck (that got acquired by Twitter). He's creating value as far as I'm concerned.
You are too quick to close this big door here. You could do them relatively "ugly" and "difficult to use" if you'd do a driverless cars, a plane with real beds, a self-backuped unlimited size hard-drive for music and movies, a viable water desalinisator, a cheap enough 3D printer, a bodyless computer monitor, or even a working dating site.
Not that I disagree with the rest, but let's not say everything is done already and just needs to be done better.
Really? Because it seems damn logical to me.
"""The author's conniption would appear to be around graphic design. Graphic design is a subset of design, and covers nothing close to the full scope of what goes into the design of a new product. Design is about how things work and, often, what feelings they evoke in the process. How they look can be a part of that, but it needn't always be."""
Yeah. Only in web design it almost always are. And in the specific "over-designed" startup web services he rants about it always is. We all heard the quote "design is how it works" from Jobs et co. But:
1) In most cases it's 80% graphic design and 20% though of how it works. 2) How it works still means nothing, if WHAT IT DOES does not add value.
Customers don't care how "well designed" (graphically AND in "how it works") a service is, if that service does nothing useful for them.
Example: a well designed and totally usable "social something" site -- and why would I want to use that if no one of my friends is using it?
tl;dr: both how it looks and how it works are secondary to what if offers the customer
This is a good point; the value proposition is independent of design. And in fact if the value proposition is strong enough than people will fight through terrible design as long as it minimally works. However for most products the value is either middling or else obscured by novelty (often the case with new tech), and this is where bad design can sink a viable product by frustrating too many people, or great design can flip the viral coefficient to positive growth by increasing conversions of casual visitors.
The product (App/Pizza/Car/Suppository/Whatever) still needs designing; i.e. a problem exists that needs solving. However you want to phrase it, a problem is solved by designing, be it using established patterns or generating new solutions. How it looks and how it works should be intrinsic to what a product offers. None of the elements are mutually exclusive.
Design is intention.
Design is function.
Design is appeal.
And, sure, design is appearance.
It should be no surprise that, yes, if you can pump enough raw "value" into something, however you care to define value, that you can ignore or short shrift design. Go ahead, limit your chances by killing your first impressions. Write poorly in your presentations while you are at it.
I mean if gold starts pouring out of your user's computer's USB ports when they load up your web page, you're right. They won't care what the background color is or what that blob in your logo is supposed to represent. If the reward is high enough, they'll kill themselves finding that magic button among all the log ins, captchas, and cryptic navigation tools.
But if you're trying to sell a new idea, one that may be unfamiliar, or if your "value" depends on the size of your user base, you might want to spent the time and effort to respect your user enough to make it clear what you intend to do. And what's in it for them.
Good ideas, and value, are sometimes not enough. They require a context to be useful and acceptable. Good engineers know this.
And, sometimes, a nice little shrubbery, in just the right place, and a splash of color, can make all the difference.
Invoice is in the mail.
> Stop creating shitty startups that look amazing. A product or service that is indispensably useful yet looks like ass is infinitely more likely to be successful than a product that solves zero problems but looks like a work of art.
I'd say sure, in general, though that does beg the question for what problems so many "useless" but successful apps solve. (Mindless entertainment, I guess.) More importantly, though, "design" and functionality and usefulness are not at odds.
For some fun (probably less comprehensible) rantings in the other direction, have a look at http://richardkulisz.blogspot.com/2011/05/engineers-are-infe... and http://richardkulisz.blogspot.com/2011/06/design-principles-...
Saying "design is horseshit" makes about as much sense as saying "engineering is horseshit" or "writing well is horseshit". Read: it makes absolutely no sense.
The whole point of the article is that the foundation of any successful company lies in the value it provides people. Everything else--design is singled out because of the earlier article on the matter--is built on that foundation. Since a startup is just the foundation of a company, its primary goal should be creating a product people use.
In short, he didn't really mean that design is completely worthless--it is merely worthless without a solid product behind it. The same could be said about engineering and strong copy; neither is going to matter if you're making something utterly useless. Thus, given this meaning of "design is horseshit", "engineering/writing well is horseshit" actually makes sense.
Coincidentally, I agree with the idea behind the post: producing something viable is the most important thing a startup can do; the younger a startup is, the more important the product's value. However, I think the overly sensational, antagonistic and slightly misleading title was poorly chosen to represent his point. The post is solid but the title isn't. It does drive clicks and readers, so in a sense it was successful, but primarily from its less desirable qualities.
In short, he didn't really mean that design is completely worthless
And there is inherent value to delivering overall value quicker.
Jobs had a major role in how the products at Apple have worked from the start.
I also recall Jobs making interface design references in his Stanford commencement speech about typography, calligraphy, kerning, and typesets. This happened before he started Apple.
"It is to a massive degree much, much easier to spend a week pushing pixels to create something beautiful"
"Everyone’s a fucking designer now
If there’s one thing you can rely on everyone having an opinion on, it’s how something should look."
"no shimmering design"
"They didn’t solve problems! Who fucking cares how it looks!"
I don't think he gets it at all.
Design alone is horseshit. Engineering alone is horshit. Blogging alone is horseshit. Marketing alone is horseshit.
But put these together in the right proportion and you get a beautiful product. The proportion depends on your product/service. It takes a lot less selling, if the visual design of the product is impressive. It releases dopamine in your customer's head which urges them to put their credit card number in the checkout form. It may not be important for enterprise product as the person signing the cheque does not use your product. But it is vital for consumer and small business based products. But I agree with the author that pretty design is not a substitute for good engineering, good customer support or good marketing.
you were right at the start: Engineering is also horseshit. You can have the most beautifully engineered solution to a problem that nobody has or is willing to pay to have solved, and you'll still have a bullshit startup. Marketing is also horseshit. You can have the most amazingly viral video for a product that nobody wants and you will still end up with 0 sales and long-term, 0 customers.
the point here is that there isn't a startup fund or growing sentiment that seems to champion engineering or blogging or X as a fundamental part of the startup equation. it's all just a toolbox. but strangely, there is one for design.
the real issue that early startups need to focus on is solving a problem and creating value. that's actually much, much harder than you think and it should be 100% of the focus in the early stages.
forget about engineering and design.
Design starts from understanding and empathizing with the user. Design helps to shape the product and connect with the users emotionally.
The Design Fund highlights the importance of designers in startups not just because they make things look pretty. Designers are usually trained to understand users emotionally. An engineer look at a problem and start using equations to solve it. A designer look at a problem, start by understanding the user, and develop a way to solve it.
Design teams in big companies have User Researchers (on the ground, understanding users, find out needs, etc), User Experience Designers (connecting the dots from research to product, how the product should function and flow), Interaction Designers (that transition effect you see in iOS? not just pretty. Helps users to orientate where they are at), Visual Designers (make things pretty).
As you can see, in the whole field of design, only Visual Designers are the ones who really make things pretty. Once again, The Design Fund values designers because they look at things differently, and they can build products with emotion. (Apple products have a lot of emotion tied to people)
*I am not part of The Design Fund.
In fact, the design community faces a huge problem because almost everyone thinks design == make things beautiful and that is one of the things that has been holding back design in startups for so long.
commieneko said it well:
"Design is clarity. Design is intention. Design is function. Design is appeal. And, sure, design is appearance."
So yes, spending a ton of time altering the drop shadow on your button and the RGB value of your logo might be time wasted in a startup. But spending time clarifying what your product does, or devising a smoother way to onboard users, or figuring out a way to highlight your more expensive plan, or any number of other things good designers are thinking about while also "making things beautiful" is not wasting time.
> 1. Designers tweet and blog
> 2. Design is a cheap way to appear like you’re creating value
...
> I’ve created products / services in the past that have garnered praise for their design.
> 3. Everyone’s a fucking designer now
Face it, you're a designer.
> Design enhances value, it does not create it. Stop creating shitty startups that look amazing.
I don't understand how enhancing value doesn't create value. Value is value, there isn't good value and bad value, there's only more or less of it. If pushing pixels does a better job enhancing value than creating features then I am absolutely going to (have someone else) design the shit out of that product.
I see design much like I see testing. Both of these are meant to build integrity in your product. Design is perceived integrity, while testing is conceptual. If you don't proactively maintain the integrity then the lack of quality compounds. Treating them like a second class citizen will do nothing but cause troubles.
He was saying that design is multiplicative, not additive. You could have an extremely beautiful and well designed app but, if the idea doesn't first provide value to your customers, you're just polishing the brass on the Titanic.
As an example, Roy Fielding describes the URLs that a RESTful webservice includes in its representation of a resource (for what transitions are available to other states) as "affordances". It could even be argued that Codd's relational model was a better "design" for thinking about databases, which he presented in terms of the problem of data models being too closely coupled with storage representation.
Of course, even this broad sense of design doesn't address whether there's a market for a solution; but it does address whether you can make a solution that's better. I can see the sense in seeking a problem that needs to be solved - in being "market-driven"... but personally, I'm much more excited about creating something better (which is only possible when you already know the problem and some existing solution, because "better than" takes two operands). And that seems to be the history of all the products I admire.
Design is everywhere not just in the shiny stuff. Design is a workflow, response, messaging, interaction... These are all areas of design you might not be able to see immediately but are often the key components of making a great product.
My guess is that every one of the companies he considers successful had good design baked into their products somewhere (even if they had terrible aesthetics).
To categorize all design in this way is very misleading to those starting a company.
Some final words on this. Some people have interpreted this as me not understanding the value of good design. I assure you I do from experience, tweet at me if you want specifics.
However - create value before exploring how design can enhance the experience. Solve a real customer problem. If you’re an early stage startup with no revenue, don’t even think about design! Think hard about what problem you can solve that a customer will give you $10 for and work your ass off at delivering that $10 of value as fast and as cheaply as possible. It doesn’t even matter if you’re not aiming to make a paid service. If people won’t give you money to solve their problems, it’s not a real fucking problem. It’s just another novelty echo-chamber startup that you might get a chance to flip to a bigger fish if you win the startup lottery. Don’t be an idiot and buy into that. Solve a problem, live forever. The idea that design is what early stage startups should be busying their time with is a notion I find utterly wrong.
One would thinking that making your credit card form easy to use and find for customers is fairly integral to making revenue. You can have the most awesome service in the world but if you make it hard for people to pay you money, you're not going to make money.
Worrying about how to get money for a product without value is a waste of time/resources.
that's what early stage startups are supposed to be figuring out, not optimizing their credit card forms.
Why so many of these content-less posts on HN front page lately?
[edit- regarding issue of straw man perception] The issue is that nobody who makes beautiful novelty thinks their own work is beautiful novelty. (So nobody will appear in favor of it, even if they make it.)
So it's not quite a straw man. Everybody agrees that a certain type of thing is bad, but nobody thinks they themselves are responsible for that thing.
I suspect the author has some specific start-ups in mind but didn't want to call them out. Why have people be distracted by the drama of him dissing $startup in a blog post when he really wants people to ponder a more big picture idea?
The author is not suggesting not having quality design. He isn't even saying design isn't an itegral part of product development.
he's saying everyone is skipping step one, namely figure out what problem you're going to solve. No one asks the proverbial question 'How is my product going to get them laid' (to paraphrase jwz) They just skip straight to having a great way of doing the same exact thing everyone else does just as well.
I am a huge fan of the "how will it get my users laid" way of thinking. If your product/service can provide that kind of value even in some protracted form (i.e. I'm not just talking about dating sites) you're on the way to nailing it.
I see design as an enabler. Engineering is where the heavy lifting is done, but design is what makes that possible. I hate to bring up Apple as an example, but when you look at, for example, Siri: voice recognition, understanding grammar and meaning within human sentences and the all technology behind it is fantastic engineering. But what differentiates Siri from anything else out there is the design. The fact that the AI has a personality, that it jokes around and does not feel like a machine, that's what makes it accessible to humans and what makes it so insanely great. And that's design.
I agree with the author to the extend that glossy buttons and a textured background does not a good product make. Indeed, there's a lot of good-looking crap out there—but that's not design, and the author's argument that that's what design is makes him look like an ignorant fool.
If I (programmer, no design education or talent whatsoever) sit down with a pen and paper and draw a user interface (1 page) 100 times, the 100th time, it'll be quite optimal, consistent and nice. After that it goes through the pretty machine, an artist who cannot do IA, but can do pretty. It's a great combi. With programming, you cannot really do the same trick; you'll end up with crap.
I do agree that it an be a greater catalyst than pure engineering. I don't think it can be much of anything without engineering and value and that was the author his point. Of course when you made a product you want to make it look good and work well ergonomically, but you want the value and the engineering in place first. After reading the article I felt like his real beef is actually with nonsensical vaporware looking pretty to attract investors and morons signing up anyway.
If you agree with the flawed logic of Jon then you must substitute the word “Design” with any discipline concerning the action or behavior of creating value. Thus making a series of useless posts like “Engineering is Horseshit” and so on. You don’t see the design community getting mad at engineers who spend weeks designing an optimal database sharding strategy for building things like a daily-deal aggregator which has 0 users and a growth rate of “Divide by Zero Error” and no viable user acquisition strategy. Of course entrepreneurs should focus on value creation and finding product market fit before spending an inappropriate amount of energy on other activities whether that be visual design or backend infrastructure. Any entrepreneur I invest in should know that elementary lesson from experience or reading the Lean Startup etc.
Personally I find myself in that situation, early stage startup where whilst I have the tech background, design has never come easily to me (and my co-founders are even worst). As we have bootstrapped we didnt have the money for great design and did the best we could! That said it hasnt been the make or break as we have executed well, however first impressions always count... and when looking for investment we have more than once had potential investors misjudge how far we have come or compare us negatively to others in our space as we did not have the design 'edge'. Its a shame, but its a fact of life appearances mean a lot..
Perhaps off topic but be interesting to know how others have managed to overcome gaps in skillsets when bootstrapping? we dont seem to have any contacts with good design skills and available time..
Entirely incorrect. Read the Lean Startup. Value creation is 100% possible without any UX or anything tangible that the customer "sees" at all. A delivery pizza place provides value. I call them, they deliver pizza. There's no "UX" there beyond what already existed (my phone, a working phone line).
Too many people think the first thing that needs to be solved is how something looks or feels. It's not. You can solve a problem without any UX.
Give me a moment to finish making my Picard face, here.
The entirety of pizza delivery is user experience.
- Answering the phone with clarity and promptness
- Taking an order with accuracy and clarity
- Creating a pizza that tastes good while matching the customer's order parameters
- Not giving people diarrhea
- Estimating a delivery timeframe
- Delivering the pizza within that timeframe
Botch any one of those things and the experience of ordering the pizza sucks. Botch several and people will stop ordering from that restaurant. Food, in particular, is possibly the largest user experience challenge outside of software. Maybe toolmaking is bigger. But food and restaurants are way up there.
I think you have a fair point.
However it's important to remember that startups are out there to prove a core value proposition. Everything else, the UX on top of it - that can come later. After you've proven the core. It's all bullshit until then.
So say I'm starting a new pizza place. My value proposition: is pizzas in 10 minutes or less.
that is what I should be optimizing all my efforts around. if I can prove that people want and will pay for pizzas delivered in 10 minutes, even if they taste average, even if my phone etiquette is shitty, even if my delivery guys are smelly - then I know I have something as a startup. my core hypothesis has been proven correct.
then I can spend time working on the "UX" - the layers on top of that core that make the experience much more pleasant.
there are too many new startups obsessed with the layers and not with the core.
I'd like to think that design = caring.
As in: If you care for your users you spend time thinking about how the product should work for them.
Those who aren't building the product often can't express ideas about what they don't see or know about. To them, the design is the surface, the user interface. So naturally they assume that if they want to create a product with "good" design, they should hire someone who does the visual part, and make their product look just like other products that they think are well designed.
If you want a good counter-example, about good design that is very subtle and runs very deep, read "The Pencil: A History of Design and Circumstance" by Henry Petroski.
It's unfortunate that designers still have to battle ignorant misconceptions that their work is about pushing pixels and making things look pretty. At it's heart, design is exactly what this article is advocating for; understanding a deep user need and developing an elegant experience that fulfills that need.
I don't understand what the author is so riled up about. Why not just delegate responsibilities? Let a designer focus on design, while the engineers focus on the actual product. Does it hurt to have a designer? I don't see why it would.
Good luck trying to sell something to the general public that looks horrid. No matter how well it works.
you're selling directly to people you find who have the problem that you're solving.
it's exactly that mentality of getting way ahead of yourself before you've even validated and honed your value proposition that I take issue with.
fuck the general public. go solve a real problem for 10 people - it's 1000x more difficult than creating something that looks and feels awesome.
Did I mention it's silly?
...you've also [wisely?] abandoned projects that had great promise without to due diligence necessary to hand them off to a willing steward (Sweetcron).
I was pleased to see your domain here on HN, but I still have a bitter taste after being forced to abandon Sweetcron in favor of Chyrp. Regardless, I've been quite impressed by what you've delivered thus far and am pleased to see your weight provided in the direction of reason.
Can't blame me for no one wanting to fork Sweetcron.
Graphic design is visual engineering.
Sometimes the value proposition put forward by a company is 'a way to [do x] better'; if better is equivalent to 'more efficiently', 'more cheaply' or 'more easily' - chances are design is going to be factor that allows the change to happen.
The update is worthy to read too.
Why is such a simple concept so hard for people to understand in practice?
There is huge value in being able to communicate problems visually that comes with the experience provided by being a designer early career.
This is exactly what design is.
Articles like this are the real droppings. The submitter merely the bowels.
To single out design from any other process involved in creating value makes zero sense. In fact in many products design, including visual design is a key differentiator that actually gives the product value (think iPod vs all other mp3 players).
Only programmers or engineers creating extemely cutting edge products that have no competitors could take this attitude than design issues can be set aside till later. What serious person would consider starting a business without incorporating design from the beginning?
Whatever meme out there about design being an edge in a startup is responding to what I see is an incorrect undervaluing of design in the tech community.
Another subtext in the discussion is many tech start ups are making software, web based or otherwise. On a typical program huge amounts of value are delivered as pixels. The user interface is also pixels. A lot of software are tools. Graphic design is mandatory for the thing to exist! Widgets are make or break whether a software tool even works at all.
I use audio software in my job (all day) and many competing applications in this space are at feature parity. UI and Ux is what separate apps that work really well from apps that are painfully slow and frustrating to use. Just consider how color is used in a complex app. It communicates feedback, breaks up function grouping, it helps you find and remember features, it provides a hopefully not unpleasant visual experience since one is staring at for extended periods. I think we are in the Dark Ages of human computer interaction and that bad visual design is a huge contributor to the problem.
BTW, anyone have examples of web services with great design don't offer value?
Design with utility has inherent value that can be quantified. It's silly to categorically say design is horseshit.
Developers might respond that they created a great product that solves a problem without any designers. To that my reply is that you then you have designed as well.
2. Count the number of Apple devices in use. White earbuds are a dead giveaway.
3. Go hire a designer that knows what they're doing and try and accomodate their ideas into those of engineering without making a capon out of anyone.
4. Keep iterating.