Showing posts with label social networking. Show all posts
Showing posts with label social networking. Show all posts

2011-06-03

Making Connections in an Enterprise

The value of social media to an enterprise is still being proven in many organizations. Since most such 2.0 technologies employ a 'pull' or 'opt-in model', getting staff engaged can be a challenge at first.

I recently developed a 10-step approach to effective enterprise social networking specifically to use within OpenText.
  • The first step is to add a picture of yourself, not an avatar or the default icon.
  • The second step is to add information to your profile.

In support of these two steps I developed the following two-minute video which we have deployed on the login page of our Intranet systems.
  • It isn't supposed to be super-professional as we are also encouraging staff to make more videos - if they think they need professional production for every video they'll never get started.

Anyway, here's the video. It shows screen shots of our internal Content Server system called Ollie, and specifically some of the features of the Pulse social networking offering.




Pulse combines the style of microblogging or status posts made famous by twitter, together with Content Updates. Comments associated with newly added content (digital files) are shown in a 'stream' and other users can add additional comments or 'like' the item.

2011-05-05

How Coupons led to Social Commerce

A colleague asked me for my take on Social Commerce. This seemed like a good reason to delve into very a hot area.

I decided to look from a historic perspective – what preceded modern social commerce? A very good case can be made that social commerce had its origin with the first coupons. The story involves both technological changes in how content is presented, as well as how various types of social interactions are enabled. There are fascinating parallels with the rise Enterprise Content Management (ECM) and the interplay between push and pull models of distribution. I’ll likely make several more posts on these topics.

First the historic perspective.

Coupons Appear for Physical Stores

The vast majority of today’s coupons are paper and therefore distributed by print media and mass mailings, typically by manufacturers of consumer packaged goods and by retailers. Asa Griggs Candler who acquired Coca-Cola (Coke) in 1888, is credited with the invention of the modern coupon. In its first year, only nine glasses of Coke were sold on average each day. By 1913, Coca-Cola had redeemed 8.5 million “free drink” coupons.

Coupons are a way for manufacturers and retailers to selectively offer discounts to price sensitive shoppers who might otherwise go elsewhere. Price sensitive shoppers are those most likely to make an extra effort to receive a discount. The distribution of coupons also enables the list price, which will be paid by less price-sensitive shoppers, to be increased! It is sobering to realize that if you don’t use coupons then on average your purchase costs will be higher because you have been identified as someone prepared to pay more!

Coupons also enable various forms of market research and segmentation.

The ubiquity of coupons today is demonstrated by Extreme Couponing, a popular television series that profiles people who manage to pyramid coupons to acquire merchandise with little or no cash outlay.

Distribution

Initially all coupons were distributed in paper form, typically in periodicals and mass mailings. The Internet created a new distribution channel enabling the downloading and printing of electronic coupons to paper. From that point on though the printed coupon is treated in the same way as any other paper coupon and taken to the physical point of purchase.

With the recent widespread adoption of mobile devices, it has become possible to carry an electronic image of a coupon to the point of sale and have that scanned, obviating the need for paper coupons. For this to be effective, widespread ownership of mobile devices such as smart phones, even among price-sensitive shopper, is obviously required.

Tying Coupons to Commerce Systems in Stores

Whether in paper form or electronic images, coupons to be used in physical stores are tied to electronic commerce systems by scanned bar codes. Products have UPC bar codes, as do the coupons that can provide discounts. Product and coupon UPC bar codes are similar, but not identical. At the time of purchase the point-of-sale (POS) computer decodes a product family code from the coupon bar code and matches it to any item purchased from that product family (identified by the product bar code), derives a value and sends a discount amount to the cash register (details).

Internet Coupons for Online Stores

When the point of sale is not a physical environment, but rather an online store, then an alternate approach is commonly used – Internet coupons. These are typically numeric or text strings entered by the customer in a web form at the time of sale. They are referred to by a variety of names such as “promotional codes”, “discount codes”, “key codes” or something similar. In this case the electronic commerce system is an integral part of the online store.

Once coupons and coupon codes became available online, an opportunity was created to consolidate them on coupon services sites like Coupon Craze (video overview). The top ten coupon services sites have recently been reviewed. Couponers can see a very large variety of available printable coupons and/or online coupon codes from many stores, pick up the necessary coupon code and be redirected to the appropriate online store. These sites are generally centered on individual consumers, but do have limited social support – for example by providing a link to send an offer to friends by traditional email or social networks.

Social/Collaboration

At times there have been attempts to limit the trading of coupons, but these have generally failed. Since coupons have inherent value to those prepared to go to extra effort, and this value can be exchanged or traded, people committed to using coupons (i.e. "couponers") have formed coupon exchange clubs – typically meeting in residences, churches, club facilities, etc. to exchange physical coupons. These coupon clubs are prevalent in geographic regions where coupons are especially heavily distributed and build off existing in-person, social networks. They also have the potential to create new social relationships based on shared goals.

The differences between societies often manifest themselves in online social communities. For example, Tuangou, is a shopping strategy that originated in China. People connect over the Internet in order to haggle with a vendor as a group. They benefit from group leverage to get a larger discount and the vendor increases their volume. Haggling is of course a Chinese shopping tradition. There is no intermediary in the transaction and the social bartering groups have to organize themselves, typically using online forums.

In contrast, in Europe and North America, where consumers expect most prices are fixed (with the notable exception of automobiles and houses) unless a coupon can be used, intermediaries are the norm. The group-buy, or “deal a day” leaders are Groupon, LivingSocial and BuyWithMe. In essence a special price is offered for a limited time on one product or service to an entire group in a given geographic location. While deals are distributed by RSS feeds and email, an essential social element of these sites is the targeted use of online forums which encourage consumers the share their questions, opinions and experiences with the product or service on offer.

 While services like Groupon were preceded by other deal-a-day sites, such as Woot, those only supported online transactions. The newer sites appeal to a much wider range of merchants as they are able to offer deals for any type of product or service (i.e. not just consumer packaged goods), especially tailored to specific geographies. They are of interest to smaller merchants and local services like restaurants, sports activities and spas. It should be noted that group members actually purchase a coupon or voucher that is redeemable with the merchant, typically at a physical location (i.e. not usually online). Deal sharing using email and social media outside the subscribed group is actively encouraged, and there are direct benefits for assisting in recruiting others (i.e. referral rewards).

The success of Groupon has both attracted suitors to buy the company at elevated prices of up to $6 billion (e.g. Yahoo! and Google), as well as motivating existing major Internet players to replicate it – notably Google offers and Facebook Deals.

Parallels to Enterprise Content Management

Content – In many ways coupons have followed the same historical path as more classical content types such as documents, moving from paper form to electronic – first on PCs and later on mobile devices. However, whereas documents are key elements in business-to-business (B2B) commercial transactions, coupons support business-to-consumer (B2C) interactions, where the business party may be a manufacturer or retailer, as already noted.

Collaboration/Social – In a similar fashion, for much of their history, the primary coupon-related interactions were pushes from the vendor or manufacturer to individual consumers - much as business have interacted with employees (B2E - see an earlier post). But consumers have discovered that they can realize greater benefits if they work together using both generic social tools as well as purpose-built tools. Given the flood of coupon and discount opportunities consumers have also started to favour pull instead of push mechanisms - which are increasingly perceived as spam.

