Top Banner
NEW ASSUMPTIONS FOR DESIGNERS OF THE SOCIAL WEB Chris Messina WebVisions May 22, 2009 Portland, Oregon
153

New Assumptions for Designing for the Social Web

Sep 08, 2014

Download

Technology

Chris Messina

 
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: New Assumptions for Designing for the Social Web

NEW ASSUMPTIONS FOR DESIGNERS OF THE SOCIAL WEB

Chris Messina • WebVisions • May 22, 2009 • Portland, Oregon

Page 2: New Assumptions for Designing for the Social Web

What is the social web?

Page 3: New Assumptions for Designing for the Social Web

Let’s begin with Web 2.0

Page 4: New Assumptions for Designing for the Social Web

“Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the

intrinsic advantages of that platform: delivering software as a

continually-updated service that gets better the more people

use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating

network effects through an “architecture of participation,” and

going beyond the page metaphor of Web 1.0 to deliver rich user

experiences.”

— Tim O’Reilly, Web 2.0: Compact Definition?

Photo credit: Adam Tinworth

“Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it,consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an “architecture of participation,” and going beyond the page metaphor of Web 1.0 to deliver rich user experiences.”

Page 5: New Assumptions for Designing for the Social Web

Photo credit: Adam Tinworth

“Web 2.0 is the business revolution in the computer industry

caused by the move to the internet as platform, and an attempt to understand the rules for success on that new

platform. Chief among those rules is this: Build applications

that harness network effects to get better the more people

use them. (This is what I’ve elsewhere called ‘harnessing

collective intelligence.’)”

— Tim O’Reilly

Web 2.0 is the business revolution in the computer industry caused by the move to the internet as platform, and an attempt to understand the rules for success on that new platform. Chief among those rules is this: Build applications that harness network effects to get better the more people use them. (This is what I’ve elsewhere called “harnessing collective intelligence.”)

Page 6: New Assumptions for Designing for the Social Web

WWW

and so fundamentally, we’re moving from a web of documents... (CLICK)

Page 7: New Assumptions for Designing for the Social Web

WWW

to a web of people.

And so when we talk about the “social” web,

Page 8: New Assumptions for Designing for the Social Web

“Social” is the state of living as a “society”

we’re really talking about society — the collection of norms, habits and behaviors that define what a fairly large collection of people are all about.

Page 9: New Assumptions for Designing for the Social Web

the basic atomic unity of society is the individual.

which is critical when it comes to the designing for the social web

Page 10: New Assumptions for Designing for the Social Web

the basic atomic unity of society is the individual.

which is critical when it comes to the designing for the social web

Page 11: New Assumptions for Designing for the Social Web

social is also probably the most overused word of 2009.

so let’s get back to some basics. (CLICK)

Page 12: New Assumptions for Designing for the Social Web

A few old assumptions

before we talk about what’s new, let’s talk about some things that haven’t changed

they apply throughout the historical development of technology.

Page 13: New Assumptions for Designing for the Social Web

People are busy

First, People are busy

Page 14: New Assumptions for Designing for the Social Web

People have limited attention

Second, People have limited attention

Page 15: New Assumptions for Designing for the Social Web

People want to know what’s in it for them

Third, people want to know what’s in it for them

“why should I care?”

Page 16: New Assumptions for Designing for the Social Web

People want it to “just work”

Fourth, People want it to be easy and “just work”

Page 17: New Assumptions for Designing for the Social Web

People don’t care about technology

Fifth, people don’t care about technology. Not really.

natural skepticism: “don’t complicate my life”

technology creates aprehension: “i don’t want to learn something new”

Page 18: New Assumptions for Designing for the Social Web

People shouldn’t need to care about technology

Sixth, they shouldn’t need to care about it to benefit from it.

Page 19: New Assumptions for Designing for the Social Web

Good technology is largely invisible — it blends in and enhances without encumbering. Think of the iPod and all the technology that makes it possible.

Page 20: New Assumptions for Designing for the Social Web

Then contrast it with the Zune.

Page 21: New Assumptions for Designing for the Social Web

12:00

Or better yet, the VCR.

Page 22: New Assumptions for Designing for the Social Web

12:00

