Making it Suck
cooper.com
cooper.com
Elsewhere, Microsoft intentionally designed Vista's User Access Control dialogs to be irritating [1]. Microsoft wanted applications to stop using Administrator rights for no reason, so every privilege escalation painfully obvious: The screen fades to gray, and an extra dialog appears. Application developers get the same dialogs, and can trim unnecessary escalations out of their code.
[0] http://support.apple.com/kb/ht1320?viewlocale=en_us&loca...
[1] http://www.pcworld.com/businesscenter/blogs/on_software/1445...
Making your software suck makes the user hate you (unless you have a reality disorder field).
Sure, most of us then don't consider the result to suck, but it actually does. And we do this a lot.
Some more examples from the top of my head:
- making landing suck for fun --> skydiving
- making sitting suck --> for better posture
- making reading in light suck [iPad/etc] --> for better contrast
- making privacy suck --> to get 500M users
- making security suck --> to gain a monopoly
Yep, pretty brilliant. Let's all start making things that suck! It's obviously working.
I think this is related to the "ugly for authenticity" point in the article.
While the sucky seating prevents the behaviour (sleeping) right there, it doesn't address the need/problem at all.
People don't want to sleep in airports, they'd much rather sleep at home, but their connections suck or delays made them miss their connection etc.
So sleeping will happen, but on the floor beside the seats.
Oh, and some people do want to sleep in airports -- cheapskates who don't want to pay for hotel rooms. Check out "The Budget Traveller's Guide To Sleeping In Airports":
http://www.sleepinginairports.net/
for far more information than you ever wanted about the best places to sleep at airports all around the world.
And less missed flights from oversleeping.
For example, near where I live, someone recently posted a flier for her house cleaning service. It was on green construction paper and written with a red marker.
My initial thought was 'maybe she'll be cheap' and then 'do I want someone in my house that thinks magic marker is the proper way to make a sign for their business?'
Another example: I buy a LOT of things online. But I only buy from sites that I feel I can trust. That means they don't -look- like a scam, and they look like they know what they're doing. When I go to a site that looks like it came from 1990, I might check prices, but I -never- buy. Instead, I go back to somewhere 'safe' like Amazon and pay a little more.
Most of the examples (shoes, chairs, tables) were designed to prevent or force certain behaviors. They don't 'suck', they 'work' for exactly what they were intended.
Conveying the right expectations is a part of good design. If looking cheap is a selling point, a design that looks expensive is a failure. It's the "nice and clean" design which sucks.
jakevoytko also brought up Vista's UAC dialogs, which I agree is a Good Thing. In my experience though(especially with my younger cousins despite my repeated yelling), they simply log in as admin and bypass the whole thing.
The truth is that design is as much for ease and comfort, as it is for differentiation and in that department, there is only one slot for the perfect web site, the rest of us have to stand out!
catchy headline, though. :)
(Exactly what happens to the homeless is not discussed.)
I think anything sucking is bad. You can have a site that is well-designed to elicit a local flavor, which might mean "suck" to some, but it doesn't suck.
You can have an airport with bad chairs, but a built-in hotel. That wouldn't suck.
I guess that in fact proves the point that something can suck and still suck. I guess the problem was that it didn't suck by design.