FOWA: Enterprise Adoption of Social Software (Suw Charman) [en]

[fr] Notes prises à l'occasion de la conférence Future of Web Apps (FOWA) à Londres.

*Here are my live notes of this [Future of Web Apps (FOWA)](http://www.futureofwebapps.com/) session. They are probably incomplete and may contain mistakes, though I do my best to be accurate. [Suw has written a blog post about her presentation.](http://strange.corante.com/archives/2007/10/05/fowa07b_me_preparing_for_enterprise_adoption.php)*

FOWA 2007 105

Suw is a freelance consultant, has done a lot of work with businesses and vendors. Guide on getting your stuff used by businesses, based on her experience.

A couple of areas to think about:

– tech readiness? does our tool work?
– support readiness? are we ready to provide support to our customers, and how they will adopt our tool and convince people in their business to adopt the tool?

Two sides of the same tool.

Important: make sure your tool is really ready. If it’s still buggy, if the interface or language is confusing, don’t try to sell it into enterprise. Get more funding first. You only get one chance in enterprise. They won’t come back to see where you’re at.

FOWA 2007 106

Incremental improvements based on user feedback won’t work in businesses. They want something that works now, and regular but not-too-frequent updates. Stability.

Have a process for feature requests. Difference between big vendors (MS, Oracle) “this is what we’re giving you, deal with it” and small vendors.

Pilots aren’t an opportunity to do user testing. They’ll shy away if they feel they’re being used as guiney-pigs.

Don’t assume simple tools will automatically get adopted. People very resistant to use software. They don’t use software because it’s cool. They just want to get the job done, and will find ways to work around the tools they’re given.

Where do you start? Try to figure out what businesses want from you as a vendor, and your tool.

– integration with their existing systems, single sign-on, active directory, LDAP
– very concerned about security: “can our employees use this and put data in it and have that data be safe from accidental stupidness or prying eyes?” Technical security and user stupidness security (delete everything by mistake). Big plus for wikis, which have history. Disaster recovery: offices burn down, how will you help them retrieve their data

Understanding time scales. It can take months for things to happen. Lots of things can get in the way of adoption, even with vocal evangelists inside. Contracts, lawyers, packaging…

– be aware of internal political rankings (stakeholder management)
– be flexible about how you intend to sell into business. You might end up having to host your service (very different from selling a chunk of software). Trojan mouse solutions.
– be prepared for runaway success. Can you scale? Really? Quickly? Administration can turn around from “against it” to “we want this everywhere, now!” in the space of weeks
– be prepared for failure — understand what happened, and have processes in place so that you can learn from failure, but possibly not the same way. Try and fail in new and innovative ways.

Businesses are quite happy to spend money on hardware, software, but not really on operational (people) stuff. Bundle in your support costs into your selling price. If you do an unsupported package, they’ll take that, and you’ll still get the calls. You need to make sure you can afford to help your client get the best out of your tool. How will you be responsive? How will you deal with your contacts in the business, and all the (possibly tens of thousands) of people in the business using your tool?

Sales! One case where a business tried to get through to the sales people to buy, and didn’t get a response. Had to call the CEO! Have someone available to talk to a client.

How are you going to explain your tool to the people who are going to use it? You *need* an adoption strategy. No use in just giving people your tool. *steph-note: as I say, [throwing blogs at people doesn’t make them bloggers](http://climbtothestars.org/archives/2007/09/24/how-blogging-brings-dialogue-to-corporate-communications/).* What kind of materials are you going to provide them with?

A good place to start: **pilots**. Groups of like people. Who are groups of people who might benefit from this? Case with wiki: PAs and secretaries, for example. People like very specific use cases. Not good at generalising. Who are you talking to and what do they need from your tool?

**Adoption isn’t a business goal.** Running the business is the business goal. You need to meet both the wider business goals and the individual people’s goals.

**People don’t use documentation.** They don’t click help. They ask human beings instead. There is a lot of informal and semi-formal learning going on in businesses. 80% is informal, it seems. Formal learning, training courses aren’t effective. How can you provide ad hoc support? IRC channel? Social collaborative learning tools? (blogs, wikis)

**Centralised support** is important for the people using the tool. If the company is going to take over that role, they’ll need the materials for it. Make your material user task oriented, not software task oriented. “This is how you do a meeting agenda in the wiki.” Not “this is how you make a page”. Present it to them on a plate.

A qualitative leap needs to be made between old and new things, even if the new things aren’t so much more complicated. That leap can be difficult. But at some point, when enough people in the organisation are using the tool, they start helping each other. Provide the materials for that. Giving people the confidence that they know how it works.

Don’t try to make it up as you go along. **Plan in advance.** Bring people in. You don’t have to do it all alone (materials, etc).

[More about this!](http://tinyurl.com/zbnfq) Important: both management and grassroots buy-in. Balancing top-down with bottom-up approaches.

Q: tips for demonstrating tool usefulness?
A: work on the use cases. ROI: investing time and money and getting something in return. Important to understand those metrics. Careful, metrics don’t tell you what an individual’s use of something is. One of the problems with social software is that it can sound a little fluffy. “It improves collaboration.” But people think like “I want it to improve productivity to the point I can fire someone.”

Q: is it different for open source tools?
A: enterprises can be very wary of it (how will we get support?) even though there is a huge amount of open source being used. The more technically savvy they are, the more likely they’ll go for it, and the more business-oriented, the less. No hard and fast rules.

Similar Posts:

Suw Charman at Google: Does Social Software Have Fangs? [en]

[fr] Mes notes de la conférence que mon amie Suw a donné chez Google aujourd'hui.

*Here are the notes I took of [Suw Charman](http://chocnvodka.blogware.com/blog)’s talk. They’re not necessarily well-constructed, and may even contain inaccuracies. I did my best, though!*

It’s trickier than it seems when using blogs in business.

Will talk about using blogs and wikis internally. What can you do when things go a bit wrong?

Software is easy to install, so companies install it, some people start using it, but they’re not getting everything they can out of it.

Wikis are for collaboration, blogs are for publishing. Clear how the technology works, but not clear why some people don’t adopt social software internally for their work.

Suw Talks at Google

Reasons?

Low-level fear of social humiliation. How are they going to come across to their peers and bosses? Fear of making mistake. People don’t realise they’re afraid, they just feel a bit uncomfortable talking /publicly/ to their collegues. E-mail is different because it feels private, it’s 1-1 communication. You’re not exposing yourself as much. People become “shy” when you give them a very public place to work.

Also, some people aren’t comfortable in writing. Some are better talkers than writers, and are not comfortable writing in a semi-formal environment. E-mail is more informal. Blogs and wikis are perceived as requiring a higher level of writing skill. Again, people don’t admit to this.

This doesn’t happen in very open organisations, but often if permission isn’t explicitly given to use such tools, that will really get in the way. “Blogs as diaries”, etc — psychological mismatch. What the boss /thinks/ blogs are, and what they are used for in business.

Trust in the tool. “So you mean anybody can change my stuff?” for wikis. “Can I stop them?” Not comfortable trusting the content placed in such tools, and the tools themselves. “What if the tool loses everything?”

Will the tool still be around in one or two years? If we pour our data into this wiki, am I going to just lose everything if management pulls it down?

Many people just don’t see the point. See social software as something they need to do /in addition/ to what they’re already doing. Parallel with KM disasters.

Biggest problem: how to get people involved. Two basic routes: top-down, and bottom-up.

Top-down can work all right if you have a hierarchical company and control what people are doing. Will work while managers go “you have to use this, or…” but people will abandon it when pressure disappears.

Bottom-up. Trojan mouse. People start using stuff because they think it’s useful, and it spreads through the organisation. Grassroots can be very powerful in getting people to use this kind of software. Risk: incompatible software, duplication of efforts, managers closing things down.

Go for the middle way: support from above (yes, you can use that, we encourage you to use this) but rely on the “bottom”, people using the software to have it spread.

Adoption strategy:

1. Figure out who your users are, not globally, but as small groups with shared needs. You need to understand what these people do every day. Good place to start: look at how they’re using e-mail. E-mail is a very abused tool. CCing just to let you know stuff — we get a huge amount of e-mail for things we don’t really need. Or things like conversation often happen badly in e-mail: somebody missing from the CC list, or somebody replying to one instead of all. And you can’t just access somebody’s inbox. People send out attachments to half a dozen people, and they all send back with comments, need to merge. There are places where these things can be done better/quicker. Identify who is influential within your area — supernodes — who can help you spread adoption, push a tool from something that is used locally to something that is used business-wide.

2. How is this going to make their lives easier? Some use cases can be very small, not very impressive, but very practical. E.g. coming up with a presentation in a short time by using a wiki. Doing that by e-mail wouldn’t work, not in four hours. Another thing is meeting agendas. Put it on the wiki instead of sending out agendas in Powerpoint, Excel, Word… The minutes can go on the wiki too. Looking for places where conversations are fragmented => wiki. Blogs: look for people publishing stuff on a regular basis. Start with those simple use cases, then these practices will spread to other uses. People are bad at generalising from a high level (ie, wikis are for collaboration — d’uh?)

3. Help material on the wiki won’t help people who aren’t comfortable with it. Print it out! Or people are so used to hierarchy, that they recreate it in the wiki, even though it might not seem necessary. If this is the behaviour they feel comfortable with, then we’ll enable this. Come up with naming schemes to make this possible. Be very open to letting the people use these tools the way they want to: coffee rotation, sports page, etc.

4. At one point, requests for help etc. dropped. Critical mass had been reached. People were self-organising.

Top-down stuff: Suw’s more in favour of bottom-up, but often needs to be married to top-down.

Important thing: having managers who accept the tools. Some people can really get in the way of this kind of adoption project. Work around them in a way.

Managers who are the most successful in getting their people to use these tools are those who are the most active, who blog, use the wiki, encourage their people to use it. E.g. manager who would put everything on the wiki and send one-liner replies to e-mails containing questions about this with pointer to the wiki.

Use the tools regularly if possible. Easy to slip back into the old ways, but go back to using the tools.

Beware: adoption and usage is not the goal. Getting your job done is.

Q: what about privacy and secrecy?
A: easy to create little walled gardens in a wiki. also, everything that happens on a wiki is logged.

Need for wiki-gardners. Most of the problems are not technological, but cultural. How people react to the environment. Social vs. hierarchical organisation.

Tool recommendation: depends a lot on who is going to use it. E.g. MediaWiki sets business users running screaming, because it doesn’t look like Word. Happier with SocialText, maybe. What is the users’ comfort zone regarding tools? What about the existing IT infrastructure? Businessy users tend to like shiny stuff, branded, Word-like. More technical users tend to be happy with bland-looking things that might even be broken.

Q: external use cases for blogging?
A: “blogs are diaries” => scary for businesses. Some very mundane use cases: Disney used blogs to announce events (threw away their customer crappy tool). Personal knowledge management — “what have I been doing, what stuff do I need to find again?” Person who has to report on what he’s doing: blog about it, and let boss read. Competitive intelligence. What’s happening out there/in here. Also, “oh this is interesting!” — people blogging about social things, not business-related things. Actually good, allows people to get to know each other. *steph-note: I think Google understands that.* We tend to underestimate the importance of social relationships in business.

**Update, July 3rd: the video**

Similar Posts:

Groups, Groupings, and Taming My Buddy List. And Twitter. [en]

[fr] Long, long billet sur la notion de "groupe" en social software et les différentes formes que peut prendre cette notion. Trop raide pour traduire ou résumer, navrée.

*Warning: very long post. Not proof-read. Hope it makes sense. Mostly dictated, so if you see funky stuff that isn’t a typo and really looks weird, try reading out loud.*

“Group” is a word which is thrown around a lot in the social software/social tools/social networking/social thingy arena. Flickr has [groups](http://www.flickr.com/help/groups/). Google has [groups](http://groups.google.com/). So does [Yahoo!](http://groups.yahoo.com/), of course. CoComment is [working on groups](http://raphaelbriner.electronlibre.com/?p=89#comment-42) (and have been for ages). Twitter is [being advised against them](http://twitter.com/missrogue/statuses/49364082) (I [second that](http://twitter.com/stephtara/statuses/49408962)). [YouTube](http://www.youtube.com/groups_main), [Facebook](http://www.facebook.com/help.php?page=17), [Orkut](http://www.orkut.com/), [Last.fm](http://www.last.fm/help/faq/?category=Groups#1012) — “groups” seem to be a compulsory feature for any 2.0 service today. It’s very natural, too: we need to break down large communities in order to be able to function within them (see [The Dunbar Number as a Limit to Group Sizes](http://www.lifewithalacrity.com/2004/03/the_dunbar_numb.html) for some thinking around this issue). Unfortunately, it’s also a result of all the 2.0 “community” buzz stuff floating around: “implement groups, and your tool/app will have communities!”

Like many overused words, “group” is actually used in different contexts to mean different things, and this brings about quite a lot of confusion. “How to implement groups” is a theme that I’ve had a few exchanges about with both the coComment and the Twitter people, and I think it’s an impossible question to answer unless we have cleared up the vocabulary a little to start with.

I would like to distinguish between three types of “groups”, which are often all called “groups”, but which have different characteristics and different uses:

– “groups” or “shared-interest groups” (“Flickr-groups”)
– “groupings” (“ad hoc assemblages of people with similar interests” — Stowe Boyd)
– “contact groups” (organising my contacts)

#### Shared-Interest Groups

This is usually what people think of when they say “group”. It is a set of people who come together to (hopefully) form a community around a shared interest. Usually, one chooses to join such groups. Belonging to the group gives you some kind of special connection to other members (which you might not know, but you now have one thing in common with), and allows you to “do things” you would not be able to do if you were outside the group. (For exemple: send a message to all the people in the group, or post a photo to a shared album.)

Typical examples of this kind of group are Yahoo! Groups or Flickr Groups. People join these groups to be able to build something, share something, or simply hang out with the other members of the group. However, if you look at the way people use this kind of group in communities which are more “social networking”-oriented, like Facebook or Orkut, you will see that they tend to not be that active *inside* the groups, but that they use them a bit like “tags” to advertise their interests. These groups are therefore not only a way of connecting with other people, but also a way of saying something about yourself. And in some communities, the latter is clearly more important.

#### Groupings

Shared-interest groups are a bit limited when it comes to making your application truly “social”, as I heard Stowe Boyd point out during his [Building Social Applications Workshop](http://climbtothestars.org/archives/2007/02/07/stowe-boyd-building-social-applications/) at the LIFT conference earlier this year. Now, I’ve been through Stowe’s blog to try to serve you with a nice citation that explains exactly what he means by “groupings”, and haven’t really found anything that satisfied me. (As far as I can see, Stowe first talks about groupings in [In The Time Of “Me First”: IBM Slowr?](http://www.stoweboyd.com/message/2007/01/in_the_time_of_.html), and explains a bit more in [In The Time Of “Me-First”: Stikkit](http://www.stoweboyd.com/message/2007/01/in_the_time_of__1.html).)

Here’s the definition Stowe gives in [his workshop slideshow, slide 24](http://www.slideshare.net/stoweboyd/building-social-applications):

> Groupings: ad hoc assemblages of people with similar interests.

Stowe Boyd

As I understand it, groupings are things that “happen” rather than things that people elect to join or build. Groupings emerge within a social network because of the way people are using it. Groupings are things that occur naturally and all the time inside networks, but the tricky part will be to decide which groupings to make visible to the users and how.

The first time I really encountered this type of automatic grouping of users based on their behaviour was in Last.fm. Last.fm tells you who your “[neighbours](http://www.last.fm/help/faq/?category=User+Profiles#10113)” are, by picking out people who have similar music-listening habits as yours. So, in last FM, not only can you see [my contacts or “friends”](http://www.last.fm/user/Steph-Tara/friends/), people **I have elected to be connected to** in some way in the online world of last FM even though our musical tastes may have little in common, but you can also see [my neighbours](http://www.last.fm/user/Steph-Tara/neighbours/), people I probably do not know and definitely **have not chosen to be connected to**, but which I am inevitably connected to because we share similar musical tastes.

Isn’t this a more interesting way of interconnecting people than having them explicitly join groups saying “I like this or that artist”? CoComment also has a [neighbours feature](http://www.cocomment.com/you/community) (I like to think that I’m for something in its existence, as it was one of the first suggestions I made and pushed for about a year ago), but unfortunately you can’t see other people’s neighbours or do much with your neighbourhood. The value groupings will add to your tool or service will depend greatly on which groupings you decide to make visible to your users, what doors being part of a given grouping opens up for the user, basically, what you choose to **do** with these groupings (display them? Nice, but not enough in most cases).

With all this in mind, if you are trying to figure out “the best way to implement groups” for your application/tool /2.0 service, here is what I would recommend. Start by taking a long hard look at how your application already organises users into possible groupings. What can you make visible? What is interesting? What doors could you open to people who are inside the same grouping? What are your users going to want to do with these groupings?

Some examples of groupings could be:

– people who have listened to a particular song regularly over the last six months
– people who favourite my photographs on Flickr
– people who subscribe to a given blog
– people who have commented on a given post or blog
– people who have marked me as a contact
– people who use a given tag
– people who comment on posts or photographs tagged “cat”
– people who ordered this or that book on Amazon
– people who have been marked as a contact by somebody
– people who have joined a certain group…

As you can see, the definition of “grouping” is much wider than the definition of “group”. “Groups” are a small subset of “groupings”, which have a performative flavour, as you become part of them by the simple act of stating that you desire to be part of them.

The example before last is a little bit problematic in my sense. Most of the time, a user ends up belonging to a grouping because of the way he or she uses the system. It is your actions which make you part of a grouping. Here, you are not part of a grouping because of something you have done, but because of what somebody else has done to you (added you to her contacts). I have been hesitant for this reason to consider “being somebody’s contact” as a grouping, but if you look at it from the point of view of the social network, it is still a way in which “usage” organisers to people who are part of the network.

The existence of these “passive groupings” (from the point of view of the user who is part of the grouping) invites us to go through the looking-glass and examine what goes on from the perspective of the user creating the groupings by making his connection to other users explicit.

#### Contact Groups

I hope that we have now come to accept that networks are asymmetrical. It is not because I have marked you as a contact, that you have to mark me back as a contact too. I think that a great source of confusion is the [general use of the word “friend” in social networks](http://www.thomaspurves.com/2007/02/27/are-we-really-friends-the-trouble-with-buddy-lists-in-social-applications/). There is an emotional component in there that makes it rather difficult to say “well, you might think I’m your friend, but I don’t.” Friendship is supposed to go both ways. “Contact” is a much more neutral word, which is easily understood as meaning “you are, in some way, part of my world here.”

“In what way?” is the big question here. In what way is John part of my world? In what way am I part of his, if at all? I will leave the second of these two questions completely aside in this discussion, for I consider it to be a psychological, emotional, and relational minefield. In our offline relationships, we don’t usually get to know exactly how important we are for our friends or acquaintances, or even love interests. We are treading on eggs, here. And to make things even more delicate, different people use different words to describe the people who are part of their world. These are, in my opinion, human relational issues which are way too delicate to be formalised in a social network without a lot of serious thinking, if they are to be respectful of people’s feelings and meaningful in any way.

The first question, however, is a crucial one. I personally think that it is also the key to managing many privacy issues intelligently. How do I organise the people in my world? Well, of course, it’s fuzzy, shifting, changing. But if I look at my IM buddy list, I might notice that I have classified the people on it to some point: I might have “close friends”, “co-workers”, “blog friends”, “offline friends”, “IRC friends”, “girlfriends”, “ex-clients”, “boring stalkers”, “other people”, “tech support”… I might not want to make public which groups my buddies belong to, or worse, let them know (especially if I’ve put them in “boring stalkers” or “tech support” and suspect that they might have placed me in “best friends” or “love interests”… yes, human relationships can be complicated…)

[Flickr](http://www.flickr.com/help/contacts/) offers a half-baked version of this. I say “half-baked” because it does allow me to introduce *some* organisation in my contacts, but it is not quite satisfying. And regarding what has been said above, this classification is made public — so inevitably, there is no way that it can be satisfying to the person making the classification. It has to remain politically correct. Basically, what Flickr does is allow you to single out certain contacts as “friends” or “family”. This is tame enough, particularly given that the word “friend” has been emptied of much of its meaning by social networks which use it as a synonym for “contact”. What is interesting here is how Flickr uses this classification to help users manage privacy. I can make certain photographs visible only to my friends or my family. I can decide to allow only my contacts to comment. But this kind of control remains quite coarse, because the groups are predefined and may not map well to the way I view my social world and want to manage my privacy.

A more useful way to let a user organise his contacts is simply to let him tag them. [Xing](https://www.xing.com/) does that. Unfortunately, it does not allow one to do much with the contact groups thus defined, besides displaying contacts by tag, which is of course nice, but about as useful as making groupings visible without actually *doing* anything with them.

#### Use more precise vocabulary than “group”

Have you noticed how I’ve been using the word “groups” to speak of this way of classifying one’s contacts? Well, instant messaging software uses the word “group” (“buddy groups”, “contact groups”), and that’s what people are used to. Now, imagine the confusion if somebody says “[Twitter](http://twitter.com) needs groups”, meaning “contact groups”, and the person listening understands it as “shared-interest groups”? **These are two very different kinds of groups. They are organised differently and serve a different purpose.** See why I think we need to stop speaking about “groups” in general and be much more precise with our vocabulary?

– **Shared-interest groups** are groupings that we actively choose to be part of, they are generally public, or at the least, we know who the other members are, and the point of **being part of such a shared-interest group** is to be able to do certain things with the other members, or get to know them.
– **Contact groups** (normally) passive groupings that somebody puts us into, they are generally private, to the extent that one does not know exactly what grouping one is in, and the interest of such contact groups is mainly **for the person creating them**, who can choose to treat the people inside them differently (mainly regarding privacy).
– **Groupings**, defined by Stowe Boyd as ad hoc assemblages of people with similar interests, can actually be understood as a very generic expression, including the two previous ones, to refer to “ad hoc assemblages of people emerging through social network/software/tool usage.” When it is one’s actions which bring him/her into a grouping, we can speak of “active groupings”, and when it is another’s actions, “passive groupings”.

One could probably say that the way in which a social application implements groupings (which are made visible and how, and which actions, features, permissions or characteristics are associated to them) — shared interest groups and contact groups being two particular species of groupings — is going to play an important role in how successful it is, because groupings in general are the key through which users will interact with each other.

Maybe somebody could start working on a taxonomy of sorts for groupings? We already have active and passive, the weird performative ones that are the similar-interest groups, all the contact group stuff, but we could imagine classifying and analysing groupings by looking at what brings one into a grouping: is it interaction of some type with other users? Quantity of something? Centred around one object, or a collection of objects? Is there a time component? Does it involve reciprocity? What kind of pattern of usage is it linked to? We could go on, and on…

#### Case-study: Twitter

Even though this post has been ripening in my head (ew!) since February, the reason I am writing it today is the following twitter from [Tara Hunt](http://horsepigcow.com):

> Advising Twitter (Britt) AGAINST groups (gameable/spammable) and FOR personal lists (solves group messaging)

twitter from Tara

I have [blogged about Twitter](http://technorati.com/tag/twitter?from=climbtothestars.org) quite a few times already, spoken with the Twitter people [when I was in San Francisco](http://climbtothestars.org/archives/2007/01/12/im-really-liking-san-francisco/) and sent them a bunch of feedback and ideas that I haven’t got around to blogging yet (I wonder when I will). This should make pretty obvious that I really really like this service. (So that’s the disclaimer: fangirl.)

If you’re still reading this, your head is probably full of groupings/similar-interest groups/contact groups ideas and concepts. Let’s see how they apply to Twitter. The nice thing about Twitter is that it’s a rather simple application, feature-wise (and that’s one of the things that makes it so nice). So, where are the groupings? Here are some:

– users who are friends with John
– users John is friends with (not the same grouping!)
– users John is following (still another grouping, because of the distinction twitter makes between friends/contacts and the act of “following”)
– users who are following John but he is not following (fans/stalkers, depending on how you look at it)
– users who answer John’s twitters (with @John)
– users who use the word “LIFT07” in their twitters
– …

What makes Twitter great? Well, besides the great online/offline integration through the use of mobile phones, the clean, usable interface, the great people using it and the cats in the servers, one of the things that makes Twitter Twitter (if I may say) is what it does with the grouping “users John is friends with”. Well, it’s pretty simple, in fact, and you’ll probably think I’m pointing out the obvious (but that, in my mind, simply indicates how good a job Twitter have done with it): they display all the twitters of those users in that grouping on one page. Well, yeah, I guess that was the [Obvious](http://obvious.com/) thing to do with that grouping.

Amongst the other types of groupings, one can wonder if Twitter needs to introduce similar-interest groups, or contact groups. I don’t see much of a case for the former, as Twitter is centred around people and relationships rather than the content of their interactions. Twitter is not really about what I’m saying to people. It’s about who I’m talking to. Twitter is precious because it gives me a space in which I can share a little things about my life with anybody who has decided that these little things had some value to them (and that can include non-Twitter users). Twitter it is equally precious because it provides me with a space (and this is where the “what they actually *did* with that grouping” thing comes in) through which I can stay informed of the little things in lives of others that I have decided were meaningful for me.

Which brings me to contact groups. Contact groups could have two purposes for twitter:
– privacy management
– twitter overflow management, particularly on mobile devices.

Without getting into the technicalities involved (and I’m aware they are not straightforward), let’s imagine that I can tag my Twitter contacts. This allows me to give some structure to my online world in Twitter. I can use that structure in two ways: make certain messages visible only to certain people I have chosen (privacy), receive messages on a given device only from certain people (overflow).

Tagging is the best way to create these contact groups. It leaves each user completely free to organise their world how they wish. It allows multiple classification of contacts. Keep the tags private, and personal dramas are avoided. Multiple classification requires establishing rules for when conflicting orders are given. Interfaces (web and mobile) need to be devised to tag contacts, to set message privacy (default, message by message, on/off style), and following behaviour. Not straightforward, of course, but can certainly be done.

Remains the basic question: does this kind of feature address a real need? (For me, it does.) How is it going to change Twitter if it is implemented? (If this can be predicted…) What might happen if it is not implemented? Well, you know, the usual stuff when making a decision.

Similar Posts:

Blogging 4 Business Afternoon Keynote: Michael Steckler [en]

Gossip: casual talking, especially about other people’s affairs.

SN are a large and highly engaged audience, so there is a great advertising and branding opportunity there. Rules?

Blogging 4 Business

75% use SN to keep in touch with family and friends.
62% for being nosey
55% express my opinions
49% meet people with similar interests

*steph-note: totally tuned out I’m afraid. I think the initial idea of viewing social networks as advertising space put me off, to the point I’m not even sure if he’s saying if it’s a good or a bad thing. Today I just feel like telling people to [ride on the Cluetrain](http://cluetrain.com).*

Personal spaces set up by a brand.

How do you get into that personal area?

– understand consumers’ motivations for using social networks
– express yourself as a brand *steph-note: I’m wondering if people shouldn’t just forget about brands a bit — not that they’re totally useless, but branding for branding gets tiring*
– create and maintain good conversations
– empower participants

Participation ecosystem. Recommendations based on personalities.

*steph-note: did a really shitty job of taking notes. I’m getting worse and worse today.*

Early adopters, onine mavens, online connectors (really important!), followers.

How to? create your own community, find influential bloggers, segment existing customers, attack the niche, start the gossip, reward customers… *steph-note: this is exactly the war-marketing vocabulary/mentality [the Cluetrain speaks against](http://cluetrain.com/book/markets.html)… Eek.*

Summary: SN = large and engaged audience => huge opportunity for branded content and advertising, but there are strict guidelines to how to approach this.

Similar Posts:

Blogging 4 Business Conference [en]

[fr] Notes de la conférence Blogging4Business à laquelle j'assiste en ce moment à Londres.

So, unless some miracle happens, I’ll be blogging this day offline and posting it tonight when I get back at Suw’s. There seems to be no wifi provided for conference attendees unless you are willing to shell out £25 for a daily pass. (Actually, it seems there were a certain number of passes available.)

I would honestly have expected an event titled “**Blogging** 4 Business” to be “blog-aware” enough to realise that providing free wifi to connected people will encourage blogging of the event. Granted, most of the people I see in the room are taking paper notes (not that there is anything wrong with that) — this doesn’t seem to be an audience of bloggers. But wouldn’t it be an intelligent move to encourage the blogging public to “do their thing” at such an event?

I missed most of the first keynote and panel, spending time in the lobby chatting with Lee and Livio of [Headshift](http://headshift.com) (my kind hosts today), and [Adam](http://onemanandhisblog.com).

**Panel 1** incomplete and possibly inaccurate notes (they’re more snippets than a real account of what was said, partly because I don’t understand everything — audio and accents)

How do you respond to crisis online? (cf. Kryptonite)

Ged Carroll: In the 90s, faulty lock was broadcast on consumer TV. Mistake: didn’t tell the blogs that they were monitoring what was being said in that space, and that they were working on a solution (they *were* in fact acknowledging the problem, but hadn’t communicated that state of things to the public).

Moderator (Paul Munford?): how do you prevent something like that from being so predominently visible (search etc.)?

Darren Strange: owns his name. Same if you type “Microsoft Office”, his blog comes up pretty quickly too. Blogs attract links, good for search engine ranking.

Question: brands need ambassadors, OK, but where’s the ongoing material to blog about Budweiser?

Tamara Littleton: brand involvement in the site keeps things alive and happening. Reward ambassadors with merchandise.

*steph-note: on my way to London, I was reading the Cluetrain Manifesto (yeah, I’m a bit late on that train) and was particularly inspired by the part about how most of traditional marketing is trying to get people to hear a “message” for which there is actually no “audience” (nobody really wants to hear it), and so ends up coming up with ways to shove it into people’s faces and make them listen. This idea is kind of trotting in the back of my mind these days, and it’s colouring what I’m getting out of this event too.*

Question: transparency is a big thing… “creating ambassadors” (*steph-note: one “creates” ambassadors?!)… where is the space for disclosure?

Tamara Littleton: it’s about creating an environment, not saying “if you do this you’ll get that reward”. Rewards could be access to information about the product. Invite people to take part in something.

Ged Carroll: two types of rewards: merchandise etc, and also reputation-ego. Doesn’t have to be tangible.

Darren Strange: trying to have non-techie people try new releases of Vista, etc. Installed everything on a laptop, shipped it to the people’s house, and gave it to them. “Take the laptop, use it, blog if you want to, write good or bad things, or send it back to us, or give it to charity, or keep it, we don’t really care.” Huge debate about this. Professional journalists will be used to this kind of “approach”, but bloggers are kind of amateurs at this, they don’t know how to react. Disclosure: just state when you received something. *steph-note: and if you’re uncomfortable, say it too!*

**Panel: Lee Bryant, Adam Tinworth, David ??, Olivier Creiche**

*steph-note: got wifi, will publish*

Blogging 4 Business

Lee presenting first. Headshift have quite a bunch of nice products in the social software department. “It aint what you do it’s the way that you do it, and that’s what gets results.” (Bananarama)

Concrete business use cases.

Olivier talking now. “To blog or not to blog?” Simple answer: blog. Serious Eats. Citrix: a lot of knowledge disappeared when people left the company — a lot of knowledge out there that is only waiting to be gathered out of people’s e-mail boxes. Used Movable Type for that.

Another case study: AEP, also wanted to prevent e-mails from being the central repository of company knowledge (e-mails are not shared spaces!) Start small, experimental. Need to find the right people to start with. Another one: Arcelor/Mittal merger. Decided to communicate publicly about the lot of stuff. Video channel. Wanted to be very open about what they were doing and how, and answer questions. Good results, good press coverage.

David: allowing lawyers to share their knowledge and expertise, not just in their offices. Blogs, RSS, wikis allows time-critical sharing of information. *steph-note: like I’ll be publishing this as soon as the panel is over…* Catch things on the fly and make them available over a very short period of time.

Adam: starting to roll out business blogs just to allow communication. Bringing about profound change. *steph-note: very bad account of what Adam said, sorry — audio issues.* Other problems: educational issues. Best to not force people to use this or that tool, but open up. Share. Get people inside the teams to show their collegues what they’re using.

Question (moderator): a lot of evangelising going on in terms of blogs. Do blogs/wikis etc deliver on the promise of breaking down barriers, etc, when it comes to internal communication.

Lee: not a simple black/white situation. It comes down to people. Big problem: people bear a high cost to interact with communication systems and get no feedback. But with social tools (lightweight), we get immediate feedback. Integration with existing corporate systems.

Question: is social media the end of communications as we know it.

Lee: every generation of technology sees itself as a ground-breaker. But they’re all layered on top of each other. We have technology that delivers on the initial promise of the web (equal publication, sharing, etc) *(steph-note: yay! I keep saying that!)*

*steph-note: more northern English please ;-)*

David: now, using the web to create communities of practice, getting lawyers to communicate with people unthought of before.

Question: how do you deal with outdated material.

Lee: with mature social software implementations, any piece of information gathers its own context. So what is relevant to this time tends to come to the surface, so out-dated material sinks down. More about information surfacing when it’s time than getting out-dated stuff out of the way.

David: social tools make it very easy to keep your content up-to-date (which was a big problem with static sites).

Similar Posts:

Musique: bénéfices d'une bonne stratégie internet [fr]

[en] This is a description of the benefits a musician or singer can find in implementing a sound internet ("web2.0-ish") strategy (blogs, social software, online presence...). It's lifted from a project proposal I sent a client recently, but it's in my opinion general enough to be of interest to other people. Oh, and check out SellABand.

Pour une personne faisant carrière dans le monde de la musique, avoir une bonne stratégie internet apporte un certain nombre de bénéfices non-négligeables. J’entends ici par “bonne stratégie internet” le fait de s’ouvrir à la dimension sociale et participative de l’internet vivant (blog, outils de social networking, sites communautaires, etc.) et de se “mouiller” dans cette culture. Expliquer ce genre de chose fait partie de mon travail de [consultante en blogs ou spécialiste(!) de la culture en ligne](http://stephanie-booth.com) (je cherche encore et toujours un moyen concis et efficace de décrire ce que je fais…)

Ce qui suit est une description des bénéfices auxquels pourrait s’attendre un chanteur ou un musicien s’il décide d’investir dans ce média intelligemment. En fait, cet argumentaire est repris presque tel quel d’une [proposition de projet](http://climbtothestars.org/archives/2007/02/07/martin-roell-getting-started-in-consulting-lift07/) que j’ai envoyée récemment à un client. Je le reproduis ici car il est assez général et peut à mon avis intéresser autrui.

#### Un site web facile à mettre à jour et bien référencé

Aujourd’hui, il est indispensable d’avoir un site web qui soit bien référencé et facile à garder à jour. Les outils de blog comme WordPress sont des systèmes de gestion de contenu légers et techniquement relativement faciles à manipuler.

Ils permettent à une personne n’ayant pas de compétences techniques particulières de publier et d’organiser le contenu du site et de le faire croître au fur et à mesure. Le site ainsi construit contient donc aussi bien une partie “blog” (organisée chronologiquement, qui donne en tous temps et un coup d’oeil les informations les plus fraîches) et une partie “classique” organisée hiérarchiquement (pages “contact”, “bio”, “discographie” etc.). Quelques sites construits sur ce modèle: [le blog du CRAB](http://crablog.net), [Groupe Vocal Café-Café](http://cafecafe.ch) et [Vibrations Music](http://vibrationsmusic.com).

De plus, ces outils séparent complètement le design du contenu du site: il est donc très aisé de changer la ligne graphique du site sans avoir besoin de toucher au contenu lui-même. La structure des pages est également telle qu’elle encourage un bon référencement par les moteurs de recherche (accessibilité, balisage sémantique), sans avoir recours à des techniques de SEO (“Search Engine Optimisation”) parfois douteuses.

En deux mots, gérer un site internet avec un outil de blog permet de le mettre à jour soi-même très facilement et garantit un bon placement dans les moteurs de recherche, en fonction du contenu du site bien entendu.

#### Tirer profit de la dimension sociale d’internet pour la promotion

Internet n’est pas juste une plate-forme de publication, à la différence d’un média traditionnel. C’est un lieu de vie, d’échanges, de relations, de bouche-à-oreille et de conversations. Cette dimension d’internet est souvent encore mal comprise et son importance sous-estimée. Avoir un site permettant les commentaires du public en regard des publications (une des caractéristiques du blog) est un premier pas. Il existe des également des dizaines de services, centrés ou non autour de la musique, qui permettent d’avoir un pied-à-terre virtuel dans diverses communautés en ligne. En comprenant les dynamiques sociales en jeu, on peut augmenter encore sa visibilité sur internet et lui donner une dimension plus humaine et personnelle.

Rassembler une communauté sur internet autour de soi ou de son travail ajoute un double bénéfice: la communauté est visible, ce qui peut attirer l’attention de personnes extérieures (médias traditionnels ou organisateurs d’événements) et encourager autrui à la rejoindre; d’autre part, les membres de la communauté sont eux-mêmes au centre de leur “réseau personnel”, leur propre communauté, dans laquelle ils jouent un rôle d’influenceur. Cette dynamique existe hors internet bien évidemment, mais elle est décuplée sur internet par l’absence d’obstacles géographiques et la facilité avec laquelle on peut faire circuler des informations dans le monde numérique.

#### Mettre de la musique à disposition en ligne et favoriser ainsi sa diffusion

Mettre à disposition sa musique en ligne favorise de façon générale sa diffusion, et donne l’occasion à des personnes qui ne l’auraient pas eue autrement de l’écouter et de l’apprécier. C’est la popularité d’un artiste auprès de son public qui va influencer les ventes de CD, et non le contraire. Il est donc intéressant d’une part d’utiliser internet comme véhicule ouvert de diffusion de la musique (afin d’augmenter visibilité et popularité), et également de permettre l’achat de CDs ou d’autres produits via internet, ce qui libère le public des contraintes géographiques. L’utilisation de licences adaptées ([Creative Commons](http://creativecommons.com)) permet de protéger les droits commerciaux tout en encourageant le partage et la diffusion de la musique.

Des sites comme YouTube, consacrés à la publication et au partage de vidéos, ou MySpace, ont déjà eu un impact considérable dans le lancement d’artistes, parfois avec des moyens extrêmement limités. La promotion du matériel ne coûte rien, elle est faite par le public qui lui trouve une valeur suffisante pour le partager avec son réseau.

#### Se former aux nouveaux médias afin d’être autonome et adéquat

Internet est un média (ou une collection de médias) dont une des caractéristiques principales est de contenir une dimension conversationnelle ou participative. Ces médias sont nouveaux et encore relativement mal maîtrisés en général, et ceci d’autant plus que l’on a pas eu l’occasion d’y être exposés passivement en grandissant. Ces nouveaux médias ont également comme caractéristique de remettre l’individu (avec sa personnalité propre) au centre, de favoriser le contact direct en libérant des intermédiaires, et de mettre en avant les valeurs de transparence, d’authenticité et d’honnêteté. Une formation sérieuse à l’utilisation adéquate de ces médias permettra d’en faire un usage efficace et autonome, et également d’éviter des faux-pas dûs à une méconnaissance de la culture en ligne.

Similar Posts:

More LIFT Notes: Sampo Karjalainen, Lee Bryant (and Stowe again) [en]

***As always, can contain inaccurate material.***

#### Sampo Karjalainen

Habbo: hang-out place. You get a character, you can configure it. *steph-note: looks like a very lo-res version of Second Life*

Sampo Karjalainen

There are games inside Habbo.

What makes people come back? People can create their own room/spaces. Can buy furniture (in-game credits), pets, kissing booths, armies, banks. *steph-note: this **really** looks like pixelised Second Life. Question: can you create stuff and objects as you can in Second Life? People seem to be having a ball in Habbo, in any case.*

Playful environment, though people might find it “uncool” to say they’re “playing” in there. A part of unexpected in what people did with Habbo.

Provide building/playing blocks. Intuitive interaction. Get people in the mood for play.

#### Lee Bryant: Collective Intelligence for the Enterprise

Brain Leak

*[Original photo by Violator3 on Flickr](http://www.flickr.com/photos/violator3/93589371/).*

Basic problem: wasting a lot of brain power in large organisations.

Our IT systems don’t understand how we work. People are great at pattern matching. We don’t go “yellow object, subset with large hairy objects, teeth => lion” — we just shout “Lion!”.

We need to feed our minds, not the machine. *steph-note: Lee has got **much** better at slides since BlogTalk 2004*

Many intelligent people inside organisations are surprisingly open to using social tools.

Lee Bryant

Usually, enterprise tools get worse the more people use them. Social tools get better the more people use them.

There is no such thing as a global collective intelligence. Collective intelligence exists only within a defined community.

Large large companies (>1k) have enough scale to make these things work, and do internal versions of these tools.

Bottom line for doing social stuff:

– potential cost savings if we work in a smarter way
– multiplier effect on productivity
– greater peripheral vision
– less duplication of effort
– closer, more responsive client relationships

Basic principles: reading, writing, filtering.

Over time, information starts to find you. If I miss something in my news reader, it’ll probably pop up again, because somebody else in my network is going to blog/link/del.icio.us it.

Concretely:

– feeds everywhere
– feed library management
– filtering tools
– clipstream tools
– social search

Importance of engagement and context. There is no magic tool. Adapt the solution to the context and situation.

Engaging people with new ways of working is not easy.

There is *perception* of dangers, risks, security — and the “real” evalutation.

#### Stowe Boyd

This is a shorter version of the [workshop notes](http://climbtothestars.org/archives/2007/02/07/stowe-boyd-building-social-applications/), so I’ll send you there. Or read [Bruno’s notes], which, as always, are quite complete.

Similar Posts:

Stowe Boyd: Building Social Applications [en]

***Warning: these are my notes of [Stowe](http://stoweboyd.com/message)’s workshop at [LIFT](http://liftconference.com), meaning my understanding and interpretation of what he said. They might not reflect accurately what Stowe told us, and might even be outright wrong in some places. Let me know if you think I really messed up somewhere.***

**Update 05.2007:** enjoy the (http://www.slideshare.net/stoweboyd/building-social-applications) and the (http://www.stoweboyd.com/message/2007/03/social_me_first.html) (not the workshop!).

Questions to play ball with:

1. What makes social applications social (or not)
2. How can we make applications more social?
3. What are the common factors in successful social applications?
4. What is worth building?

1. iTunes vs. Last.fm; also non-social applications which implement, at some point, some social component.

“Software intended to shape culture.” Stowe Boyd, in Message, August 1999

*steph-note: a step further than “groupware”*

LIFT'07... Stowe Boyd

Applications which are qualitatively different. But they haven’t replaced the rest: people are still building applications which allow people to buy stuff online. But we’re looking for ways to stick the humans back in there (“what do the top 10 authorities on cellphones recommend?”)

Read: The Great Good Place by Ray Oldenburg (Third Place, not home and not work)

Decreasing affiliation in the USA (Putnam — sp?). People spend less time “hanging out” with people. *steph-note: cf. danah/MySpace* More TV. Commuting isn’t that significant, but hours in front of the TV is. The light at the end of the tunnel, the only hope we’ve got left, is the internet. Social hours spent on the internet are hours not spent watching TV *(steph-note: yep!)*

TV is not involvement in people, but in this “entertainment culture”. TV reached lowest numbers in the USA since ’50s.

One way we can measure the success of a social application is how much it moves us in that direction.

Social: me first. Put the individual in the centre. Look at the difference between traditional journalism (disembodied third voice) and blogging (first person, you know who’s writing and who’s reading). Need to start with needs and desires of the people using it (?).

Adoption happens in stages. First, the application needs to satisfy the needs of an individual, in such a way that he/she comes back. And then, there needs to be stuff to share that encourages the individual to invite his friends in.

my passions — my people — my markets

Start with the people. Put the people in the foreground (but how?) Easy to fail if you don’t do that right. How are people going to find each other? Second, support their networks/networking.

Only third: realisation of money — markets — shipping etc.

Give up control to the users: “the edge dissolves the centre”.

To review a social app, you need to use it “for real” over an extended period of time.

Xing: the edge doesn’t dissolve the centre. E.g. can’t create a group. Need to ask them by e-mail, and they try to control group creation and management.

Build an environment in which people are “free”. Allow them to find each other.

Success factors for a social application: me first and bottom up. Otherwise, it won’t spread.

Blogging: primary goal is social interaction and networking *(steph-note: half agree, there is the “writing and being read and getting some recognition” goal too — and that is not necessarily social **interaction** and does not necessarily lead to **network contacts**)*

What suicide girls get right: low price, real people, real lives, social stuff like chat, pictures, etc. They have the connections between the people as the primary way to go around.

**Semi/a-social**

– iTunes
– Bestbuy.com
– Pandora (until recently)
– After the fact (eBay: reputation, Netflix: friends in a tab, Amazon: recommendations from other users, Basecamp: not that social, fails some of the critical tests)

**The Buddylist is the Centre of the Universe…**

A case against IM being disruptive: the user chooses how disruptive the client is (blings, pop-up messages, etc… same with e-mail)

Totally acceptable to not answer on IM. But also, maybe at times your personal productivity is less important than your relationship with the person IMing you.

“I am made greater by the sum of my connections, and so are my connections.”

(Give to others, and they’ll give to you. Help your buddies out, be there for them, and others will be there for you when you need them.)

List of hand-picked people who are on *your* list.

Groups help huge communities scale, in the way they bring them down to manageable sizes for human beings again. (Dunbar constant, roughly 150 people.)

Six degrees of connection doesn’t work. People are strangers. Even second degree is really weak.

Difference between people you really talk to, and “contacts” (often people will have two accounts => should build this kind of thing into the service — cf. Twitter with “friends” and “people you follow”).

**Me, Mine, and Market.**

Market: it’s the marketplace where the application builders are going to be able to make money by supporting my interaction/networking with “mine”.

You can’t “make an app social”, you need to start over most of the time.

Think about the social dimension first, and then what the market is. E.g. social invoicing app, what could the market be? Finding people to do work for you. And then you can invoice them using the system.

E.g. Individual: “I need a perfect black dress for that dinner party.” => who knows where to shop for the most fashionable stuff? => market = buying the perfect black dress, with commission to the recommender. (New social business model!)

Facebook profile: all about flow, it’s not static. It’s a collection of stuff going on in my world. Information about my blog (posts), friends… I don’t have to do anything, and it changes.

It represents my links to the world. People want to *belong*. Be in a context where what they do and say matters. Make it easy for users to find other people who will care about them.

Orkut failed because it was just social networking for the sake of social networking. Not targeted at a specific group of people. Nobody who cares! Disease-like replication and then died down. Nothing to do there.

Swarm intelligence. People align around authority and influence. Some people are more connected then others. Inevitable. Swarmth = Stowe-speak for measure of reputation. As soon as reputation brings something to those who have it, charlatans step in and try to figure out how to game the system. Need to be aware of that, to discover those cheating mechanisms and counter them.

General principle: things are flowing, and we want to support the rapid flow of information (ie, stuff that goes in my profile). “traffic”: do you make it possible for people to get information from a variety of sources delivered quickly to them? (e.g. Facebook bookmarklet) (traffic=possible metric).

The media hold the pieces, but not the sense of the conversation. You need to immerse yourself into the flow to get it. How transformative is it to get a constant flow of information from people you care about? Can’t evaluate that from the outside.

**Tags**

cf. David Weinberger: tags matter for social reasons. The power of classification is handed out to the users. They use it to find information and to find each other. They define implicit social groupings.

If people don’t “get” tags, the interface isn’t good. Because the concept is really simple. (e.g. Flickr, del.icio.us get it right)

**Discovery**

Primary abiding motivator of anybody on the internet: discovery (things, places, people, self)

**One of Stowe’s pet peeves: Groups and Groupings**

Networks are asymmetric, accept it. Everybody is **not** equal in a group. The groups are always to some extent asymmetric.

Groupings are ad hoc assemblages of peope with similar interests (from my point of view). (My buddy list categorisation.)

Groups try to be symmetric.

Community of tags. They happen automatically.

**Power Laws**

There will always be people with more power than others, get over it. The recommendation of somebody with more swarmth should count more than that of one with no swarmth.

Accept and work with the imbalance of power.

But careful! The people decide who has more swarmth. And you need to constantly counter the games. Natural social systems are self-policient (sp?).

**Reputation**

Measure and reward swarmth *(steph-note: !== popularity, quantity)*

Reputation is not transportable from one network to another.

**Deep Design**

– last.fm (neighbours!)
– upcoming.org (events are nothing without people!!)
– Facebook
– ThisNext (about design and fashion)

First, just build the social app. Once the social stuff is in place, build the market (see Last.fm).

Journal where you can integrate music references. With backlinks from artists.

Mistake? tags aren’t source of groupings.

*steph-thought: Flickr groups are not just about people, they are about editing content (creating collective photo albums).*

If you have an existing social app, and an entrenched body of users, to make people switch to your new product you need to be an order of magnitude better.

Tag beacons: a recommended tag (e.g. lift07)

If you make people tag an item, the tags used stabilize over time. After a while, the same 10-15 tags. Little chance a new user two years latter will suddenly introduce another tag.

ThisNext is pretty. A piece of social interaction stuff missing however — can’t communicate with other people. Profile just leads to recommendations.

**Cautionary Tales**

Basecamp and the Federation of Work: multiple logins, domains — fragmentation. Wanted to be able to pull everything in a single place. Not simple to keep track of everything one has in the system. Pervasive static models with hardly any flow. It’s an online groupware app, not a social app. It doesn’t put me in the foreground.

Outside.in is about finding people who are in your zipcode. I remember Stowe did a post on this some time back. “Where’s the people?”

You only get one first launch. What’s the point of missing it by doing it before you got to the social tipping point?

Blinksale: where’s the market? (invoicing thing)

**Explorations**

Where is all this going? All commerce on the internet in the future will be social. Put in context of social recommendations etc (perfect little black dresses). A social iTunes — what would it look like? They could acquire Last.fm and integrate them to iTunes, for example. I could recommend music to my friends via iTunes…

Calendars are hard! We’re still waiting for the perfect (at least good) calendar-sharing system.

Social browsing… “What should I look at today, based on recommendations of these n people I really find smart?”

Safety/privacy concerns: solutions we have in the offline world need to be emulated online.

Similar Posts:

"Learning Blogs": GWNG Meeting Presentation [en]

[fr] Présentation donnée vendredi passé au GWNG à UNAIDS.

Here are the slides I used as a backbone to my presentation of blogs as educational tools during the Global Net Manager Networking Group last Friday at UNAIDS. You can download them in three formats. As specified on the presentation, they are licensed [CC by-nc-nd](http://creativecommons.org/licenses/by-nc-nd/2.5/).

– [20061215-gwng-learning-blogs.odp](/files/20061215-gwng-learning-blogs.odp) (OpenOffice Impress)
– [20061215-gwng-learning-blogs.pdf](/files/20061215-gwng-learning-blogs.pdf) (PDF)
– [20061215-gwng-learning-blogs.ppt](/files/20061215-gwng-learning-blogs.ppt) (Microsoft Powerpoint)

Similar Posts: