Niti Bhan does strategic design planning and concept development in emerging markets like India and some African countries. She begins her article Developing a user centered methodology for emerging markets and the bottom of the pyramid by discussing what happens when companies in the developed world try to introduce products in lower-income markets:

So the value propositions of the products, services, and programs introduced for lower income markets—particularly in the developing world—are still based on elements of the value system prevalent in global consumer culture. There is a gap here, and it’s most obvious in the marketing messages, advertising and communications which tend to emphasize product benefits or value that may not be relevant—much less contextually appropriate—to the BoP [Bottom of the Pyramid] customer’s life. When the value proposition of the seller has little or no resonance with the value system of the target market, it will most likely be ignored.

Even more interesting, she questions the value of using a standard user-centered design (UCD) methodology in these markets. Her point is that it’s not just products that need to be tailored specifically for these markets, the methodology we use to identify user needs should be different as well:

UCD has emerged from the same operating environment as that of the majority of the producers and most certainly has been part of, if not partially the creator of, the global mainstream consumer culture in which we’re all immersed. Therein lies the rub. The process is not divorced from its context and thus, we found, it needed to be far more flexible as it evolved and was adapted to the challenge of conducting exploratory user research in slums and villages and townships across the developing world. For the human centered designer, more likely to have been trained in the heart of the most sophisticated consumer markets in the world, there were additional challenges when considering the new and emerging consumer markets at the BoP.

I see this in our work at Flow as well. We constantly have to adjust how we do usability testing or contextual interviews to make sure participants are comfortable enough for us to uncover their real needs/issues. Niti’s work looks fascinating, so I definitely recommend reading her post and checking out some of her other writing as well.

John Gruber wrote the following in the context of recent leadership changes at Apple, but it’s applicable to life in general. From Seriously, Apple Is Doomed:

What you want is to be (1) right more often than wrong; (2) willing to recognize when you are wrong; and (3) able and willing to correct whatever is wrong. If you expect perfection, to be right all the time, you’re going to fail on all three of those — you will be wrong sometimes, that’s just human nature; you’ll be less willing or unwilling to recognize when you’re wrong because you’ve talked yourself into expecting perfection; and you won’t fix what’s wrong because you’ll have convinced yourself you weren’t wrong in the first place.

I’ve mentioned before that the ability to admit that you’re wrong is an essential characteristic of a good designer. I maintain that some of the biggest product failures can be traced back to a refusal to recognize that the idea/design isn’t perfect.

“Design like you’re right, listen like you’re wrong.”

Christopher Butler shares a long and interesting agency perspective on responsive design in What We’ve Learned About Responsive Design. He shares tips, case studies, and some unresolved issues — including how to deal with larger display sizes:

So, the parting question for me is this: What about upward responsiveness? If we’re heading toward bigger displays with much higher pixel density, how will our designs adapt to make use of them? We’re all excited and sold on the concept of responsive design, but so far that has been limited to responding to smaller conditions. If we’re up for that challenge, than I know we can do better on the “desktop,” too.

So far we’ve dealt with that issue either by setting a maximum width for websites, or to live with acres of white space. Christopher rightly points out that we need to experiment more with ways to take advantage of larger displays without overwhelming users with too much content.

(link via @smashingmag)

Dan Frommer believes that when it comes to live events, Twitter Stands Alone:

Then look over at Twitter, where the room is bursting with fresh news, links, photos from everywhere, alerts that Karl Rove is melting down or that Diane Sawyer seems wasted, jokes coming so fast that you can barely keep up. (Many of them even funny.) You control the content, the sources, the volume, the pace, and your drink. Sometimes, it’s wrong, but it’s quickly corrected, and you should be more skeptical anyway. And if you want, you can participate. You’re not just watching.

This sentiment resonates with me — especially because we don’t have cable TV at home. On election night (morning in South Africa) I went to the gym at 5:30am so I could watch CNN on the TVs there (two birds with one stone and all that). But all the TVs in the section I was in when the race was called were set to sports channels, so how did I find out who won? Twitter, of course.

Twitter is also my first port of call when there is an issue on this site, or with one of the apps I use. If my site is down, the first thing I do after running a traceroute is send a tweet to Cloudflare or Mediatemple. When Tweetbot isn’t sending push notifications, I just search for “Tweetbot notifications” to find out if it’s just me. This has been said before, but there is simply no service out there that is better for real-time search.

Ok, that was more of a Twitter love letter than I thought it would be. I’ll stop now.

Des Traynor shares some insights on how he works with startups in Asking Questions beats Giving Advice:

The first question I ask (though sometimes I just ask myself) is an easy one: is this viable, feasible, and desirable? The answer has to be yes on all three counts—no two are enough. In fact, pick any two, and you’ll think of a start up that failed because they missed the third.