Or better yet, the VCR.

Page 23: New Assumptions for Designing for the Social Web

10 new assumptions

Page 24: New Assumptions for Designing for the Social Web

1.Most people already signed up elsewhere

in other words, people don’t need an account on every site.

Page 25: New Assumptions for Designing for the Social Web

Take FriendFeed for example.

They let me sign up with ONE click. (CLICK)

So say I want to sign in with Facebook. (CLICK)

Page 26: New Assumptions for Designing for the Social Web

Take FriendFeed for example.

They let me sign up with ONE click. (CLICK)

So say I want to sign in with Facebook. (CLICK)

Page 27: New Assumptions for Designing for the Social Web

Here I am at Facebook — and I can sign up without creating another account.

Let’s go back.

Page 28: New Assumptions for Designing for the Social Web

Here I am at Facebook — and I can sign up without creating another account.

Let’s go back.

Page 29: New Assumptions for Designing for the Social Web

Now, if I click on the Google logo (CLICK)...

Page 30: New Assumptions for Designing for the Social Web

Now, if I click on the Google logo (CLICK)...

Page 31: New Assumptions for Designing for the Social Web

I’m taken to Google where — same thing — I can sign up without creating another FriendFeed username and password.

Page 32: New Assumptions for Designing for the Social Web

I’m taken to Google where — same thing — I can sign up without creating another FriendFeed username and password.

Page 33: New Assumptions for Designing for the Social Web

Now as a sidenote, this is made possible using protocols like OpenID and OAuth.

Page 34: New Assumptions for Designing for the Social Web

Just for geeks?

But isn’t just for geeks? Not really.

Page 35: New Assumptions for Designing for the Social Web

How about this guy?

Page 36: New Assumptions for Designing for the Social Web

How about Eminem?

Page 37: New Assumptions for Designing for the Social Web

How about Eminem?

Page 38: New Assumptions for Designing for the Social Web

check it out. Eminem’s doing this too.

Page 39: New Assumptions for Designing for the Social Web

Lessons

• Remove all barriers to getting in to your service

• Let people sign up and login to your site using an existing account that they already have

• Realize that this shift is the beginning of internet identity

• It’s not about “owning your customer”

* Remove barriers* Let people sign up using an existing account* this is the beginning of internet identity* It’s not about “owning your customer” -- it’s about SERVING your customer

Page 40: New Assumptions for Designing for the Social Web

2.Their friends are online

Now, of course if you make it really easy for people to sign up, you’ll find that people WILL sign up.

Which means more and more people are actually online — and those people have friends who are also online.

So, I’ve been doing a lot of travel recently and I was in London briefly on my way back to San Francisco from Europe. (CLICK)

Page 41: New Assumptions for Designing for the Social Web

In the terminal was this funny little computer that advertised a very interesting service... CHECK YOUR BEBO FACEBOOK MYSPACE HERE!

...all social networks that we know and love, right? (CLICK)

Page 42: New Assumptions for Designing for the Social Web

Well, the killer was that they had a WHOLE SCREEN devoted just to Twitter.

I mean, this is in Heathrow, whose typical clientele (CLICK)

Page 43: New Assumptions for Designing for the Social Web

Photo by Erin SiffingI wouldn’t imagine would be all that into Twitter.... But then again, I could be wrong.

But I think underlying this is the fact that people and their friends are online.

Page 44: New Assumptions for Designing for the Social Web

so clearly you want to make it easy for people to connect with people that they know.

however, what you DON’T want to do, is ask for people’s passwords (CLICK)

Page 45: New Assumptions for Designing for the Social Web

so clearly you want to make it easy for people to connect with people that they know.

however, what you DON’T want to do, is ask for people’s passwords (CLICK)

Page 46: New Assumptions for Designing for the Social Web

in fact, there are even better ways of making use of PUBLIC data to import friends. (CLICK)

For example, by searching over someone’s Twitter friends.

Page 47: New Assumptions for Designing for the Social Web

in fact, there are even better ways of making use of PUBLIC data to import friends. (CLICK)

For example, by searching over someone’s Twitter friends.

Page 48: New Assumptions for Designing for the Social Web

Lessons

• People want to be where their friends are

