Time To Get Out Of The Bubble And Design For The Average User
futurephilanthropreneur.wordpress.com
futurephilanthropreneur.wordpress.com
We care about this technology because it allows us to provide a better end result. We talk about it internally because we want to share our successes and failures so that we can educate and learn from our peers and create better end results for the average user.
I don't care why my house stays up, but I'm glad that there are people (line engineers and architects) who do so that I have a wonderful, stable home. We're the architects of the web.
Engineers to engineers of course need to care about the technology. However, in terms of design, so many products seem to forget about the core user of their product and their needs.
I would expect that the majority of us here at HN can easily build stable, reasonably scalable applications quite easily. I would expect that far fewer of us really understand the needs, desires and abilities of the average user. To me, it seems ridiculous that we continue to worry about marginal, incremental improvements in the technology when it is readily apparent that "technically better" solutions are easily beaten in the market by solutions that resonate better with users.
To use your architecture analogy, few architects worry about whether or not a house will stay up, because they have mature processes and frameworks in place to guarantee the soundness of the design. The real work of architects, the part that separates the likes of Foster and Gehry from everyone else, is of aesthetics and usability. What makes an architect great is not their ability to build cheaper or stronger or bigger buildings, but their ability to build beautiful and elegant ones. We have a great deal to learn from them.
The last statement in your second paragraph is especially wise, and the ability to resonate with users is the absolute key.
> I think the real point of the article is that almost all
> of the technologies at our disposal are good enough. We
> spend endless time debating Ruby vs Python, RoR vs Django
> and navel gazing about Lisp or Haskell or Smalltalk, but
> how often do we talk about users?
Frankly, I do not see any shortage of talk about "users" or "delivering" or any other of hundreds of similar terms. I think this line of reasoning overlooks some pretty crucial factors:- Arguing about X vs. Y beyond a certain point often has nothing to do with "productivity" or some other undefinable metric. It is entertainment. Not ha-ha entertainment, but something to pass the time - trading quips, debating and so on.
- New paradigms, languages, frameworks and applications - as well as hardware and architecture - certainly affect users. Some directly, some by providing developers the ability to concentrate on the essence rather than the unnecessary boilerplate obstacles.
It often seems that the people writing the "stop language wars" posts and the like are the ones most emotionally invested in the topic.
> To use your architecture analogy, few architects worry
> about whether or not a house will stay up, because they
> have mature processes and frameworks in place to
> guarantee the soundness of the design.
Yeah, and those processes did not just spring up from nothing. There have been centuries, millennia, of development - and you can be sure there were more than a few "pyramid vs. cube" and "vaulted vs. flat" debates in there.An example: a friend was heading up the alpha test team for Sid Meier's Civilization IV, and invited me to join. I was the only tester without previous Civ experience. At one point I expressed my frustration with not being able to view certain information except when the game popped it up. The other testers and devs were surprised that I didn't know to press F5 through F9 to bring up that information. The devs added buttons for those screens to the GUI in the very next release, with clear icons and helpful mouseover text, and my user experience was much improved.
Point being, the thing that gave me trouble wasn't being "non-technical", but inexperienced with the particular conventions being used. The challenge in UI design is to figure out conventions that both experienced and new users will be able to understand, and to replace conventions that new users struggle with. The only useful piece of advice I have is to make sure you have some testers who can compare your product to others like it, and other testers who have never used anything of the sort, so that you can see what conventions people from each camp struggle with.
http://news.ycombinator.com/item?id=1120820 and http://blog.bumblebeelabs.com/the-5-guerrilla-user-test/
the basic idea is to go into a bar and find someone who's a little bit drunk who'll spend 15 minutes using your software in exchange for a drink. "Watch your application crash & burn as people do all sorts of ridiculous ass shit they would never do in a lab but constantly do in real life", and learn from it.
But how can we do it, what have we been getting wrong so far, what design idioms need to be thrown out and what innovative ui's help users? thats what I want to hear.
Less talk, more rock. Go out and do something, and then blog about it once you've learned something interesting. If you want to psych yourself up with self-help stuff, keep a private diary.
* Campuses used to hand out "facebooks" to freshman so they could get to know their fellow students + have a directory.
* Spreadsheets used to be large pieces of grid paper used by accountants.
* Encyclopedias did really well until Wikipedia came along. Encarta was the first sign of trouble, but Wikipedia was the nail in the coffin.
* We used to mail physical letters. Email has replaced significantly replaced that (of course physical mail still exists, but you don't send physical mail for social interactions anymore).
* We think our generation and their families won't be storing photos, memories, and vhs tapes in a shoebox. What's the specific digital equivalent of that is the question we're trying to answer with the new version of Ramamia (to be renamed Genevine).
There are probably others.
This is incidental to your comment, but I think your details are wrong in this example.
Multimedia digital encyclopedias replaced physical encyclopedias long before Wikipedia came along, in fact throughout the 80s and early 90s it is a pretty safe bet that encylopedias on CD-ROM and later DVD significantly outsold the dead-tree versions, and by the mid-90s the major brands (at least in the US) already had online versions as well.
Encarta (which was initially a rebranded Funk & Wagnalls encyclopedia) was just one example, and a later one at that, of many encyclopedias that were transitioning from print to digital. Encarta doesn't represent some kind of paradigm shift in the encyclopedia business, just a large company snatching up a small player in a market they were trying to penetrate. Interestingly enough, Encarta has ceased production, while World Book, Encyclopedia Britannica and others are still in business and presumably profitable (for now).
Wikipedia was and continues to be a threat to "traditional" encyclpedias, but not because they didn't anticipate a transition from physical to digital publication.
I strongly believe that we are in a new industrial revolution.
Is this another "techie" blinder of mine? Am I wrong to think that the "average user" cares at all about what the URL looks like?
In any case, I believe that if you're asking user's for their email, then you should tell them what you are doing. You don't have to give much details. A short 3 line summary would be enough. In my opinion, "Explore. Connect. Achieve." isn't going to get you a lot of emails. Just my two cents.
I have researched both approaches, both stealth and iterative development with lots of attention. We are trying to create a hybrid of the two. The stealth is only temporary until we are in a position to show the world and then iterate.