2011-04-26

The tipping point for social and push technologies in the enterprise

"I don't have time for social media at work!" A colleague made that comment to me recently.

My response was: "You have to replace something you already do. It isn't about squeezing yet more time out of an already busy work day, but of finding when a social media tool better suits some task you are already performing."

Some people have suggested that one or more social media tools will replace email in the workplace. Unfortunately a direct one-for-one technology exchange is not always possible. This becomes clear when you consider the range of use cases for which an existing technology is used.

Here's a common business use case:
  • You want to share an interesting webpage or video that you have found with colleagues. It may be about a competitor, a market trend, a new technology, a new regulation, etc. and you expect that it may be useful to the recipients.
In recent years a typical approach would have been to email a link (or even an attachment) to the six people you think might be interested. Likely you will forget three others who would have been interested, and maybe there are a couple of others you didn't know would be interested. So the approach would always have been flawed since you could not or did not completely predict who would value the information.

In addition, another problem has grown in recent years: namely email overload and developing user resistance. In the above example, of the six actual recipients, maybe two will resent the intrusion and consider your email spam. The issue here with email is that it is a Push technology - recipients get it whether they want to or not - and it also has a narrow reach, going initially only to those people you define.

So if the original solution always had a limitation, and over time is becoming less effective, is there a better alternative? Currently the best technological alternative for this example use is a Pull technology. You post the information and users decide whether they want to follow you and/or a specific topic.
  • A good example of a Pull approach is social bookmarking. To share an interesting website, you could instead have used a bookmarklet installed in your browser to automatically post the link and your comments to an internal collaboration site.
While this approach is effective in reducing the perception of span, it is limited because others might not be aware that you are someone they should follow, or may not yet have learned and adopted the technology.

Pull technologies have an inherent entry barrier that limits their usefulness and can be hard to overcome. Most social media are pull technologies. This is a critical problem for organizations looking to use social media tools effectively.

In the above use case there is an expectation of benefit if the information is shared widely, but it is seldom critical. What if the aim is circulate 'critical' information to the widest possible audience?

In most current enterprises, if the organization wants everyone to be informed about something they will send an email to 'all staff' on the assumption that it will reach everyone and be read. In reality this assumption is increasingly false for a growing proportion of staff - they don't bother to read, don't have time or have even set email filters so they don't see such emails! An alternative is to post the same information to a stream that users can watch, but in most organizations usage has not yet achieved a level that the post will reach most staff.

So email pushes are increasingly ineffective, while social pulls have yet to achieve sufficient adoption to take their place as workplace tools. It seems there is a growing communications chasm which will create a tipping point to drive adoption of social media in enterprises at some time in the future.

2011-04-20

Where is the concept of Employee-to-Employee (E2E)?

Organizations are struggling to understand the relevance of social networking tools internally. You can see the lack of maturity in this field by looking up E2E on Wikipedia; of the several interpretations of E2E, none refer to Employee-to-Employee.

Other X2X concepts are better documented:
  1. B2B - Business-to-Business
  2. B2C - Business-to-Consumer
  3. B2G - Business-to-Government
These three all have aspects of commerce for the provision of products or services between different parties.

A more recent, fourth X2X entry is B2E - Business-to-Employee, recognizing what goes on within a given organization rather than its external interactions. As the Wikipedia entry notes (2011-04-20):
"Business-to-employee (B2E) electronic commerce uses an intrabusiness network which allows companies to provide products and/or services to their employees. Typically, companies use B2E networks to automate employee-related corporate processes.
Examples of B2E applications include:
  • Online insurance policy management
  • Corporate announcement dissemination
  • Online supply requests
  • Special employee offers
  • Employee benefits reporting
  • 401(k) Management"
The traditional 1.0-style of Intranet is one of the tools used by businesses to provide information to their employees, so it can be regarded as a B2E platform. Typically the provision of information is controlled in a top-down manner.

With the newer 2.0-style of Intranets, employees are able to contribute, either by adding documents and other forms of content, or by participating socially. But B2E tools are ineffective at supporting social interactions. It isn't about what a business tells its employees, but rather what the employees tell each other.

Social interactions within an organization typically enable the execution of a wide range of critical business processes that aid commerce. Workers requesting input on a task, or notifying the next performer that they are finished, engage in social interactions that increasingly use mediating technologies such as email, instant messaging, telephone, fax, workflow, online discussion, videoconferencing, online web meeting, etc. Seen in that light the more recently available social tools such as wikis, blogs, microblogs, communities, ideation sites, expertise location, etc. just provide more choices to increase the effectiveness and timeliness of those critical, internal social interactions in support of commerce. 

E2E seems overdue for recognition.

Syndicated at http://conversations.opentext.com/

2011-02-11

Blocked Community Arteries

Online communities can form around many different technologies. But once they have formed, they can be very difficult to update, convert or move. The problem is not one of technology conversion, but rather user habits and preferences, which seem to become more solidified the longer the community has existed.

I've been reminded of this as I started to get involved with some online automotive forums. Recently I purchased an old car that I am refurbishing as a hobby. There are now fantastic online resources, with detailed illustrated procedures that are far better than the factory manuals.

You can also ask for help and people respond almost immediately, provided you don't violate the many customs and expectations. The most important of which is that you must have searched first. Since the forum I use has been around for a decade and the cars it covers are from 16 to more than 30 years old, most issues have already been covered in previous posts, often many times. This also means the veterans are intolerant of people asking the same old questions. So I search really carefully first and only if I don't find what I'm looking for make an apologetic posts along the lines of: "I have searched, but can't seem to find out how to..."

The community is very centered on classic, threaded discussions and search. Just how centered was recently illustrated by a post by a brake vendor offering to provide free brake pads to the person who posted the best explanation of why they should get free brakes, as judged by 'like' votes on Facebook. The resulting furor was really fascinating to watch.

There were a succession of 'Fail' posts. The first started:
  • "I don't have a facebook account so can't enter. Don't you have your own business website?" 
Others chimed in with incrementing posts; very quickly 18 negative votes were posted. The comment about a business website certainly illustrated that the poster has missed out on current trends. Other anti-Facebook comments included:
  • "Rarely use the FB. Don't Like"
  • "What's a facebook?"
  • "I have no plans on signing up for facebook at all, ever"
  • "C'mon, without FB how am I going to check out all the girls that wouldn't date me in 1985 and feel better now about the bullet(s) that I unknowingly dodged?"
  • "I don't "do" facebook either, and it might be a long, long time before I find a reason to sign up for it."
  • "I have some semblance of a life..."
  • "I am worthy of getting the brake pads for the simple fact that I don't use facebook."
  • "No interest in joining MyFace or any of the other ones. I'm waiting for the 'winner' to emerge. This one is probably just another fad like parachute pants and jackets with zippers all over them. Boy am I glad I passed on those."
  • "News feature today mentioned employers and now banks using FB and twitter to help evaluate the qualifications of business/job/loan candidates."
