It seems like there is an assumption that if collaboration tools are deployed within an organisation, they will be instantly used by all staff in the most productive way possible. This is clearly not the case, a lesson that wasn’t learned from the era of Lotus Notes, and is presently being replicated in the current generation of tools.

This makes the new book by Michael Sampson, Collaboration Roadmap, particularly important. This is the latest masterwork from the undisputed thought leader in the collaboration space, and it provides an insightful view of how to make collaboration tools work.

The book starts by exploring the technology options, through the lens of Michael’s models, including the Seven Pillars and Four Connectors. These help to understand the strengths and weaknesses of different types of collaboration tools, and how they can potentially fit together.

Much of the rest of the book focuses on how to strategically approach deployment and adoption, starting with creating a compelling vision, through to governance and engagement.

Be warned though: this book will make you think. Michael’s greatest strength as an expert and author is creating models and frameworks for collaboration, and this book is packed with them. I would encourage most readers to dip into sections as required, and to use each model at the point of need to guide design and planning.

In short: there’s no other book like this. If want to do collaboration successfully, get this book.

What makes an intranet ‘social’, and what are the differences between ‘social intranets’ and ‘traditional intranets’?

A philosophy and way of working

Social intranets are not a technology, or a specific set of features or functionality. Instead, they represent an emerging view of how organisations should work, and how staff can interact.

The underlying philosophy of social intranets includes:

• recognising that organisations are made up of people, with interests, activities and interactions
• delivering human-friendly solutions that match how people work in real life
• supporting two-way dialogue and interaction between staff
• facilitating cross-organisational communication and collaboration
• enabling staff to be active participants and owners on intranets, and not just passive consumers
• drawing on network effects within organisations, recognising that groups can do more than individuals
• enriching traditional business and internet activities with a social layer

[October article by James Robertson, read the full article]

The first is the move by internal communications teams away from just top-down corporate communications to two-way communication and dialogue.

The second is the rise of collaborative and social tools, which promise to transform how staff find each other, connect, and work together.

Both of these trends have driven the adoption of increasingly sophisticated collaboration tools, including team sites, blogs, wikis, microblogging and rich staff profiles.

While the benefits of these tools are already being seen among early adopters, their power and functionality makes adoption a non-trivial task.

Significant communication, education and change management is required to get staff up to speed with these often unfamiliar tools.

There is, however, a ‘low-hanging fruit’ that has been overlooked on many intranets: commenting on news.

Simple to implement and easy to use, commenting on news delivers many of the desired cultural benefits with less effort than more complex tools.

[September article, read the full article]

Alongside brand-new “social intranets” are traditional intranets still focusing on the fundamentals.
What we’re seeing is a landscape of two-speed intranets. While there is plenty of overlap between the go-fast and go-slow intranets, there are also many differences. If we’re to close the gaps, we need to recognize that there is no one-size- fits-all approach.

Stealing approaches from the public web, the enterprise space is becoming much richer and more vibrant. Collaboration tools of all kinds are being tried and adopted, introducing new ways of connecting staff members. In some cases, organizations are ditching old intranets and replacing them with social intranets that democratize participation.

Beyond the purely social and collaborative space, modern approaches dramatically simplify developing enterprise applications. This has enabled innovative teams to deliver business solutions targeting key needs in months rather than years. This has transformed go-fast intranets into powerful business tools.

While these intranets are the ones that you hear about at conferences, the reality is that they’re still very much in the minority. In these early stages, the right conditions need to be in place to enable this type of innovation. The challenge for these new intranets is to avoid throwing the baby out with the bathwater. In some cases, the lessons hard learned over the past decade have been forgotten, on the idealistic assumption that new technologies trump old problems.

[Editorial in Intranets magazine, read the full post]

“Blogs and wikis are dead.”

This caused quite a stir in the room, and more than a few follow-up questions during the breaks. So I thought I would expand on this statement here. Let’s start with wikis.

Wikis

Wikis aren’t the easiest tool to use. While wikipedia has been a stratospheric success, this hasn’t translated into huge adoption for wikis. Most people don’t know what they are, and this number is falling rather than growing.

