Showing posts with label adoption. Show all posts
Showing posts with label adoption. Show all posts

Corporate communications ?= internal marketing

Corporate communications ?= internal marketing
Photo by Eric Ziegler
Isn't a corporate communications teams really just internal marketing team? Why don't they act like external marketing teams, using the same techniques?  The ones that I know, have not changed their ways to match the methods external marketing. In some instances, they don't embrace some of the newer ideas and technologies.

Are there reasons why? My guess? The biggest reason is probably that the focus and value provided by these corporate communications teams is perceived to not be as high as the ones that are "driving" people to purchase the products and services of the company. Because of that, they do not get the funding or the encouragement to step outside of the basic tools they are provided.

Unfortunately, enterprise communications teams are probalby more valuable than most people think.  They have the ability to really drive change in the organization, change to processes and new technologies. And unfortunately, they are often left with either the lack of tools to do the job of external marketing teams or the lack the ability to realize that they could be more like the external marketing teams.

This note was inspired by +David Amerland 's book, Google Semantic Search.

Helping corporate communication find value with an #ESN

Photo by Eric Ziegler
In my previous post, I talked about helping team find the value in using a new technology.  In this post, I am going to focus on one very specific example. Helping a corporate communications team that is stuck in their old methods of communication style.

In the traditional corporate communications world, most teams are just familiar with the intranet and email as primary vehicles to communications. In many cases this specific team will resist the desire to change communication methods. My guess on why they resist? They don't see the value. They are uncertain and doubt that a new method might be better. As I stated in my last post, to help a team like this find value, their biggest concerns, their biggest issues with communication need to be understood.  For example, are they seeing a drop in people reading their communications?  Are they hearing that people only hear about events after they occur?  Are they hearing that people can't find appropriate content?  

