It’s not about the like?

It’s not about the like?
I’ve heard lots of talk recently around metrics and ROI on knowledge and collaboration tools. Many of the intranet, social media, IT, HR and marketing people I speak to are still looking for metrics that will provide some of the traditional measurements around attraction, attention and adoption, such as downloads, unique users, popular pages etc. In the new world of social, open and collaborative business should we be looking at ‘likes’, ‘favourites’ or user comments?
For me it has to be more than just a ‘like’ or thumbs up but something deeper about exploring the depth of connection to people and content that has been developed.

In many ways the measurement still produced for various stakeholder dashboards has not changed for many years. We still see the benchmark of activity as something which should be measured. The value of the activity is something which stakeholders rarely asked for.To measure the value of the relationships and transparency created by the individuals, groups and communities residing on collaborative or social platforms we still need to conduct a lot of manual digging to find measurement around such artifacts as:

• Social Knowledge – this can be defined in many ways such as assets being shared around a community (and beyond) and related practices emerge.

• Relationship development – the ability to create new relationships and networks that previously didn’t exists

• Number of relationships created by individuals and their depth – look at followers and participation in threads

• Discovery of communities – have members joined communities outside their ‘physical’ or existing network

• What collaborative activities are emerging

• What threads, replies, comments or connections contain referrers to potential collaborators

• What threads contain creative or innovative ideas

• Are members sharing personal stories and how much emotional support is provided

The various web metric packages and social business tool reports do not provide this type of information and much of it will be antidotal evidence. Social analytics are poor within most social tools (it will be a major revenue stream for a vendor that can start to provide some of the softer metrics that articulate quality and not just quantity).

Over the years I’ve reported on numerous ROI and metrics to various groups of stakeholders. My top 3 in no particular order are:

  1. Creating an online community platform saw a 25% increase in the production of material for clients – by providing a collaboration platform for an existing professional service group their monthly ‘physical’ were supported by an online community platform. It enabled the sourcing of wider expertise (from across the country) that resulted in a 25% increase in the production of thought leadership material to be issues to clients (you could argue if that was a good thing but that is missing the point).
  2. IA change resulted in senior managers saving an hour per month searching for documents – by conducting user research into how audit managers worked a change of IA and navigation within their community site saw, on average, senior managers save 1 hour per month in sourcing the relevant methodology documentation required, enabling greater time to be spent on finding and minding clients
  3. Developing the online community sees a rise in employee satisfaction scores – a large customer service group within a global organisation were given access to form their own online community. With good strategy, governance and stewardship the community thrived. In annual employee satisfaction surveys the groups average % score increased significantly (I’m sure there were many other factors involved by why spoil a good tale) and was over 20% higher than other similar customer service groups. In some areas a 1% rise in employee satisfaction equates to £2m extra revenue – so you can work out the potential benefit!

On the downside my most disappointing metrics was reporting the drop in homepage visit after an expensive rebranding exercise on our intranet homepage but that did reflect an increasing trend in the value of the homepage becoming diminished

My favourite ‘metric’ as such involves a community set up to bring two very diverse groups together, to collaborate in reporting common faults and reporting back workarounds and fixes. I am hard pressed to call it a community as neither group had any previous interaction (which was part of the issue) and I do preach that unless a conversation is already taking place in the physical world it is hard to develop this online.

One group was a skilled manual workforce based across the UK. The other group dealt with customer service and could be located across the global. With governance and steward in place the volume of activity began to increase.

When it came to the assessment report the ‘metric’ I took most pride in was not the volume of activity nor the number of cases solved but the anecdotal evidence from both sides of the fence that the visibility and transparency created through the forum had begun to create a greater appreciation from each group, an understanding of the issues each face and how to work with them.

You could then spend months evaluating how much benefit this continuing of connections could save the organisation but sometimes the user comments mean so much more than a hard metric.

Given the unheard a voice

Given the unheard a voice
One of our manager groups on Yammer is thriving. Recently launched, with a little stage management, the number of contributions has been higher than expected and, of more interest, is the value of the conversations and connections being made.

The group has a visible leader (important for user faith and compliance issues) and leadership support. The group was launched to support a physical event and early contributions were used to deal with issues leading up to the physical event (call for table leaders, logistic information etc).

However, it has branched out and we now find it is being used by managers outside London to showcase their knowledge and skills – in a very London centric community. It has given them a true voice to be heard. Some habits are still hard to break. The ‘leader’ is still being emailed and asked to post contributions while one office held a meeting to discuss what they wanted posted on the site, and then who should post the contribution.

At the launch there was no mention of technology and introduced as a tool to address an identifiable need – the ability to support a physical event.

Movement of the People

Movement of the People

Is it me but do all the major issues over the summer appear to deal with ‘movement’ (or maybe transportation)? The news agenda is full of items around the movement of:

  • People (across borders, cities and the basic A-B of getting from work to home – or maybe the issues of why many people still do this as networks, drones and live video streaming becomes more common).
  • Identities – easily replaced, replicated or stolen
  • Data – see above
  • Finance – across borders and laws
  • Goods – whether physical or how they will be replaced by 3D printing