One poster was particularly incensed that the vendor had posted on more than one such site (which is a typical social marketing approach):
  • "When he posted this I went to his FB page and was pretty put out that it looked like they spammed every car forum out there with the same offer. Needless to say, I didn't "Like" this."
After this tirade, there was a tentative response from a few Facebook users. I was one of the first to point out that there was a Facebook page dedicated to this particular car, but supposed they would not be using it, which was quickly answered with an, "uhhhh... no." There were actually a couple of positive posts:
  • "I actually love facebook. It is a very useful way for me to stay in contact with many friends that I would have otherwise lost due to lack of free time. I have re-connected with old friends and use it to schedule real life get togethers. It's actually a pretty amazing site."
  • "Wasn't saying anything negative about FB, I'm on there entirely tooooooo much."
One of the final posts directed to the vendor was spot on (if sexist):
  • "Don't worry (not that you were) about the crotchety old hags on this forum somehow connecting your company to the terror threat of FB. Its just new and different, and not many here are early adopters." 

    And the last one:
  • "I found this funny on a forum dedicated to owners of 16-34 year old cars."
So they are not open to change. Which is a pity because there are newer technologies that would actually help the community:
  1. The illustrated procedures would be far better in a wiki format that could be refined over time, rather than depending on original posts with some threaded discussion additions that are hard to follow
  2. Likewise, some of the threads are really just social conversations that have little to do with the subject car. A microblogging application would be far more suitable
This well-entrenched community is very much wed to a traditional, content-centric model (threaded posts and search) and most members don't understand the people-centered, social model of collaboration. Although comprised of technically-savvy people, their preferred technology is old, as are their cars. I don't think this community is ready to change.

2010-09-16

Value for Knowledge Workers

Demonstrable value goes a long way to supporting the deployment of new software tools.

For structured business processes, return on investment (r.o.i.) is comparatively easy to estimate. Where unstructured or semi-structured digital content items (e.g. documents, spreadsheets, faxes, etc.) enable a given structured process (e.g. accounts receivable) their contribution to the overall value created is also typically quantifiable.

Where the process itself is unstructured the measurement of value is much harder. Perhaps the largest class of unstructured processes in a company fall in the category of knowledge work. The difficulties organizations have in understanding knowledge work is highlighted in an article just published in the McKinsey Quarterly entitled: "Boosting the productivity of knowledge workers".

  • Aside: Unfortunately a subscription is required to read the full article – hopefully you have one.

The article starts with the proposition that few senior executives can answer the question: "Are you doing all that you can to enhance the productivity of your knowledge workers?" This is unfortunate because, "Organizations around the world struggle to crack the code for improving the effectiveness of managers, salespeople, scientists, and others whose jobs consist primarily of interactions—with other employees, customers, and suppliers—and complex decision making based on knowledge and judgment."

The authors, Eric Matson and Laurence Prusak, describe five common barriers that hinder knowledge workers in more than half of the interactions in surveyed companies:

  1. Physical
  2. Technical
  3. Social or Cultural
  4. Contextual, and
  5. Temporal

Physical barriers include geographic and time zone separation between workers, and are typically linked to Technical challenges – where workers lack the necessary tools to overcome the physical barriers that separate them. As the article notes, there are a many software tools available that can help – these would include the various collaborative and social media tools, as well as the more classic document management applications that are encompassed in the broadest definitions of Enterprise Content Management (ECM).

Of course the availability of software tools does not guarantee that users will use them effectively; indeed, Social (e.g. organizational restrictions, opposing incentives and motivations) and Contextual barriers (e.g. not knowing who to consult or to trust) play a large part in hindering adoption.

The fifth barrier is Temporal. Time, or rather the perceived lack of it, is also a critical factor. In my experience knowledge workers do not consider time spent using social media and collaborative tools as important as other activities. Under time pressure they will stop using these tools if they need to spend more time on other activities they perceive as "real work".

What struck me in reading the article is that while an increasing proportion of staff in companies are knowledge workers, it is clear that what knowledge work is and how to best enable it to drive productivity gains is not clear. Given that, it is hardly surprising that people struggle to define the value of those software tools best able to support knowledge management.

2010-08-05

The Myth of Real-time Collaborative Authoring

In the document management field there has been a succession of products designed to support users working on a document at the same time, even if they are in different locations. These products have failed. They have failed because people don't work on documents together very often.

I wonder where the belief in concurrent creation of documents came from. In the physical world you seldom see people saying, "Come to my office and we'll write a document together," so why expect users to want to do it virtually?

Documents may well be created to summarize a brainstorming session or record the minutes of a general meeting, but the designated author usually 'goes away' to somewhere quiet to write the first draft.

Even in the review phase, reviewers independently make comments, suggestions and edits at different times. The author then pulls these together to make a revised version. Email is no different, especially since emails of any length are essentially documents.

Sure the stepwise, asynchronous approach to content authoring and review takes place over a longer period, but it actually makes best use of each participant's time, and is therefore more efficient overall.

I started to think about this again with yesterday's announcement that Google Wave will not be further developed (http://googleblog.blogspot.com/2010/08/update-on-google-wave.html). As the blog post says, Google Wave was, "...a web app for real time communication and collaboration". For the purposes of this discussion let's consider both collaboration and communication independently.

Collaboration in Authoring

A technical tour-de-force, Wave enabled users to see others changing content as they themselves changed it. Very cool, but actually disconcerting. I wouldn't have wanted you to have watched me author this blog post, for several reasons:

  • I'm easily distracted and need to concentrate to develop some cohesive thoughts
  • While writing I jump around adding sections, changing others, moving text blocks – it would be hard to follow and I'd have to explain what I was doing which would further slow me down and distract me
  • I'm the World's worst typist

I'm probably no different than most people, at least regarding the first two points. And perhaps more lethal to the concept of concurrent authoring:

  • You'd get bored – it takes far longer to author a document than read it, and you'd probably want to be doing something else while I work, preferring to comment on my finished work

And that's the crux of the matter – most people are busy, with many demands on their time, and collaborative authoring is just too inefficient.

Communication Delays are Good

While Wave was designed for collaboration, it was also intended for communication (see quotation above). Essentially email and instant messaging rolled into one. But I think there is a problem there too – most people actually don't want to use real-time communication!!

Many commentators have remarked on the tendency for young people to use their mobile phones for text messaging far more than as telephones. You'd think it would be easier to engage in a conversation by talk rather than typing, so why is texting preferred?

I think people prefer texting because it allows them to be engaged in many, independent conversations with different people. For this to work they need to be able to send and receive messages in real time, but also need an agreed expectation that replies may take several minutes. Awkward silences of several minutes on a phone aren't agreeable, and since voice isn't cached locally like a text message you have to listen to each voice channel concurrently – which isn't practical.

Interestingly while they are short, both mobile text messages and instant messages (IM) are generally only sent when they are completed. It is usually enough to see that the recipient is typing (i.e. with Instant Messaging) or to just assume that they are (i.e. with texting). All stumbles, pauses, and corrections are not sent – but they were with Google Wave.

Summary

With small pieces of content: true real-time communication is often undesirable, with near real-time being better.