• Make it easy to bring friends in from elsewhere

• Don’t ask people for their passwords!

* People want to be where their friends are* Make it easy to bring friends in from elsewhere* Don’t ask people for their passwords!

Page 49: New Assumptions for Designing for the Social Web

3.Email is the new fax machine

Not long ago, the fax machine was the darling of industry.

All kinds of business was conducted over telephone lines, sending data at whopping speeds up to 33.6 kbit/s. (CLICK)

Page 50: New Assumptions for Designing for the Social Web

Photo by Fenchurch!but those days are over.

and that might be the case for email too as well. (CLICK)

Page 52: New Assumptions for Designing for the Social Web

in its place, we’re seeing people use social network-based messaging and instant messaging services like MSN and AIM, even Twitter.

Page 54: New Assumptions for Designing for the Social Web

One useful anecdote... my girlfriend Brynn has a friend named Celea who she used to babysit for and is now 15.

They hung out last weekend and Brynn talked to her about how she keeps in touch with her friends. She has unlimited SMS plan... but can't make phone calls. She says "twitter doesn't exist for her".

It’s a whole new world which demands thinking beyond email.

Page 55: New Assumptions for Designing for the Social Web

Crusher is an evite-killer that gives you quite a few options for controlling how they notify you.

Page 56: New Assumptions for Designing for the Social Web

FriendFeed similarly gives you a good deal of control, including email, but also offering IM and desktop notification.

Page 57: New Assumptions for Designing for the Social Web

again, brightkite provides a nice way to control all your notifications with a simple switch.

Page 58: New Assumptions for Designing for the Social Web

Lessons

• Don’t rely on just email to communicate with your customers

• Let your customers specify how they want to be contacted

Page 59: New Assumptions for Designing for the Social Web

4.Discovery will save us all

one of the problems that we have once we make assumptions like people have accounts and friends elsewhere is how we go about asking people for this information. (CLICK)

Page 60: New Assumptions for Designing for the Social Web

we end up overwhelming the user with choices — so what does someone do here when they have a google, yahoo and AOL account?

Page 61: New Assumptions for Designing for the Social Web

what if people really just want this?

Page 62: New Assumptions for Designing for the Social Web

what if people really just want this?

Page 63: New Assumptions for Designing for the Social Web

Photo by Timothy Vogelthis is what we call the NASCAR problem, something that I think we’re going to hear a lot more about.

Page 64: New Assumptions for Designing for the Social Web

And this problem isn’t just related to OpenID. In general it’s increasingly challenging to provide all the possible choices.

now things will get better here, but we have a long way to go.

Page 65: New Assumptions for Designing for the Social Web

Lessons

• Keep an eye out for XRD/LRDD (new discovery protocols)

• Keep in mind that the shotgun approach is painful

all that i can really offer you now is to:

Keep an eye out for XRD/LRDD (new discovery protocols)Keep in mind that the shotgun approach is painful

Page 66: New Assumptions for Designing for the Social Web

5.Cloud computing is upon us

on the heels of discovery, or maybe because of discovery, I think

Page 67: New Assumptions for Designing for the Social Web

c:\

icon by Seedling Designwe’re going from owning our own hard drives with our data... (CLICK)

Page 68: New Assumptions for Designing for the Social Web

http://

icon by Seedling Designto moving our data to the cloud.

Page 69: New Assumptions for Designing for the Social Web

icons by Seedling Design and Fast Iconyou’ve got your youtube, facebook, flickr... no one will need to do backups anymore, but this will have a profound impact on how you design services.

Page 70: New Assumptions for Designing for the Social Web

icons by Seedling Design, etchybrid applications like this essentially require a connection to function.

Page 71: New Assumptions for Designing for the Social Web

and we’re even seeing this creep into desktop applications like Keynote where there is now a Share menu... that I imagine will slowly replace the File menu (like the fax machine).

Page 72: New Assumptions for Designing for the Social Web

icon by Seedling Designwhich brings me back to openid.

combined with discovery, I believe that you will use your OpenID as a universal pointer to all of your services, so when a great new web applications launches, you simply sign in, provide authorization and BOOM, you can get to work.

this is how cloud computing will be put to work for us.

