The Naming Of Things: Social Business

I guess the Dachis folks are getting some push back on the use of the ‘social business’ and ‘social business design’ handles to characterize the impacts of social tools on business.

[via Defining Social Business Design: Style vs. Substance by Peter Kim]

For the most part, people understand that we’re talking about what’s on the horizon for business. However, most detractors seem to take issue with the style of the idea’s communication rather than its substance. Some say they don’t understand. I’ll take that at face value and suggest they try harder. Others ask why simpler words weren’t used. Well, as a certain bald-headed guru told me, “words matter.”

Some new terms take a lot of persuading before they become lodged in the zeitgeist, like Web 2.0 and social tools, in the past ten years. But, now, on balance, we can see that these ideas have helped to characterize what is going on: to clarify, not to confuse.

Many people are naturally reluctant to adopt what might just be specious terms, especially after being subjected to ‘knowledge management’ projects, or asked to ‘think out of the box’ at company offsites, or being barraged with market speak by a word-happy advertising culture.

But I believe that words, and even more importantly, metaphors, matter. How we choose to name things makes a difference.

Unlike Peter Kim and his associates at Dachis, I might have been more metaphorical and less riveted down in my prose for a social business description than Peter was in his post today, and in the earlier group post (see Social Business Design). Of course, they are advancing a more complex picture — social business design, and its moving parts — while I am simply sketching out the anthropology of the thing.

Since I am doing a ten minute sprint presentation on social business at tomorrow’s 140 Character conference, here’s my handwave.

Social Business

‘Social Business’ denotes businesses organized around social ties and the use of social technologies to support them.

This is intended to represent a break between companies (in general) organized prior to the rise of the social web.

Leaving aside any implied methods for designing, building, or even managing such organizations, I offer a few one-liners to try to capture the essential elements of these organizations. I don’t want to undercut my 10 minutes of glory, so here’s a few teasers:

  • the individual is the new group
  • business is a village, not an army
  • small talk is big again
  • meaning is the new search
  • time is the new space
  • flow is the new center

New Models Of Work: The Individual Is The New Group, Reprised

I have been talking with a wide range of companies recently that are developing business “Web 2.0” apps. I put the word in scare quotes, because not many of the core principles (or at least what I perceive to be the core principles) of Web 2.0 are showing up in many of these apps.

How many web apps have I seen so recently that provide some sort of intranet, supposedly for small/medium businesses? Way too many, and with way too little differentiation, and hardly any new thoughts about business.

First of all, I believe that because of the way that we live and work the individual is the new group (see my original post on this from January). Stated differently, apps that purport to help us order our work should start by solving the problems of the individual, realizing that one of the issues involved in work is sharing with others.

So, I am amazed to see how many apps continue the old, old ways, where membership in groups is the primary (if not only) notion at work. All of these apps that support projects as a collection of folders into which we move documents and people get access to them through group membership.

Yawn.

Not that this model doesn’t ‘work’. Obviously we have been able to get work done, and to share things, using this model. It’s been around for decades.

But I am more interested in bottom-up organization schemes, both at the interpersonal level and at the tool level.

Just some examples of these ideas, and a few notes about tools I have been trying to use:

  • Contrast the notion of Gmail’s ‘labels’ — which are essentially tags — and the typical use of folders and categories in these intranet solutions. In Gmail, I can tag any email with dozens of tags, if I want, so I can aggregate and find it in a variety of ways. An email from a particular client is denoted with the company name, a location, and perhaps a project, task, or issue. As a result, I can pull up all emails related to London, specific project, or the topic of ‘conceptual design’ independent of project. With folders, things are put in one place, and can’t be sliced in other ways.
  • Parts versus Wholes — I favor (in principle, since no one has built something like this) treating everything I am fooling with as miscellaneous (thank you, Dr Weinberger, wherever you are), basically a big pile of parts. Here’s a picture, here’s an email, here’s some notes on some topic, here’s a to-do item, and here’s a file (which has parts inside, like slides or sections or spreadsheet pages). What I’d like to be able to do is define assemblages of all the things wearing some tag, or defined by some tag algebra. Imagine pulling together an on the fly assemblage of all the bits in my heap that are tagged ‘conceptual modeling’ and ‘public’, and creating a workspace with that. At the same time, many of those public bits on the topic of conceptual modeling might be included in private assemblages, but they would still be public.
  • Flow, Traffic, and kinds of Parts — The explosion of interest in Twitter, Facebook, Jaiku, and related flow apps turns certain premises on their ear, but even most users seem unable to articulate what is going on here. One factor is the shift to information flowing through defined social relationships in an asymmetric fashion, away from the symmetric and closed groups of the pre-2.0 era. Another factor is the flow of various parts, not wholes, thought the apps. For example, Facebook does not embed my blog as an element in a portal presentation. Instead, new posts appear as they pop into my RSS feed: a flow of parts instead of embedding the whole. Now, a gazillion sorts of bits are starting to flow through Facebook’s traffic: new slideshows, new answers to questions, new events created, and so on. And we see a similar emergence of types of traffic in Jaiku and Pownce.
  • Mobile versus Stabile — The other shift (very early) is toward pulling information from the traffic of these flow apps, and doing appropriate things with it. (I have appropriated Calder’s terms based on the different kinds of statuary: those that move and those that don’t.) If someone updates an event that I am interested in, and that I have added to my calendar. I think what I want is not automated updating a la iCal subscription, but instead seeing the change go by in a highlighted way, allowing me to acknowledge it or reject it. For example, a smart desktop companion app could be reading my Facebook traffic just looking for event information, and I might get a Growlr update popping on my desktop. I want to stay still, working, and have things of interest find their way to me. The world of browsing, where people are mobile and information is stabile, looks very 20th century.
  • So a wish list, of sorts:
    • Work Management tools that start with individuals and bits, and work outward to assemblages and networks.
    • Tools that allow us to be stabile and make more and more critical information mobile, not vice versa.
    • New models of access and visibility based on networks and tags, not groups and folders.
    • Agreed upon conventions for flow apps to be able to interoperate, not just platform plays like Facebook. I don’t necessarily want one platform with ten thousand services streaming through it. I want to be able to use best of breed solutions, and have them stream together the way I want. As an example, I use Dopplr now to define where I will be geographically, and I stream that information into a specific calendar in Google. I might want to stream things so that my planned travels to various locations would lead to postings in Facebook local networks, and I would like to stream responses from those networks back to the trips in Dopplr. Obviously, this sort of gasketry is impossible today, but given enough interest by the community, and motivations among the developers for maximum network effects might push things in this direction.