This approach shares parallels to the “problem frame diagram” approach I discuss in Usable yet Useless: Why Every Business Needs Product Discovery. The goal with that approach is to identify the user needs and business goals of the product, as well as the core competencies of the organisation.

Des goes on to describe some of the key things you have to think about before launching a product. If you do Product Management on the web, his post is highly recommended.

Micah Baldwin in Silent But Deadly:

Yet, there is something amazing, maybe even beautiful in execution. In silently creating something of immense value without the need to be everywhere to be seen by everyone. That our worth as entrepreneurs is built through our products, not through our names.

It’s a great story and a great post.

(link via @PaulCartmel)

In a response to a series of posts on eBook pagination vs. scrolling (including mine), Dr. Drang presents the strongest argument against pagination that I’ve seen so far. From Scrolling or paging?:

Authors don’t write in pages, they write in sentences and paragraphs, neither of which are honored in a paged interface.

That’s a really good point. Pages artificially break up authors’ thoughts. Pagination is the hurdle-race to scrolling’s 400-meter dash. Everything is a trade-off though, so for the time being I will stubbornly stick to my preference for pagination, because as I said, I just find it easier to deal with.

I want to challenge Dr. Drang on one point, though. He says:

As for the sense of accomplishment, I am, if anything, even more dubious. Flipping a page, whether in a physical book or an ebook, has never charged me with a feeling of achievement. In fact, in paged ebooks I seldom have any sense of how far along I am—in physical books there is, at least, the thickness of what’s in your left hand compared to what’s in your right.

I don’t agree with that. Most eBook readers have sorted out the “sense of place” problem, and now provide both visual and text indicators to help you figure out how far along you are in the book you’re reading. Below are the interfaces for iBooks and Readmill:

Note the text-based information about the number of pages that have been read, and how many pages there are in total. The visual indicators, in turn, give you a sense of the “weight” of the number of pages you’ve already read — Readmill does a particularly good job of this. And iBooks even tells you how many pages you have left in any given chapter. Those indicators combined serve as a worthy replacement for “the thickness of what’s in your left hand compared to what’s in your right”.

Kontra wrote a great post on the real problems Apple needs to address in their software and operating systems. Apple’s design problems aren’t skeuomorphic starts with a statement everyone needs to take to heart:

The current meme of Ive coming on a white horse to rescue geeks in distress from Scott Forstallian skeuomorphism is wishfully hilarious.

Exactly. As Gruber pointed out:

The speculation regarding skeuomorphism as a factor in Forstall’s ouster has gotten out of hand. That’s not what this was about. This is about Forstall’s relationship with the other senior executives at the company. Personalities and politics, not rich Corinthian leather.

Anyway, moving on. Kontra goes on to list some of Apple’s current software issues, and concludes:

In the end, what’s wrong with iOS isn’t the dark linen behind the app icons at the bottom of the screen, but the fact that iOS ought to have much better inter-application management and navigation than users fiddling with tiny icons. I’m fairly sure most Apple users would gladly continue to use what are supposed to be skeuomorphically challenged Calendar or Notebook apps for another thousand years if Apple could only solve the far more vexing software problems of AppleID unification when using iTunes and App Store, or the performance and reliability of the same. And yet these are the twin sides of the same systems design problem: the display layer surfacing or hiding the power within or, increasingly, lack thereof.

Read Apple’s design problems aren’t skeuomorphic.

Jenna Wortham shares some fascinating stories in How New Yorkers Adjusted to Sudden Smartphone Withdrawal:

On the scale of hardships suffered in the storm and its aftermath, these were more like minor annoyances. But the experience of being suddenly smartphoneless caused some to realize just how dependent on the technology they had become. […]

“It’s strange, how in the end you feel like a prisoner to your device,” [Steve Juh] said. “It’s the one thing you wanted to work, more than anything.”

What most people find most disconcerting is the sudden lack (and unreliability) of information. As one person said, “You had to make plans and stick to them. It felt so old-school, like we were back in 1998.”

(link via The system that breaks is not the system that repairs)

In Bridging the gap between humans and computers Heather Kelly takes a look at some recent ethnographic research on our relationship with technology. It’s full of interesting stories like this one:

In one experiment, Ju’s group rigged automatic doors to open in different ways: Some would open slowly, then pause before fully opening; others would immediately jerk all the way open. The people walking by the doors assigned them different levels of intelligence, and thought the doors that opened in two steps just seemed smarter.

It turned out that adding the pause gave illusion of forethought, even though it was just an extra programming step. People thought the door was more intelligent because it appeared to think before carrying out an action.

One of my favorite books on this topic is Sherry Turkle’s Alone Together: Why We Expect More from Technology and Less from Each Other. The first half of the book is all about our relationship with high tech “things” — what we find creepy vs. comforting, how different cultures behave differently, etc. Highly recommended.