Page 73: New Assumptions for Designing for the Social Web

6.People want to share

Page 74: New Assumptions for Designing for the Social Web

facebook has made it their mantra that they want to make it easy for people to share.

Page 75: New Assumptions for Designing for the Social Web

turns out that if you give people a good amount of control over how they share their data (CLICK)

Page 76: New Assumptions for Designing for the Social Web

they’re more likely to share more of it.

Page 77: New Assumptions for Designing for the Social Web

on the flip side, if software doesn’t have sharing built in, i think it’s broken.

this is from google spreadsheets... this is why Microsoft Office is going to ultimately fail unless they really move towards a web-friendly, open sharing model.

Page 78: New Assumptions for Designing for the Social Web

Lessons

• Sharing is a core feature of social applications

• Giving people good privacy controls and sane defaults is critical to getting people to share

• Software that doesn’t have sharing built-in is broken

• Don’t rely on proprietary/platform-specific sharing mechanisms; embrace the web

* Sharing is a core feature of social applications* Giving people good privacy controls and sane defaults is critical to getting people to share* Software that doesn’t have sharing built-in is broken* Don’t rely on proprietary/platform-specific sharing mechanisms; embrace the web

Page 79: New Assumptions for Designing for the Social Web

7.Real identity online is becoming the norm

Page 80: New Assumptions for Designing for the Social Web

Facebook recommendationsNo where is this more obvious than on Facebook.

Here is a list of three people that Facebook has recommended to me.

The second one was suggested because we went to the same high school. Kind of a stretch, right? I mean, what is that in the photo? A pillow? I have no idea WHO SHE IS

Page 81: New Assumptions for Designing for the Social Web

So let’s say I actually dive in and ask Facebook to list ALL the people it thinks I might know... this is where it gets interesting.

(click)

Now, here I see someone I know. I’ve met Eric in person; I could probably add him as a friend... but is it really him? It’s not like I have some shared secret with him to verify that this is actually an online representation of his...

Page 82: New Assumptions for Designing for the Social Web

So let’s say I actually dive in and ask Facebook to list ALL the people it thinks I might know... this is where it gets interesting.

(click)

Now, here I see someone I know. I’ve met Eric in person; I could probably add him as a friend... but is it really him? It’s not like I have some shared secret with him to verify that this is actually an online representation of his...

Page 83: New Assumptions for Designing for the Social Web

so I decide to do a search — and lo, out of 444 results, he comes up first. Sure, but this is the same guy from the previous page.

(click)

If we have 63 mutual friends, well, that’s starting make this more plausible...

Page 84: New Assumptions for Designing for the Social Web

so I decide to do a search — and lo, out of 444 results, he comes up first. Sure, but this is the same guy from the previous page.

(click)

If we have 63 mutual friends, well, that’s starting make this more plausible...

Page 85: New Assumptions for Designing for the Social Web

Ok, now I’m feeling pretty confident. In lieu of a shared secret between us, a familiar social graph is a reasonable substitute. Get that: by revealing one’s social connections I get closer to someone’s real identity.

Page 86: New Assumptions for Designing for the Social Web

your social graph is essentially a kind of identity fingerprint for people who know you and know who you know.

but this is really only possible because my mutual friends shared their identities first.

Page 87: New Assumptions for Designing for the Social Web

@factoryjoe

so some of you might know that I use “factoryjoe” as my username on the web.

But, no one in the real world has any frigging clue who “factoryjoe” is, especially without context.

And so people have come up to me and called me “Joe” without even thinking about it.

This online identity was becoming better known than me!

Page 88: New Assumptions for Designing for the Social Web

@factoryjoe@chrismessina

So I killed it. At least on Twitter. And now I’m just @chrismessina.

Like I was before, and always have been.

But I’ve seen other people do the same thing since I made this change.

And it looks like it’s only becoming more common.

Page 89: New Assumptions for Designing for the Social Web

Let’s take a look at another example.

Compare the chat list on the left with the one on the right.

With AIM, you’ve got all these foreign-looking usernames... whereas on the right you have real names.

CLICK - focus on pirillo

[talk about Facebook’s early decision to swear off usernames]

Page 90: New Assumptions for Designing for the Social Web