At any rate, I am amazed that no one has started to move away from folders and documents in the intranet space, and I am amazed on the other hand that consumer-oriented frenzy in these flow apps hasn’t translated manifested itself in a new metaphor for work based on flow. I guess it’s going to take a while, and perhaps a couple of index apps, before these ideas can get off the ground.

If there is anyone out there pushing these ideas — and I don’t mean just another ‘dead easy to use’ old school intranet app — please contact me. I am willing to believe.

The Individual Is The New Group

Spread throughout my recent writing, a certain latent idea is lurking, incompletely articulated, which I summarize in the title: the individual is the new group.

About a decade ago, the one of the then-current terms of art for social tools was groupware, and the term was intended to impart the core metaphor: groups need to collaborate, and tools need to be defined with that in mind. As a result, we saw the rise of application platforms like Lotus Notes, intended to counter the flaws of operating systems and applications that were organized around an earlier, less group-oriented metaphor of use.

The central motif of groupware solutions was the need for groups to have a shared repository for online documents, and a collection of communication and collaboration tools to enable a distributed team to collectively accomplish goals. These tools included email, group calendaring, discussion forums, shared to do lists, and real-time support, in the late 90s and early 00s, for instant messaging, chat rooms, and web conferencing.

This model of group collaboration has become the basic form factor of work in many large organizations. However, I have come to believe that this model is being eclipsed by a new epicenter of social context: the individual, rather than the group.

Contrasting group forums with blogging is a good example in which to make the distinction between group- and individual-oriented social tools. In group forums, members of a closed group can post threads and comment on them. It is a closed model. When individuals blog in the open web, trackbacks and comments allow discussions to take place that are — in many cases — logically equivalent to forums, but since each individual blogger decides where to turn their focus, and what other blogs to comment on, bloggers are members of many groups at the same time. More importantly, the structure of blogging supports that model directly. In a group forum, you are a member of that one group, and not a member of any others: the fact that you may be a member of other groups is not explicitly supported.

Another driver of this change toward the individual is the rise of instant messaging. I have said many times recently that “the buddy list is the center of the universe 2.0” — meaning that the presence and real-time proximity of the most critical individuals in our lives is the center of our social interaction. The fact that a particular contact on my buddy list is the member of several groups in my life is less relevant that our social connectedness, individual to individual. While I am IMing a buddy about work related issues, I may veer off into personal issues. I am constantly switching context while in communication with individuals, and real-time communication supports that directly: its natural to do so.

So the groupware model of collaboration, where neatly partitioned worlds are created, and individuals are made to shift context in order to shift from one social thread to another, seems unnatural to me. The primacy of groups and group membership in old-school groupware is outmoded.

The shift to the individual changes everything, and in revolutionary ways. Moving from groupware premises to “soloware” shifts the dialog about standards and interoperability. In the old groupware model, a company would buy a groupware platform and applications, and roll it out across all the users. It was standardized because everyone was using the same rev of the same product. When the issue of interoperability and standards were brought up, it was approached from the perspective of inter-company communication, or different sites within the same company. But in the “soloware” model, individuals may be using completely different tools, and share nothing in common but certain standards. But the glue that connects the dots in the “soloware” world are standards like RSS, IM interoperability, and blog trackback conventions: standards that allow individuals to do their thing, but to allow bottom-up aggregation of their artifacts along social connections. The groups are there, but latent, implicit in the gestural relationships of crosslinking, tags, comments, and blogrolls.

I envision a time where even in the largest organization, our lives as individuals will define the norm for computer-assisted work. The model of “soloware” will displace the 90s ideals of groupware in exactly the same way that the pre-groupware assembly line models were dethroned in the 90s. In our work lives, even in the largest, most conservative companies, we are instantaneously involved in dozens of projects, with teams of people that are constantly changing, with outside consultants and partner companies, and there is no end in sight. When everything fractures away from stable, long-lasting, closed teams toward the exact opposite, what is left are individuals in contact with each other, through soloware: individual needs first, group needs second, by extension.

We are, first and foremost, individuals. The concept that whenever we do something it should be intentionally in the context of a specific well-defined group is outmoded, and was always an approximation of what is really going on, socially. We are involved in social relationships, and what we do with others is always social, but not necessarily part of a group, or only of one group. So, let’s put aside groups, and focus on the individual. The groups will follow.