So when a new technology like an Enterprise Social Network (#ESN) is implemented, identifying solutions that will reduce the issues they see today is a great way of getting a team like this to adopt the new technology. So the question is how can an ESN help corporate communications with these hypothetical issues?

By using an ESN to advertise and promote the latest news article or event, people visiting the ESN will start to read more of the content. It is a secondary channel to share and obtain a greater readership. And if done well, the reach of the message could be even larger, as people share and re-share the information.

In addition, by sharing out the enterprise social network, the sharing and resharing will have an impact on the ability for people to find the best and most appropriate information and content. Similar to the internet, social plays a huge role in how search works. And by having employees engage with the content will allow search engines to automatically assess the most important information and will allow people to find the content faster (through multiple channels including the ESN and search).

This statement might seem out of place, but ...  the concepts of traditional inside the enterprise marketing has to adapt. Especially as semantic and social in the enterprise collide. The quality of the content that is created is all that much more important.  The higher and more relevant the content, the more likely it will be found.

This note was inspired by +David Amerland 's book, Google Semantic Search.

Adoption is about helping to find value

Adoption is about helping to find value
Photo by Benjamin Ziegler
In the enterprise, when a new technology is brought in that all employees would use, the challenge is often not with the implementation but convincing all employees to adopt and use the new technology. A great example is an Enterprise Social Network (#ESN). How do you obtain adoption that meets your business needs and goals? Grass roots? Top down?

Often much of the effort of adoption center around some type of marketing campaign. And more often than not, to do the marketing of a new communication technology requires using the old communication technology.  eMail, intranet, etc. are likely the tools that will be used to market the new ESN. These are still important, but are there other ways?

One of the methods to help with adoption is to work with enterprise business units to help them realize the true value of the new tool. Find groups, small teams in the enterprise that will benefit from the new tool. Look for reasons they might not have realized were there to help them understand the true value of the new product. Listen to the employees of that team. Hear how they work, not just how they communicate. Look for opportunities of  how their jobs could be enhanced and then work with them over time to start using new techniques to make their work "betterer".


Reputation --> Trust --> Semantic Search in the Enterprise

Reputation --> Trust --> Semantic Search in the Enterprise
Photo by Eric Ziegler
Based on what I have been reading I believe that I understand that semantic search is built on the trusting the content that has been written. This trust can be gained via trusting the individual and can the trustworthiness can be increased by people indicating that they trust the content.  

Based on this assumption and assuming that reputation is built based on both digital and analog interactions (especially in a closed environment like the enterprise), how can a complete picture of reputation (and hence trust) be built within the enterprise? And how can a great enterprise search experience be built without the full enterprise reputation picture being created? I would venture to guess that the interactions in digital will approximate the reputation in the analog world, but then again, that is assuming that there is 100% adoption and interaction in the enterprise digital systems. 

Anyone else have any thoughts?

This note was inspired by +David Amerland 's book, Google Semantic Search - Amazon location 1853.

Setting Expectations


Photo by Sarah Ziegler
A friend and I were recently talking about adoption. Specifically we were talking about the adoption of tools that help build enterprise communities. One idea we discussed that I haven't read that much about is:
        Setting expectations.
While I know this idea is not new, I have not heard much about the use of setting expectations for Enterprise 2.0 or Social Business or adopting enterprise social networks. For example, as a people manager, if you have read it once, you have read a million times. To help guide your employees to ensure they know what to do, you need to set expectations with your employees. If you don't the manager is at a higher risk of not getting the best performance out of each employee.  This is an oldie but goody. But why don't we use this same idea in the enterprise for adopting enterprise social tools?

I find that for some people, they just want to create a community because their peer has one (the me too syndrome).  Others have good intentions but don't know where to even start to build a vibrant community. In both situations, neither have defined what expectations they have for their community. In both situations, instead of just allowing them to create the community and have it fail, the requester needs to clearly understand their goals so they can use the technology to meet their goals.

So, step 1: get the requester to define their hopes and dreams for the community they want to build.  Have them define how do they see the community working. Have them, articulate what their goals are for the community.  Work with them to design how the community will work. The key to the success, is to get them to set their own expectations for the community and then have them work to have their community meet that expectation.  

While setting expectations are great for the community, one of the keys to ensuring the community is as vibrant as desired, the community manager must communicate what expectations they have for the community to the community. In addition, as the community grows, the community manager must influence the community to meet those expectations, while being willing to reset their expectations and adapt to how the community grows.  

Setting expectations are crucial, being influential and flexible is equally important.  But then again, isn't that the recipe for success in almost all situations?








New Dogs, New Tricks

Photo by Eric Ziegler
I read a quote recently in Harold Jarche's post, "Old dog, new tricks"t .  What caught my eye first was the quote from Euan Semple's blog post, "Old folks and shiny things". Euan states: 
Senior folks have seen technology hucksterism too many times before to fall for hard sell, but equally more and more of them are becoming aware that, partly thanks to the internet, things are changing as never before. They know that they need to get their heads around what is happening – even if they decide that active engagement in it isn’t right for them or their organisations. – Euan Semple
Of course I kept on reading, intrigued on where Harold was going. Harold follows up the quote from Euan with his own example.
After a presentation to the Conference Board of Canada’s HR Executives Forum, a senior VP told me that there was no way some kid was going to advise him on social media. However, he was was willing to listen to me, as I was in my fifties, seemed to understand his situation, and didn’t make him feel uncomfortable. I think there is a great need to teach old dogs new tricks, especially senior managers and executives – my generation.
What I find so interesting is that in some recent experiences, I have found that the 30 and younger crowd is sometimes equally hesitant to use some of the latest tools, especially within the enterprise. In addition, I have found that the 40's and older group is quickly picking up these tools and using them effectively.  
As I encounter these reverse stereotypes, the question that I continue to ask is, no matter who the person is, where they come from, what their position is in the company, and what type of job they do, how do we help them turn the corner to realizing the power of social in the enterprise?







The 1 v. 9 Rule

change management,1 v 9,
Gettysburg Battle Field Monument
Photo by Eric Ziegler
Have you ever implemented a technology for an enterprise that had the chicken and egg syndrome?  You know the type.  You implement a valuable technology but no one is using the technology. As you analyze why this might happen, you realize that you need people to use the tool, but the value is not there until you have a large number of people using the tool.  Which should come first?  The people or the tool?  How do you get people to change behavior, adopt a tool, adapt the way they work when you realize that to really have change, you need a large number of people to change almost all at once?

I have seen this situation more than once. You have a small set of people dispersed throughout the enterprise that is interested in the technology. You think you have won the battle because interest is high from these advocates.  But if you peel away the edges, you would see that while they are excited and are some of the biggest advocates for the technology and while they each represent a team that could use the technology to great effectiveness and the technology has potential to realize get value within the team, there is an issue. 

This is a big issue.  The rest of the team is not aware of the value, they don't see the need for the tool and they provide every excuse under the sun for why not to use the tool. I like to call this the 1 vs 9 rule.  You have one person that is ready and eager to adopt, adapt, and use the technology but you have 9 people (2 through 10) that are not.  More often than not, this is one of the biggest reasons a technology like this fails.  It is not about the implementation of the technology, it is about the change management.

As the person in charge of the technology and responsible for enterprise adoption and change management related to the technology, what do you do?  This is not a time to give up and fail.  What techniques could you use to get #2 through #10 to adopt the tool along side of #1.  

Here are some ideas.
  1. You are not alone:  Seems simple enough but this is often the first step that people forget.  You need to get the advocates, the 1's, to help in driving the adoption of their team. One team at a time. While you are responsible for change management and adoption, you are not alone.  The #1's need to know what is expected of them and need to know that it will not be easy.  
  2. Build a play book: Now that you have set the expectation you need to provide the techniques and tools that the #1s will use to get 2 through 10 engaged. Depending on the technology being implemented, these tips and techniques could include having them set expectations to the team, have them get their own advocates within the team, and have them remind (nag or ankle bite) the team periodically.
  3. Lower management:  Work with the first line of management of that team. Get them to understand where the value is and then get them to help drive adoption within the team.  Have them set expectations for their team, but don't let them mandate, that type of technique could backfire.  Do this in conjunction with the advocate of the technology. They can help sell the story.
The hope is that you can do this over and over again with each group until you have critical mass in the enterprise using the technology effectively. Think of the first group as the keystone, that the rest can use as an example or template of how to drive adoption in their teams.

While I write these words into this blog, I know that I have not done justice to all of the ideas others have used to drive adoption of 2 through 10.  What techniques, tricks, and methods do you use to drive this type of adoption?  What has worked for you?

Winning

Gettysburg Day 1 Battlefield
Photo by Eric Ziegler
The question that I have heard several times is, how do I know that I am successful, or asked in a different way, how do you know that you have won? This question is particularly intriguing to me.  If you only look at the surface, the answer can appear quite easy to answer.  I win when I beat the other team.  I win when I am faster than other people.  I win when I have completed the task that was requested of me. But if you dig deeper than just giving a surface level answer, you can learn much more about yourself and learn more about what drives you.

I work in IT and provide tools and technologies to the entire enterprise.  I am responsible for delivering these tools and technologies to people in the globally.  At the surface, I can declare success or that I have won by stating that I implemented the technology and tool.  But that is much too easy of an answer, and while I could be happy, in the long run, I know that if I just deliver the tools and technologies I really have not won, and I am not as happy as I could be.

Success in my job is about delivering the tools and technologies but is much deeper than that. It includes helping people learn how to use the tools and technologies to enhance how they do their job.  I am successful when I am able to talk with business areas, listen to what they do today and provide ideas on how they could use a technology to improve how they work.  I am successful when a business area uses the technology and incorporates it into their business processes.   I win when a business area uses a technology and they are much more effective in working with each other and their customers / clients.

The definition of success changes with each implementation.  A win from implementing one tool looks completely different than a win when implementing another technology.  The one constant between each implementation? Success is much deeper than just what is at the surface.  Success and winning only really occurs when you have thought through why you are doing the implementation.  If success is defined without the full picture, than almost guaranteed something is being left on the table and a win didn't actually occur. 

How do you define success?  What does winning look like to you?






Perceived Value

perceived value
Image: from Tim Scullin blog
The other day I was in Disney with my family.  It was great fun, we did almost all of our favorite rides, Haunted Mansion, Thunder Mountain, Pirate's of the Carribean.   Unfortunately we missed out on going on Splash Mountain as it barely got to 60 degrees and we were not brave enough to risk getting wet and being cold.

What I found so interesting as we walked around the park is how quickly some of the lines grew (of course spring break has that effect).  The thing that was so interesting was that they were not the rides that I would have chosen - which was great for us. That got me to asking the question, why do some rides have longer lines faster than other lines.  I believe that one of the reasons is that every person places their own value on each ride.  Some people valued the rides like Winnie the Pooh, while others valued Haunted Mansion, some liked Dumbo while others valued Thunder Mountain.  Each person places their own value on each ride and decides which ones they want to ride first, which rides they are most willing to wait in a long line for, and which rides they just won't ride that day.

This got me to thinking about how employees adopt different technologies, tools and techniques based on the value they perceive they will provide.  For example, I can apply this to the work that I am doing related to driving adoption of activity streams (btw, this is just one example of a large variety of technologies).  As I talk with employees about how they might use an activity stream, some say that it seems just like email and they wonder (aloud sometimes) what value the activity stream provides beyond email.   Some employees never see any value in using an activity stream.  Some know that moving away from email is valuable in some situations, but don't know if the activity stream is the best method.  Some believe a RSS feed aggregator or other technologies are better. Others, thankfully, understand the value right away, but when they start to use the new tool, they find that no one else is using it, which diminishes the value for this individual.

So how do you get people to use the new technology, the new tool, or technique?   There are many ways, and you need to use them all.  Going back to Disney, they use many different methods to entice you to ride their rides (and even to come to Disney World). One of their methods is to nudge people to ride the next ride.  Enterprise can use similar techniques to attract employees to use the new "stuff".

When a nudge is provided, typically the goal is to increase the value that the employees sees in the new tool, or technique or technology.  Or said a different way, the employee's perceived value of the tool needs to increase.  Disney World uses many techniques to nudge people to ride each of their rides.  Most Disney World rides use great visual effects on the outside of the ride.   For example, as you walk into the Haunted Mansion, the people are in character, giving you the "eye" and the line leading into the ride has grave stones with funny things written on them and book shelves that have books that move in and out.   They attract you to the ride using over the top decorations such as the carriage with a ghost horse.

Following the Disney World example, enterprises need to use techniques to get employee to change and use the new "stuff".  To drive this the employee perceived value of that tool, technique or technology must increase. If that does not happen, they won't ever use the new "stuff".  Unfortunately, as you have probably guessed, this is the most difficult part of driving adoption of technology, but it is also the most rewarding.