Let’s take a look at another example.

Compare the chat list on the left with the one on the right.

With AIM, you’ve got all these foreign-looking usernames... whereas on the right you have real names.

CLICK - focus on pirillo

[talk about Facebook’s early decision to swear off usernames]

Page 91: New Assumptions for Designing for the Social Web

“l0ckergn0me”vs.

Chris Pirillo

understand that this DESIGN decision was as important as Flickr’s public-by-default decision.

Heck, I don’t even know what a “locker gnome” is. But here’s the change.

Page 92: New Assumptions for Designing for the Social Web

Eventboxand you can see this in software like eventbox

Page 93: New Assumptions for Designing for the Social Web

Eventboxwhy does this option even exist?

This to me proves that we are in a transitional period, from assumed aliases to one of real, public, transparent identities.

Page 94: New Assumptions for Designing for the Social Web

Eventboxwhy does this option even exist?

This to me proves that we are in a transitional period, from assumed aliases to one of real, public, transparent identities.

Page 95: New Assumptions for Designing for the Social Web

Self-actualization

Esteem

Love/belonging

Safety

Physiological

morality, creativity,

spontaneity, problem solving, lack of prejudice,

acceptance of facts

self-esteem, confidence, achievement, respect of others,

respect by others

friendship, family, sexual intimacy

security of: body, employment, resources, morality, the family, health, property

breathing, food, water, sex, sleep, homeostasis, excretion

Maslow’s Hierarchy of Needsnow, I think this what this means is that we’re seeing a shift to using real identity because the social web is becoming a increasingly important piece of many people “self-actualization”.

self-actualization is from mazlow’s hierarchy of needs and is at the top of the pyramid here.

Page 96: New Assumptions for Designing for the Social Web

even places like MySpace, where pseudonymity reigns is moving in this direction...

Page 97: New Assumptions for Designing for the Social Web

even places like MySpace, where pseudonymity reigns is moving in this direction...

Page 98: New Assumptions for Designing for the Social Web

even to the point where sites are allowing you to VERIFY your identity. this is huge.

Page 99: New Assumptions for Designing for the Social Web

even to the point where sites are allowing you to VERIFY your identity. this is huge.

Page 100: New Assumptions for Designing for the Social Web

Lessons

• Facebook is causing a shift in how peoople feel about identity online

• Real identity can provide for more transparency and accountability; it can incentivize good behavior

• Leverage real life attributes to improve your service

Page 101: New Assumptions for Designing for the Social Web

8.Connectivity is increasing

Page 102: New Assumptions for Designing for the Social Web

people want to know what’s going on RIGHT now and services like Friendfeed, Facebook and of course Twitter are rising to meet that challenge.

Page 103: New Assumptions for Designing for the Social Web

but when everyone is publishing, it’s hard to get to the good stuff.

we have primitive tools to search over this corpus, but it’s the early days.

Page 104: New Assumptions for Designing for the Social Web

i think this will have some unintended consequences though.

the “techmemization” of content... where if you don’t respond to something AS IT’S HAPPENING, you’ll miss the boat.

hemispheric effect -- when the other half of the world is sleeping...

Page 105: New Assumptions for Designing for the Social Web

Lessons

• Half-life of digital information is decreasing

• Conversations are becoming more contemporaneous (Techmemization)

• Beware of the “hemispheric effect”

• We’re seeing the rise of the real-time web

Page 106: New Assumptions for Designing for the Social Web

9.The stream is the new hallmark of a social app

Page 107: New Assumptions for Designing for the Social Web

Feed formats like ATOM and RSS were designed with blog posts in mind, but people are doing a lot more on the web today, beyond blogging.

Page 108: New Assumptions for Designing for the Social Web

streams are great because they allow people to learn about and discover what other people are doing and then model the same behaviors

Page 109: New Assumptions for Designing for the Social Web

consider the basic nytimes homepage. it doesn’t provide me with a whole lot of social hooks to get into this content... except if you look at the header here... (CLICK)

you can see that they’re finding clever ways to highlight activity on the site.

Page 110: New Assumptions for Designing for the Social Web

consider the basic nytimes homepage. it doesn’t provide me with a whole lot of social hooks to get into this content... except if you look at the header here... (CLICK)

