Designing for the Social Web by Joshua Porter
Joshua Porter had some interesting ideas.
Not How, But Why
The book is less of a how-to and more of a why-to, if that makes sense. If you’re looking for code examples, look elsewhere. Instead, the book covers theory and explains how and why certain tasks need to be done.
Essentially, any social site, whether in the shape of forums or something else, faces the following user hurdles:
- Pay attention – users need to have an idea that they want your software, product, services, etc.
- Decision to sign up
- Input personal information
- Pay money (if applicable)
- Decide for someone else (if applicable)
- Give up the old way of doing things
Back Up a Second
Frankly, there’s even one item before #1, call it #0 if you will: the potential user must understand that he or she has a need. And, hand in hand with that, the potential user also needs to decide to fulfill that need online. Hence if a potential user, say, decides that they want support because they’ve just gotten a cancer diagnosis, but they further decide to only get their support via an in-person group and not an online board then, so far as you’re concerned, it’s game over. After all, not everyone “gets” the social aspect of the web.
Get Over Those Hurdles
Joshua Porter covers the handling of some of these basic hurdles, such as designing to favor signing up and hanging around. One main point he makes is: don’t make signing up too arduous a task. And its corollary: don’t ask for information you don’t need. Far too often, sites ask for what ends up being ludicrous levels of granularity of detail. After all, when was the last time that anyone, really, needed your middle name for you to apply for a job? Yet sites ask for this trivial piece of data. And, even if they don’t require it, that begs the question even further. Why is the field even there in the first place if the site so openly acknowledges that it’s just plain unnecessary?
Eight Seconds to Impress
Porter makes the point all too forcefully: the decision to sign up for an online service is made in eight seconds. That’s an awfully short window of opportunity to convince a potential user that his or her time and attention should be paid to you and not your competition.
The book abounds with these kinds of helpful nuggets, and is also chockful of references to blogs and books to support the author’s recommendations. The generous sprinkling of citations was helpful as it was a clear signpost suggesting online readings. It can seem counterintuitive to learn about designing for the web by reading a completely offline book. Porter’s work bridges the gap back to the web and lets the reader in on where to find more information situated a lot closer to where the reader is going to be placing new social software or services.
Finally, Designing for the Social Web does not seem to draw an overall conclusion. Rather, the book instead seems to simply run out of gas in the end. It’s as if the author had run out of what to say. Hence a final upshot or even some words of encouragement would have, I feel, helped. But that’s a small issue with an otherwise interesting and eminently practical work.