With larger pieces of content: collaborative authoring is best done asynchronously.

Collaborative authoring seems to be something that IT professionals believe will lead to greater efficiencies, while end users don't have the time for it!

2010-05-14

Taking the Pulse of your Business Content with microblogging


When many users first encounter microblogging they don't 'get it'.

Twitter is of course the classic and most widely known microblogging site, and its style has been taken up by many others such as Facebook in a broader set of social media approaches. A common initial reaction is something to the effect: "I don't care if your cat just threw up – in fact, I'd rather NOT know!!"

Once people start to microblog, they find many different ways that it can provide value, beyond answering the question: "What's happening?" that twitter poses. Commentators have described endless ways of using twitter such as: 5 marketing approaches, 10 diverse applications, 50 different topics, etc.

But how does microblogging add value within an organization? Most of the discussions about business value have been on better ways to reach outside an organization to customers and partners by breaking down barriers, increasing transparency and the like.

At first blush making the case for microblogging in the workplace might seem to be hard. People often comment that they are too busy to engage in 'chit-chat' while at work. But over the last couple of years the use cases that have real business value have become clearer.

For me there are two general styles of internal business microblogging:
  1. User status updates – close to the twitter model, but with a distinctly different topic set
  2. Content status updates – fairly unique to business and keyed to the fact that many work processes produce and manage content (i.e. documents and other business files as understood in content management)
At Open Text we recently released the Pulse module for Livelink 9.7.1 that adds microblogging capabilities to support both styles (available for free to customers from the Knowledge Center).

Status updates are pretty much what you'd expect – you can make a post about anything, although some of the most useful ones are:
  • "I'm looking for..."
  • "Anyone interested in..."
  • "Have we..."
These have value because they help people to be more effective through better networking in an organization.

You can select specific users to follow and you can follow the stream from all users. We have a very similar Pulse capability in Open Text Social Workplace.

BUT, I think the real advance in Livelink/Content Server Pulse is to follow the status of content irrespective of location in a range of very powerful and comprehensive ways.

Sure you can post a link to content in twitter, and many microblogging services allow you to attach documents or other kinds of files to your posts. But the advance here is to have the act of adding or changing a piece of content anywhere in an ECM system create a status post. The feed is reporting a content action by another person. If I'm following Joe and he adds a new sales presentation anywhere I can see it in the status stream – provided of course I have permission in the repository to see the added content. All of the important support for compliance is maintained.

There are many ways to slice-and-dice: by following specific people or all people, and following changes in user status, content or both.

You can also 'pulse' specific content objects, so all changes and all comments about a piece of content are seen in the unique Pulse stream of that object. It's like a filtered window into the stream looking at just one object, even if the ECM system contains millions of documents.

And Pulsing is not just limited to files/documents, but is applied to containers like folders and places such as project workspaces and communities. You can imagine the power of an accumulated stream of all content and status activity related to a project!

Livelink has had a notification capability for many years, but it requires users to first identify existing documents and containers that they would like to follow. Pulse adds the human dimension – you can be notified of changes based on the people you follow and what they do with the content.

To honest I'm still 'figuring out' all of the ramifications and power of Livelink/Content Server Pulse but I'm very excited!
 

If you'd like to learn more:
  • Initial description in the May 2010 issue of NewsLink
  • Free Webinar Thursday 3 June 2010
  • Software and documentation in the Knowledge Center
  • And if you are an Open Text Online Communities member you'll be able to use Pulse very shortly (announcement)

Syndicated at http://conversations.opentext.com/

2010-04-06

What’s in a name? Or do you mean what I think you do? Implications for enterprise content culture


Most people love a good rant, especially when it is well-founded, and I'm no different.

And so it was that I really enjoyed Laurence Hart's recent, self-admitted rant (http://wordofpie.com/2010/03/04/a-rant-against-cms/). In his Word-of-Pie blog, Laurence railed against his perceived miss-use of the term 'Content Management Systems' or CMS. It was topical, well-informed, and most importantly to me, resonated on several fronts.

In brief, Laurence's position is that:

"...All you Web CMS people need to give the term CMS back! It doesn't belong to you. A long time ago you took it while the broader content community was trying to futz with the term ECM [Enterprise Content Management]. By the time we realized what was happening, you had taken the term..."
His issue is that while web content management (WCM) is a valid description, it is too often abbreviated to content management (CMS), even though there are a wide range of content types beyond web pages. The common use of CMS is much narrower than is implied. Enterprise Content Management (ECM) was coined in part to describe all content that an enterprise might have.

I'm not interested in the semantic debate about what each term means and what is the correct term to use.

I am interested in what this discussion says about culture and the difficulty getting people in an enterprise to take a broad view of content.

There seem to be at least 'two solitudes' in content management – ECM and CMS.

It is interesting how specific technology applications shape and restrict expectations.

Last year my employer, Open Text, acquired Vignette (history), one of the oldest and most established CMS vendors. Most of Open Text heritage is from document and record management (Livelink and Hummingbird eDOCS for example), process management (IXOS) and collaboration; in other words ECM. We published a trilogy of books on ECM in 2003-2005. While some staff came from acquisitions prior to Vignette that had expertise in WCM (notably RedDot), they represented a comparatively small portion of the Company. The Vignette acquisition brought a much larger group of CMS-oriented staff to Open Text.
I think Open Text is richer for the breadth of perspectives, but we have had to work through the challenge to merge the different cultures. Note I'm not talking corporate cultures, as indeed the companies were quite similar, but rather the application culture of how best to manage content to meet all the needs of our enterprise customers. Each of us has tended to think mostly of some content types, some approaches to content management, and some business needs.

Take Open Text's own Intranet as an example. Open Text has been running an Intranet called 'Ollie' on Livelink technology since 1996. Fundamentally the Livelink model is one of web folders containing 'documents' of any type. This model works really well when individual and team work products to be shared are typically documents – so it's great in supporting teams and managing records. However, linked webpages are a much better vehicle to support the dissemination of centrally managed content, especially information from an organization to its staff. So last year we broadened our Intranet Systems to include a true WCM capability in parallel.
For some in Open Text, the internal use of WCM came none too soon, while for others it was a surprise! I had to make a video to 'educate' staff on why we had both approaches and how to choose the best system for their specific needs. It turned out to be easiest to provide context by talking about the parallel evolution of ECM and WCM technologies over the course of the last 15 to 20 years.
The application of social media in an enterprise has also challenged cultural expectations.

Those with a WCM background have generally talked about the advantages of working closely with customers through external websites. Most of their value propositions of breaking down barriers and being more transparent are absolute anathemas to those ECM practitioners who have focussed on internal process and records management for compliance.
Traditional document management approaches provide another example of cultural expectations nurtured by specific technology experiences.

As I mentioned above, Livelink used a web folder paradigm to organize content. It also had rich metadata capabilities, but users tend to think of these as supplementary or optional ways of organizing content. It is fair to say that most users tend to think first and foremost of folders – so it can be a challenge to collect metadata from them. In contrast, with our eDOCS content management system (from Hummingbird) there are no folders – everything is organized through metadata. eDOCS users find browsing folders can be frustrating. Going forward these alternate approaches are merged in our Open Text Content Server 2010 under our ECM Suite.
Defining effective taxonomies to organize content can be one of the biggest challenges for an enterprise.