you can see that they’re finding clever ways to highlight activity on the site.

Page 111: New Assumptions for Designing for the Social Web

another great site that’s all about the stream is called Enjoysthings.

it;s like friendfeed but with it’s own flare.

Page 112: New Assumptions for Designing for the Social Web
Page 113: New Assumptions for Designing for the Social Web
Page 114: New Assumptions for Designing for the Social Web

Lessons

• People are doing more than just blogging.

• Consider an activity-centric model for your site.

• Show what people are doing on your site.

• Streams are a great way to promote social discovery.

Page 115: New Assumptions for Designing for the Social Web

10.Assume that your data will flow

Page 116: New Assumptions for Designing for the Social Web

now that we have connected people’s accounts, the next thing that we need to work on is getting the data to flow...

Page 117: New Assumptions for Designing for the Social Web

and so because of this, you need to think about how your content is going to look when it goes offsite.

Page 118: New Assumptions for Designing for the Social Web

Lessons

• Design your content to move off-site

• Think about the design of atomic content that is self-contained

• Again, provide good privacy controls and settings: keep the user in control

Page 119: New Assumptions for Designing for the Social Web

Review

Page 120: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

Page 121: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

Page 122: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

Page 123: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

4. Discovery will save us all

Page 124: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

4. Discovery will save us all

5. Cloud computing is upon us

Page 125: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

4. Discovery will save us all

5. Cloud computing is upon us

6. People want to share

Page 126: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

4. Discovery will save us all

5. Cloud computing is upon us

6. People want to share

7. Real identity online is becoming the norm

Page 127: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

4. Discovery will save us all

5. Cloud computing is upon us

6. People want to share

7. Real identity online is becoming the norm

8. Connectivity is increasing

Page 128: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

4. Discovery will save us all

5. Cloud computing is upon us

6. People want to share

7. Real identity online is becoming the norm

8. Connectivity is increasing

9. The stream is the new hallmark of a social app

Page 129: New Assumptions for Designing for the Social Web

Review1. Most people already signed up elsewhere

2. Their friends are online

3. Email is the new fax machine

4. Discovery will save us all

5. Cloud computing is upon us

6. People want to share

7. Real identity online is becoming the norm

8. Connectivity is increasing

9. The stream is the new hallmark of a social app

10. Assume that your data will flow

Page 130: New Assumptions for Designing for the Social Web

so those are 10 new assumptions for designers of the social web.

(CLICK) but i’ve got 5 more to give you.

Page 131: New Assumptions for Designing for the Social Web

+5

so those are 10 new assumptions for designers of the social web.

(CLICK) but i’ve got 5 more to give you.

Page 132: New Assumptions for Designing for the Social Web

location: think about designing your service to take advantage of location.tara talked about this, but expectations are rising for customer service.

Page 133: New Assumptions for Designing for the Social Web

11. Location, location, location

location: think about designing your service to take advantage of location.tara talked about this, but expectations are rising for customer service.

Page 134: New Assumptions for Designing for the Social Web

location is coming to the browser as well.

Page 135: New Assumptions for Designing for the Social Web

customer service: alaska airtrustworthy relationships improve over time (pandora, last.fm)people aren’t obsolete: mturk, aardvarkbrowsers are getting more powerful... so the web apps we use will become more compelling.

Page 136: New Assumptions for Designing for the Social Web

11. Location, location, location

customer service: alaska airtrustworthy relationships improve over time (pandora, last.fm)people aren’t obsolete: mturk, aardvarkbrowsers are getting more powerful... so the web apps we use will become more compelling.

Page 137: New Assumptions for Designing for the Social Web

11. Location, location, location

12. Expectations for customer service are rising

customer service: alaska airtrustworthy relationships improve over time (pandora, last.fm)people aren’t obsolete: mturk, aardvarkbrowsers are getting more powerful... so the web apps we use will become more compelling.

Page 138: New Assumptions for Designing for the Social Web

11. Location, location, location

12. Expectations for customer service are rising

13. People will reward trustworthy relationships with service providers that improve over time

customer service: alaska airtrustworthy relationships improve over time (pandora, last.fm)people aren’t obsolete: mturk, aardvarkbrowsers are getting more powerful... so the web apps we use will become more compelling.