One of the problems is wiki markup, which I’ve argued against in the past (wiki markup has no future). Even the wiki products themselves are ditching wiki markup, replacing it with WYSIWYG editing.

So while we should be doing more collaborative content creation, it needs to be simpler and more intuitive than wikis.

Blogs

Let’s face it, blogs have struggled within the enterprise. It’s a great idea to give a voice to senior management and key experts, but people are hesitant to take up the baton. In part, it’s the name “blogs”, which can be quite intimidating. It also takes real commitment to keep blogging, and it’s hard to sustain in the medium to long term.

Why not just add commenting to news? And then open up news so that most (all?) staff can post news items. (This is something I’ll be covering in an article soon.) Better this than a separate “blog central” that competes with other communication channels.

Escaping tools

Both wikis and blogs sell a technology. They are fundamentally geeky tools, alongside RSS and personalisation. The majority of staff don’t really understand them, beyond a vague familiarity with the name.

Am I arguing against collaboration and social tools? Quite the opposite! We need to substantially grow these capabilities within organisations, and spread their adoption and use.

But instead of pushing tools and functionality, each delivered on a separate platform, we should be providing simple, integrated and coordinated experiences. Facebook doesn’t need to provide a “blog central” and “video central” — these are just two elements of the overall solution (they don’t even get a distinct name).

So let’s stop talking about “blogs and wikis”, and instead talk more about helping staff to work better together.

Deploying microblogging involves more than understanding the technology, because it is really about providing opportunities for conversations between staff. The content of microblogging messages can vary widely, from accounts of what staff are working on, and questions for other staff, to updates about products, projects or situations.

The growth in microblogging is a relatively recent phenomenon and its success within organisations varies greatly. Where it has been successful, microblogging has been able to better connect staff, break down hierarchical structures and improve the sense of belonging felt by staff.

As with many of the social media tools, there is an impact on the intranet, particularly on communication channels and siloing of information. This article outlines:

• strategic considerations
• practicalities on how to set up microblogging
• how to drive adoption

Microblogging is a quick informal channel people can subscribe to with a low time commitment. It goes beyond Twitter-style 140-character comments but it is less structured and time-consuming than blogging. Ease of use and high levels of engagement make this a powerful tool to complement any intranet.

(July article by Catherine Grenfell, read the full article)

Yesterday in Stockholm, I gave a presentation at a local IntraTeam community group meeting. A friendly bunch of people, with lots of good conversations (and great lunch!). These were the key points of my presentation:

• The unmanaged spread of collaboration tools is anti knowledge sharing.
• Intranets and collaboration tools can’t afford to compete: both lose.
• Instead, collaboration tools and intranets must be brought together.
• Start by clarifying the role of the intranet and collaboration tools (including using the shop window metaphor).
• Establish good governance for collaboration tools
• Explore the many ways that the two sides can be seamlessly integrated, including simple ways of providing access to collaboration tools.

The basic scenario that I’ll be addressing is the rapid and unmanaged spread of collaboration tools alongside an existing intranet. Before you know it, the (not greatly loved) intranet is now surrounded by thousands of individual team sites. As I’ve covered in the past, this is anti knowledge sharing.

The broad strategies I’ll be covering:

• Have a clarity of purpose for collaboration tools
• Establish clear governance
• Over time, integration the intranet and collaboration tools

It should be a fun and friendly evening, with lots of screenshots and discussions. See you there…

For all this, these are deeply unfamiliar tools for most “normal” staff (ie not us). They are not drop-in replacements for our old ways of working, and require different behaviours and ways of thinking.

It is therefore strange to see so many organisations rolling out these tools with little or no training or support. In many cases, there isn’t even an announcement heralding the release of these new tools, with adoption left to organic growth through word-of-mouth.

Is it any surprise, therefore, to see staff replicate their old behaviours in the new tools?

Rich team spaces become online copies of the file shares they were meant to replace, with the same problems. Social tools are used as replacements for all-staff emails, increasing noise rather than reducing it. Collaboration spaces are created as experiments, and then quickly abandoned.

If these tools are meant to transform our organisations, why are we not making the change management effort required to achieve this outcome?

