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
Getting Info into the Field with Extension
This week I was down in Raleigh, North Carolina to speak at National Extension Technology Conference (NETC) 2008, which is for the people running the web and technology components for what used to be the agricultural extension of state universities, but now includes much more. This was a great conference to connect with people trying to bring education, information, and knowledge services to all communities, including those in rural areas where only have dial-up connectivity to get internet access. The subject matter presented is very familiar to many other conferences I attend and present at, but with a slightly different twist, they focus on ease of use and access to information for everybody and not just the relatively early adopters. The real values of light easy to use interfaces that are clear to understand, well structured, easy to load, and include affordance in the initial design consideration is essential.
I sat in on a few sessions, so to help tie my presentation to the audience, but also listen to interest and problems as they compare to the organizations I normally talk to and work with (mid-size member organizations up to very large global enterprise). I sat in on a MOSS discussion. This discussion about Sharepoint was indiscernible from any other type of organization around getting it to work well, licensing, and really clumsy as well as restrictive sociality. The discussion about the templates for different types of interface (blogs and wikis) were the same as they they do not really do or act like the template names. The group seemed to have less frustration with the wiki template, although admitted it was far less than perfect, it did work to some degree with the blog template was a failure (I normally hear both are less than useful and only resemble the tools in name not use). [This still has me thinking Sharepoint is like the entry drug for social software in organizations, it looks and sounds right and cool, but is lacking the desired kick.]
I also sat down with the project leads and developers of an eXtension wide tool that is really interesting to me. It serves the eXtension community and they are really uncoupling the guts of the web tools to ease greater access to relevant information. This flattening of the structures and new ways of accessing information is already proving beneficial to them, but it also has brought up the potential to improve ease some of the transition for those new to the tools. I was able to provide feedback that should provide a good next step. I am looking forward to see that tool and the feedback in the next three to six months as it has incredible potential to ease information use into the hands that really need it. It will also be a good example for how other organizations can benefit from similar approaches.
May 2, 2008 in Access to Info, Accessibility, Community, Connectivity, Enterprise, Folksonomy, Interface, Knowledge Management, Model of Attraction, Portability, Reference, Syndication, Technology, Tools, Web | Permalink | Comments (0) | TrackBack
Explaining the Granular Social Network
This post on Granular Social Networks has been years in the making and is a follow-up to one I previously made in January 2005 on Granular Social Networks as a concept I had been presenting and talking about for quite some time at that point. In the past few years it has floated in and out of my presentations, but is quite often mentioned when the problems of much of the current social networking ideology comes up. Most of the social networking tools and services assume we are broadline friends with people we connect to, even when we are just "contacts" or other less than "friend" labels. The interest we have in others (and others in us) is rarely 100 percent and even rarer is that this 100 percent interest and appreciation is equal in both directions (I have yet to run across this in any pairing of people, but I am open to the option that it exists somewhere).
Social Tools Need to Embrace Granularity
What we have is partial likes in others and their interests and offerings. Our social tools have yet to grasp this and the few that do have only taken small steps to get there (I am rather impressed with Jaiku and their granular listening capability for their feed aggregation, which should be the starting point for all feed aggregators). Part of grasping the problem is a lack of quickly understanding the complexity, which leads to deconstructing and getting to two variables: 1) people (their identities online and their personas on various services) and 2) interests. These two elements and their combinations can (hopefully) be seen in the quick annotated video of one of my slides I have been using in presentations and workshops lately.
Showing Granular Social Network
Granular Social Network from Thomas Vander Wal on Vimeo.
The Granular Social Network begins with one person, lets take the self, and the various interest we have. In the example I am using just five elements of interest (work, music, movies, food, and biking). These are interest we have and share information about that we create or find. This sharing may be on one service or across many services and digital environments. The interests are taken as a whole as they make up our interests (most of us have more interests than five and we have various degrees of interest, but I am leaving that out for the sake of simplicity).
Connections with Others
Our digital social lives contain our interests, but as it is social it contains other people who are our contacts (friends is presumptive and gets in the way of understanding). These contacts have and share some interests in common with us. But, rarely do the share all of the same interest, let alone share the same perspective on these interests.
Mapping Interests with Contacts
But, we see when we map the interests across just six contacts that this lack of fully compatible interests makes things a wee bit more complicated than just a simple broadline friend. Even Facebook and their touted social graph does not come close to grasping this granularity as it is still a clumsy tool for sharing, finding, claiming, and capturing this granularity. If we think about trying a new service that we enjoy around music we can not easily group and capture then try to identify the people we are connected to on that new service from a service like Facebook, but using another service focussed on that interest area it could be a little easier.
When we start mapping our own interest back to the interest that other have quickly see that it is even more complicated. We may not have the same reciprocal interest in the same thing or same perception or context as the people we connect to. I illustrate with the first contact in yellow that we have interest in what they share about work or their interest in work, even though they are not stating or sharing that information publicly or even in selective social means. We may e-mail, chat in IM or talk face to face about work and would like to work with them in some manner. We want to follow what they share and share with them in a closer manner and that is what this visual relationship intends to mean. As we move across the connections we see that the reciprocal relationships are not always consistent. We do not always want to listen to all those who are sharing things, with use or the social collective in a service or even across services.
Focus On One Interest
Taking the complexity and noise out of the visualization the focus is placed on just music. We can easily see that there are four of our six contacts that have interest in music and are sharing their interest out. But, for various reasons we only have interests in what two of the four contacts share out. This relationship is not capturing what interest our contacts have in what we are sharing, it only captures what they share out.
Moving Social Connections Forward
Grasping this as a relatively simple representation of Granular Social Networks allows for us to begin to think about the social tools we are building. They need to start accounting for our granular interests. The Facebook groups as well as listserves and other group lists need to grasp the nature of individuals interests and provide the means to explicitly or implicitly start to understand and use these as filter options over time. When we are discussing portable social networks this understanding has be understood and the move toward embracing this understanding taken forward and enabled in the tools we build. The portable social network as well as social graph begin to have a really good value when the who is tied with what and why of interest. We are not there yet and I have rarely seen or heard these elements mentioned in the discussions.
One area of social tools where I see this value beginning to surface in through tagging for individuals to start to state (personally I see this as a private or closed declaration that only the person tagging see with the option of sharing with the person being tagged, or at least have this capability) the reasons for interest. But, when I look at tools like Last.fm I am not seeing this really taking off and I hear people talking about not fully understanding tagging as as it sometimes narrows the interest too narrowly. It is all an area for exploration and growth in understanding, but digital social tools, for them to have more value for following and filtering the flows in more manageable ways need to more in grasping this more granular understanding of social interaction between people in a digital space.
April 15, 2008 in Attraction, Attraction Receptor, Community, Folksonomy, Knowledge Management, Local InfoCloud, Model of Attraction, Portability, Privacy, Social Software | Permalink | Comments (2) | TrackBack
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
Can Facebook Change Its DNA?
The posting on Facebook for Business or LinkedIn Gets More Valuable received a lot of feedback and discussion. The e-mail discussions has urged me to post about the Facebook DNA and why it will be tough to transition Facebook into a really valuable tool for business without changing the services to a great degree. A social platform like Facebook is desperately needed for business, within enterprise, and organization that have information flows between the people interested in or that are members of an organization. The platform for this type of community has slightly different needs that Facebook does not provide.
Facebook and Its Initial User-base
It is not secret that Facebook started as a services that was by and for students and members of a university setting. The focus was connecting to people you have run across or will run across as friends, acquaintances from social events, or classmates. The services is quite conversational and does a decent job pulling together a person's shared digital lifestream (many others have done this for years and do it much better, Jaiku (now owned by Google) is one example of a much better approach).
Facebook as a service tended to focus on the current conversation as students largely are focussed on the now or short-time frame planning, e.g. it is Tuesday and what are people doing on Thursday through the weekend or who is going skiing this weekend and putting together a carpool. The time span of conversation and interest is etherial and Facebook very much reflects the short term nature of conversation. The focus is also students in networks framed as campuses, which enables this Local InfoCloud of familiarity to be used for memory, which is not needed in the service. This means if I see something in Facebook, say a good restaurant for a special date night, I can track down the person who suggested the restaurant or tap friends in the network (on campus) to recall the restaurant. This foundation of building a digital space for people in a common physical network does not need strong search or capability to hold-on to information that may have future value.
The reliance on building a digital services that replicates the frailties of physical communication (all hallway, classroom, or party conversation is lost to the ether and is reliant of human memory) is problematic when the people using the service are physically distributed.
Future Information Value
Facebook's largest failure is the lack of using digital conversation for the great value digital conversation provides, which is capturing conversation and information. This capturing of digital conversation has great value as the information that is shared often has much greater future value than current value. Take the same restaurant example from before, when a friend recommends a restaurant I may not have a need for that romantic restaurant now, but I most likely may need that information at sometime in the future. There are two things that I can do with that information: 1) Know the information is in the service and can search for it at a later time ("restaurant" and "romantic" in search, which may also find others have made the same recommendation); or 2) Mark the information in some manner for my ease of refinding (flag, favorite, or bookmark it with annotation from my perspective and context).
The Challenge Facebook has Changing
Making this shift in Facebook will be a huge challenge, not for the developers or technology (although Facebook has not modified its interface to handle the scaling of information flows of applications or increase in traffic, but that is another real problem that needs addressing) as they seem capable to make the minor technology changes that would be needed to use the service for improved search or holding onto information. The big pain point will be making a change that is counter to the understanding and use of those who still make up the core of its use-base, university students. When Facebook opened its doors beyond university students it created panic (well deserved) as their closed society was open to all viewers. The difficulty in holding on to information and searching through the services did not keep people from finding party photos or profiles that were meant for just friends and not future employers or others outside their immediate network. A large number of people left, or more accurately stopped using the service as much as they did (after removing the potentially problematic images and content).
There is an incredible mass of information in Facebook, most of it nearly impossible to find and hold onto at this point. Many of the people who have used the service have relied on this obscurity to keep from removing the (at the moment funny, ironic, humorous, or even not fully informed) statements made on walls, groups, status updates, and other places. Changing the core platform to create value for the people using the service as a digital information platform, that is similar to what is expected outside Facebook could have dire repercussions for Facebook as a service. But, not making these changes makes Facebook a really poor platform for business and knowledge sharing.
Valuable Lesson in Foundations
Having build many web base services, intranet, and networked services over the many years I have been doing this it continually comes back to the initial foundations are the ones that are hardest to shake. The initial people using a service shape it for the future and the initial technology decisions of a service often are the ones that are hardest to change. This change is difficult as the practices are socially ingrained into the understanding of the mores of the system and the social interactions are predicated on these understandings. All design and all interaction aspects of systems are political and drive people's motivation for use as they set the rules and social scripts for interaction. The components are not intentionally political, but they have do trigger reaction and alter motivations no mate how slightly. Not only does the medium have a message, but how the services works or does not work has a message that triggers a response for if and how it is used.
November 2, 2007 in Access to Info, Community, Enterprise, Identity, Information Creation, Local InfoCloud, Portability, Refindability, Social Software | Permalink | Comments (1) | TrackBack
A Stale State of Tagging?
David Weinberger posted a comment about Tagging like it was 2002, which quotes Matt Mower discussing the state of tagging. I mostly agree, but not completely. In the consumer space thing have been stagnant for a while, but in the enterprise space there is some good forward movement and some innovation taking place. But, let me break down a bit of what has gone on in the consumer space.
History of Tagging
The history of tagging in the consumer space is a much deeper and older topic than most have thought. One of the first consumer products to include tagging or annotations was the Lotus Magellan product, which appeared in 1988 and allowed annotations of documents and objects on one's hard drive to ease finding and refinding the them (it was a full text search which was remarkably fast for its day). By the mid-90s Compuserve had tagging for objects uploaded into its forum libraries. In 2001 Bitzi allowed tagging of any media what had a URL.
The down side of this tagging was the it did not capture identity and assuming every person uses words (tag terms) in the same manner is a quick trip to the tag dump where tags are not fully useful. In 2003 Joshua Schacter showed the way with del.icio.us that not only allowed identity, upon which we can disambiguate, but it also had a set object in common with all those identities tagging it. The common object being annotated allows for a beginning point to discern similarity of identityĵs tag terms. Part of this has been driven on Joshua's focus on the person consuming the content and allowing a means for that consumer to get back to their information and objects of interest. (It is around this concept that folksonomy was coined to separate it from the content publisher tagging and non-identity related tagging.) This picked up on the tagging for one's self that was in Lotus Magellan and brings it forward to the web.
Valuable Tagging
It was in del.icio.us that we saw tagging that really did not work well in the past begin to become valuable as the clarity in tag terms that was missing in most all other tagging systems was corrected for in the use of a common object being tagged and the identity of the tagger. This set the foundation for some great things to happen, but have great things happened?
Tagging Future Promise
Del.icio.us set many of out minds a flutter with insight into the dreams of the capability of tagging having a good foothold with proper structure under them. A brilliant next step was made by RawSugar (now gone) to use this structure to make ease of disambiguating the tag terms (by appleseed did you mean: Johnny Appleseed, appleseeds for gardening/farming, the appleseed in the fruit apple, or appleseed the anime movie?). RawSugar was a wee bit before its time as it is a tool that is needed after there tagging (particularly folksonomy related tagging systems) start scaling. It is a tool that many in enterprise are beginning to seek to help find clarity and greater value in their internal tagging systems they built 12 to 18 months ago or longer. Unfortunately, the venture capitalists did not have the vision that the creators of RawSugar did nor the patience needed for the market to catch-up to the need in a more mature market and they pulled the plug on the development of RawSugar to put the technology to use for another purpose (ironically as the market they needed was just easing into maturity).
The del.icio.us movement drove blog tags, laid out by Technorati. This mirrored the previous methods of publisher tagging, which is most often better served from set categories that usually are derived from a taxonomy or simple set (small or large) of controlled vocabulary terms. Part of the problem inherent in publisher tags and categories is that they are difficult to use outside of their own domain (however wide their domain is intended - a specific site or cross-sites of a publisher). Using tags from one blog to another blog has problems for the same reason that Bitzi and all other publisher tags have and had problems, they are missing identity of the tagger AND a clear common object being tagged. Publisher tags can work well as categories for aggregating similar content within a site or set of commonly published sites where a tag definition has been set (but that really makes them set categories) and used consistently. Using Technorati tag search most often surfaces this problem quickly with many variation of tag use surfacing or tag terms being used to attract traffic for non-related content (Technorati's keyword search is less problematic as it relies on the terms being used in context in the content - unfortunately the two searches have been tied together making search really messy at the moment). There is need for an improved tool that could take the blog tags and marry them to the linked items in the content (if that is what is being talked about - discerning predicate in blog tags is not clear yet).
Current Tools that Advanced
As of a year ago there were more than 140 social bookmarking tools in the consumer space, but there was little advancement. But, there are a few services that have innovated and brought new and valuable features to market in tagging. As mentioned recently Ma.gnolia has done a really good job of taking the next steps with social interaction in social bookmarking. Clipmarks pioneered the sub-page tagging and annotation in the consumer tagging space and has a really valuable resource in that tool. ConnectBeam is doing some really good things in the enterprise space, mostly taking the next couple steps that Yahoo MyWeb2 should have taken and pairing it with enterprise search. Sadly, del.icio.us (according to comments in their discussion board) is under a slow rebuilding of the underlying framework (but many complaints from enterprise companies I have worked with and spoken indepth with complain del.icio.us continually blocks their access and they prefer not to use the service and are finding current solutions and options to be better for them).
A Long Way to Go
While there are examples that tagging services have moved forward, there is so much more room to advance and improve. As people's own collection of tagged pages and objects have grown the tools are needed to better refind them. This will require time search and time related viewing/scanning of items. The ability to use co-occurance of tag terms (what other tags were used on the object), with useful interfaces to view and scan the possibilities.
Portability and interoperability is extremely important for both the individual person and enterprise to aggregate, migrate, and search across their collections across services and devices (now that devices have tagging and have had for some time, as in Mac OS X Tiger and now Vista). Enterprises should also have the ability to move external tagged items in through their firewall and publish out as needed, mostly on an employee level. There is also desire to have B2B tagging with customers tagging items purchased so the invoicing can be in the customers terminology rather than the seller terminology.
One of the advances in personal tagging portability and interoperability can easily be seen when we tag on one device and move the object to a second device or service (parts of this are not quite available yet). Some people will take a photo on their mobile phone and add quick tags like "sset" and others to a photo of a sunset. They send that photo to a service or move it to their desktop (or laptop) and import the photo and the tag goes along with it. The application sees the "sset" and knows the photo was transfered from that person's mobile device and knows it is their short code for "sunset" and expands the tag to sunset accordingly. The person then adds some color attribute tags to the photo and moves the photo to their photo sharing service of choice with the tags appended.
The current tools and services need tools and functionality to heal some of the messiness. This includes stemming to align versions of the same word (e.g. tag, tags, tagging, bookmark, bookmarking). Tag with disambiguation in mind by offering co-occurrence options (e.g. appleseed and anime or johnny or gardening or apple). String matching to identify facets for time and date, names (from your address book), products, secret tag terms (to have them blocked from sharing), etc. (similar to Stikkit and GMail).
Monitoring Tools
Enterprise is what the next development steps really need to take off (these needs also apply to the power knowledge worker as well). The monitoring tools for tags from others and around objects (URLs) really need to fleshed out and come to market. The tag monitoring tools need to become granular based on identity and co-occurance so to more tightly filter content. The ability to monitor a URL and how it is tagged across various services is a really strong need (there are kludgy and manual means of doing this today) particularly for simple and efficient tools (respecting the tagging service processing and privacy).
Analysis Tools
Enterprise and power knowledge workers also are in need of some solid analysis tools. These tools should be able to identify others in a service that have similar interests and vocabulary, this helps to surface people that should be collaborating. It should also look at shifts in terminology and vocabulary so to identify terms to be added to a taxonomy, but also provide an easy step for adding current emergent terms to related older tagged items. Identify system use patterns.
Just the Tip
We are still at the tip of the usefulness of tagging and the tools really need to make some big leaps. The demands are there in the enterprise marketplace, some in the enterprise are aware of them and many more a getting to there everyday as the find the value real and ability to improve the worklife and workflow for their knowledge workers is great.
The people using the tools, including enterprise need to grasp what is possible beyond that is offered and start asking for it. We are back to where we were in 2003 when del.icio.us arrived on the scene, we need new and improved tools that understand what we need and provide usable tools for those solutions. We are developing tag islands and silos that desperately need interoperability and portability to get real value out of these stranded tag silos around or digital life.
August 29, 2007 in Access to Info, Enterprise, Folksonomy, Identity, Portability | Permalink | Comments (0) | 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
The Future is Now for Information Access
An interview with Microsoft's Steve Ballmer in the in the San Francisco Chronicle regarding Steve's thoughts about the future of technology, information, and Microsoft (including their competition) sparked a few things regarding the Personal InfoCloud and Local InfoCloud. It could be the people I hang out with and the stay-at-home parents I run across during the day, but the future Ballmer talks about is happening now! The future will more widely distributed in 10 years, but the desire and devices are in place now. The thing holding everything back is content management systems that are built for the "I Go Get Web" and people implementing those systems that see technology and not a web of data.
Let's begin with Ballmer's response to the question, "Ten years from now, what is the digital world going to look like? To which Ballmer responds: A: People are going to have access to intelligence in multiple ways. I'm going to want to have intelligence in my pocket. I'm going to want to have intelligence in my TV. I'm going to want to have intelligence in my den and in my office. And what I may want in terms of size, of screen size, of input techniques, keyboard, handwriting, voice, may vary.I think what we'll see is, we have intelligence everywhere. We have multiple input techniques, meaning in some sense you may have some bit of storage which travels with you everywhere, effectively. Today, people carry around these USB storage devices, but you'll carry around some mobile device.
The problem is people have the devices in their pockets today in the form of Blackberries, Treos, Nokia 770s, and just regular mobile phones with browsing and syncing. The access to the information is in people's pockets. The software to make it simple with few clicks is where the battle lies. My Palm OS-based Treo 650 is decent, but it has few clicks to get me to my information. My friends with the Windows version of the same device have six or more clicks for basic things like calendar and address book. Going through menus is not simplicity. Going directly to information that is desired is simplicity. A mobile devices needs simplicity as it is putting information in our hands with new contexts and other tasks we are trying to solve (driving, walking, meeting, getting in a taxi, getting on a bus, etc.).
The Information
Not only does the software have to be simple to access information in our Personal InfoCloud (the information that we have stated we want and need near us, but have structured in our personal framework of understanding). We also interact with the Local InfoCloud with is information sources that is familiar to us to which we have set a means of easing interaction (cognitively, physically, or mechanically).This "intelligence" that Ballmer refers to is information in the form of data. It needs to be structured to make solid use of that information in our lives. This structure needs to ascend below the page level to at least the object level. The object level can be a photo with the associated metadata (caption, photographer, rights, permanent source, size, etc.), event information (event name, location, date and time, permanent location of the information, organizer, etc.), full-text and partial-text access (title, author, contact info, version, date published, rights, headers, paragraphs, etc.).
These objects may comprise a page or document on the web, but they not only have value as a whole, they have value as discrete objects. The web is a transient information store for data and media, it is a place to rest this information and object on its journey of use and reuse. People use and want (if not need) to use these objects in their lives. Their lives are comprised of various devices with various pieces of software that work best in their life. They want to track events, dates, people, ideas, media, memes, experts, friends, industries, finances, workspaces, competition, collaborators, entertainment, etc. as part of their regular lives. This gets very difficult when there is an ever growing flood of information and data bombarding us daily, hourly, consistently.
This is not a future problem. This is a problem right now! The information pollution is getting worse every moment we sit here. How do we dig through the information? How do we make sense of the information? How do we hold on to the information?
The solutions is using the resources we have at our finger tips. We need access to the object level data and the means to attach hooks to this data. One solution that is rising up is Microformats, which Ray Ozzie of Microsoft embraces and has been extending with his Live Clipboard, which is open for all (yes all operating systems and all applications) to use, develop, and extend. The web, as a transient information store, must be open to all comers (not walled off for those with a certain operating system, media player, browser, certain paid software, etc.) if the information is intended for free usage (I am seeing Microsoft actually understand this and seemingly embrace this).
Once we have the information and media we can use it and reuse it as we need. But, as we all know information and media is volatile, as it changes (for corrections, updates, expanding, etc.) and we need to know that what we are using and reusing is the best and more accurate information. We need the means to aggregate the information and sync the information when it changes. In our daily lives if we are doing research on something we want to buy and we bookmark it, should we not have the capability to get updates on the prices of the item? We made an explicit connection to that item, which at least conveys interest. Is it not in the interest of those selling the information to make sure we have the last price, if not changes to that product? People want and need this. It needs to be made simple. Those that get this right will win in the marketplace.
What is Standing in the Way?
So, the big question is, "what is standing in the way"? To some degree it is the tools with which we create the information and some of it is people not caring about the information, data, and media they expose.The tools many of the large information providers are using are not up to the task. Many of the large content management systems (CMS) do not provide simple data structures. The CMS focusses on the end points (the devices, software, tools, etc.) not the simple data structures that permit simple efficient use and reuse of the objects. I have witnessed far too many times a simple web page that is well structured that is relatively small (under 40KB) get turned into an utter mess that is unstructured and large (over 200KB). Usable, parseable, and grabable information is broken by the tools. The tools focus on what looks good and not what is good. Not only is the structure of the data and objects broken, but they are no longer addressable. There are very few CMS that get it right, or let the developers get it right (one that gets it right is Axiom [open disclosure: I have done work with Siteworx the developer of Axiom]).
The other part of the problem is the people problem, which is often driven by not understanding the medium they are working within. They are focus on the tools, which are far from perfect and don't care enough to extend the tools to do what they should. Knowing the proper format for information, data, media, etc. on the web is a requirement for working on the web, not something that would be nice to learn someday. Implementing, building, and/or creating tools or content for the web requires understanding the medium and the structures that are inherent to building that well. I have had far too many discussions with people who do not understand the basics of the web nor the browser, which makes it nearly impossible to explain why their implementation fails. Content on the web has requirements to be structured well and the pages efficiently built. The pages need to degrade (not with an $80,000 plug-in) by default. Media on the web that is for open consumption must work across all modern systems (this should be a 3 year window if not longer for the "modern" definition).
Summary
So what is the take away from this? Content needs to be built with proper structure to the sub-object level (objects need the metadata attached and in standard formats). The content needs to be open and easily accessed. Portability of the information into the tools people use that put information in our pockets and lives must be done now. We have the technology now to do this, but often it is the poorly structured or formatted information, data, media, etc. that stands in the way. We know better and for those that don't know yet the hurdle is quite low and easy to cross.May 23, 2006 in Access to Info, Attraction, Coding, Content Mangement, Devices, Information Creation, Local InfoCloud, Marketplace, Mobile, Personal InfoCloud, PIM, Portability, Standards, Syndication, Ubiquitous Computing, Usability | Permalink | Comments (1) | TrackBack
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
Europe Presentations from October
I am late in posting the links to my two presentations given in Europe. I presented the Personal Digital Convergence as the opening keynote to the SIGCHI.NL - HCI Close to You conference. I have also posted the final presentation, IA for the Personal InfoCloud, at the Euro IA Summit 2005.
October 25, 2005 in Access to Info, Attraction, Devices, Local InfoCloud, Model of Attraction, Personal InfoCloud, PIM, Portability, Ubiquitous Computing | 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
Social Machines
Those of you that follow this site will also likely enjoy Wade Roush's continuousblog. Wade is the West Coast editor for the MIT Technology Review magazine. He has the August cover story in the TechReview titled, "Social Machines" and has posted Social Machines on his site as of today. Please be sure to pick up a print copy and/or read the article on the TechReview site when it is published there.
[I should mention I am quoted in the "Social Machines" article]
July 5, 2005 in Access to Info, Community, Devices, Mobile, Portability, Social Software, Ubiquitous Computing, Web | 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)
A Look at iPIM and Chandler
There are two articles that are direct hits on managing information for the individual and allowing the individual to use the information when they needed it and share it as needed. Yes, this is in line with the Personal Information Cloud.
The first article, The inter-personal information manager (iPim) by Mark Sigal about the problem with users finding information and how the can or should be able to then manage that information. There are many problems with applications (as well as the information format itself) that inhibit users reuse of information. In the comments of the article there is a link to products that are moving forward with information clients, which also fit into the Personal Information Cloud or iPIM concept. (The Personal Information Cloud tools should be easily portable or mobile device enabled or have the ability to be retrieved from anywhere sent to any device.
The second article is from the MIT Technology Review (registration required) titled Trash Your Desktop about Mitch Kapor (of founding Lotus Development fame) and his Open Source project to build Chandler. Chandler is not only a personal information manager (PIM), but the tool is a general information manager that is contextually aware. The article not only focusses on Mitch and the product (due late 2004), but the open and honest development practices of those that are building Chandler at the Open Source Application Foundation for Windows, Mac, Linux, etc. distribution.
November 1, 2003 in Access to Info, Connectivity, Content Mangement, Information Creation, Mobile, Portability, Technology, Usability | Permalink | Comments (0) | TrackBack
Information Structure for Information Reuse
John Udell's discussion of Apple's Knowledge Navigator is a wonderful overview of a Personal Information Cloud. If the tools was more mobile or was shown synching with a similar mobile device to have the "knowledge" with the user at all time it is would be a perfect representation.
Information in a Personal Information Cloud is not only what the user wants to have stored for retrieval when it is needed (role-based information and contextual) but portable and always accessible. Having tools that allow the user to capture, categorize, and have attracted to the user so it is always with them is only one part of the equation. The other component is having information that is capable of being captured and reused. Standards structures for information, like (X)HTML and XML are the beginnings of reusable information. These structures must be open to ensure ease of access and reuse in proper context. Information stored in graphics, proprietary software, and proprietary file formats greatly hinders the initial usefulness of the information as it can be in accessible, but it even more grea