Generally people in specific departments, and using specific systems, tend to define taxonomies that meet their immediate needs, but the taxonomies they create are generally too limited for wider use. Similarly, other groups create incompatible taxonomies often to address similar needs. These limitations ultimately contribute to failure. Creating new taxonomies seems to be a recurring theme in many enterprises as most are never broad enough, scalable or robust.
Ironically then, what a person means by 'content', the 'content taxonomy' they think is required for their organization, and their perception of the critical features of a 'content management system' are all highly subjective!


2009-12-18

Customer Community Success Metrics for 2009

Customer communities are all the rage nowadays, but it is not always clear what works and indeed how to measure success.

As 2009 draws to a close we have been reviewing how Open Text customer communities have been doing.

Background: For those not familiar with Open Text, we are a vendor of enterprise-class software to manage digital files (called content). The term enterprise indicates that we sell to organizations not consumers. We have relatively few customer organizations, but they are often typically some of the biggest organizations in business and government. We estimate that at least 1 in 3 Internet users visit sites that run our software! The software we use for our own communities is the same as we sell.

The Sites

For historic reasons, we run three primary community sites (requiring membership) in addition to our typical corporate websites. The community sites are:


  • Open Text Knowledge Centre (KC)
    • Primarily for system administrators of the software we sell


  • Open Text Developer Network (OTDN) which is housed on the KC
    • Primarily for developers using Open Text APIs


  • Open Text Online Communities
    • Primarily for business champions and power users

Site Metrics

  1. The Knowledge Centre is by far the oldest community, dating back to 1996! As you'd expect, it has the most members and the most ongoing activity. Every day approximately 4,000 users access the site, and between 150,000-200,000 documents downloads are performed every month!
  2. OTDN just completed its first full year during which just over 3,200 unique users participated over the past year
  3. Online Communities got started in its present form in 2005. This last year 10,600 members collectively visited 118,000 times over the year
These numbers only measure direct participation. As you might expect, many community members participate through email-mediated discussions.

Convergence

Multiple systems have traditionally meant that there are multiple, disconnected silos of information. As a result, users don't know where to look and administrators have to duplicate critical content between systems.

A better approach is to deploy a single, 'enterprise library' of digital files (content) which contains all of the files, but just one active copy of each. The three sites above will soon converge to use the same enterprise library, which will also be used by our corporate website that is open to the general public.

One single repository can make user navigation harder unless the most relevant content is presented and organized in a fashion that best meets the needs of each type of user (i.e. persona). Communities of users with similar interests or jobs are one approach to organizing content, but of course there are others, including personalization based on the activities and preferences of specific users.

Measuring 2010 success

These communities will continue to develop, but the latest social networking approaches provide new ways to surface important content. As we deploy more social networking approaches during 2010 we'll have a solid base of community metrics from 2009 to judge progress. As you might expect, activities on external sites like twitter, YouTube and facebook are becoming increasingly important.


Syndicated at http://conversations.opentext.com/

2009-10-27

Some Thoughts on Effective Enterprise Taxonomies for Content

While discussions of content management are usually referred to in the context of the needs of enterprises (i.e. Enterprise Content Management, ECM) in reality most ECM deployments start at the departmental level. This is not bad – on the contrary departmental deployments typically address specific business needs thereby sharpening their focus to improve their chances of success. However, over time as an enterprise begins to deploy ECM technologies in many departments, the benefits of an enterprise strategy to support cross-enterprise deployment become apparent.

At Open Text we have recognized that there are a number of essential elements without which transitions from departmental to enterprise-wide deployments tend to fall into a 'chasm.' It may seem obvious, but it essential to treat enterprises differently than individual departments, especially since:


  • Enterprise deployments inherently connect departmental deployments rather than replace them
    • If your aim is to facilitate the timely, process-dependent flow of content between departments then you have to accommodate varied work cultures, processes, content types, taxonomies and technologies already in place in order to make the necessary connections as part of a clear enterprise-level content architecture. Wholesale replacement is seldom a realistic option, but supplementing and amending can be effective.


  • Enterprise deployments can also create additional value by enabling new, enterprise-spanning, content-centric processes and perspectives that cannot be achieved solely by connecting departmental deployments
One element to successfully implementing enterprise-level content management is an effective enterprise taxonomy.

  • Enterprise or corporate taxonomies (see Wikipedia definition) are becoming increasingly critical to classify, save, access, reuse and report on growing volumes of information within an enterprise
  • Enterprise taxonomies are particularly important for Content Management and Knowledge Management, but the needs of each of these disciplines are not exactly the same