Maybe how we fuse the physical and digital worlds will be the key to dealing with the issue of movement over the next 5 years?

Nudge the network

Nudge the network

If you do have a spare 30 minutes I would recommend reading the Behavioural Insights Team Update report.

Click to access BIT_Update-Report-Final-2013-2015.pdf

As more enterprise tools such as O365 / Yammer and Jive the old traditional methods of IT adoption fail (if they ever succeeded) and that’s where the digital transformation agenda takes over. IMO any deployment of collaboration tools need to look at behvaioural insights, nudging the network and behavioural economics to ensure success adoption.

Stick to the recipe for Enterprise Social Software success

Stick to the recipe for Enterprise Social Software success

When I look at reasons given by organisations for the failure of their Enterprise Social Software project to deliver any success or value (whether this is adoption or return on investment or engagement) I still hear the same issues around poor adoption, cultural issues specific to the organisation, change management, alignment to business needs etc. You could date stamp this as ‘2010’ and the issues haven’t changed.

It still amazes me that in 2015 organisations are struggling to get value from social software despite a reliable ‘recipe’ now being known.

All consultancies both large and small have a framework which is pitched to potential clients that will deliver various degrees of success – but success nevertheless.

Every software vendor has similar material that it will tell clients prior to any adoption programme how to get success (actually an interesting exercise would be to look at how the vendors have changed their ‘tune’ from 2008 onwards by looking at how their client adoption material has changed from ‘just plug it in’ to more strategic thinking).

I would also suggest that the vast majority of organisations that deploy Enterprise Social Software have an understanding or at least an awareness of what needs to be done – and I speak from a perspective or having sat on both sides of the table (industry and consultancy) and I would estimate that 90% plus of people I have dealt understand this.

But despite all this material a large majority of organisations appear to ignore the recipe.

I’m trying to find a simple analogy to compare this with so let’s try cooking.

If I were a chef (the ‘sponsor’ of the deployment) and I wanted to make a paella (deploying the tool) and I have a known recipe on how to make paella (the vendors material, consultants material, freely available material online etc.); then why do I think my paella will turn out fine if I refuse to use some key ingredients like the correct rice, saffron, paprika, wine etc. (change management, governance, use cases etc.)?

Some may be down to cost; some may be lack of knowledge – but wouldn’t you look at the recipe before you start!; some may be down to stubbornness (you deployed other tools before and your way has always worked) but I believe in many cases it’s down to the simple fact that most sponsors are purely concerned with plugging it and making sure it works from a technical perspective – and not appraised on the engagement or value it brings. No different to a chef not being appraised on how good the paella is but the fact they have served up a plate of rice that is dressed up as paella but has none of the taste.

Unless the success criteria is driven by engagement and value – which often happens a number of months into the adoption phase then organisations will continue to cite the same issues with their Enterprise Social Software.

The vendors realised their business model needs to change – not so much about selling licences every 5 years but seeing their software being adopted, adapted to working ways and providing value.

Few areas of an organisation focus on how engaged their workforce is with the ‘service’ provided but this will change. It will eventually filter down to project teams that are built to deploy social software.

In my ideal future world deployments will focus on behavioural change rather than just technology change in order for social software to be a success.

A project team for future deployments will have a very different line-up. The focus won’t be around IT Project Managers or business analysts but instead recruit business psychologists, community developers and social network analysts to ensure social software success.

We all love a good story

cropped-712.jpg

Storytelling can be a powerful tool when you want to explain how collaboration tools can help colleagues.

Stories are one of the most powerful emotional currencies we possess. They move people to feel, and they move people to act.

At work, stories take the form of narratives, conversations and anecdotes that connect us with the narrator and the subjects and broaden our pool of knowledge. When you share a story, you will spark a story or idea.

We use stories to make sense of our environment. They make us care. They provide a shared context for mutual understanding of events and issues that impact us. And they inspire us to change our point of view.

Ideally a good story around working with collaboration tools should communicate some form of causal resolution of a problem and also have the addition of meaning and significance for the audience.

When I speak to people around the capabilities of collaboration tools I generally don’t talk about what each feature or button does but how the enabling tool (and associated behaviour coaching) has changed the way people have solved an issue; or created innovation; or developed new engagement channels.

My favourite stories of how these type of tools have helped include:

  • Solving departure delays at Istanbul airport
  • Ensured passengers flying into Heathrow received their ‘Bloody Mary’s’ just the way they like them
  • Helping sped up the alterations to passenger wash bags
  • Safety lessons from drilling rigs were shared across an organisation within hours
  • How a banana ice cream maker could peel a thousand bananas at the same time

Obviously these lose much of their currency once taken outside the context of that particular sector so it’s beneficial to begin building a library of wins / case studies as soon as possible. They don’t need to be too details – just a good story. .

Often a new manager or colleague won’t know how these tools and behaviours may have made a difference, but peers and other leaders may have a rich store of anecdotes and memories to make the use meaningful.

