Enterprise Social Tools: Components for Success
One of the things I continually run across talking with organizations deploying social tools inside their organization is the difficultly getting all the components to mesh. Nearly everybody is having or had a tough time with getting employees and partners to engage with the services, but everybody is finding out it is much more than just the tools that are needed to consider. The tools provide the foundation, but once service types and features are sorted out, it get much tougher. I get frustrated (as do many organizations whom I talk with lately) that social tools and services that make up enterprise 2.0, or whatever people want to call it, are far from the end of the need for getting it right. There is great value in these tools and the cost of the tools is much less than previous generations of enterprise (large organization) offerings.
Social tools require much more than just the tools for their implementation to be successful. Tool selection is tough as no tool is doing everything well and they all are focussing on niche areas. But, as difficult as the tool selection can be, there are three more elements that make up what the a successful deployment of the tools and can be considered part of the tools.
Four Rings of Enterprise Social Tools
The four elements really have to work together to make for a successful services that people will use and continue to use over time. Yes, I am using a venn diagram for the four rings as it helps point out the overlaps and gaps where the implementations can fall short. The overlaps in the diagram is where the interesting things are happening. A year ago I was running into organizations with self proclaimed success with deployments of social tools (blogs, wikis, social bookmarking, forums, etc.), but as the desire for more than a simple set of blogs (or whichever tool or set of tools was selected) in-house there is a desire for greater use beyond some internal early adopters. This requires paying close attention to the four rings.
Tools
The first ring is rather obvious, it is the tools. The tools come down to functionality and features that are offered, how they are run (OS, rack mount, other software needed, skills needed to keep them running, etc.), how the tools are integrated into the organization (authentication, back-up, etc.), external data services, and the rest of the the usual IT department checklist. The tools get a lot of attention from many analysts and tech evangelists. There is an incredible amount of attention on widgets, feeds, APIs, and elements for user generated contribution. But, the tools do not get you all of the way to a successful implementation. The tools are not a mix and match proposition.
Interface & Ease of Use
One thing that the social software tools from the consumer web have brought is ease of use and simple to understand interfaces. The tools basically get out of the way and bring in more advanced features and functionality as needed. The interface also needs to conform to expectations and understandings inside an organization to handle the flow of interaction. What works for one organization may be difficult for another organization, largely due to the tools and training, and exposure to services outside their organization. Many traditional enterprise tools have been trying to improve the usability and ease of use for their tools over the last 4 to 5 years or so, but those efforts still require massive training and large binders that walk people through the tools. If the people using the tools (not administering the tools need massive amounts of training or large binders for social software the wrong tool has been purchased).
Sociality
Sociality is the area where people manage their sharing of information and their connections to others. Many people make the assumption that social tools focus on everything being shared with everybody, but that is not the reality in organizations. Most organizations have tight boundaries on who can share what with whom, but most of those boundaries get in the way. One of the things I do to help organizations is help them realize what really needs to be private and not shared is often much less than what they regulate. Most people are not really comfortable sharing information with people they do not know, so having comfortable spaces for people to share things is important, but these spaces need to have permeable walls that encourage sharing and opening up when people are sure they are correct with their findings.
Sociality also includes the selective groups people belong to in organizations for project work, research, support, etc. that are normal inside organizations to optimize efficiency. But, where things get really difficult is when groups are working on similar tasks that will benefit from horizontal connections and sharing of information. This horizontal sharing (as well as diagonal sharing) is where the real power of social tools come into play as the vertical channels of traditional organization structures largely serve to make organizations inefficient and lacking intelligence. The real challenge for the tools is the capability to surface the information of relevance from selective groups to other selective groups (or share information more easily out) along the way. Most tools are not to this point yet, largely because customers have not been asking for this (it is a need that comes from use over time) and it can be a difficult problem to solve.
One prime ingredient for social tool use by people is providing a focus on the people using the tools and their needs for managing the information they share and the information from others that flow through the tool. Far too often the tools focus on the value the user generated content has on the system and information, which lacks the focus of why people use the tools over time. People use tools that provide value to them. The personal sociality elements of whom are they following and sharing things with, managing all contributions and activities they personally made in a tool, ease of tracking information they have interest in, and making modifications are all valuable elements for the tools to incorporate. The social tools are not in place just to serve the organization, they must also serve the people using the tools if adoption and long term use important.
Encouraging Use
Encouraging use and engagement with the tools is an area that all organizations find they have a need for at some point and time. Use of these tools and engagement by people in an organization often does not happen easily. Why? Normally, most of the people in the organization do not have a conceptual framework for what the tools do and the value the individuals will derive. The value they people using the tools will derive needs to be brought to the forefront. People also usually need to have it explained that the tools are as simple as they seem. People also need to be reassured that their voice matters and they are encouraged to share what they know (problems, solutions, and observations).
While the egregious actions that happen out on the open web are very rare inside an organization (transparency of who a person is keeps this from happening) there is a need for a community manager and social tool leader. This role highlights how the tools can be used. They are there to help people find value in the tools and provide comfort around understanding how the information is used and how sharing with others is beneficial. Encouraging use takes understanding the tools, interface, sociality, and the organization with its traditions and ways of working.
The Overlaps
The overlaps in the graphic are where things really start to surface with the value and the need for a holistic view. Where two rings over lap the value is easy to see, but where three rings overlap the missing element or element that is deficient is easier to understand its value.
Tools and Interface
Traditional enterprise offerings have focussed on the tools and interface through usability and personalization. But the tools have always been cumbersome and the interfaces are not easy to use. The combination of the tools and interface are the core capabilities that traditionally get considered. The interface is often quite flexible for modification to meet an organizations needs and desires, but the capabilities for the interface need to be there to be flexible. The interface design and interaction needs people who have depth in understanding the broad social and information needs the new tools require, which is going to be different than the consumer web offerings (many of them are not well thought through and do not warrant copying).
Tools and Sociality
Intelligence and business needs are what surface out of the tools capabilities and sociality. Having proper sociality that provides personal tools for managing information flows and sharing with groups as well as everybody as it makes sense to an individual is important. Opening up the sharing as early as possible will help an organization get smarter about itself and within itself. Sociality also include personal use and information management, which far few tools consider. This overlap of tools and sociality is where many tools are needing improvement today.
Interface and Encouraging Use
Good interfaces with easy interaction and general ease of use as well as support for encouraging use are where expanding use of the tools takes place, which in turn improves the return on investment. The ease of use and simple interfaces on combined with guidance that provides conceptual understanding of what these tools do as well as providing understanding that eases fears around using the tools (often people are fearful that what they share will be used against them or their job will go away because they shared what they know, rather than they become more valuable to an organization by sharing as they exhibit expertise). Many people are also unsure of tools that are not overly cumbersome and that get out of the way of putting information in to the tools. This needs explanation and encouragement, which is different than in-depth training sessions.
Sociality and Encouraging Use
The real advantages of social tools come from the combination of getting sociality and encouraging use correct. The sociality component provides the means to interact (or not) as needed. This is provided by the capabilities of the product or products used. This coupled with a person or persons encouraging use that show the value, take away the fears, and provide a common framework for people to think about and use the tools is where social comfort is created. From social comfort people come to rely on the tools and services more as a means to share, connect, and engage with the organization as a whole. The richness of the tools is enabled when these two elements are done well.
The Missing Piece in Overlaps
This section focusses on the graphic and the three-way overlaps (listed by letter: A; B; C; and D). The element missing in the overlap or where that element is deficient is the focus.
Overlap A
This overlap has sociality missing. When the tool, interface, and engagement are solid, but sociality is not done well for an organization there may be strong initial use, but use will often stagnate. This happens because the sharing is not done in a manner that provides comfort or the services are missing a personal management space to hold on to a person's own actions. Tracking one's own actions and the relevant activities of others around the personal actions is essential to engaging socially with the tools, people, and organization. Providing comfortable spaces to work with others is essential. One element of comfort is built from know who the others are whom people are working with, see Elements of Social Software and Selective Sociality and Social Villages (particularly the build order of social software elements) to understand the importance.
Overlap B
This overlap has tools missing, but has sociality, interface, and encouraging use done well. The tools can be deficient as they may not provide needed functionality, features, or may not scale as needed. Often organizations can grow out of a tool as their needs expand or change as people use the tools need more functionality. I have talked with a few organizations that have used tools that provide simple functionality as blogs, wikis, or social bookmarking tools find that as the use of the tools grows the tools do not keep up with the needs. At times the tools have to be heavily modified to provide functionality or additional elements are needed from a different type of tool.
Overlap C
Interface and ease of use is missing, while sociality, tool, and encouraging use are covered well. This is an area where traditional enterprise tools have problems or tools that are built internally often stumble. This scenario often leads to a lot more training or encouraging use. Another downfall is enterprise tools are focussed on having their tools look and interact like consumer social web tools, which often are lacking in solid interaction design and user testing. The use of social tools in-house will often not have broad use of these consumer services so the normal conventions are not understood or are not comfortable. Often the interfaces inside organizations will need to be tested and there many need to be more than one interface and feature set provided for depth of use and match to use perceptions.
Also, what works for one organization, subset of an organization, or reviewer/analyst will not work for others. The understanding of an organization along with user testing and evaluation with a cross section of real people will provide the best understanding of compatibility with interface. Interfaces can also take time to take hold and makes sense. Interfaces that focus on ease of use with more advanced capabilities with in reach, as well as being easily modified for look and interactions that are familiar to an organization can help resolve this.
Overlap D
Encouraging use and providing people to help ease people's engagement is missing in many organizations. This is a task that is often overlooked. The tools, interface, and proper sociality can all be in place, but not having people to help provide a framework to show the value people get from using the tools, easing concerns, giving examples of uses for different roles and needs, and continually showing people success others in an organization have with the social tool offerings is where many organization find they get stuck. The early adopters in an organization may use the tools as will those with some familiarity with the consumer web social services, but that is often a small percentage of an organization.
Summary
All of this is still emergent and early, but these trends and highlights are things I am finding common. The two areas that are toughest to get things right are sociality and encouraging use. Sociality is largely dependent on the tools, finding the limitations in the tools takes a fair amount of testing often to find limitations. Encouraging use is more difficult at the moment as there are relatively few people who understand the tools and the context that organizations bring to the tools, which is quite different from the context of the consumer social web tools. I personally only know of a handful or so of people who really grasp this well enough to be hired. Knowing the "it depends moments" is essential and knowing that use is granular as are the needs of the people in the organization. Often there are more than 10 different use personas if not more that are needed for evaluating tools, interface, sociality, and encouraging use (in some organizations it can be over 20). The tools can be simple, but getting this mix right is not simple, yet.
May 6, 2008 in Applications, Community, Enterprise, Folksonomy, Identity, Interface, Knowledge Management, Local InfoCloud, Personal Info, Personal InfoCloud, Portability, Social Software, Technology, Usability, Web, Weblogs | Permalink | Comments (3) | TrackBack
Selective Sociality and Social Villages
The web provides wonderful serindipity on many fronts, but in this case it brought together two ideas I have been thinking about, working around, and writing about quite a bit lately. The ideas intersect at the junction of the pattern of building social bonds with people and comfort of know interactions that selective sociality brings.
The piece that struck me regarding building and identifying a common bond with another person came out of Robert Paterson's "Mystery of Attraction" post (it is a real gem). Robert describes his introduction and phases of getting to know and appreciate Luis Suarez (who I am a huge fan of and deeply appreciate the conversations I have with him). What Robert lays out in his introduction (through a common friend on-line) is a following of each other's posts and digital trail that is shared out with others. This builds an understanding of each others reputation in their own minds and the shared interest. Upon this listening to the other and joint following they built a relationship of friendship and mutual appreciation (it is not always mutual) and they began to converse and realized they had a lot more in common.
What Robert echos is the Elements in Social Software and its build order. This build order is common in human relationships, but quite often social software leaves out steps or expects conversations, groups, and collaboration to happen with out accounting for the human elements needed to get to this stage. Quite often the interest, ideas, and object (all social objects) are the stimulus for social interaction as they are the hooks that connect us. This is what makes the web so valuable as it brings together those who are near in thought and provides a means to connect, share, and listen to each other. I really like Robert's analogy of the web being like university.
Selective Sociality of Villages
The piece that resonated along similar threads to Robert's post is Susan Mernit's "Twitter & Friend Feed: The Pleasure of Permissions". Susan's post brings to light the value of knowing who you are sharing information with and likes the private or permission-based options that both Twitter and FriendFeed offer. This selective sociality as known Local InfoCloud of people and resources that are trusted and known, which we use as resources. In this case it is not only those with whom we listen to and query, but those with whom we share. This knowing who somebody is (to some degree) adds comfort, which is very much like Robert Patterson and Luis Suarez#039; villages where people know each other and there is a lot of transparency. Having pockets where our social armor is down and we can be free to share and participate in our lives with others we know and are familiar to us is valuable.
I am found these two pieces quite comforting as they reflect much of what I see in the physical community around me as well as the work environments I interact with of clients and collaborators. The one social web service I have kept rather private is Twitter and I really want to know who someone is before I will accept them as a connection. This has given me much freedom to share silly (down right stupid - in a humorous way) observations and statements. This is something I hear from other adults around kids playgrounds and practices of having more select social interactions on line in the services and really wanting to connect with people whom they share interests and most often have known (or followed/listened to) for sometime before formally connecting. Most often these people want to connect with the same people on various services they are trying out, based on recommendation (and often are leaving a service as their friends are no longer there or the service does not meet their needs) of people whom they trust. This is the core of the masses who have access and are not early adopters, but have some comfort with the web and computers and likely make up 80 to 90 percent of web users.
April 5, 2008 in Access to Info, Attraction, Community, Identity, Local InfoCloud, Location, Model of Attraction, Personal Info, Privacy, Social Software, Technology | Permalink | Comments (1) | TrackBack
Challenges as Opportunities for Social Networks and Services
Jeremiah Owyang posts "The Many Challenges of Social Network Sites" that lays out many of the complaints that have risen around social networking sites (and other social computing services). He has a good list of complaints, which all sounded incredibly familiar from the glory days of 1990 to 1992 for IT in the enterprise (tongue firmly planted in cheek). We have been through these similar cycles before, but things are much more connected now, but things also have changed very little (other than many of the faces). His question really needs addressing when dealing with Enterprise 2.0 efforts as these are the things I hear initially when talking with organizations too. Jeremiah asked for responses and the following is what I posted...
Response to Challenges of Social Network/Services
The past year or two, largely with Facebook growing the social networks and social computing tools have grown into the edges of mainstream. Nearly every argument made against these tools and services was laid down against e-mail, rich UI desktops (people spent hours changing the colors and arranging the interfaces), and IM years ago.
Where these tools are "seemingly" not working is mostly attributed to a severe lack of defining the value derived from using the tools. These news tools and services, even more so those of us working around them, need to communicate how to use the tools effectively and efficiently (efficiently is difficult as the many of the tools are difficult to use or the task flows are not as simple as they should be). The conceptual models & frameworks for those of us analyzing the tools have been really poor and missing giant perspectives and frameworks.
One of the biggest problems with many of these tools and services is they have yet to move out of early product mode. The tools and services are working on maturity getting features in the tools that people need and want, working on scaling, and iterating based on early adopters (the first two or three waves of people), which is not necessarily how those who follow will use the tools or need the tools to work.
Simplicity and limited options on top of tools that work easily and provide good derived value for the worklife and . As the tools that were disrupters to work culture in the past learned the focus needs to be on what is getting done and let people do it. Friending people, adding applications, tweaking the interface, etc. are not things that lead to easy monetization. Tools that help people really be social, interact, and get more value in their life (fun, entertainment, connecting with people near in thought, filtering information from the massive flow, and using the information and social connections in context where people need it) from the tools is there things must head. We are building the platforms for this, but we need to also focus on how to improve use of these platforms and have strong vision of what this is and how to get there.
February 11, 2008 in Enterprise, Identity, Local InfoCloud, Personal Info, Social Software, Usability, Web | Permalink | Comments (0) | TrackBack
The Elements in the Social Software Stack
When thinking through social software (also known as social computing, social media, and social web) I have been influenced by many ideas, but at the core there are two things that stick in my head: 1) Good visualization; and 2) Object-centered sociality. Getting the two to mesh, while accounting for most of the important components of social software has been really difficult for me to square for quite some time.
One of my starting point for visualization has been Gene Smith's wonderful honeycomb adaption of the social software building blocks. The strength of the graphic is having identity at the core of the social interaction. The honeycomb allows Gene to display many different services deployed has the pieces of the social software stack (stack is a collection of elements that comprise a whole set of services).
One of the things with Gene's graphic that has always bugged me is I have not been able to square it with the object also being at the center of the social interaction. A second piece that also bothered me is it did not account for the action element of collaboration (people working together as part of a group or team to build something, while acting with one goal as their focus, which can be a broad goal). Collaboration is central to nearly every enterprise or work organization effort (directly or tangentially) I am or have been involved in professionally, so I feel it is essential to include it.
Object-Centered Sociality
It was through reading Jyri Engeström's blog post about "Why some social network services work and others don't — Or: the case for object-centered sociality" that I came to have familiarity with Karin Knorr Cetina's object-centered sociality. It was through the repeated mentioning of this Knorr Cetina concept by Rashmi Sinha in her presentations and from personal conversations with Rashmi that the ideas deep value sunk in (it is a concept central to Rashmi and Jon Boutelle's product SlideShare).
Knorr Cetina's work brings into view the individual and the object as central elements in social interaction. She proposes physical objects, around which discussions take place help focus and start conversation and other social interaction between and among people. In her and Urs Bruegger's journal article "The Market as an Object of Attachment: Exploring Postsocial Relations in Financial Markets" in Canadian Journal of Sociology 25, 2 (2000): 141-168, they state:
One characteristic of the present situation is that perhaps for the first time in recent history it appears unclear whether other persons are, for human beings, the most fascinating part of their environment. Objects may also be the risk winners of the relationship risks which may authors find inherent in contemporary human relations.
The short of this is the person may not be the sole focus and possibly the person is not the focus of social interaction as the objects being discussed in social interactions is the focus for the people and take the role of the most interesting element in the social discourse.
When we look at social web services like Flickr we see the photos that a person takes and shares are the focus of social interaction. It is around these objects that the conversation takes place. Jyri Engeström calls these objects of social focus "social objects".
It is these social objects that are in need of being accounted for in a visualization of the social software stack. While in Germany for the most recent IA Konferenz I wanted to include his more fleshed out understanding of the social software stack, in this case it is actions or components that comprise sociality from the perspective on an individual in a social environment. I really wanted a graphic that brought these elements together so I could talk through it more easily in a workshop on the foundations of social software and tagging. The visual model is this Venn diagram that I put together sitting in the hallway for an hour or so. While it is not as interesting as Gene's graphic, for me it is a much better representation of the important components in social software if your goal is wanting your service/software to work optimally.
Explaining the Graphic
Yes, the inclusion of the object into the graphic is given a central focus equal to that of identity. Identity and the object are the two important elements that comprise the social software stack. All elements that are represented in the graphic may or could be seen by others and are triggers for social interaction with other people (yes, the interaction can be with just other objects, but that is another subject I am not addressing in this writing). This ability to see all the elements represented is the social aspect of the software service. The overlaps are where there are direct interactions. But, there is a specific order to the revealing and relevance of each of the elements after the identity and object are shown.
The order is important because if one leaves out an element (or does not account for the elements in some manner) the next step is really not going to be capable of being fully realized and there will be a weakness in the social software. I can not stress this enough, this is not a list of items to pick from, but if you want to have reputation in the system there previous elements really need to be in place or accounted for through using an outside service that can be pointed to or brought into the service through using an outside service.
Order of the Elements
The order is: Identity and Object; Presence; Actions; Sharing; Reputation; Relationships; Conversation; Groups; and Collaboration.
The colors were chosen so the bridging elements were orange and fit with the color scheme of my company and the usual slide templates I use when presenting (orange with blue highlights, text, and accents). After I built the graphic I realized the similarity to a finance industry logo, but when playing with other color combinations the graphic lost its punch and also did not fit within the color scheme of my long used slide template, so I have left the colors alone.
The Elements in the Social Software Stack
The Central Focus
Identity
Identity is comprised of the information about the person using the social software tool. Often the identity is a built upon profile information such as name, username, location, personal website, e-mail, photo or avatar, and sometimes the person's age. These pieces help others recognize the person and can carry associations from other interactions and/or services to the current service (that is if the individual wants this cross-service tracking). Contact information is normally required for setting up an account so the service (and the people running the service) can communicate with the person. Sometimes the contact information is shared if the person using the service permits the sharing of the contact information with other people using the software/service.
Identity is also augmented through the inclusion of usernames on other services and sites the person contributes to or has an account on. This cross-service identity helps people who use other services to find their friends and contacts more easily. The cross-service identity also helps tie others understanding of the identity and possibly reputation as understood by other people. Cross-service identity connecting can also be used for aggregating content that an identity shared on another service into a new service.
Identity is included in the focus on object-centered sociality as it is people who are being social around the object. It seems that there is a codependent relationship between the person (their perceptions as expressed through their interest and actions around and about an object). The identity is a pivot to learn more about these understandings for a richer understanding by those reading/consuming what has been shared. This is much like the object is a pivot to find others who have interest in the same type of things.
Object
The object is the core focus of object-centered sociality and in this representation with one identity interacting it is part of the the codependent at the core of the graphic. The object is the center of the sociality. The object is what is being shared with others. This shared object may be a photo, bookmark/link, video, statement, or other matter. The object may be digital or non-digital in nature. Lastly, the object can also be what is being built in a collaboration-focussed effort.
Active Elements
Now that we have the cornerstone set of the two main components for sociality we can start looking at the elements around these two components. Again, these actions and elements are in a specific order that build upon the previous elements. These are active elements because they are either actions or are the result of sets of actions.
Presence
The identity is often built around static profile information, but people are not static as they have lives they lead and people have locations and tasks they perform that provide context for understanding perspective of statements or related actions. Presence can be a simple as Twitter's question of "what are you doing?" It can also be location, time, availability, and/or activity. These provide others a glimpse of understanding, or at least a hint of the identity's perspective.
In the case of Twitter and similar services the statement of presence is not necessarily related to another object, but the presence statement in and of itself acts as the object. In the case where presence is the object, the object is directly related to the person and not an external object. The presence statements may or may not be shared with others as the understanding is quite helpful information for the individual for later recollection as to why they made other statements or actions.
Actions
Using stated presence or the inferred presence, as the actions connote presence around an object that action is taking place around. The actions are what is being done as an expression communicating to one's self or to others what they understand. This may be as simple as just expressing interest (even if the interest is negative). These actions are expressions of the person's understanding can take the form of annotation, messaging, modification of the object, commenting, rating, tagging, flagging or favoring, storing, naming, etc. The actions are tied to the person who is taking the action and linked to the object around which they are taking the action. These actions are are in most cases the some form of adding data or meta data to or around the object.
In social bookmarking in del.icio.us the object is the link expressed as the URL and the person is taking the action of saving the link and is likely also annotating and tagging that link for at least their own retrieval.
The actions always include the identity and the object (which may be the person's own identity and presence). Actions may or may not be shared with others. As many services provide public, selective, and private access to the information and actions.
Sharing
The act of sharing is where we finally start fully acknowledging social actions. The presence and actions elements can be private, if the person behind the identity wishes. Sharing is the social action that opens up the capability for all others (or only others whom have been given permission) to see their actions and possibly presence around an object. This can also include opening access to an object for others to see and others to add their annotations and actions around the object. This includes open annotations of other's openly shared objects or objects shared to a closed community to which the person has access.
Reputation
Shared presence and actions are the elemental building blocks for reputation. Reputation can build upon something as simple as existence on a service, by having an identity there. Reputation grows based on the interpretation of others based on shared presence and actions.
The actions that build reputation can be through the content that has been created by that identity. Others' understanding grows through seeing annotations that are by an identity (ratings, notes, comments, what is shared, etc.). Others also see actions that have been attributed to the identity, which may not be the direct actions that are seen, but can be actions of stating a relationship, joining a group, rewards (top contributor, etc.), or other indirectly perceived action.
The volume of actions also builds reputation. This can be the breadth of actions or breadth of subjects covered. Volume can also be depth of actions. Depth is how many in a subject area and/or the depth of understanding showed on a subject.
The breadth and depth lead to understanding of quality. Quality is often attributed by others based on their own perceptions and understanding. Perceptions, as we know, vary from person to person and that builds trends of reputation. Quality is also interpreted through perception. These interpretations are can be reflected in what others actions taken around an identity (identity can be the focal object in this activity) such as rating contributions made by an identity, favoriting/holding on to the actions of an identity (comments, their favorites, etc.), electing to follow the actions through subscribing or other similar actions, etc. Others may also write about an identity to express and understanding of the identity.
Relationships
Based on reputation people chose to interact with that identity. Through interaction relationships are established or built. This may be explicitly stated in some manner (the "connection" or "collaborator" or "friend" distinctions in some social services are examples). Relationships may also be an inferred relationship based upon actions. The inferred relationship is through another's actions of following, subscribing to actions, annotating an object, or other actions.
Relationships may be causal (as result of actions) or intended. The breadth of the relationship needs also be considered. A relationship between people or their identities can be based only on a precise subject matter or many distinct subjects in a granular social manner. The relationship may be more broad-line by encompassing most subjects that around a person and their identity.
There is rich derived value that can be built upon through identifying and understanding the granular subjects of common interest between people. The relationship can be one that is expansive, in that one person or both are learning and exploring new ideas and material through the shared experiences and shared understanding of the other. Understanding that a relationship is only as broad as a similar interest(s) (it does not have to be the same polarity (like/dislike)) such as for acoustic bebop jazz will help framing the relationship for what is shared, followed, and interaction made around.
Conversation
A relationship predicated on some understanding of reputation (remembering that it may be a rather thin understanding of reputation) provides a good foundation the next stage, conversation. The conversation is most often with an identity about or around an object.
The conversation may be a 2-way or multi-directional. This communication may be a synchronous live conversation or asynchronous over time (message boards or other services what allow comments or time ordered annotations. The conversation in a social environment is open and often around an object (keeping in mind the object may be a person's presence statements as in Twitter).
These conversations may be structured through form-based forums or listserves. The conversations may be free-form as in Consumating'sflirting through tagging or other open communication structures.
Groups
It is in the conversation (derived from relationships based on reputation) that people with similar interest come to the point where they want a more formal relationship so to have more focussed communication and sharing and these people form a group. The group is a sub-set of the whole service, as in Ma.gnolia's groups for sharing social bookmarks (Ma.gnolia's groups can be open to all or they can be closed and not seen). The sharing is a collective understanding of the group with each individual identity openly sharing their actions around that subject matter or interest. The group is normally comprised of trusted listeners who have a relatively strong understanding of reputation. The group is a collective voice what accounts for each voice. There does not have to be a common goal other than sharing information around (tightly or broadly clinging to the subject of interest) and each voice matters in the group.
Collaboration
Groups working often leads to collaboration where not only are people openly sharing information as individuals, but aim to work together to build objects. One example of this is a wiki where there the object is the development of a page or set of pages built through a collaborative process. The collaborative process has one goal (explaining a subject in the case of a wiki) and the group works with a single focus and intentionally becomes a single voice. The object being built may be text content, video with different production tasks and skills needed, other media, an application or service, or other object (physical or digital). Central to collaboration is an understanding of what is being built. Collaboration is most often iterative though building upon what is there with the goal of improving it.
Summary
A walk through the elements in the social software stack should provide an understanding of the progressive relationship between the elements. The aim is for this to be used a guide to think through building and implementing social software. I talk to many organizations that are trying to get to collaboration but are missing some or many pieces of the social software stack that collaboration is built upon. Not all of the elements need to be in the same tool, but they need to be accounted for in an environment that is collaborating.
Those not building collaborative services will also greatly benefit from understanding at what stage their social software service or tool is aiming to serve and ensuring all of the preceding elements are included or accounted for in the service.
Lastly, but not least it is important to understand what is the object of focus in the social software tool or service. This social object is part of the starting foundation and the better the understanding of the object and how it works in the service or tool the better the whole of the project/product will be in the end.
January 9, 2008 in Access to Info, Community, Identity, Information Creation, Knowledge Management, Personal Info, PIM, Research, Social Software, Technology, Web | Permalink | Comments (5)
Pffft! Social Graph, We Need the Portable Social Network
In reading Alex Rudloff's "Privacy as Currancy" post I had two thoughts reoccur: 1) privacy is a currency back by trust; and 2) Pfffft! Social graph? Where is my Portable Social Network?
I agree with what Alex stated about wanting to move out of Facebook as my trust in them is gone completely (mostly driven by even though they apologized (poorly) Facebook still receives trackings of all your travels on the internet after you opt out, Om Malik's Zuckerberg's Mea Culp, Not Enough, and Brian Oberkirk's Facebook Harder to Shake than the Columbia Record Tape Club (a great read on the hurdles of really getting out of Facebook)). I will likely blog about the relationship between privacy and trust in another post in the not too distant future, as I have been talking about it in recent presentations on Social Software (Going Social and Putting Users First).
The Dire Need for Portable Social Networks
When Alex states:
Beacon had me so freaked out that I walked through what would happen if I simply removed my account (my natural, gut reaction). The fact is, I'd lose contact with a lot of people instantly. There's no easy way for me to take my data out and apply it somewhere else. There is no friend export and there isn't anywhere suitable for me to go.
I think we need portable social networks (or Social Network Portability as it is also known) before we need the social graph. Part of the interest in the social graph (mapping the relationships) is based on Facebook, but Facebook is a really poor interface for this information, it has some of the connections, some of the context, but it is not granular and does not measure strength (strong or weak ties) of relationships on a contextual and/or a preferential interest level. This social graph does little to help us move from one social software service to another other than to show a linkage.
There are strong reasons for wanting and needing the Portable Social Network. One is it makes it easy to drop into a new social software service and try it with social interactions with people whom we are already having social interactions. Whilst this is good it is also really important if something tragic or dire happens with a social software service we are already using, such as it is shut down, it is no longer performing for us, or it has given us a reason to leave through loss of trust. As I noted in the past (Following Friends Across Walled Gardens") leaving social software services is nothing new (even predates people leaving Delphi for Prodigy and Prodigy for AOL, etc.), but we still are not ready for this seemingly natural progression of moving house from one walled off social platform for another.
The Call for Action for Portable Social Network is Now
I am finding many of my friends have put their Facebook account on in hibernation (Facebook calls it &#quot;deactivation") and many have started taking the painful steps of really getting all of their information out of Facebook and planning to never go back. My friends have not sorted out what robust social software platform they will surface on next (many are still using Flickr, Twitter, Pownce, Tumblr and/or other options along with their personal blogs), but they would like to hold on to the digital statements of social relationship they made in Facebook and be able to drop those into some other service or platform easily.
One option could a just having a Smart Address Book or as Tim O'Reilly states Address Book 2.0. I believe that this should be a tool/service should have the relationships private and that privacy is controlled by the individual that owns the address book, possibly even accounting for the privacy request of the person whose address is in the address book. But, this is one option of many.
The big thing is we need Portable Social Networks now! This is not a far off in the future need it is a need of today.
December 6, 2007 in Access to Info, Community, Local InfoCloud, Personal Info, Personal InfoCloud, Portability, Social Software, Technology, Web | Permalink | Comments (23) | TrackBack
Open Conversations and Privacy Needs for Business
I thought I would share the latest press bit around this joint, Thomas Vander Wal was quoted in Inc Magazine What's Next: Shout it Out Loud (or in the August 2007 issue beginning on page 69). The article focuses the need and desire for companies to share and be open with more of their data and information. Quite often companies are getting bit by their privacy around what they do (how their source their products/resources, who they donate money to, etc.) and rumors start. It is far more efficient and helpful to be open with that information, as it gets out anyway.
Ironically, in the same paper issue on page 26 there is a an article about When Scandal Knocks..., which includes a story about Jamba Juice and a blog post that inaccurately claimed it had milk in its products, which could have easily been avoided if Jamba Juice had an ingredients listing on its web site.
The Flip Side
There are two flip sides to this. One is the Apple converse, which is a rare example of a company really making a mythic organization out of its privacy. The second is companies really need privacy for some things, but the control of information is often too extreme and is now more harmful than helpful.
Viable Privacy
I have been working on a much longer post looking at the social software/web tools for and in the enterprise. Much of of the extreme openness touted in the new web charge is not a viable reality inside enterprise. There are a myriad of things that need to be private (or still qualify as valid reasons for many). The list include preparations for mergers and acquisitions, securities information dealings (the laws around this are what drive much of the privacy and are out dated), reorganizations (restructuring and layoffs, which organizations that have been open about this have found innovative solutions from the least likely places), personal employee records, as well as contractual reasons (advising or producing products for competitors in the same industry or market segment). Out side of these issues, which normally add up to under 30 to 40% of the whole of the information that flows through an organization, there is a lot of room for openness in-house and to the outside world.
Need for Enterprise Social Tools Grasping Partial Privacy
When we look at the consumer space for social software there are very few consumer tools that grasp social interaction and information sharing on a granular level (Ma.gnolia, Flickr, and the SixApart tools Vox and LiveJournal are the exceptions that always come to mind). But, many of the tools out there that are commonly used as examples of social web tools really fall down when business looks at them and thinks about privacy and selective sociality (small groups). The social web tools all around really need to grow up and improve in this area. As we are seeing the collaboration and social tools evolve to more viable options we start to see their more glaring holes that do not reflect the reality of human social interaction.
Closing the Gap
What we need is for companies to be more open so the marketplace is a more consumer and communicative environment, but we also need our still early social web tools to reflect our social realities that not everything is public and having tools that better fit those needs.
August 12, 2007 in Access to Info, Community, Enterprise, Identity, Local InfoCloud, Personal Info, Personal InfoCloud, Social Software | Permalink | Comments (1) | TrackBack
Stitching Conversation Threads Fractured Across Channels
Communicating is simple. Well it is simple at its core of one person talking with another person face-to-face. When we communicate and add technology into the mix (phone, video-chat, text message, etc.) it becomes more difficult. Technology becomes noise in the pure flow of communication.
Now With More Complexity
But, what we have today is even more complex and difficult as we are often holding conversation across many of these technologies. The communication streams (the back and forth communication between two or more people) are now often not contained in on communication channel (channel is the flavor or medium used to communicate, such as AIM, SMS, Twitter, e-mail, mobile phone, etc.).
We are seeing our communications move across channels, which can be good as this is fluid and keeping with our digital presence. More often than not we are seeing our communication streams fracture across channels. This fracturing becomes really apparent when we are trying to reconstruct our communication stream. I am finding this fracturing and attempting to stitch the stream back together becoming more and more common as for those who are moving into and across many applications and devices with their own messaging systems.
The communication streams fracture as we pick-up an idea or need from Twitter, then direct respond in Twitter that moves it to SMS, the SMS text message is responded back to in regular SMS outside of Twitter, a few volleys back and forth in SMS text, then one person leaves a voicemail, it is responded to in an e-mail, there are two responses back and forth in e-mail, an hour later both people are on Skype and chat there, in Skype chat they decide to meet in person.
Why Do We Want to Stitch the Communication Stream Together?
When they meet there is a little confusion over there being no written overview and guide. Both parties are sure they talked about it, but have different understandings of what was agreed upon. Having the communication fractured across channels makes reconstruction of the conversation problematic today. The conversation needs to be stitched back together using time stamps to reconstruct everything [the misunderstanding revolved around recommendations as one person understands that to mean a written document and the other it does not mean that].
Increasingly the reality of our personal and professional lives is this cross channel communication stream. Some want to limit the problem by keeping to just one channel through the process. While this is well intentioned it does not meet reality of today. Increasingly, the informal networking leads to meaningful conversations, but the conversations drifts across channels and mediums. Pushing a natural flow, as it currently stands, does not seem to be the best solution in the long run.
Why Does Conversation Drift Across Channels?
There are a few reasons conversations drift across channels and mediums. One reason is presence as when two people notice proximity on a channel they will use that channel to communicate. When a person is seen as present, by availability or recently posting a message in the service, it can be a prompt to communicate. Many times when the conversation starts in a presence channel it will move to another channel or medium. This shift can be driven by personal preference or putting the conversation in a medium or channel that is more conducive for the conversation style between people involved. Some people have a preferred medium for all their conversations, such as text messaging (SMS), e-mail, voice on phone, video chat, IM, etc.. While other people have a preferred medium for certain types of conversation, like quick and short questions on SMS, long single responses in e-mail, and extended conversations in IM. Some people prefer to keep their short messages in the channel where they begin, such as conversations that start in Facebook may stay there. While other people do not pay attention to message or conversation length and prefer conversations in one channel over others.
Solving the Fractured Communication Across Channels
Since there are more than a few reasons for the fractured communications to occur it is something that needs resolution. One solution is making all conversations open and use public APIs for the tools to pull the conversations together. This may be the quickest means to get to capturing and stitching the conversation thread back together today. While viable there are many conversations in our lives that we do not want public for one reason or many.
Another solution is to try to keep your conversations in channels that we can capture for our own use (optimally this should be easily sharable with the person we had the conversation with, while still remaining private). This may be where we should be heading in the near future. Tools like Twitter have become a bridge between web and SMS, which allows us to capture SMS conversations in an interface that can be easily pointed to and stitched back together with other parts of a conversation. E-mail is relatively easy to thread, if done in a web interface and/or with some tagging to pull pieces in from across different e-mail addresses. Skype chat also allows for SMS interactions and allows for them to be captured, searched, and pulled back together. IM conversations can easily be saved out and often each item is time stamped for easy stitching. VoIP conversations are often easily recorded (we are asking permission first, right?) and can be transcribed by hand accurately or be transcribed relatively accurately via speech-to-text tools. Voice-mail can now be captured and threaded using speech-to-text services or even is pushed as an attachment into e-mail in services as (and similar to) JConnect.
Who Will Make This Effortless?
There are three types of service that are or should be building this stitching together the fractured communications across channels into one threaded stream. I see tools that are already stitching out public (or partially public) lifestreams into one flow as one player in this pre-emergent market (Facebook, Jaiku, etc.). The other public player would be telecoms (or network provider) companies providing this as a service as they currently are providing some of these services, but as their markets get lost to VoIP, e-mail, on-line community messaging, Second Life, etc., they need to provide a service that keeps them viable (regulation is not a viable solution in the long run). Lastly, for those that do not trust or want their conversation streams in others hands the personally controlled application will become a solutions, it seems that Skype could be on its way to providing this.
Is There Demand Yet?
I am regularly fielding questions along these lines from enterprise as they are trying to deal with these issues for employees who have lost or can not put their hands on vital customer conversations or essential bits of information that can make the difference in delivering what their customers expect from them. Many have been using Cisco networking solutions that have some of these capabilities, but still not providing a catch all. I am getting queries from various telecom companies as they see reflections of where they would like to be providing tools in a Come to Me Web or facilitating bits of the Personal InfoCloud. I am getting requests from many professionals that want this type of solution for their lives. I am also getting queries from many who are considering building these tools, or pieces of them.
Some of us need these solutions now. Nearly all of us will need these solutions in the very near future.
June 16, 2007 in Access to Info, Attraction, Community, Information Architecture, Local InfoCloud, Model of Attraction, Personal Info, Personal InfoCloud, Portability, Privacy, Social Software, Technology, Ubiquitous Computing | Permalink | Comments (0) | TrackBack
Following Friends Across Walled Gardens
Phil Gyford makes his plea for a single social network sign-on or as it was stated last week by Jeremy Keith on Twitter, "portable social network with XFN" [Jeremy posted his More thoughts on portable social networks on his blog.]
The single sign-on is an often heard request these days. Nearly as much as a dashboard, er central interface to monitor all one's friends across the various walled social gardens.
I have been watching ClaimID and Marc's People Aggregator to make huge strides on this front. Some recent conversations seem to point to others possibly providing this solution. So far it is the early adopters that are needing these tools, but a recent post by Scott Andrew about people moving from MySpace to Facebook makes me think the cross-garden social tools will have a mainstream appeal in the very near future. Well, those of us that are veterans of the on-line services of the early 90s will recognize the need as our friends jumped from one closed service to another when there was a 5 dollar a month fee hike. Your buddies left Prodigy and went where? AOL, Compuserve, Delphi, usenet groups, etc.?
The current web environment makes the keeping up with your friends (if they grant you permission - this really should be the case) easier across closed social services. Digital identity will be essential as will our trusted list (or grouped list) of friends we want to keep in they loop with our life (lives).
November 22, 2006 in Community, Identity, Local InfoCloud, Personal Info, Personal InfoCloud, Social Software | Permalink | Comments (5)
The Come To Me Web
Until May of 2005 I had trouble with one element in my work around the Model of Attraction and Personal InfoCloud (including the Local and Global InfoClouds as well) to build a framework for cross-platform design and development of information and media systems and services. This problem was lack of an easy of explaination of what changes have taken place in the last few years on the web and other means of accessing digital information. In preparing for a presentation I realized this change is manifest in how people get and interact with the digital information and media.
This change is easily framed as the "Come to Me" web. The "Come to Me" web, which is not interchangeable with the push/pull ideas and terms used in the late 90s (I will get to this distinction shortly). It is a little closer to the idea of the current, "beyond the page" examinations, which most of us that were working with digital information pre-web have always had in mind in our metaphors and ideologies, like the Model of Attraction and InfoClouds.
The I Go Get Web
Before we look at the "Come to Me" web we should look at what preceded it. The "I Go Get" metaphor for the web was the precursor. In this incarnation we sought their information. The focus was on the providers of the content and the people consuming the information (or users) were targeted and lured in, in the extreme people were drawn in regardless of a person's interest in the information or topic covered. The content was that of the the organization or site that provided that information.
This incarnation focussed on people accessing the information on one device, usually the desktop computer. Early on the information was developed for proprietary formats. Each browser variant had their own proprietary way of doing things, based around a few central markup tags. People had to put up with the "best view with on X browser" messages. Information was also distributed in various other proprietary formats that required software on the device just so the person could get the information.
The focus providing information was to serve one goal (or use) reading. Some of this was driven by software limitations. But it was also an extension of information distribution in the analog physical space (as opposed to the digital space). In the physical space the written word was distributed on paper and it was consumed by reading (reuse of it meant copying it for reading) and it took physical effort to reconstruct those words to repurpose that information (quoting sources, showing examples, etc.).
The focus was on information creation and the struggle was making it findable. On the web there were only limited central resources used to find information, as many of the search engines were not robust enough, did not have friendly interfaces. Findability was a huge undertaking, either to get people what they desired/needed or to "get eyeballs".
Just as the use of the information was an extension of the physical realm that predated the digital information environment, the dominant metaphor in the "I Go Get" web was based in the physical realm. We all designed and developed for findability around the navigation/wayfinding metaphor. This directly correlates to going somewhere. Cues we use to get us to information were patterned and developed from practices in the physical world.
Physical? Digital? Does it Matter?
You ask, "So what we used ideas from the physical world to develop our metaphors and methodologies for web design and development?" We know that metaphors guide our practices. This is a very good thing. But, metaphors also constrain our practices and can limit our exploration for solutions to those that fit within the boundaries of that metaphor. In the physical realm we have many constraints that do not exist in the digital realm. Objects are not constrained by the resources they are made from (other than the energy to drive digital realm - no power no digital realm). Once an object exists in the digital realm replicating them is relatively insignificant (just copy it).
Paths and connections between information and objects is not constrained by much, other than humans choosing to block its free flow (firewalls, filtering, limiting access to devices, etc.). Much like Peter Merholz desire lines where people wear the path between two places in a manner that works best for them (the shortest distance between two points is a straight line). Now, don't think of the physical limitation between two points, I need to go from my classroom on the fourth floor of building "X" to across campus, up the hill to the sixth floor office of my professor. Draw a straight line and walk directly. This does not work in physical space because of gravity and physical impediments.
Now we are ready to understand what really happens on the web. We go from the classroom to our professors office, but we don't move. The connection brings what we desire to us and our screen. In this case we may just chat (text or video - it does not matter) with the professor from our seat in the classroom (if we even need to be in the classroom). Connections draw objects to our screens through the manifestation of links. As differently as people's minds work to connect ideas together, there can be as many paths between two objects. Use of physical space is limited by limitations outlined in physics, but the limitations are vastly different in digital space, use of the same information and media has vastly different limitations also.
It is through breaking the constraints of old metaphors and letting the digital realm exist that we get to a new understanding of digital information on the networks of the digital realm, which include the web.
The Come to Me Web
The improved understanding of the digital realm and its possibilities beyond our metaphors of the physical environment allows us to focus on a "Come to Me" web. What many people are doing today with current technologies is quite different than was done four or five years ago. This is today for some and will be the future for many.
When you talk to people about information and media today they frame it is terms of, "my information", "my media", and "my collection". This label is applied to not only information they created, but information they have found and read/used. The information is with them in their mind and more often than not it is on one or more of their devices drives, either explicitly saved or in cache.
Many of us as designers and developers have embraced "user-centered" or "user experience" design as part of our practice. These mantras place the focus on the people using our tools and information as we have moved to making what we produce "usable". The "use" in "usable" goes beyond the person just reading the information and to meeting peoples desires and needs for reusing information. Microformats and Structured Blogging are two recent projects (among many) that focus on and provide for reuse of information. People can not only read the information, but can easily drop the information into their appropriate application (date related information gets put in the person's calendar, names and contact information are easily dropped into the address book, etc.). These tools also ease the finding and aggregating of the content types.
As people get more accustom to reusing information and media as they want and need, they find they are not focussed on just one device (the desktop/laptop), but many devices across their life. They have devices at work, at home, mobile, in their living space and they want to have the information that they desire to remain attracted to them no matter where they are. We see the proliferation of web-based bookmarking sites providing people access their bookmarks/favorites from any web browser on any capable device. We see people working to sync their address books and calendars between devices and using web-based tools to help ensure the information is on the devices near them. People send e-mail and other text/media messages to their various devices and services so information and files are near them. We are seeing people using their web-based or web-connected calendars to program settings on their personal digital video recorders in their living room (or wherever it is located).
Keeping information attracted to one's self or within easy reach, not only requires the information and media be available across devices, but to be in common or open formats. We have moved away from a world where all of our information and media distribution required developing for a proprietary format to one where standards and open formats prevail. Even most current proprietary formats have non-proprietary means of accessing the content or creating the content. We can do this because application protocols interfaces (APIs) are made available for developers or tools based on the APIs can be used to quickly and easily create, recreate, or consume the information or media.
People have moved from finding information and media as being their biggest hurdle, to refinding things in "my collection" being the biggest problem. Managing what people come across and have access to (or had access to) again when they want it and need it is a large problem. In the "come to me" web there is a lot of filtering of information, as we have more avenues to receive information and media.
The metaphor and model in the "I go get" web was navigation and wayfinding. In the "come to me" web a model based on attraction. This is not the push and pull metaphor from the late 1990s (as that was mostly focussed on single devices and applications). Today's usage is truly focussed on the person and how they set their personal information workflow for digital information. The focus is slightly different. Push and pull focussed on technology, today the focus is on person and technology is just the conduit, which could (and should) fade into the background. The conduits can be used to filter information that is not desired so what is of interest is more easily identified.
January 19, 2006 in Access to Info, Attraction, Calendar, Devices, Model of Attraction, Personal Info, Personal InfoCloud, PIM, Portability, Ubiquitous Computing, Usability | Permalink | Comments (2) | TrackBack
WebVisions Designing for the Personal InfoCloud Presentation
The presentation at WebVisions of Designing for the Personal InfoCloud went quite well yesterday. There is ever growing interest in the Personal InfoCloud as there are many people working to design digital information for use across devices, for reuse, for constant access to information each individual person desires, and building applications around these interests.
In an always on world peoples desires and expectations are changing for their access to information. The tools that will help ease this desire are now being built and some are great starts have been made in this direction. I will be writing about some of these tools in the near future.
I am more exited today than I have been in quite some time by what I see as great progress for the reality of a Personal InfoCloud. It is ever closer for the Personal InfoCloud being more automated and beginning to function in ways that really help people find efficient ways to use information they have found or created in their lives when they want it or need it.
Not only does the Personal InfoCloud need devices but it needs people designing the information for the realities of Web2.0, which is not the old web of "I Go Get", but the new web of "Come to Me". This change in focus demands better understanding of sharing digital assets, designing across platforms and devices, and information being reused and organized externally.
July 16, 2005 in Access to Info, Conferences, Mobile, Personal Info, Portability, Standards, Syndication, Ubiquitous Computing, Web | Permalink | Comments (0) | TrackBack
Who Are You
The person is the center of focus in the Personal InfoCloud, but each person has to interact with others and others' information. It is at this point of interaction where identity becomes important. We use many services around the web. From Epinions to LinkedIn to our personal blogs and beyond we all have many identities and usernames. These "can" be manageable for ourselves, but often our friends value what we say and some of our opinions. We are also interested in what others say, for those opinions and taste that run similar to ours. We also are a verbose bunch writing in volumes over time. We also comment and review on many different services, like restaurant reviews on Yahoo Local, Amazon A9, and other sites.
Now lets say we are going to another city on travel. How do we leverage our friend's opinions and their network of friends reviews? In part we need granular social networks, but we also need digital identity that works.
The digital identity light went off thanks to Brett Lider and it has been a deep interest in the many months since. This may have also been triggered by the Identity Gang and the Gilmore Gang's December 30, 2004 digital identity show. Identity has been a solution fraught with schisms and opposing camps, but it seems to be coming together to some degree at this point. The more I read about digital identity from the Identity Gang and in particular Kim Cameron I realize it is central to the Personal InfoCloud.
At this point we need to modify our address books or use their notes forms to dump in our friends identities and usernames we know about across the various systems we interact with them on. This is unmanageable and not easily usable at this point. But if we want to follow John Doe and his reviews we have to know he uses jdoe, doe, paininmaximus, and 33482aad across various systems. We have to know what systems he is what identifier/username. Now lets say he gave us a card/key that he managed what we knew and he could update as he changed his information. We could then use that information in our own aggregation of information he has posted
June 12, 2005 in Access to Info, Identity, Personal Info, Social Software | Permalink | Comments (0) | TrackBack
It is Getting Personal
One of the main concepts around the Personal InfoCloud is access to our information when we need it. It has become relatively easy to find digital information on the internet these days, but keeping track of information for ourselves is a huge problem. Not only do we have the problem of tracking our information on one device, but across our devices (our laptop and desktop at work, our mobile, our PDA, our desktop at home) it become nightmare. We have gone from the scent of information (Xerox Parc term), to the current stench of information, and we are trying to get to the sweet smell of information.
One of the tools that has helped many manage some of the information they find on the web is del.icio.us. Del.icio.us is a social bookmarking tool that give the person the means to save the bookmark in a web-based tool and add tags (keywords) to the link that are of their choosing for their own bookmark retrieval. The tool really caught on as people can easily refind that information they stored because it is saved using their own vocabulary. Other people can find the same object (it is a shared "social" tool) if they use the same vocabulary to describe the same object.
It is time we all start to focus on the person and how they use and reuse the information. How do people combine disparate information in what have been separate applications and separate devices? Our design and development has to get personal.
It is these solutions an focus that are lacking from many approaches to web and application development today. Yes, it is still lacking, but it may not be for much longer.
What has changed the environment? Personalization has triggered much of this change. No, not the giant portal personalization that the content management overloads want to sell for mega-bucks and still provide mini-returns. This is personalization that allows the person to decide what information or information source is important to follow. People and vendors (be it information or products) have a desire to strengthen their connection. Vendors need to make it easy on the person who has an interest in the vendor and one or many of their products.
One of the tools that has caught on in the mainstream is RSS/Atom feeds. This allows a person to subscribe to the information that most interests them. This information can be news feeds that are targeted to specific genres or it can be a listing of products newly available, as Apple is doing with its new additions to iTunes each week and Amazon is doing for it product categories. In the past e-mail has been one of the few avenues that has been available to provide a personal connection.
So if it is getting easier to have the information from vendors easily subscribed to, how difficult should it be to subscribe to our own information? This is one of the del.icio.us solutions, well it seems to be targeted to others subscribing to our shared bookmarks, but we can easily subscribe to an RSS feed of our own bookmarks or even our own specific tagged bookmarks, should we wish to.
With calendaring we have similar subscription options if we use the iCal standard. There are even RSS event capabilities that can be incorporated (RSS with Dublin Core attributes as Upcoming does, or event module attributes). Subscribing is one solution, but often I need to add calendar events into my mobile device (Treo 600 or Nokia Series 60 phone) with out having to rekey everything. There are open standards for calendaring, why don't mobile device calendar applications just incorporate accepting these standard file types? Using standard solutions to keep all of the facets of our life, or at least our calendar related facets, seems to be a wise and relatively easy solution.
May 31, 2005 in Access to Info, Calendar, Devices, Folksonomy, Mobile, Personal Info, PIM | Permalink | Comments (1) | TrackBack
Focus of Startups
David Weingberger discusses Meet-up new charge to use plan and wonders about free competition. David, and those commenting on the posting, offer alternatives to Meetup. I am not so concerned with Meetup charging money as I am the changes that have come to Meetup in the past year, some have been very good.
I have been watching trends in the last year or two that bring a needed tool to market. It catches on and one of two things happen most often 1) they do not innovate and listen to their user base and improve on their great start, or 2) they start including other components and start looking like a social network or something not quite related to their initial goal. The exceptions to these are those that go under quickly or those that do it well get bought for their great special tool. There are many that fall into category one that flourish and stagnate and there are many valid reasons for this, change in life for the developers (married, baby, death, new job, etc.) or loss of interest. The second category seems to be the influence of money and advisors, or some odd force unknown to me.
Companies that fall into category one still have a chance. They are thin and can innovate if they focus. Look at what Upcoming.org did in a couple weeks after John Udell made some insightful comments. This is what many of us users of the site had wished for. Hopefully Upcoming will continue with the progress, but it is sticking to what it has done well, build a site around events that keeps the calendar open and easy to get a subscription to the event. Upcoming has always had a great interface that was easy to figure out and was fun to explore.
Meetup seems to have fallen in to the second category. It has been a solid site and resource, but it kept adding user features for finding people and communicating with people. Nice, but there was a lot of effort there rather than improving the ability to organize a meeting and get it off the ground. The meeting focus came back (nearly everybody I knew had the same complaint, they could not change the date or place for the event) and the site started to work much better for many. The social networking components are nice, but to have sacrificed their core interests, getting people to meet face-to-face and helping the meeting come off. Now Meetup will, inevitably loose some of its audience, but how much will be left? Had Meetup focussed on building tools for the meeting organizers they would already have something special. If the meetings don't happen they loose the flocks that come to check in on their meetings, I watched local groups wither because of Meetup's lack of focus. I am really not trying to blame anybody, just making observations.
What is the point? Focus on what you are doing that is different. Listen to your core constituency that makes your site worth going to. Make your offerings open so that the person using the service feels like they have control of their information (they should have control of that information as they are trusting the site owner's with it and trust can wither quickly). Make it easy to for the people to not only manage what information they give you, but allow them to consume this information in the manner they wish (Upcoming allowing me to subscribe to my own events I am following is a great step and that is the focus interaction should take -- the person chooses how they best want to consume the information). Focus on simplicity (of interface, of interaction, of purpose). Provide an element of play in your offering as life does not have to be boring (not too cute as cute ages fast).
April 14, 2005 in Access to Info, Information Architecture, Personal Info, Social Software, Technology, Usability | Permalink | Comments (0) | TrackBack
Good Bye to the User?
One of the side-effects of my focus on the Personal InfoCloud has been finding putting the focus on the person gets to more options than focussing on the "user". When doing user interviews for existing systems and sites, we are interviewing people. These people we ask: What works for them; what is missing; What are the devices they use; What locations do they use the information; In what context do they use the information; and How do they reuse and repurpose the information (as some of the questions). These are real people supplying the answers.
In the past we roll-up these people's answers and build an user persona. In rolling up we are building one or many common users and try to generalize. This simplification of the problem set we build to starts to limit our solutions. If one percent or less of our user base is using a mobile device to access information or our application do we throw them out of the persona? Normally, we would tend to do this and focus on a higher portion of our population.
But, in building a user-centered approach we can miss some of the easy solutions that will help the people that are part of the smaller populations. By keeping the person with the mobile needs in the mix, we are able to build scenarios and solutions that will work across many device needs. The steps between a desktop/laptop web browser only community and many mobile devices is relatively small. The difference to the desktop/laptop user is minimal, but to the mobile user it can be the difference between having access to information when it is needed and not having access at all when the information is needed most (like working remotely on a project that is 50 miles from the nearest landline and internet connection).
As we look at providing solutions we base our choices on users who make up a large percentage of our population. Lets take the 80/20 rule, we build for 80 percent of our users with 20 percent of the work. Sounds good, until we realize that one in five users are left out of the equation. By focussing on the person, we can look at extending our success. Often by building more than one solution into our products or one interface metaphor (folders versus tags for storing e-mail) we can provide better solutions that work for more people. Does this add complexity? Many times, yes it adds complexity on the design and development side, but knowing early enough in the process we can build more open and more flexible systems that lead to greater adoption. Not, only do we get greater adoption, but we open up the potential for uses beyond what we designed into being.
No two people are alike and we should build toward this reality so that there is choice, freedom, and ease. The more granular approach does not completely wipe out the user personas, but greatly enhances their functionality. Go back to the original people interviewed and use them in scenario planning for their needs across their contexts and tasks. How well does what we are designing work for them? How different will a solution need to be to have it work for them? Do these users have older technology? Do we want to rule people out categorically or can we do a little more work and be inclusive?
Focussing on the person and the granularity is where things get more difficult, but this is where we can make huge differences. This is what we get paid for right?
April 12, 2005 in Access to Info, Accessibility, Devices, Location, Mobile, Personal Info, Portability, Usability | Permalink | Comments (0) | TrackBack
SXSW Calendar the Personal Way
I really enjoyed my short time at SXSW Interactive Festival this year. One of the things that helped me was their step to help people interested in SXSW to build their "own" calendar. Yes, they understood the people attending have a lot of offerings to consider and nobody wants to miss anything they really would like to see. The SXSW site showed the conference sessions and if you liked it you could add it to your SXSW calendar. This calendar could be accessed as an iCal, which means as you update the calendar on the site, or the calendar is changed by the SXSW folks, you calendar is updated. Being that it is iCal it is relatively easy to synch this to your mobile device.
Why is this important? It is not only a great step to help the people attending the Festival, but it builds a connection between the person and the SXSW site as well as a enables the person enjoyment of the Festival. Technology should help the person control what they would like to do and help them do it with out worry.
I remember my first SXSW in 2001, where they had a Palm Pilot that would beam you a packet including the conference sessions as well as food and other amenities. The application allowed you to add the SXSW sessions into your Palm calendar and restaurants into your address book. It was a great app, but you only got the application when you got there and you had to have a Palm device (luckily I did). This year's version greatly improved on this as it allows the person attending to build their own calendar and choose how they want the information to follow them. The person attending just added the information to their own Personal InfoCloud and the person consumed and reused the information as needed.
Brilliant and Bravo.
March 26, 2005 in Access to Info, Applications, Information Creation, Personal Info, Portability | Permalink | Comments (0) | TrackBack
Recent Speaking Engagements
I have posted the last three presentations I have given in the last five days. The presentations and a little about each presentation are available as follows: IA for the Personal InfoCloud from the IA Summit, Folksonomy: A Wrapper's Delight a panel at the IA Summit, and The Blog as Personal Knowledge Managment from a panel at the local Potomac Chapter of ASIS&T.
Some of the ideas and themes in these will bubble up here fairly soon. I am also speaking in Austin at SXSW Interactive Festival this upcoming Sunday. Stop by and say hello.
March 10, 2005 in Access to Info, Conferences, Folksonomy, Information Architecture, Location, Mobile, Personal Info, Portability | Permalink | Comments (1) | TrackBack
Stitching our Lives Together
Not long ago Jeffrey Veen posted about Will you be my friend, which brought up some needs to better stitch together our own disperse information. An excellent example is:
For example, when I plan a trip, I try to find out who else will be around so I have people to hang out with. So my calendar should ask Upcoming.org, "Hey, Jeff says he's friends with Tim. Will he be in New York for GEL?"
This example would allow up to interact with our shared information in a manner that keeps it within our extended Personal InfoCloud (the Personal InfoCloud is the information we keep with us, is self-organized, and we have easy access to). Too many of the Web's resources where we store our information and that information's correlation to ourselves (, Flickr seems to use. The advent of wide usage of RSS feeds and RSS aggregators is really putting the user back in control of the information they would like to track. Too many sites have moved toward the portal model and failed (there are large volumes of accounts of failed portal attempts, where the sites should provide a feed of their information as it is a limited quantity). When users get asked about their lack of interest in a company's new portal they nearly always state, "I already have a portal where I aggregate my information". Most often these portals are ones like My Yahoo, MSN, or AOL. Many users state they have tried keeping more than one portal, but find they loose information very quickly and they can not remember, which portal holds what information.
It seems the companies that sell portal tools should rather focus on integration with existing portals. Currently Yahoo offers the an RSS feed aggregator. Yahoo is moving toward a one stop shopping for information for individuals. Yahoo also synchs with PDA, which is how many people keep their needed information close to themselves.
There are also those of us that prefer to be our own aggregators to information. We choose to structure our large volumes of information and the means to access that information. The down side of the person controlling the information is the lack of common APIs and accessible Web Services to permit the connecting of Upcoming to our calendar (it can already do this), with lists of known or stated friends and their interests.
This has been the dream of many of us for many years, but it always seems just around the corner. Now seems to be a good time to just make it happen. Now is good because there is growing adoption of standards and information that can be personally aggregated. Now is good because there are more and more services allowing us to categorize various bits of information about our lives. Now is good because we have the technology. Now is good because we are smart enough to make it happen.
(Originally posted at vanderwal.net.)
April 11, 2004 in Access to Info, Community, Information Creation, Mobile, Personal Info, Portability, Social Software, Standards, Syndication, Usability | Permalink | Comments (4)
PC Forum Eventspace - Users Make Content Their Own
PC Forum Eventspace - Users Make Content Their Own seems to have only part of the equation correct.
It seems that the commercial ventures only partly understand the Personal InfoCloud. The panel, as I read the excerpts, (Rob Glaser of Real Networks, Lisa Gansky of Ofoto and Shane Robison of HP) understand users creation of information as content creators. Having used Real products and Ofoto, they do not seems to fully get the personal management of the information very well. These products set barriers to reuse and have poor interaction design.
Lets look at Ofoto, which has a good business model to upload photos to share them and allow the user and their friends to make prints of the photos. The tools for photo management have a lot to be desired. The tools only permit management of the photos for Ofoto's use. Users want more management than these uses. I have been frustrated with photos that have gone missing in Ofoto albums.
The tools do not allow the user to manage information across devices. Moving digital media easily from PC to handheld and to the Web easily and seamlessly should be the goal. This transfer of digital media and content is the idea behind the Personal InfoCloud. This is what keeps the users from using devices and technology in general to help their lives.
Maybe next years PC Forum will focus on better understanding the Personal InfoCloud. In the Great Weird Ideas notes Brett Fausett's ideas on Personal Data for Personal Services is on target with the Personal InfoCloud.
March 28, 2004 in Applications, Content Mangement, Information Creation, Marketplace, Personal Info