While the principals of taxonomy development are relatively well understood, there are particular challenges associated with effective enterprise taxonomies. In my discussions with colleagues several recommendations have emerged:

  1. Externally derived and validated taxonomies should be adopted whenever possible – this can be especially critical when you are faced with multiple, overlapping taxonomies that were adopted and typically custom built to suit the needs of specific departments
  2. If you adopt an external taxonomy (#1 above) it is most likely that you should only implement a simplified subset – aim for 'just enough' detail
  3. Natural language taxonomies are preferable to numeric or other code-type taxonomies to support user adoption
  4. The appropriate taxonomy type or structure should be chosen before implementation is started, i.e. flat, hierarchical, network or faceted
  5. Each taxonomy you deploy at the enterprise level should be orthogonal to any other
Typically enterprise taxonomy discussions begin when staff become frustrated because they cannot access the information, and especially content, they need from one location. In such cases an enterprise taxonomy may be seen as an access enabler (e.g. through a portal) where the focus is on information presentation.

Another driver may be the need to manage key records to meet regulatory demands. In this case an enterprise taxonomy is expected to support storage of all relevant content and effective retrieval on demand by a small set of users. Such taxonomies often don't serve the general needs of all staff.

A third scenario is becoming more common: ensuring that appropriate content items are presented in the context of business processes that already rely on structured data (e.g. in ERP or CRM systems). In effect metadata applied to content can be the effective bridge between structured data and unstructured content.

The recent application of social networking technologies within enterprises has brought with it demands to classify unprecedented volumes of small content items where much of the meaning depends on the context of discussions and may not be captured within the content itself. In this case we need to consider deriving social metadata.

These are some initial thoughts on the topic of enterprise content taxonomies. It is a rich topic that I expect to explore in greater detail in future posts, especially looking at reconciling nor only classic, mandated taxonomies, but also the more recent emerged user-managed cloud taxonomies.
Syndicated at http://conversations.opentext.com/

2009-10-13

The tale of two coffees – or why altruism doesn’t work in ECM

Our facilities management has been changing how coffee is provided, and judging by the posts on our internal social network, they have been failing miserably.

On the face of it, the new system should be much better – freshly brewed coffee in a range of blends and flavours. It replaced a system using single pouches of reconstituted, dried coffee that most people felt was tolerable at best.

So where's the problem? The new system depends on altruism. The coffee must first be brewed in several large batches that are then saved in thermal carafes to hold the brewed coffee without burning it. There are five or six blends, and therefore an equal number of carafes in every small office kitchen.

In the ideal use case, a 'user' comes to a kitchen, selects the blend they would like and dispenses a steaming mug-full. If they see that a given carafe is almost empty they set it under the coffee machine, select the right blend, push various buttons and then ideally wait ten minutes until it is completely brewed, or at least expect another colleague to finish the process and move the carafe back to its stand.

Of course anyone reading this knows what actually happens. You come to get a coffee, find several carafes empty, take some coffee from one of the only carafes with some left, and then find it is lukewarm. To rectify this situation you would need to brew up at least three or four large carafes, but you're already in a foul mood so you just walk away in disgust. After all, you have an important business meeting in one minute and the company isn't paying you to make coffee for everyone!

There have been attempts to rectify this. I've seen helpful Post-it notes saying, "Brewed at 1:35pm" – which at 4:00pm tells me I don't want to even try the half-empty carafe! Packages of the correct blend are kept next to the carafes to make sure people can find the right one – as if that was the only reason they hadn't re-filled an empty carafe before!

So it's pretty clear un-recognized altruism doesn't work in the workplace. That's as true for coffee-making as it is for managing content.

ECM implementations that depend on users to do more than they need to do to discharge a task don't work. Enforcement efforts only work until people find an alternative, which is becoming increasingly easy to do with the availability of free Cloud resources.

But self-promotion works, which is recognized in successful social networking implementations. So look to social networking as a way to get people to do things that they wouldn't otherwise do in your ECM systems! After all, why else would I be writing this piece on my personal time?!

Syndicated at http://conversations.opentext.com/

2009-10-08

Instant Messaging: dating or working?

Instant Messaging (IM) is becoming more common in enterprises, although the latest statistics I have seen suggest not as much yet as some people expect.

Personally I use IM in a work context almost every day. I hadn't given much thought on how I use it, other than realizing:

  1. I am a lousy typist who needs an autocorrect feature in my IM client, and
  2. Often IM is a preamble to a telephone call as I mostly work in a home office. My IM posts often go as follows: "hi > are you free? > can I call?"

So when I saw the results of a survey on the right and the wrong way of using IM in dating, it made me reconsider how I use IM at work.

The OKCupid.com survey results were published in my local newspaper, The Globe and Mail – in case you were thinking I've been using that dating service!

The worst greetings are "hi", "hey" or "hello" – I mostly say "hi"...

Far better are questions such as "how's it going?", "what's up?", or even "hola"!

In a dating context I can see how a question would more likely lead to a follow-up. But in a business context, would it be better to say, "How's it going?", "Are you busy?" or "Can you spare a minute?" than opening with a "hi?" Maybe "hi" is fine if you've established a working relationship already, i.e. got past first contact.

Interestingly in dating use of netspeak (e.g. lol, bfn, imo, etc.) is not a good idea on first contact. The recommendation is to, "ditch the slang" for the proper language and to make sure you proofread, since it suggests that you consider the interaction important.

I think that same care very much speaks to being 'professional' at work as well, although with close colleagues with whom you chat a lot netspeak almost becomes a way to indicate that you are an expert IM user, not just a work-only user.

Mini-IM essays are a turn-off in dating, and I think likewise in work chats.

Your personal picture is critical in dating IM of course. I think it's even true for work IM. I see a larger proportion of people using real pictures of themselves in work IM settings rather than the cartoons, avatars or seemingly random graphics typically used in consumer IM and social networks. At work it's very important for people to recognize you so they can link their online perceptions of you with what they find when you meet face-to-face.

In my experience when you first interact with a colleague through telephone and conference calls with no pictures, you build a mental image of them that often conflicts dramatically with the reality you find when you first meet them in person.

There are a lot of parallels to being an effective IM user in the workplace and when dating, but of course you do have to be careful not to be seen as flirting when you compose a work instant message!! The content of the messages is what makes the difference, but both work and dating are more serious than some other social situations, so share some common rules.

2009-07-14

Official vs. unofficial social networks and their impact on user adoption

Guest post from my colleague Agnes Kolkiewicz originally posted to Open Text Online Communities Metrics community (Metrics Blog).





In my last post, we looked at the correlation between the success of collaborative systems and user adoption. Many of you struggle to obtain user adoption within your organizations for communities of practice (CoP). We mentioned that staged deployments are usually recommended by analysts and that the resultant 'success stories' can then be showcased within the company to further promote user adoption and justify the investment. But where can you find a good initial 'use case' within your company that is likely to succeed?

Consider the following excerpt here from a post by Etienne Wenger, an internationally recognized expert in the field of learning theory:

"A community of practice is different from a team in that the shared learning and interest of its members are what keep it together. It is defined by knowledge rather than by task, and exists because participation has value to its members. A community of practice's life cycle is determined by the value it provides to its members, not by an institutional schedule. It does not appear the minute a project is started and does not disappear with the end of a task. It takes a while to come into being and may live long after a project is completed or an official team has disbanded." (http://www.co-i-l.com/coil/knowledge-garden/cop/lss.shtml)

It has long been observed that unofficial networks exist within a company. People join these because they see value in participation. Knowledge is being exchanged within those networks outside of any organizational structure, crossing information silos. When designing an information system that supports communities of practice and collaboration, the challenge of an administrator may very well lie then with initially identifying what unofficial networks already exist within the organization and designing systems that will support these networks.

You can start by asking yourself the following questions:

  • What is important to our employees?
  • Where do they find value?

What might follow then is that a community of practice should not be imposed on a group of people according to organizational structures – rather, it should serve as support for unofficial networks that have already been created within the company. The value to the organization exists then because the knowledge that is already being exchanged through informal discussions, IMs, or email is now being captured and archived within a community of practice, and is then easily searchable by newcomers to the organization or people outside of the specific community that also have an interest in the subjects being discussed. This type of exchange is much more difficult to recreate when establishing a community of practice based on official organizational structures.

This is not say that communities of practice should not adhere to organizational principles further down the line, but chances are that by identifying such unofficial networks within a company, and supporting then using social media, you might stumble upon an initial 'success story' that could be then used to promote the technology throughout the organization.

2009-07-07

Meeting the needs of both the enterprise and staff

It seems that for many people the enterprise goal of corporate compliance is seen to be at odds with the goals of users. I think that's wrong!

This was brought home to me by the surprised reaction of observers at the recent Enterprise 2.0 conference in Boston to Open Text's new Social Media offering.

In recent years the primary driver for implementation of enterprise content management (ECM) systems in organizations has been regulatory compliance. Organizations need to manage critical records in a consistent manner over time, as required by relevant laws and regulations.

Ensuring that staff (the 'users' of enterprise systems) are aware of requirements and use the implemented systems is often a challenge. Well designed ECM systems can ensure organizational compliance while requiring little change in behaviour as users create and deposit content – but it can take real effort.

As Web 2.0 has shown, users want simple applications, that can be learned quickly, and work smoothly. Increasingly they want these applications to be available for mobile devices as well as desktop computers.

Staff want to interact effectively with their colleagues. Social networking tools are seen as a way to achieve this in enterprises. As I described in an earlier post, this approach is, "people-centered not document-centered." It is also becoming independent of device and therefore location.

It was therefore a pleasant surprise to some observers that Open Text, as one of the largest ECM vendors, with a long history of content management, would come out with a people-centered application that runs on mobile devices like Blackberries and iPhones, in addition to the expected personal computers. And most importantly, this application enables users to exchange content with established content repositories.

In commenting on the Enterprise 2.0 conference, Gil Yehuda, for example, said:

"Open Text impressed many people with their new enterprise social media and collaboration tools. With a solid enterprise-class suite of tools, Open Text was one of the few ECM/Portal players to make a showing and a splash at the conference. Whereas many E2.0 vendors target low-tech SMBs, only some vendors have the depth of credentials to handle Enterprise 2.0 (with a capital "E") with its many hairy concerns."

Nice sentiments – my thanks to Gil – but I think we would all agree that technical integration supporting both enterprise-driven content-centricity, and user needs for mobile networking, is but a first step as we rebalance the needs of enterprises and their staff. I expect we'll soon see considerable advances in implementation practices.

There has been much discussion about how compliance requires that all communications by staff be managed as potential corporate records, but a recent AIIM study has shown that most organizations have yet to tackle the problem. It seems that many assume that the way to do so is to 'stuff' transactions from email, IM, social networking, etc. into a content store. The problem is that these people-centered communications will generally not map to content-centric hierarchies. In some cases the only indexing field that can be used is the date of creation. As a result it is necessary to rely on full text search for later discovery, which is then followed with painful, manual recreation of context. Imagine trying to determine who said what and when – from a collection of stored emails that mention a specified term! And email is relatively easy compared to instant messages (IM) and 140 character tweets, since email communications are generally more comprehensive and richer in derivable context.

If you accept that social networking has its own, distinct organizational principles, then compliance applied to social networking must take a different tack. How users interact with each other and the network of communication links that they establish are the most important contextual elements – the medium is the message. Helping users make the connections easily automatically creates context. That context must then be preserved if the saved communications are to be reliable and meaningful from a compliance perspective.

So enabling users to network more effectively actually supports compliance in a developing paradigm!

2009-06-29

Will the real Gen Y please stand up?

Much of the discussion about social media in the enterprise posits that the incoming generation will demand the new technology tools that they have learned to depend on.

However, In working with some old ECM systems I have been surprised at times how new, young staff have just accepted them, rather than 'demanding' something better.

So will in coming workers 'demand' change or meekly accept the status quo?

An article called, "After the recession, the fallout will be lasting," in the Canadian newspaper The Globe and Mail this weekend suggests an answer. The theme of this article is that the recession has had a profound and sobering effect on career expectations:

"…many young people I talk to have significantly, and resentfully, lowered their expectations. They didn't imagine themselves in this situation in their wildest dreams."

The article goes on to say this change is affecting workers of all ages:

"This hard-line attitude will leave a bad taste in many workers' mouths. Some will develop a lasting cynicism and suspicion of organizational motives. They will not expect anything good of their employers. Others will be traumatized. Whatever cockiness employers have accused Gen Yers of having, for instance, will be knocked out of some."

So it is not hard to see why some workers simply put up with bad systems at work.

On the other hand, others are more likely to seek alternatives:

"Others will develop a healthier self-reliance. They will understand that organizations will not necessarily look after them and they will have to look after themselves." I think it is these people that are more likely to 'go around' what their employer provides to find the cloud-based, social networking tools they want.

So the current recession has polarized the response of Gen Y in the workplace. On the one hand some staff will resentfully use old technology, while others will be more likely to seek alternatives, with less concern for the risks to their employers.

2009-06-24

Obtaining and Using Key User Adoption Metrics for Enterprise Communities

Online communities are an appealing but challenging topic for enterprises. Most organizations feel they will increasingly use social networking tools, but are uncertain how best to proceed.

Proving business benefit and responding to deployment challenges can be a difficult, but these activities must be grounded on objective data, so obtaining key metrics is essential. However, often community and social networking applications intended for enterprise deployment lack the necessary query and reporting tools to support business champions and system administrators.

Recently we launched a Success Metrics community on Open Text Online Communities for those who have deployed Open Text Communities of Practice (CoP). Members of that community have access to reporting tools and templates specifically designed to provide community metrics.

My colleague Agnes Kolkiewicz just made the following blog post in that community (see Metrics Blog):

 
 

Many of you have mentioned that you are struggling with user adoption within your communities. As I believe that the success of any software project (and particularly where document management and collaboration are concerned) is largely dependent on user adoption, I believe it would be within the scope of this community to include some best practices on user adoption. To support this, I will start a "user adoption best practices" wiki in the community with the hope that all of you can add to it as we progress.

Metrics and user adoption, especially in the case of collaborative or social media software go hand-in-hand. The more that substantive content is added and the higher the participation and log-in rates, the more value your system will bring to the organization, but you need to be able to measure that progress and growth in participation:

  • Measuring log-in and participation ratios will enable you to determine how your efforts to improve user adoption are progressing. These ratios will also enable you to identify "peak times" in participation - this way you can likely pinpoint what had caused the surge in participation and aim to recreate the event. By measuring these ratios on a regular basis, you will also be able to demonstrate at a later date how the system has improved over time and set a foundation on which the overall value of the system can be determined.
  • Metrics are applicable throughout a project lifecycle. This applies to any software project but it can easily get out of hand where large enterprise deployments are concerned. This is why most analysts recommend that you start off with smaller deployments and apply metrics to measure progress. Once successfully deployed, you can then use the success of this project, and any ROI realized, to champion the solution as a "success story" throughout your enterprise to further promote user adoption in subsequent projects.
  • You should start looking at metrics in the pre-project phase taking into consideration what your objectives are for the software project at hand: these objectives will help you identify metrics as well as KPIs for the deployment. The developed metrics should then be measured throughout the lifecycle of your software deployment until the software is no longer used by your organization.
  • In many cases, the same metrics that were used to evaluate the overall health of your system will also form the foundation for any later cost-benefit or ROI calculation. Where no metrics are kept during deployment, it is much more difficult to "go back in time" and determine how the project has progressed over time and identify realized improvements as there is no benchmark for comparison. We have tried to overcome this obstacle by creating some reports that allow you to measure certain aspects of your deployment at a specified date, but that hasn't been always possible. A rule of thumb here is to start thinking of metrics as an integral part of any project you undertake.

I would encourage everyone to use metrics throughout your project lifecycles – please keep in mind that metrics not only help you prove an ROI, but also help guide your project as it progresses by enabling you to measure progress and identify areas that work well and those that need improvement. In the case of document management or collaborative software, user adoption goes a long way in helping ensure the "success" of your project.

  

2009-06-15

Don’t interrupt, I’m writing a new business document

Bud Porter-Roth posted an article (The SharePoint Myth) which describes why technology solutions to address enterprise content management (ECM) often fail. He points out that if you don't understand the role of People and Process, then any new Technology (he cites SharePoint as an example) is bound to fail for the same reasons as similar technologies before it have.

Bud gives three reasons why people don't use document systems:

1. Employees create their own file structure that they only use for their work because they don't like the way the team file share is organized.

2. Workers recreate in whole or part many documents they know exist, but couldn't find.

3. Nobody trusts the information they do find on the file share because they can't tell if it is the latest version of that information.

But I think there is a fourth reason, somewhat related to #2. People routinely prefer to repeat work. Often this is not because they can't find past work, they simply don't look for it – they are unaware, uninterested, or believe it would have no value. They are confident they can do something better and more current!

I see people starting new projects and initiatives to address old issues over and over. While some staff are aware of similar past efforts which are often well documented, even if those documents are stored and readily available, people seldom review them for lessons learned.

Could you be a culprit? If your boss asks you to write a report, do you look to see what was done before, or just hit Google and start writing? This seems like a common People issue in all companies to me.

People can work for days writing and reviewing a report or similar document. Despite this effort, the final product may be read, or even just scanned, by one or just a few people. The effort devoted to production is many times greater than the effort others devote to comprehension. Despite this, report writing is seen by many as 'real work' – something that traditional email, and more especially modern social network tools, simply interrupt and frustrate.

When you do something at work you want it to be effective – it needs to make a difference to have worth. In any given situation, do people consider first if writing new documents is always the most important or effective at impacting an organization? And if documents are so effective, why don't others accord them enduring value and read them, when they are first finished or some time later?

2009-05-28

On being our own worst enemy

Sometimes you know you need something different and you ask for it. Then when you get it, you ask why it isn't like what you expected – based on your experience with what you already had…

I'm seeing this in new enterprise content management (ECM) products, especially around social media applied to Enterprise 2.0 concepts.

While ECM now covers a wide range of technologies, at its core many of the concepts come from document management. Those concepts are mature and consequently well-embedded.

Many, but not all ECM systems follow a 'folder' paradigm – Livelink is one such ECM system – and of course Windows and Mac OS has used folders for many years. Most people just expect folders.

In the case of Livelink, as collaborative tools like Forums, Blogs, Wikis, etc. were added it was 'logical' that these be offered in the context of folders (and other Livelink folder-like container types like Workspaces and Communities). In Livelink you can add a Blog to any Folder for example, if you have the appropriate rights.

This approach works well when the collaborative discussion is centered on related content.

For example, a set of product specification documents are reasonably grouped with a product discussion in a Project workspace.

In fact traditional knowledge management (KM) approaches emphasised the importance of providing context to documents – grouping the documents and the related discussions about them while they are used and when they are subsequently archived achieves this.

While Livelink collaborative objects must be placed in Folders, tools are also provided to find them irrespective of location. You can list all Blogs, Communities, etc. on one page, but in my experience almost no one uses these features – the expectation and habit of navigation to a folder location is just too strong! And when you give users a range of different approaches, they generally only follow one well worn path.

Social media comes at the problem very differently – it is people-centered
not
document-centered. You listen to what people are saying, and then create a social network based on who you want to listen to and the discussion topics you want to hear about. So users and topics become the organizing elements instead of folders. Topics are often multi-faceted and un-predictable, so are quite different from the parent-child taxonomy type of classic folders.

Sure you can add documents to the discussion, and you can link to other documents, but fundamentally you are saying, "I'm talking about this document," irrespective of its location. In fact a document is still best managed according to a document management paradigm in a repository.

Very shortly Open Text will be releasing Open Text Social Media – a solution designed to support social networks in an enterprise, both internally in the social workplace, as well as externally in the social marketplace of a company's partners and customers. The user interface is simplified in a 2.0 style, and focuses on what a user needs to network socially. It does not have the full set of document-centric options – and therein lays the rub.

Most people who have seen Open Text Social Media love it! It's easy to learn and easy to use. The key to that ease is simplicity – that means there can't be too many options and the ones that there are revolve around social network activities.

So it's interesting to watch people start asking for folders/hierarchical classification and a whole raft of document management features – they love the new stuff, but want the familiar as well. If we gave them what they asked for, then they'd loose the initial benefits.

But we haven't forgotten the document management world. Open Text Social Media allows you to talk about documents in other repositories like Livelink, while they remain where they are in an organized hierarchy, with appropriate permissions, lifecycle controls, metadata, records management, etc.

In the real world of the business or government enterprise, it's necessary to balance the what you want of 'candy' with the what's good for you of 'aspirin' (see video below).

Two paradigms. Two approaches. Designed co-existence!




2009-03-30

Social Networking in the Enterprise - Part 1

I’ve immersed myself in social networking over the last few months. I’m not particularly interested in gaining online ‘friends’, but I do want to understand the potential of the new tools to meet specific objectives, especially those of enterprises and their staff.

Take Twitter as an example.

  • BTW, if you’d like to follow me on Twitter check here: http://twitter.com/martinss. - follow me and I’ll automatically follow you by way of SocialToo.com).
  • If you look at my score on various Twitter sites I don’t currently score very highly, but that doesn’t mean I haven’t learned from Twitter ;-)

Originally Twitter’s model was one of personal status updates: “MartinSS is walking the dog”, or some such. And for many purists it should still be that way. There is certainly value in that – I’ve learnt things about colleagues that I would never have done otherwise, and maybe we interact better as a result. In the end though I think there is a limit to how many people I want to know in detail. Interestingly this was reinforced by a recent study that showed humans have an enlarged brain center that is predicted to allow them to follow about 165 people and all of the interactions between those people in detail. That number seems about right to me, or perhaps in my case a bit high ;-)