Page 139: New Assumptions for Designing for the Social Web

11. Location, location, location

12. Expectations for customer service are rising

13. People will reward trustworthy relationships with service providers that improve over time

14. Just because we have more technology doesn’t mean that people are becoming obsolete!

customer service: alaska airtrustworthy relationships improve over time (pandora, last.fm)people aren’t obsolete: mturk, aardvarkbrowsers are getting more powerful... so the web apps we use will become more compelling.

Page 140: New Assumptions for Designing for the Social Web

11. Location, location, location

12. Expectations for customer service are rising

13. People will reward trustworthy relationships with service providers that improve over time

14. Just because we have more technology doesn’t mean that people are becoming obsolete!

15. Browsers are about to get a lot more powerful

customer service: alaska airtrustworthy relationships improve over time (pandora, last.fm)people aren’t obsolete: mturk, aardvarkbrowsers are getting more powerful... so the web apps we use will become more compelling.

Page 141: New Assumptions for Designing for the Social Web

The role of standards

before i close out, i want to take a moment to highlight the role and importance of standards here for designing for the social web.

Page 142: New Assumptions for Designing for the Social Web

A standard in practice is worth more than a standard in theory

but adoption of these technologies is key.

Page 143: New Assumptions for Designing for the Social Web

Ubiquity of a standard allows an industry to move the level of

competition to a new layer

Photo by grendelkhanthe reality is, you don’t want to compete on the level of social apps that exist today.

we want to move up to a higher level of competition by commoditizing aspects of the social web that are hard today, but are also basic or fundamental.

Page 144: New Assumptions for Designing for the Social Web

creating new opportunities for innovation on user experience

Photo by Chris Metcalfin so doing, we create new opportunities to compete on the basis of offering better service and experience without relying on user lock-in.

Page 145: New Assumptions for Designing for the Social Web

vCalendar

and indeed, one of the best examples of the power of standards to change an industry is the iphone.

it is the benefactor of years of open standards development.

Page 146: New Assumptions for Designing for the Social Web

International Mobile Telecommunications-2000 (IMT-2000)IEEE 802.11 (WiFi)

JPEGShort Message Service (SMS)

MPEG-4 Part 14, ISO/IEC 14496-14:2003 (MP4)

MPEG-1 Audio Layer 3 (MP3)

vCalendar

Bluetooth

HTTP, CSS, JS, etc

vCard, etc

SMTP, IMAP, POP3

SQLite, TXT

and indeed, one of the best examples of the power of standards to change an industry is the iphone.

it is the benefactor of years of open standards development.

Page 147: New Assumptions for Designing for the Social Web

Building the social web

Page 148: New Assumptions for Designing for the Social Web

this is really the premise behind the Diso Project:

to make it make it easier to build social experiences on the web

by deriving standards and formats from popular trends.

Page 149: New Assumptions for Designing for the Social Web

Diso Components*

*subject to change(DON’T CLICK)

identity & profile

discovery & access control

contacts & friends

activity streams

messaging

groupings & shared spaces

Page 150: New Assumptions for Designing for the Social Web

1. identity & profile

2. discovery & access control

3. contacts & friends

4. activity streams

5. messaging

6. groupings & shared spaces

Diso Components*

*subject to change(DON’T CLICK)

identity & profile

discovery & access control

contacts & friends

activity streams

messaging

groupings & shared spaces

Page 151: New Assumptions for Designing for the Social Web

Our challenge is to build technologies that enhance the network and serve people so that they in turn can build better and richer societies.

BECAUSE

Our fundamental challenge is to build technologies that enhance the network and serve people so that they in turn can build better and richer societies.

Page 152: New Assumptions for Designing for the Social Web

fin.

[email protected] • @chrismessina • factoryjoe.com

Typeface: FTF Flama™ by Mario FelicianoColor palette: oddend by martin

so that’s it. questions?

Page 153: New Assumptions for Designing for the Social Web

fin.

[email protected] • @chrismessina • factoryjoe.com

Typeface: FTF Flama™ by Mario FelicianoColor palette: oddend by martin

so that’s it. questions?