At Social Flare, the kind of work we do involves developing an understanding of who you are as a business, and how you are perceived by the people who see you on the web. This is usually a bit different than how you -think- you are perceived, and definitely different than how you would like to be seen.
A large chunk of our skillset comes from past work in experience design and architecture. When doing this kind of work, you design total experiences for clients. This is more than just whipping up web pages; it has to do with an almost intimate understanding of how different groups of people approach your content and how they use it, and how to help them do this. It's as much art as it is science, and involves some leaps.
"Of course people will use our page commenting feature- it's so easy."
"Why wouldn't they call us if they had a problem? We get no calls, so everything must be fine."
"We've been doing things this way for years; it works just fine. We just want a total new look."
And so on.
You may recognize the above statements as ones you've made as a client, or what you've heard as an experience designer. Whether you're developing communities or single page sites or blogs, you need to be very careful about the assumptions you make about how people use your content and apps.
Google found this out, the other day. In an excellent article on one of the NYT blogs, Miguel Helft illustrated this very issue. In an effort to better position itself as a major force in social networking, Google is innovating it's own applications and putting the social spin on them. Google Reader is an app that allows you to read various blogs, and before a few days ago it let you specify other people ( Google Account holders, of course ) who you could share this content with. A few days ago it became known that Google changed this slightly; now everyone that you had IMed with using Google Talk had access to what you had read using Reader, as if you had shared the content.
The assumption of use was this: if you had IMed with someone, then certainly they were your friend.
It would therefore be fine for Google to assume that it was cool to open up sharing of all the things you'd read to your "friends" that you've IMed with.
This probably isn't true for some.
A fundamental precept of user experience is that, as much as possible, you should let the user define the experience. in the framework of what you offer, certainly, but the user should have as much control as possible. An important point here is that Google didn't offer Reader to start with, in it's initial form, as something that shared with everyone you IMed with. This was a change, and thus not something "factored in" to the user's experience. When people found out that things were different now... many had a problem.
One can make several reasonable guesses as to why Google did this; it wanted to make its apps more "social", because it believes that in doing so it positions itself as more of a leader in this type of very popular computing. It also sets the exprience trend for future Googel applications.
The problem comes in assuming how users experience your app; Google assumed it'd be just fine to give all the people you IM with access to what you read in Reader. Apparently this is not the case.
It's hard to beleive that Google did not research this point first; it's always interesting when something you assume would have showed up with a bit of user research seems to come as a total surprise to an institution like Google.
Even the biggies can make this mistake.