Twitter is just a tool – it’s how you use and the benefit that you derive that matter most. There is no right way to use Twitter any more than a right way to use a telephone. As another blogger expressed it recently, why should he have to justify using Twitter when he doesn’t have to justify using a phone?

At the other end of the spectrum from the social update users, are people epitomized by Guy Kawasaki. He unabashedly uses Twitter as the most powerful marketing tool he knows. As a result he is one of the most followed individual Twitter users, but he is also one of the most reviled but unapologetic. I find value in his posts. Recently there was a controversy when it was revealed that he uses ‘ghosts’ – other people who make posts for him – which is hardly surprising given the volume of his posts and the nature of his effort. Since his posting formula is quite clear, there is nothing wrong IMO with others following his formula under his direction.

When you start using Twitter you can be overwhelmed with the flow of information. You can select a few people to follow and keep the volume down, but inevitably over time the volume builds. One of the first things you have to learn is to, ‘let it go’. If you don’t read a feed for a period you don’t have to go back and read everything you missed – it isn’t email where people have been conditioned to try and read everything (although that’s breaking down nowadays, but that’s another topic). There is an ongoing ‘conversation’ and if you aren’t ‘in the room’, then you’ll miss it, but you have other things to do, so don’t worry.

Next you have to learn how to filter and manage the flow. There are tools to look only at replies targeted to you, posts related to specific key words, etc.

Kawasaki is using Twitter as a Social Marketplace tool. My interest is more in how tools like it can work in the Social Workplace – do they help people in an enterprise get their jobs done better or faster? And if they do, which tools are best, what features must they have and what other tools must they be connected with?

Currently within Open Text we are working on an enterprise, social networking tool currently codenamed “BlueField”. I’ve used it a lot and really like it, and I think the ways to use it best are becoming clearer.