Communication and support

When collaboration and social tools are deployed, they shouldn’t be rolled out quietly. An overall communications strategy is needed to:

• inform staff about the new tools
• educate them on how to use them
• sell them on the benefits
• encourage them to change their working practices
• answer their questions
• help them to be effective

For example, we’ve seen some great videos produced within organisations to promote the adoption of collaboration tools (including in this year’s soon-to-be-announced Intranet Innovation Awards). The Transfield case study also shows what should be done to support and educate staff.

Adoption strategies

Michael Sampson’s book User Adoption Strategies is also a must-read. In it, he compellingly outlines the need behavioural change if collaboration tools are going to succeed within organisations, and provides a simple four-stage model for planning this transformation.

Most importantly, he outlines 20 (!) different change strategies that can be applied to gain adoption of collaboration tools. These range from quick-and-easy activities to major enterprise initiatives; all are worth considering.

This is a masterwork, and it highlights what organisations must do make collaboration tools work. As Michael reminds us, “hope is not a strategy”.

When I work with global organizations to help them define the business objectives of the intranet, we do it from these 3 angles. The problem is when we push each dimension to its logical conclusion, we end up with a technology dilemma.

Whether their organisation is in a position to make use of these solutions or not, the intranet team needs to stay informed. Personal likes and dislikes should be set aside to keep an open mind on investigating tools to support the business.

To be effective, the team should be able to understand and articulate the functionality, benefits and risks of potential solutions. Often other staff in the organisation are already investigating and proposing new solutions.

It doesn’t matter if team members love or hate Twitter, or if they spend their evenings knitting rather than Facebooking or using the latest mobile applications. Intranet professionals need to be able to explore and evaluate new solutions in a range of ways:

• Practicality — how does this new element work?
• Usefulness — what could it add to an intranet?
• Execution — what is the end result?
• Emotion — how does it make users feel?

[CM Briefing 2010-11 by Catherine Grenfell, read the full article]

The use of game theory and gaming mechanics in business application development is intensifying day by day, and there are already a number of examples where lightweight gaming mechanics are being integrated with intranets and related information systems.

In this article I’ll look at how gaming mechanics are in use in business, how this innovative stream of application design could be coming to your business soon and why, together with other principles, it might help fulfil a vision for the future of intranets.

Game theory?

What exactly is game theory? Millions of words have been written about it, and even a brief introduction can take up a volume. However, calling on Wikipedia (en.wikipedia.org/wiki/Game_theory) for a summary:

"Game theory is a branch of applied mathematics that is used in the social sciences, most notably in economics, as well as in biology (most notably evolutionary biology and ecology), engineering, political science, international relations, computer science, and philosophy. Game theory attempts to mathematically capture behaviour in strategic situations, in which an individual’s success in making choices depends on the choices of others."

[June KM Column by Alex Manchester, read the full article]

Twitter has popularised the use of #hashtags as a way to aggregate relevant tweets together. #hashtag is a special kind of tag because people learn about them before using them. For example, if I want to apply a hashtag for information architecture, I will lookup the hastags.org directory to see if I should be using “information_architecture”, “information-architecture”, “#ia” or some other hashtags, based on the original intention of the hashtag, the popularity of the hashtag, the quality of information represented by the hashtag and the type of people I want to reach. This is unlike tags, which is a typical summary of content using keywords that mean something to the originator. #hastags have this powerful self-organising ability. It is this inherent ability of #hashtags that allows us to build communities organically. This is nothing new, it was the intention of #hashtags in Twitter.

In my last blog post I covered open vs. managed community creation inside the enterprise. The next logical question I am asked is “If we do go the managed creation route, what types of questions should we ask the requestors?”. I hear this question often and so decided to share what I share with my customers and ask you to chime in with what else you might have to add. (Keeping in mind we are talking about internal communities within the enterprise.)

One of the presentations was by Alstom, talking about their efforts to establish collaboration within the organisation. Under the banner of Alstom University, they’ve produced some great educational material to support the initiative. Generously, they’ve also shared some of this online.

This includes resources on YouTube, such as:

As well as a good presentation on SlideShare:

Great stuff!