Personal InfoCloud

Personal

The first step or home base, is more of a state for beginning, is the the personal space and repository. Sadly, this is the ugly step child that is very often missed in many tools/service offerings. The place were a person has a view of their resources, which is mapped in their context and needed representations to make sense with the least effort. This is the view with things they need to see surface (from their perspective and from others) and from where they jump to interacting with information, objects, tasks, and others.

Sparks (Ideas Shared)

The first step often comes from asking questions simply and easily and quick easy responses, or sharing quick notes and ideas that get feedback and interest. Many times this is done efficiently in micro sharing services like similar to Twitter but with a grasp of needs organizations have (Socialtext Signals or Socialcast are solid options to consider). But, other options, including blogs and discussion forums have the capability of doing this as well.

With sparks of ideas they need to have the ability to be found so to be responded to, aggregated, or even shared to ensure the right people see them and can interact. There is a wide breadth of types of things that flow through micro sharing services, but many will resonate, inform, or inspire others. But, quite often they get solid conversations flowing across a broad cross section of people and locations.

Campfire (Gathering of Others with Interest)

From the spark of inspiration many others with interest or affinity gather to discuss and the spark turns into a campfire. Stories are told and fuel is added to the fire. Honing of the ideas and gather inspiration, information, and content from broad sources and view is then curated and honed to some degree.

The tools needed for the campfire stage must allow from much broader conversation than the limited spark stage. Limiting the room around the campfire to those with strong interest and affinity helps keep the focus, but also these people will likely have the deepest reserves of fodder for the conversation and a wide variety of perspectives and resources they can tap ready at hand. Longer conversation and curating all that is gathers are the prime focus. Curation through tagging is often incredibly helpful (being able to tag so to aggregate and curate ideas from the sparks stage is highly important).

Bonfire (Broader Interest Gathering)

Once the ideas have been fleshed out and framed to some degree and curated to control scope the discussion turns into a bonfire. Bonfires, while much larger still need to be controlled and maintained or they get out of control and things get dangerous. At this stage broad viewing for healthy feedback and discussion, including highlighting things that have been missed, what works well, what doesn't work well, etc. are the key focus. This is the time to get understanding and direction that hones and shapes everything that is possible. It is also used to add to what has been gathered and curated in the campfire stage so to iterate on it.

Torch (Honing for Broad Use & Replication)

Lastly, is the torch stage. This is easy to handle, easy to replicate, and is safe. This requires Real Collaboration to work through the conflicting ideas and negotiate as well as intelligently work toward one final output. These final outputs can be white papers, new processes, new guidelines, new products, etc. But, the point is there is one (just like artists collaborating on a statue there is only one statue, not many and all through differences have been worked through to one salient solution).

We Can't Find Anything

There is nothing more common that I hear from an organization about their intranet and internal information services than, "We can't find anything." (Some days I swear this is the mantra that must be intoned for an organization to become real.)

There are many reasons and potential solutions for improving the situation. Some of these involve improved search technologies, some improved search interfaces, or But, understanding the cost of this inefficiency is where I find it is valuable to start.

The first step after understanding you have this problem is to measure it, but most organizations don't want to pay for that they are just looking for solutions (we all know how this turns out). The best method I find is walking through the broad understandings of the cost of inefficiencies.

The Numbers...

