Adopt – Not Adapt

Just been catching up on the wave of promotional emails sent during the festive break, from Microsoft right through to small start-ups, all advertising their new enhancements to AI technologies that enable deal with everything during my full day or back-to-back meetings, full email box or endless Team chats.

It seems to me that much of the technology that has been introduced over the years has led to this situation where little or no time is spent actually thinking and doing. My mind paints a picture of being thrown a lifebelt from the ship that caused my vessel to capsize in the first place.

I’ll be interested to see when and how AI starts to deal with guiding me on behaviours to actually stop being in back-to-back meetings and having endless Team chats and emails. I guess I already know the answer. It’s a ‘cultural’ or behavioural trait that causes the problem. The technology is only trying to help lighten a heavy load.

What we need to move away from is continually adapting to the situations are own behaviours create and start adopting new mindsets on the way we work.

Yammer and LinkedIn

Yammer and LinkedIn

I’m sure Microsoft brought LinkedIn with a specific purpose in mind although it wouldn’t be the first time they know something is good, buy it and they figure out what to do with it!

It sometimes reminds me of some of the mega-rich English Premier League clubs who buy in talent that have very little to do with the current style of play, sit them on the bench and wait for a situation to arise when it becomes clear why they brought them in the first place – or just serendipity!

I would like to think that Microsoft see the future value of collaboration around new ways of working is not to just support the current hierarchies and structures of an organisation. In essence that’s what most of O365 does in supporting this structure of group working around file uploads, storage, document production etc. All important stuff but does nothing to drive innovation and new wealth / value creation.

Where the value creation comes is from building networks, relationships and communities, nurturing new behaviours and processes and blending diversity to create new ways of working.

Yammer and Delve begin to achieve this inside the organisation and adding something like LinkedIn gives an organisation the opportunity to source content, connections and resources far beyond their current network.

I’m thinking of an example where a project manager can initiate a new project and Yammer / Delve (whatever these channels would be called in the future) to source ideas, content, connections and resources from within the organisation and then get seamless connectivity to a LinkedIn type resource (professional and educational) to source gaps or enhancements to the knowledge they have within the organisation. It changes not just the potential reach but also the relationships organisations have with professionals. It would also increase the diversity of thought that an organisational begins to call upon, ideally making it far more social, transparent, agile and democratic.

Adoption by hierarchy

Following on from the ‘Adoption by Chance’ approach an alternative if the ‘Formal Approach’ or adoption through hierarchy (and highly recommended if you were even thinking of taking the ‘Adoption by Chance’ approach).

The formal approach is based on:

  • Engagement through leadership / key stakeholders
  • Implement a formal approach (defining and delivering) to educate on the collaboration technologies.
  • Refine approach and collateral as the programme develops

Adoption through hierarchy

MERITS

  • Understanding of the ‘What, Why, How’ of the technology from a leadership perspective and ensuring they are fully aligned
  • Colleagues ‘on the same page’ and at the same stage of the journey
  • Knowledge of all available materials
  • Formal support process
  • Increased ability to maximize the applications available – larger number of use cases surfaced
  • Ability to get access and collaborate across all areas of the business
  • Comprehensive approach

DRAWBACKS

  • Slow and time consuming – early motivators may lose interest
  • Pace set by leadership or project team – not the users
  • Too much detail – information presented won’t necessarily be applicable to all
  • Too rigid
  • Loss of interest increases and users drop interest of the ‘journey’
  • Rational approach but doesn’t appeal to emotional interest
  • Potential to be exclusive and siloed

Adoption by chance

Having looked at 3 very different approaches to adoption of collaborative technologies here is my take on the drawbacks and merits of each.

Today we start with the ‘throw it over the fence’ approach. I would suggest this is generally favoured by IT folk who need to ‘get it out there’ and their focus is not on sustained usage or business value.

Success is generally low and adoption is by chance

MERITS
• Self-contained, no need to engage with other areas of the business prior to deployment
• Low cost – little resource required
• Enables rapid deployment
• Creates an enterprise-wide awareness (if communication channels are effective)
• Enables a swift campaign to be executed
• Meets immediate technology enablement requirements

DRAWBACKS
• Awareness does not guarantee engagement with tools
• Little understanding of how they can be utilised
• Little control over how the business will use it
• Little adoption once early motivated adopters have been engaged
• Little adoption or engagement once campaign has finished
• Little sustaining or legacy behaviours in place
• All behavioural change is by chance or self-understanding

Adoption by Chance, Hierarchy or Community

Sticking with the ‘power of 3’ theme from a previous post (The Power of 3) here are the least / most effective approaches to adoption (habitual usage) and sustained business value from collaborative technologies.

1 – Throw it over the fence and let the business get on with it (Adoption by Chance).
– Provide access to the tools
– Provide access to training areas
– Develop communication / launch plan
– Create messages and deliver through formal channels
– Email alerts
– Portal / Intranet
– Traditional Change Agents
– Leave it to the business to ‘go figure’
Adoption success around 10-15%

2 – Common Formal Approach (Adoption through hierarchies)
Favoured by many of the consultancies involving engagement through leadership, implementing a formal approach around defining and delivering the programme which is refined, together with collateral that is recycled and enhanced as the programme develops. The formal approach includes elements such as:
• Developing the pitch
• Defining ‘What’s in it for me’? for business areas
• Technology Planning
• Engagement planning
• Adoption services
• Build and sustain
Adoption success around 45 – 60%

