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

Finding the right trigger for success

Finding the right trigger for success

I’ve just been reading some conversations in one of the Linkedin Change Management groups I belong to. The conversation is around why organisations are still struggling to get Yammer adopted.

It still amazes me that in 2016 many 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.

Any programme / project manager with an element of common sense could also scan the internet and get a reliable formula to get those engagement / value rates above 55-60% (70% looks to be the saturation point) rather than languishing in the 20%.

Many of the previous comments have articulated the recipe for success, or lack of it, such as…  ‘not aligning to business strategy, little governance, poor planning, wrong use cases at the wrong time, treating change like a IT change programme rather than behavioural change etc. etc. etc.

A couple of areas I would raise which compounds the agony of low adoption / value:

Few of the owners of these platforms appear to be appraised on garnering value. As long as it ‘works’ from a technical perspective the responsibility appears to stop there.

Also too many project managers run traditional change programmes which deliver the rational reason to use the platform, tell them what to do, the how and why. Few look to go further and try to deliver the emotional reasons, activate leaders, shift mind-sets and behaviours or align the formal organisation. And very, very few actually work on finding the ‘triggers’ that will give people the motivation to change.

However, I know Microsoft (and others) are realising that they need to ‘raise their gam’ in terms of preaching ‘change management’ as a key element of garnering business value. Also how that change management is delivered (more open, transparent, inclusive, cross boundary etc.) is also something that needs to be promoted further.

 

However, I know Microsoft (and others) are realising that they need to ‘raise their gam’ in terms of preaching ‘change management’ as a key element of garnering business value. Also how that change management is delivered (more open, transparent, inclusive, cross boundary etc.) is also something that needs to be promoted further.

 

Becoming a social leader

Becoming a social leader

Trying to get leaders to understand the potential and value of creating an open and collaborative business can sometimes be a hard sell. One of the key milestones is to get them embracing and supporting the deployment of tools and associated behavioural change required to utilise the investment.

Key elements when approaching leaders should include:

  • Explain the key elements of open / social working
    • Outline the need to appeal to individual’s ‘intrinsic motivators’
    • Provide practical examples of individuals becoming more effective and engaged
    • Guide them on how to develop and spread the habit via doing
    • Explain how they would “contribute to people in their organisations to deepen the relationship”?And also why should they?
    • Don’t replicate a process. It has to replace it or be something new.

Using the ‘seeing is believing’ mantra here are some tips to get your leader involved. O365 is used in this examples but this would apply to most collaboration and open business technologies.

1- Explain to them the overall benefits, ideally linking to the overall strategy. Normally the benefits would include:

o Enables ‘new ways of working’ by providing:
 Access everywhere, anytime
 Transparent and open working
o Builds a connected organisation enhancing business agility
o Increases employee engagement
o Improves team collaboration
o Enables external collaborative working

2- Set out the benefits for the leader (try to understand what would be key motivations prior to the session). These could be:

• Build a personal brand across the organisation
• Network across silos
• Increase engagements and receive feedback
• Access and share documents easier
• Network / collaborate externally
• Manage meetings and reporting more effectively
• Build a connected organisation by increasing participation in Townhall events

3 – Getting the leaders started

• Update their Profile with skills and experiences and explain the benefits.
• Profiles and reputations develop fast in the online world. Yammer offers Leaders new ways to promote their views and skills
• Leaders will emerge that may otherwise have been hidden in dark corners
• Yammer gives everyone the chance to share their views in an open forum
• Contributions are a lot more transparent and the Personal Brands Leaders create allow leadership potential to be spotted
• Smart Leaders and Talent teams embrace this opportunity.

4 – Spend 5 minutes building or expanding their network on Yammer

• Guide them on how to ‘follow’ people and join ‘groups’.
• Ask them to pick a few key words around topics which reflect their role and aspirations within the company (don’t just follow the people you already know) and use the ‘search’ option to explore what people and groups have similar interests.
• Begin following and see the value it may begin to bring.
• Don’t suggest they select hundreds or they will be ‘drowned in the noise’.

5 – Explain the power of ‘liking posts’

• Leaders should be taught the power of liking posts.
• A ‘like’ from a Leader has a big impact and is a good way to drive colleague engagement and motivate action all in one second.
• Encourage Leaders to use the ‘like’ option but also to be aware of the impact that ‘like’ can have if it’s not actually genuine.
• Before they know it a whole new process could be accidentally developed.

6 – Get them to join conversations and ask them to assess what benefit this has brought them over a period of a few weeks.

• Leaders’ reactions to posts shape how people perceive them as leaders
• What’s key is to teach Leaders how to handle conversation well and to do so publicly
• Over zealous comments or poor ends up sending a much louder message than simply responding in a well thought through manner

7- More things to remember

• At the outset it’s too easy for leaders to say it’s not for me. You want colleagues to make an informed choice knowing what is on offer before they decide not to use it, not to decide against it because it’s a big unknown quantity.
• If they are resistance or believe they need ‘training’ before they use it then offer them this through beginners coaching sessions
• It’s a self-updating skill set once they are on the bandwagon but at the start you don’t want to leave good talent behind. Everyone should be given equal opportunity to shine.

8 – Next steps

Once they are confident and comfortable with this way of open working then get them to expand. The next steps will be:

• Running a crowdsourcing session ‘ Yamjam to increase participation and innovation
• Hold ‘Town Hall’ events to increase engagement
• Sharing a vision for a better future and they ask their people to co-create this together in open innovation forums.
• Get them to ask colleagues to combine our strengths and spend more time collaborating around that which we wished to accomplish, rather than that which we wished to avoid, what’s possible?
• They co-design what is next.

Engagement is ‘nice’ but democracy provides the value

Engagement is ‘nice’ but democracy provides the value

I sense we are still in the early stages of how ‘social ways of working’ can create value. Communications, engagement and knowledge sharing are early ‘adopters’ of ‘social’ but the internal audience’s affection with tools may eventually fade and move on to alternative channels. The real value from these ‘social’ tools comes when we explore how to utilise them for innovation, crowdsourcing, validation and creating more open, transparent and democratic structures within organisations.

By using collaboration and open business tools like Jive and O365 (Yammer) the chance to develop new ways of working is immense. Rapid validation of innovation and and organisational structures are enticing but the opportunity to bring democratic approaches into areas such as product development, strategy and governance can truly change the way colleagues, suppliers, customers and leaders can develop organisations for the future rather than bleak rigid corporations built on ‘war-like’ structures and sound bites.

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?

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.