At Interop 2009 I presented "Next Generation Search: Social Bookmarking and Tagging". This presentation started off with a look at the rough numbers behind the cost of search in the enterprise (see the first 16 slides). [I presented a similar presentation at the SharePoint Saturday DC event this past week, but evaluated SharePoint 2010's new social tagging as the analysis focus.]

Next Generation Search: Social Bookmarking and Tagging

View more presentations from Thomas Vander Wal.

Most of the numbers come from Google white papers on search, which gets some of their numbers from an IDC white paper. I also have a white paper that was never published and is not public that has slightly more optimistic numbers, based on the percentage of time knowledge workers search (16% rather than the Google stated ~25% of a knowledge workers time is spent searching). There are a few Google white papers, but the Return on Information: adding to your ROI with Google Enterprise Search from 2009 is good (I do not endorse the Google Search Appliance, but am just using the numbers used to state the problem).

I focus on being optimistic and have I yet to run into an organization that claims to live up to the optimistic numbers or total cost of inefficiency.

• Few organization claim they have 80 percent of or better success with employees finding what they need through search
• That is 80 percent success rate
• Or, 1 in 5 searches do not find what is they were seeking
• A sample organization with 500 searches per day has 100 failures
• An average knowledge worker spends 16% of their time searching
• 16% of a 40 hour work week is 1.25 hours spent searching
• 20% (spent with unsuccessful searches) of 1.25 hours a week is 15 minutes of inefficient productivity
• At an average salary of $60,000 per year that leads to $375 per person of inefficient productivity
• Now take that $375 per knowledge worker and multiply it by how many knowledge workers you have in an organization and the costs mount quickly
• An organization with 4,500 knowledge workers is looking at a inefficiency cost of $1,687,500 per year.
• Now keep in mind your knowledge workers are you most efficient at search
• Many organizations as a whole are running at 40% to 70% success rate for search

We Know We Have a Costly Problem

This usually is enough to illustrate there is a problem and gap with spending time resolving. The first step is to set a baseline inside your organization. Examine search patterns, look at existing taxonomies (you have them and use them to some degree, yes?) and work to identify gaps, look at solutions like tagging (folksonomy) to validate the taxonomy and identify gaps (which also gives you the terms that will likely close that gap). But get a good understanding of what you have before you take steps. Also understand the easy solutions are never easy without solid understanding.

Evaluating what, if any taxonomy you have is essential. Understand who is driving the taxonomy development and up keep. Look at how to get what people in the organization are seeking in the words (terms) they use intend to find things (this is often far broader than any taxonomy provides).

Real Value

Having a fascination with economics and the “pure flow of information...” mantra I highly value information and the tools and services that provide the value chain of data, information, and knowledge. These digital tools were not the easiest things to work with for many people and it has always been a passion to have the tools and services work better. More optimally, so people could have better access to information so to help them make smarter decisions around things that matter(should we find a new supplier, do we have a problem, do I need a coat, does our packaging need to be weather resistant, etc.).

What matters and what is work and what is personal is a very blurry line, but having the information and ease to access it so we are smarter in making decisions it the key. It comes down to efficiency, which is highly related to ease of use.

Real Populations

What fascinates me most with inside the firewall and always has is the need to understand how people use (can’t use) the tools that have been built or deployed for their use. Things that are seemingly logical and intuitive from the developer and designer’s viewpoints are not on target with those in the organizations. When I started working managing, maintaining, building, and improving the tools and services people use it was inside the firewall as the web did not exist yet and the internet was still in its nascent stages, even if it had been around for 20 years already.

The groups of people I working with needed to use these tools and services to perform their job as the paper and non-technical means of performing their tasks were replaced by computers or were never possible with out the power of digital computations. What was true then with dealing with the populations of co-workers and others inside an organization using the the tools and services is still true now, success of a product is measured by its percentage of use from those who must use it, efficiencies gained, lack of bugs, and improved time to complete tasks.

Web projects seemed to lose these values as it was easy (relatively) to get a few thousand, hundred thousand, or few million (over time) using a product or service. But, those services were only a small slice of the population, even a small slice of the population who needed a service like the one being offered.

Real Social

In the last five to eight years or so that truth around small slices of the populations using tools and services is never more relevant than around the flood of interest in social web sites and tools. Having built, managed, and iterated on intranet groupware and community tools for tens of thousands of distributed employees and business partners, I had great interest in seeing what happened with social sites on the web.

It was no surprise to me when variants of the web’s social tools and services started coming inside the firewall that adoption was less than optimal, because these social tools were being honed and iterated on early adopters and assumptions that are very counter to the majority of the population (some 90% are outside of this early adopter trend using the tools).

Early on I learned the easiest means of getting adoption with tools and services is to emulate who things are done by people without technology mediating the tasks or flows. Regarding social interactions these is never more true.

Most of the social tools are not very social in the way that the majority of people are social. This is very problematic inside an organization because businesses and organizations are social by nature and must be to have any success. People must be social and interact with each other inside the organization (meetings, reviews, research, sharing findings, etc.) as well as to the outside with their customers and clients.

What many of these social tools, and business tools in general, have done is add friction to social interactions that are required by businesses to survive. These newer class of tools are moving towards emulating true human social interactions more closely, but we still have a long long way to go. Where the social web tools have fallen down is focussing on the early adopters, but in reality that is core group of people who come to these sites and services (services like AOL, Yahoo, and Facebook have over the years broken into more mainstream customer bases, but the customers are most often not using the really new “cool” stuff).  The lessons learned from most web social services often don’t work well inside organizations as they are not lessons learned from a full broad population, like the ones inside an organization.

Real Needs

Businesses and organizations have real needs for these social tools, as their organizations are quite inefficient and they know it. They know the value that these tools can bring and many have experimented with these tools in the past year or few, but have been stumped by lack of use and adoption.

Organizations are forever trying to optimally capture what they know (hence knowledge management interest), get information out easily to those who need it (portals), connect employees to each other (groupware), connect to customers and business partners more easily (B2B tools), and better connect the company to its employees (HR tools). All of these have received incredible funding and effort over the years. Some have decent payoffs to the organization (return on investment (ROI)), but rarely are they the large successes that had been promised or hoped for.  One of the big reasons is the tools got in the way.

Real Solutions

Getting the tools out of the way and allowing for people to interact as needed and as is comfortable is where success lies for tools and services in organizations. This is why I am passionate about this area and why I like focusing inside as not only do I see real solutions lurking in what has been done in what is called Web 2.0, but business and organizations see that same.

What is needed is using the understanding of organizations, the new tools, and marrying that to how real people are social and interact so to get to real optimal solutions.

Latency from Heavy Computational Requirements

What? I am hearing screaming from the engineers about the computational power needed to do this as well as the latency in this system. Design Engaged 2005 I brought up a similar scenario, within context of my Personal InfoCloud and Local InfoCloud frameworks called Clouds, Space & Black Boxes (a 500kb PDF). The key then as it is still is using location and people to build potential context and preprocess likely queries.

When my phone is sharing my location with the social contextual memory parser service that see I am quite near a book store (queue the parsing for shared books, favorited conversations with books, recent wish list additions (as well as older additions), etc. But, it is also at the time I usually eat or pick up food for a meal, so restaurant and food conversations parsed, food blogs favorited (delicious, rated on the blogs, copied into Evernote, or stored in Together or DevonThink on my desktop, etc.) to bring new options or remind of forgotten favorites.

Now, if we pull this contextual relevance into play with augmented reality applications we get something that starts bringing Amazon type recommendations and suggestions to play into our life as well as surfacing information “we knew” at some point to our finger tips when we want it and need it.

Inside the Firewall

I have been helping many companies think through this inside the firewall to have, “have what we collectively know brought before us to help us work smarter and more efficiently”, as one client said recently. The biggest problem is poor metadata and lack of even semi-structured data from RDFa or microformats. One of the most important metadata pieces is identity, who said what, who shared it, who annotated it, who commented on it, who pointed to it, and what is that person’s relationship to me. Most organizations have not thought to ensure that tiny slice of information is available or captured in their tools or service. Once this tiny bit of information is captured and contextualized the results are dramatic. Services like Connectbeam did this years ago with tags in their social bookmarking tool, but kept it when they extended the ability to add tagging in any service and add context.

Past Attendees have Said...

“A few hours and a few hundred dollar saved us tens of thousands, if not well into six figures dollars of value through improving our understanding” (Global insurance company intranet director)

From an in-house workshop…
“We are only an hour in, can we stop? We need to get many more people here to hear this as we have been on the wrong path as an organization” (National consumer service provider)

“Can you let us know when you give this again as we need our [big consulting firm] here, they need to hear that this is the path and focus we need” (Fortune 100 company senior manager for collaboration platforms)

“In the last 15 minutes what you walked us through helped us understand a problem we have had for 2 years and a provided manner to think about it in a way we can finally move forward and solve it” (CEO social tool product company)

Is the Workshop Only for Designers?

No, the workshop is aimed at a broad audience. The focus of the workshop gets beyond the tools’ features and functionality to provide understanding of the other elements that make a giant difference in adoption, use, and value derived by people using and the system owners.

The workshop is for user experience designers (information architects, interaction designers, social interaction designers, etc.), developers, product managers, buyers, implementers, and those with social tools running already running.

Not Only for Enterprise

This workshop with address problems for designing social tools for much better adoption in the enterprise (in-house use in business, government, & non-profit), but web facing social tools.

The Workshop will Address…

Designing for social comfort requires understanding how people interact in a non-mediated environment and what realities that we know from that understanding must we include in our design and development for use and adoption of our digital social tools if we want optimal adoption and use.

• Tools do not need to be constrained by accepting the 1-9-90 myth.
• Understanding the social build order and how to use that to identify gaps that need design solutions
• Social comfort as a key component
• Matrix of Perception to better understanding who the use types are and how deeply the use the tool so to build to their needs and delivering much greater value for them, which leads to improved use and adoption
• Using the for elements for enterprise social tool success (as well as web facing) to better understand where and how to focus understanding gaps and needs for improvement.
• Ways user experience design can be implemented to increase adoption, use, and value
• How social design needs are different from Web 2.0 and what Web 2.0 could improve with this understanding

More info...

For more information and registration to to Viget Lab's Social Design for the Enterprise page.

I look forward to seeing you there.

Overview

The last couple of years I have had many conversations with a broad selection of mid-sized to large organizations. Some of these are customers of mine or potential customers while others are conversations I have had, but all having the similar discussion about social tools in the enterprise. What follows is a collection of snippets from those conversations regarding Microsoft SharePoint 2007, most are not publicly attributed as they were not intended to be “on the record”.

One common element from all of the discussions is the frustration nearly all of these organization have with their experience with Microsoft SharePoint 2007. The comments are based on those spending one month to a year with the tool (the six month to one year club with tools offer best insight).

SharePoint does some things rather well, but it is not a great tool (or even passable tool) for broad social interaction inside enterprise related to the focus of Enterprise 2.0. SharePoint works well for organization prescribed groups that live in hierarchies and are focussed on strict processes and defined sign-offs. Most organization have a need for a tool that does what SharePoint does well.

This older, prescribed category of enterprise tool needs is where we have been in the past, but this is not where organizations are moving to and trying to get to with Enterprise 2.0 mindsets and tools. The new approach is toward embracing the shift toward horizontal organizations, open sharing, self-organizing groups around subjects that matter to individuals as well as the organization. These new approaches are filling gaps that have long existed and need resolution.

Broad Footprint

What SharePoint 2007 Does Well

Microsoft SharePoint 2007 seems to be in every enterprise I talk to, at least somewhere. It is used if a variety of different ways. When SharePoint is included with addition of Microsoft Office Online (MOSS) is a helpful addition for simple use of these older prescribed methods. MOSS is also good at finalizing documents that are the result of a collective, to group, to collaboration knowledge work process. MOSS and SharePoint are not great at anything but the last step of formalizing the document for distribution in another workflow.

A recent report from AIIM that was written-up by CMS Wire in “Study Finds SharePoint Primarily Used for File Sharing” states “47% use it primarily for file sharing (and/or as an internal Portal 47%)”.

How Did We Get Here?

There is one common point I have heard with nearly every company I have talked with over the last couple years, MS SharePoint 2007 is nearly ubiquitous in deployment. Nearly every organization has deployed SharePoint in some form or another. Many organization have tested it or have only deployed pieces of it. The AIIM survey reported by CMS Wire states: “83% currently use, or planning to use, SharePoint”.

Organizations either sent their IT out for training on SharePoint 2007 and/or brought in consultants to help build an implementation that fit their requirements. Most of the requirements IT departments started with were rather thinly informed, as they have nearly all stated after using SharePoint for a month, most realize after six months or so, their requirements are vastly different than what their initial requirements were, as they have learned more deeply about social tools in the enterprise.

Many who deployed SharePoint, thought it was going to be the bridge that delivered Enterprise 2.0 and a solid platform for social tools in the enterprise is summed up statement, “We went from 5 silos in our organization to hundreds in a month after deploying SharePoint”. They continue, “There is great information being shared and flowing into the system, but we don’t know it exists, nor can we easily share it, nor do much of anything with that information.” I heard this from an organization about 2 years ago in a private meeting and have been hearing near similar statements since. This is completely counter to the Enterprise 2.0 hopes and wishes they had for SharePoint. They were of the mindset that open sharing & having the organization and individuals benefit from a social platform.

MS Marketing’s Promise

The Microsoft marketing people seem to have performed their usual, extend what the product can do to the edges of its capabilities (and occasionally beyond) to map to customer stated desires. In 2006 and 2007 the advent of social computing on the web (Web 2.0) had entered the hormone raging stage gathering attention in boardrooms and IT departments who had been playing around with the ideas of bringing these tools inside the firewall in an official manner. The desire for social software to be part of the enterprise was an interest and desire.

The Microsoft marketing materials they focus on “collaboration and social computing”, which is more of a document management and workflow process tool that they put the more fashionable moniker on. But, it is this Microsoft marketing that engendered many organizations to the idea of the value and promise of social computing inside the firewall and Enterprise 2.0. Microsoft’s marketing legitimized the marketplace, but in typical Microsoft form did not exactly deliver on the promise of marketing.

Part of the promise of SharePoint is a malleable platform, which many developers who work across platforms complain is one of the least malleable and easy to develop on platforms. There are many constraints built into SharePoint and developers for SharePoint are not cheap. Development cycles for SharePoint as said to be about one third to half longer than most other options. At the Enterprise 2.0 Conference this past Summer in Boston, Lockheed Martin had a session demonstrating what they had built on top of SharePoint and it was quite impressive. But when asked about costs and resources, they said: “It took about one year, 40 FTE, and 1 to 5 million U. S. dollars. Very few organizations have those type of resources with availability to take on that task.

What Microsoft marketing did well was sell the value that social tools bring into the enterprise. They put the ideas in the minds of those building requirements (at a minimum to be included in pilot programs) as well as the values derived from using this new generation of social software inside an organization.

Multiple Micro-silos

At various conferences, across many industries, I have spoken at I have been asked to sit in on the SharePoint sessions, which turn into something like group therapy sessions (akin to group therapy in the first Bob Newhart show). There is much frustration and anger being shared as people try to resolve how to share information between groups and easily merge and openly share information once it has been vetted. These groups consistently talk about going directly to their Microsoft support & SharePoint Experts with these problems only to be told it is doable, but far from easy and may break some other things. Finding relevant information or even the inkling that something is happening in some group is nearly impossible. The promise of setting up ad hoc open groups by employees across silos is nearly impossible with out getting authorization.

Information Locked

One of the largest complaints is the information is locked in SharePoint micro-silos and it is nearly impossible to easily reuse that information and share it. Not only is the information difficult to get at by people desiring to collaborate outside the group or across groups, but it is not easily unlocked so that it can benefit from found in search. The Microsoft SharePoint model is one that starts with things locked down (focussed on hierarchies) then opens up, but unlocking is nowhere near as easy a task as it should be.

SharePoint Roadmap Marginalized Over Time

Where do people turn that have gone down the SharePoint route? Well most start by adding solid functionality they had thought SharePoint was going to provide or wished it had. SharePoint has acknowledged some of this weaknesses and has embraced outside vendors that make far superior products to plugin as components.

Some common social tool plug-ins to SharePoint are Socialtext, Atlassian Confluence, and Connectbeam (among with many others). Then there are those who build on top of Sharepoint, like Telligent and News Gator Social Sites. While others are more prone to full platforms that deliver much of the functionality out of the box, like Jive Clearspace.

Plug-ins Extending Functionality to SharePoint

Microsoft makes great promises, or hints at them in its marketing materials for SharePoint along the lines of social software in the enterprise. The first step many organizations take with SharePoint after realizing it does not easily, or even with an abundance of effort, do the expected social software components is to start getting solid proven services and start plugging them in. Many tool makers have taken their great products an made it quite easy to plug them into the SharePoint platform. Want a great wiki tool, not the horrible wiki “template”, then Confluence or Socialtext is added. Need a great social tagging/bookmarking tool that ties into search (this starts enabling finding the good information in SharePoint’s micro-silos), then Connectbeam is added.

This list goes on with what can be plugged-in to Sharepoint to extend it into being something it hints strongly it is quite capable of doing. What one ends up with is a quite capable solution, but built on top of one of the more pricy enterprise platforms. In most cases the cost of all the plug-ins together is less than the cost of SharePoint. It is from this point that many organizations realize all of these add-ins work wonderfully with out SharePoint (however, getting all of them to work together as easy plug-ins to each other is not always easy).

Full-Suites On Top of SharePoint

Another option that organizations take is to move in the direction of putting a fully functional social platform on top of SharePoint. Tools like Telligent and NewsGator Social Sites. These are options for those who find value in what SharePoint offers and does well (but and therefore getting rid of it is not an option), but want ease of development and a lower cost of development than is the norm for SharePoint. These full-suites also provide the ease of not having to deal with working through plugging together various different best of bread solutions (this really reminds me of the path content management systems went down, which was less than optimal).

Not only is the Lockheed Martin example of building on top of SharePoint an example of expense of that platform, but the recent AIIM survey surfaces high cost of development as a rather common understanding:

“Another area of interest is the required effort to customize SharePoint and integration other third-party solutions. In this case, 50% of survey respondents indicated custom solutions required more effort than expected (33% “somewhat more” and 17% “much more”). The integration challenges focused on a lack of training/documentation and integration with non-Microsoft based repositories and existing applications.” From CMS Wire: Study Finds SharePoint Primarily Used for File Sharing.

Fully Replacing SharePoint

There is a third option I have been running into the last year or less, which is removing SharePoint from the organization completely. I know of two extremely large organizations that are removing SharePoint from their organization this year (once these organizations are public with this I can be). The reasoning is cost and under performing as a social platform and what is does well is easily replaced with other solutions as well. In one instance I know the people who brought in SharePoint are being let go as well as the whole team of developers supporting it. I am hearing business operations looking into having their IT department find something that is meets their needs and were promised by IT that SharePoint was that solution. This was echoed by Lee Bryant via Twitter [http://twitter.com/leebryant/status/1099413469]: “[…]problem is many IT depts just don’t care - it is a simple ‘solution’ for them, not their users”

When removing SharePoint some organizations are going the piece by piece approach and stitching together best of breed or are going the route of full-service social platform, like Jive Clearspace. The cost per users of such solutions is less, the time to install to up-and-running fully is reportedly a about a third and maintenance staffing is also reportedly lower.

SharePoint is not Enterprise 2.0

What is clear out of all of this is SharePoint has value, but it is not a viable platform to be considered for when thinking of enterprise 2.0. SharePoint only is viable as a cog of a much larger implementation with higher costs.

It is also very clear Microsoft’s marketing is to be commended for seeding the enterprise world of the value of social software platform in the enterprise and the real value it can bring. Ironically, or maybe true to form, Microsoft’s product does not live up to their marketing, but it has helped to greatly enhance the marketplace for products that actually do live up to the hype and deliver even more value.

Why LinkedIn Needs to Have a Better Grasp of Social

A heavy user of LinkedIn, I have been hearing identical complaints to my own as regular business networking event conversation fodder for the last six months or more. Light users of LinkedIn as well as those of us who have over 600 connections have nearly identical problems.

At its core the social interactions design is severely flawed and poorly thought through. LinkedIn integrates social interaction components and features as if they were playing a game of "me too" with Facebook. This is problematic as much of the Facebook social interaction design is poorly executed. I have stated how Facebook's DNA does not support business use (in Facebook for Business or LinkedIn Gets More Valuable. Oddly, now LinkedIn seems to be building the poorly thought-through Facebook interactions, implementations which are directly counter to their reason for being.

Wake-up LinkedIn! You may have money to get you through some sort of recession that lasts for a while, but your business relevance requires you to get these things right and get them correct now.

Too Many New Features, Too Fast

LinkedIn now has conflict and confusion about its primary focus as a service and what is the primary social object. Prior to 18 months ago LinkedIn was more or less a live resume and work connections site. The social object was the individual person and the focus was clear and social actions, while limited, were clear and focussed too. The addition of more social interaction and services has completely lost that sense of focus and could be one of the causes of poorly built social tools.

The last 18 months or so has LinkedIn seeming like it wants to be more of a Social communication site,  workplace social platform, and/or  general social site like Facebook with a quasi-focus around work-life.The lack of central understanding of what LinkedIn is also has increased the scatter shot understanding of social and voice (based on really confounding contexts for understanding). The inclusion of social elements that bleed into LinkedIn, with similarities to Facebook, are executing on the same social understanding of social interaction design that acts as if the last 8 to 15 years in digital social interaction design and knowledge did not exist.

This is a compilation of things that have been increasingly bothering me with the rollout of LinkedIn's social features. They seem to roll out features that are not fully baked. Then, they release new features rather than fixing the poorly thought through functionality already deployed. I have delayed writing this as I have heard many of these items were going to get fixed (but have not after far too long). I also have many friends at LinkedIn and have not wanted to rock their boat (but many of them have publicly and privately encouraged me to write this publicly).

Another reason for posting this is I am seeing these mistakes many places. Far too many "social x gurus" are just users of less than optimal systems. They don't grasp the less-than-optimal features are holding back the tool adoption, in addition to a lack of social interaction design.

This muddled social mess triggered Jonathan S. Knoll to proclaim on Twitter, "LinkedIn: the online community of people you don't really like."

What Worked Well

LinkedIn worked well for me as an ambient social network for business contacts. The last 3 or 4 years LinkedIn has been one tab that was always open in my work browser (until a couple weeks ago when I got fed up). I would watch the ambient flow of who changed jobs, titles, connections, and what they were seeking. These were social business clues that I used as opportunities to reconnect with people and see where I could help out.

LinkedIn was a great tool for strengthening business relationships. Quite often I would offer help to someone job seeking or send congratulations on new role or job. The communications often lead to chatting about working together, which had a really good business upside for me.

Watching people connect has value in finding people I already knew and had not connected with, as well as having some understanding of who outside a community is looking for help (those who say they can tell everything about a person by who they connect to don't understand social interaction dynamics very well, particularly around business relationships and business growth).

LinkedIn's recommendation services for finding others to connect with have been really good. The only other service that is this strong in my opinion is Plaxo, which is a service that increasingly has taken the place of LinkedIn for me. Plaxo understands volume, various levels of relationship, and keeping contact information current where you need it (in address books, not is disconnected services). LinkedIn is also really good for capturing and making recommendations of one's work.

Something LinkedIn has done rather well is its iPhone application, which really should be extended to other mobile platforms for smart phones. It finally enabled the ability to use contact information in a use context that matters and outside their service (mail does some of this but it is broken as in LinkedIn responses and external responses are not coordinated).

LinkedIn's question and answers section has been done rather well. Many people find it valuable and get good use from it. There are many things that could be done to augment it, particularly around using it to build an understanding of reputation around subject matter. It also could use the ability to easily hold on to (and annotate for one’s self) good suggested answers. This is the sign of a decently thought-through social platform.

The second part to this post, LinkedIn: Social Interaction Design Lessons Learned (not to follow) - 2 of 2 looks at some specific lessons learned from LinkedIn.