{"id":6,"date":"2006-02-10T08:19:32","date_gmt":"2006-02-10T15:19:32","guid":{"rendered":"http:\/\/www.redmonk.com\/cote\/wp\/?p=6"},"modified":"2006-02-10T08:19:32","modified_gmt":"2006-02-10T15:19:32","slug":"what-is-social-software-one-answer","status":"publish","type":"post","link":"https:\/\/redmonk.com\/cote\/2006\/02\/10\/what-is-social-software-one-answer\/","title":{"rendered":"What is Social Software? One Answer"},"content":{"rendered":"

Someone asked me yesterday what I understood the term “social software” to mean. It was a fair question, as I listed that as one of my areas of coverage<\/a>.<\/p>\n

Why Now?<\/h2>\n

The idea of social software has been floating around for several years. Stewart Butterfield, among others<\/a>, has an excellent write-up and breakdown of the term from 2003<\/a>. And there was, and is, even a social software mini-bubble with Friendster<\/a>, MySpace<\/a>, and all those other things “the kids” are spending their time on<\/a>. (You’d be tempted to list flickr<\/a> and del.icio.us<\/a> up there, but my feel is that “social software” is just one aspect of those systems, not the overriding theme.)<\/p>\n

The application of social software concepts in enterprise software, however, is just now emerging. Large vendors usually lag a year or two behind consumer software, and enterprise software users can take even longer to start widespread use of said software<\/a>. (The why on both of those will have to wait for another post). But now it’s been just long enough for product management bets put on social software a year or two ago to start paying off.<\/p>\n

With that, it’s worth considering the question, what does “social software” mean in an enterprise context?<\/p>\n

Enterprise Social Software<\/h2>\n

In the enterprise realm, I think of the term “social software” as a sub-set of the term “collaborative software.” Social
\nsoftware in that respect is software that substitutes and\/or enhances
\nperson to person interactions. In consumer software,
\nit’s meant people making explicit, declarative links<\/a> between each
\nother (these people are my friends<\/a>) and then using those links to control
\naccess to information like presence, blog posts<\/a>, photos<\/a>, or the
\nability to act on those and other pieces of data (such as adding notes and tags to flickr photos<\/a>).<\/p>\n

Presence and IM<\/h3>\n

In the enterprise world, the use of presence monitoring in IM is the
\nfirst thing I think of: I’ve had people catch as I was leaving for last minute work by noticing that I was logged out of IM. That kind of “value” is a direct substitution for the person to person interaction of someone seeing me get up and leave: instead they use software…which makes sneaking out difficult ;><\/p>\n

On this presence and communication (IM) angle, my hope is that enterprise social software will help figure out how to make geographically dispersed teams work flawlessly without being overly reliant on the people being excellent in the first place<\/a>, which seems to be the current crutch and fatal flaw of such teams and supporting software.<\/p>\n

Reputation and Networks<\/h3>\n

To a very limited extent at the moment, social software can help with
\nreputation (such as looking up people in linkedin.com<\/a>) and
\nunderstanding the people networks in a company. I haven’t seen much
\npragmatic use of those ideas behind the fire-wall: there’s spam filtering<\/a> and brainstorming<\/a> so far.<\/p>\n

There’s always been a lot of hope behind the idea of a de-centralized, reputation driven workforce<\/a>; eBay’s reputation system has kept that flame going recently. Despite that hope, such a workforce is anathema to the corporate world as I know it: a business without an org chart seems like a paradox to most folks (hopefully, at least some you, dear readers, excluded ;>). It’s difficult to sell software if the story doesn’t fit with existing world-views.<\/p>\n

Answer Grids<\/h3>\n

To come out of
\nleft field with an example, Amazon’s Mechanical Turk<\/a> seems like an interesting foray into social software,
\nthough it may not obviously be so. It’s a sort of reverse Turing Test<\/a>: who cares what or who you’re interacting with as long as you get the right answer and get it cheap? Something like the Mechanical Turk could be used to eliminate human interactions (in the realm of technology) completely. Instead of asking someone<\/i> a question, you just query the API and The System will take care of figuring out where to get the answer from.<\/p>\n

The Inverse<\/h2>\n

What social software is “not exactly” to me are things like blogs,
\nwikis, and other text and data (like pictures) collaboration software.
\nAlthough, as hinted at above, the networks expressed in social
\nsoftware can and are used as a basis for ACL control to the data and
\nprocesses in other collaborative systems. But, calling those systems only<\/i> “social software” is too limiting.<\/p>\n

Another Vague Term<\/h2>\n

Any discussion about something as fluid as social software has a big semantic disclaimer above it. As I disclaimed in a brain-storming post about the equally loose term “enterprise software,”<\/a> the definitions are never clear and concise, and the “definitions” definitely aren’t the same across different groups, or even intra-groups.<\/p>\n

On the other hand, while it’s a new term, it’s more of an adolescent than a new-born term. Meaning that it affords a lovely advantage: it’s been around for a few years for people to kick around, and we actually have some working software to point at.<\/p>\n

What do you think when you hear the term “social software”?<\/p>\n","protected":false},"excerpt":{"rendered":"

Someone asked me yesterday what I understood the term “social software” to mean. It was a fair question, as I listed that as one of my areas of coverage. Why Now? The idea of social software has been floating around for several years. Stewart Butterfield, among others, has an excellent write-up and breakdown of the […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-6","post","type-post","status-publish","format-standard","hentry","category-collaborative"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/6","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/comments?post=6"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/posts\/6\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/media?parent=6"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/categories?post=6"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/cote\/wp-json\/wp\/v2\/tags?post=6"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}