3 – Social Approach (Adoption through informal networks, tribes and communities)
This generally involves engagement through informal structure of companies with adoption built around explicit use cases (not abstract but rapid, high volume explicit use cases) and supported by:
• Deploy waves of rapid use cases
• ‘Word of mouth’ through networks
• Nudge channels
• Informal advocates
• Social learning
Adoption success around 55 – 70%

The power of 3

Over the last few years it’s been pleasing to see how some of the collaboration software vendors have been changing their tune over how to successfully adopt their technologies.

If you compare the early adoption collateral for Jive, Yammer (O365), Chatter (insert numerous names here) and look at the adoption approaches they now recommend – built around behavioural change, habit formal and other techniques from neuroscience and related disciplines – those of us from the ‘people’ side of technology feel more comfortable than ever in championing the mantra that good adoption of collaborative technologies is more about psychology than technology.

Using the ‘power of 3’ psychological approach here is my take on the ‘do’s and don’ts of adoption broken down into 3

DON’T

  • Don’t focus on technology / product names and keep use of traditional corporate channels to a minimum
  • Hierarchy won’t be effective – no ‘trickle-down’ effect in most organisations. Leadership support is important but it must be active (role modelling not just telling)
  • Don’t tell people the whole story, show then everything at once, or provide just one approach / route for success

DO

  • Focus on behaviours and scenarios with short bite size coaching and messaging (power of 3)
  • Create a bottom up / ‘word of mouth’ approach, developing social learning, role models (doing rather than telling) and nudge rather than command
  • Work on volume (light lots of little fires – develop use cases, nurture advocates, present at meetings) and then focus energy on those that catch fire and show potential to grow)

Something got me started

Something got me started

Like this article which shows the important of building momentum in driving the adoption programme.

People love to be associated with something when they garner a sense that things are happening (remember the Dancing Man) – link below.

So if you’ve deployed the technology and got little response from your colleagues then it’s time to build momentum.

In practical language that means working with some potentially interested colleagues to develop use cases – not abstracts but real ones that are helping to solve their problems and getting work done.

It’s part of a ‘social / word of mouth’ approach that begins adoption through networks and communities rather than larger formal approaches.

http://www.cmswire.com/digital-workplace/how-momentum-drives-social-collaboration/?utm_source=cmswire.com&utm_medium=email&utm_campaign=cm&utm_content=nl-daily-160707&mkt_tok=eyJpIjoiWTJWaFpqSTFOVE0zTjJJMSIsInQiOiJMOHJFMEpPams1dHZ1aUpPQU5hazNLcHk0VW1uQ2xEN2JBMmJKejg3ZVk3SDUyblNjMzZSM3lxcWNOWldJSWZ2dVd6ZDIwd1N4Y2d5RDlHb1RMVHFNdDllWVZpMlZpcEE1NzhaZUFuRFhtRT0ifQ%3D%3D

People love to be associated with something when they garner a sense that things are happening (remember the Dancing Man) – link below.

So if you’ve deployed the technology and got little response from your colleagues then it’s time to build momentum.

In practical language that means working with some potentially interested colleagues to develop use cases – not abstracts but real ones that are helping to solve their problems and getting work done.

It’s part of a ‘social / word of mouth’ approach that begins adoption through networks and communities rather than larger formal approaches.

http://ed.ted.com/on/IgslePtt#review

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.

Pandaemonium

Pandaemonium
716

 

I’m currently reading ‘Pandaemonium 1660-1886: The Coming of the Machine as Seen by Contemporary Observers’ (by Humphrey Jennings, co-founder of the Mass Observation movement of the 1930s)  

http://www.amazon.co.uk/Pandaemonium-1660-1886-Machine-Contemporary-Observers…

It fascinates me to compare the benefits and dangers of the industrial revolution with today’s digital revolution.

Pandaemonium collects texts taken from letters, diaries, literature, scientific journals and reports of the time, and traces the development of the machine age in Britain. Covering the years between 1660 and 1886, it offers a rich tapestry of human experience, from eyewitness reports of the Luddite Riots and the Peterloo Massacre to more intimate accounts of child labour, Utopian communities, the desecration of the natural world, ground-breaking scientific experiments, and the coming of the railways. Pandomonium was originally published in 1985, and in 2012 it was the inspiration behind Danny Boyle’s Opening Ceremony for the London Olympic Games.

Interestingly (for me anyway) is the book is divided into 4 sections:

 Observations and reports

  • Exploitation
  • Revolution
  • Confusion

I spend much of my time looking at how organisations introduce and sustain knowledge sharing, collaboration and communication technology and associated behaviours.  

If we get adoption and adaption right these are disruptive technologies that can assist in changing the nature of the way colleagues engage, communicate, share, learn, nurture and collaborate with each other.

If we get adoption and adaption wrong organisations, and the people / networks within them, go through the trials and pains articulated in the chapter titles above (quick reality check – I’m not comparing the suffering of the industrial revolution with that of an employee who can’t work out the # function on their enterprise social network).

We have seen the observations and reports of how a more open and transparent environment can enhance both employees and organisations.

We are at the exploitation stage where there is a mad rush to social without the analysis or change management processes needed to create the value.

We will soon have the revolution as organisations and employees fight, struggle, resist or forge ahead in the use and value of this new way of working. Many organisations will embrace, while many will fail to get value and asset it’s the technology and / or culture that is the issue.

For those that forge ahead confusion will be created if we lose interest in the on-going stewardship of these tools and behaviours and at worst we see employees burdened with another deafening channel in an already noisy eco-system or technology.

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.