Avoid the usual suspects

Transformation programmes are changing dramatically in the digital age.

The main theme of traditional deployments of tools was that change programmes were slow (cascaded from the top, filtering slowly down), soloed (by geographies, levels and departments) and exclusive (owned by leaders and nominated change agents).

In the digital era change is now fast-paced (focused on habit-forming to kick-start new behaviours), focused around behaviours not technology and inclusive (allows everyone’s input to be seen and for social learning to happen).

One of the key changes is the advocacy network that can be built. Forget reaching out to management and asking for the ‘usual suspects’ – the same folk that get volunteered for most change programmes. Use digital and networking technologies to create a broad number of advocates.

It doesn’t matter about the time commitment. Ask then to do what they can when they can. In the digital age getting volume at the ground level is important. Avoid traditional messages on the intranet and focus on getting role models, word of mouth and great use cases. This will spread the transformation far quicker than going through traditional and failing channels.

What goes where?

Employees are faced with a range of tools to communicate, collaboration, share and network. Simply deploying new tools just confuses an already overworked organisation.

To expect many to understand what tool should be used in which context is foolish. One of the most important documents you can produce in the early days of a collaboration tool deployment is guidance to participants about what goes where.

This could be dressed up as a content strategy document, outlining where implicit and explicit knowledge / content should be stored or a straightforward guide on which tool to use when. Just map out some business scenarios and give people ‘guidance’ on which tool can be used to accomplish the task most efficiently.

Get this document into the environment early and it will save you lots of time answering questions from confused new adopters of the collaboration platform.

It’s more than just the coaching

At my current client we are running a series of ‘beginners guide’ coaching sessions for those that are new to business networking platforms.

We run through the basic concept of using a networking site, the importance of your profiles, how to use the network to get value by following people and groups, etc.

Most platform vendors will claim that little training or coaching is needed as their respective tools are intuitive. But not everyone is on a social network in their personal life and I find some coaching is needed to ensure ‘no one gets left behind’. It’s a common approach, particular from IT departments that run these projects.

But the challenge does not end there. Just because someone now knows how to do something doesn’t automatically mean they will begin using it.

We mustn’t confuse ways of imparting knowledge with ways of changing behaviour. To encourage a behaviour we need to generate the best conditions for it to arise and then reinforce it. Merely knowing what you should do is often insufficient to reliably bring the behaviour about and merely knowing doesn’t offer much in the way of reinforcement.

So to support the behavioural change we are also coaching how colleagues can
develop highly engaged communities through some hints and tips around building habit formation as a step to changing behaviour online – some steps you can take to ensure your colleagues begin to regularly participate on the business networking platform.

Coaching participants on how something works is fine but the value comes from coaching on how to develop habits to utilise the capabilities of the network on a regular basis.

Don’t mandate but encourage

Don’t mandate but encourage

The key to getting sense from any networking and collaboration platform is to embed good behaviours of users rather than force templates or processes through technology.

As people gain more experience they will see the benefit of how they need to relate groups or content and begin to adopt good behaviours rather than mandate too much at the beginning which I believes restrict the desire to engage.

I firmly believe that if you alter that level of ‘control’ to an extent where you mandate to much, much of that implicit knowledge is lost due to people’s lack of engagement. I’m sure everyone has seen systems that deal with every workflow, scenario and linkage, with lovely metadata and taxonomies but they remain graveyards. I would also stress that we are not discussing a ‘heavy duty’ document management system here but a networking and collaboration platform where we are looking for people to share their knowledge.

One of the most interesting studies on knowledge sharing was conducted by Constant, Kiesler and Sproull.* One of their findings was that employees differentiated two kinds of knowledge sharing. One type was sharing products, for example, equipment manuals, or reports they had written. The second type of knowledge was what employees had learned from their own experience, for example, how to get around a certain bottle-neck in the system, or how to deal with a particularly tricky bug in a program. This second type of knowledge they regard as part of their identity – part of who they were as professionals.

They were willing to share both kinds of knowledge, but the motivation for sharing each differed greatly. The documents and programs they shared because they considered them the property of the company. But the second kind, their experiential knowledge, they shared because they gained some personal benefit from doing so. The personal benefit, however, was not money or the promise of a promotion. According to the study, “Experts will want to contribute to coworkers who need them, who will hear them, who will respect them and who may even thank them.”

As this study shows, the primary driver for sharing experiential knowledge is the respect and recognition of peers. It is hard to overestimate the psychic value peer recognition. How does this relate to controls and mandates? The less freedom a user has over the ‘platform’ (whether this was a technology or a physical environment) the less they would share their own experiential knowledge.

Organisations that have created great engagement and value from collaboration technologies have done so because they have reduced many of the controls that you would find in their more structured channels such as intranets and document management systems.

It may not always be neat and tidy but it generates this ‘experiential’ / implicit knowledge that organisations have tried to tap into since KM programmes first started. If we initially focus on getting the engagement, input and desire for folk to share then the quicker it is to make sense of the noise that social collaboration platforms can bring.