Posts Tagged ‘Social Networks’

12TipsForSuccessfulESNOver the past several weeks I’ve written a dozen blog posts, each centering around one tip for building a successful enterprise social network (ESN). This post is a simple listing of the links to those 12 posts. I’m sure I’ll revisit the subject and make modifications from time to time. For now, though, these represent the most important tips I would offer to those seeking to have a successful experience in starting or improving an ESN.

I hope you enjoy and benefit from them. I would love to hear your feedback via comments on any of the tips.

Tip12ForSuccessfulESNIn this final post in my series on building a successful enterprise social network (ESN), I draw on my learning background and goal orientation. That said, tip #12 is:

Never be satisfied – keep growing.

This is true in a variety of areas for someone who has responsibility for a company’s ESN.

First, let’s consider the area of technology.

No platform is perfect. We’re in better shape in 2014 than several years ago in the capabilities of software and in our understanding of what is possible and wise technologically. Still, community managers and others responsible for an ESN must always be on the lookout for big and little changes in the platform that help the company accomplish its objectives better and that can also improve the user experience. Work with the platform vendor as needed to suggest changes. Give your users an easy way to suggest changes that you then vet and perhaps pass on to the vendor.

If you did your homework well when selecting an ESN platform, you should be able to stay with it for a long while to come, but keep pushing for improvements. A vendor who rarely provides updates will not meet an innovative company’s needs for long. If you decide that there is no alternative but to change platforms, do so, but understand that there is great pain that accompanies such a drastic change. Only change platforms if there are overwhelming business reasons for doing so. Likewise, don’t stay locked in to a platform and vendor that refuses to evolve.

The user experience is another significant area you should always strive to improve. This is, of course, related to the technology improvements mentioned above, but it isn’t limited to that category. Identify those who have a knack for seeing and using the software from the viewpoint of a new user or another particular audience and take seriously their feedback. Listen to what is said repeatedly over time about negative aspects of the user experience and address those issues. Most workers don’t have the luxury of a lot of extra time on their hands, so be diligent – even aggressive – about championing changes that improve the user experience so that they will enjoy it and want to return. One of the great things about an ESN is that you usually don’t have to go out of your way to solicit opinions or to get volunteers for some user experience initiative. You’ll probably find a large, willing group of volunteers eager to help in response to a simple post on the platform.

A third area worthy of continuous effort at improvement is that of deeper integration of ESN use – both in its physical presence across various platforms as well as in the day-to-day processes and work flow that guides so much work that happens routinely. As was suggested in an earlier post in the series, the most successful ESN will not be the one that is its own separate destination apart from the tools and processes where people normally do their work; it will be the one easily accessed in the tools people use and in the normal workflow of how that work gets done.

Lastly, be sure to grow as an individual along the way. Make use of internal and external resources to continuously expand your knowledge and grow professionally. I cannot imagine a life without continuous learning. I have several go-to resources for learning about ESNs in particular or social media in general. For example, I’m a big fan of Rich Millington and his advice given at I also have memberships in the professional organizations The Community Roundtable and I will be blatantly biased, though, and say that my favorite ESN resource is the weekly Twitter chat I host – #ESNchat! With a different topic each week, many knowledgeable professionals contributing to the discussion weekly, and archives of that great content going back to September 2013, you will find a wealth of existing info and a tremendous opportunity for continuous learning weekly by taking part in the chat. Use the ESNchat menu at the top of this page to explore more and then join us each Thursday afternoon from 2-3pm Eastern time on Twitter by following and using the tag #ESNchat.

We don’t stop learning once we’re out of school or just because we’re no longer pursuing formal degrees or certifications. We continue to learn because we’re built that way as human beings. To quote a few lines from the children’s musical Education Rocks:

Never stop learning. Never stop growing.
Never stop seeking the brightest star.
Never stop moving from where you are.
Never stop trying. Never stop reaching.
Never stop doing what you can do.
Never stop growing your whole life through.

If we possess that attitude about learning and growing and constantly improving ourselves, I suspect that will translate into the same intention to continuously improve the areas of our work for which we have responsibility – ESNs or otherwise.

Tip #12 is Never be satisfied – keep growing.


See the following posts for previous tips in this series:

Tip10ForSuccessfulESNAfter sharing nine previous tips on building a successful enterprise social network (ESN), we come to a subject that has been near and dear to my heart for decades – training and learning. I was a professional educator/trainer for over 30 years before switching gears in 2009 to a different path. I am confident and very experienced, therefore, in the subject matter of this post.

For the first nine ESN tips, see the links at the bottom of this post. For now, let’s concentrate on tip #10:

Train, train, train.

Helping users become familiar and comfortable with the use of your ESN can take place from a number of angles. Let’s consider a few…

1. Train new employees. There is no better way to introduce new employees to your company and its culture than to encourage them to dive into the ESN. It is where they will learn the most about the company from unfiltered and unsanitized sources. Tell them in orientation sessions and documentation about the ESN and make sure they know how to establish an account and access it. HR should have a role in this, but so should the teams that welcome their new employees.

2. Welcome new account holders and give them a next step. Every day I send a welcome email to those who have established an account on our ESN in the past day, giving them a little info about it, why we have an ESN, and a few of the major links they should know about. I make sure in the email that I give them one specific call to action to take the next step. For me, that’s clicking a link to take them to a group I lead on the ESN for newbies – a place where they can ask their newbie questions and play around without any fear of doing something they think will embarrass them. It’s important to get new users to do something and not just start lurking so that they more quickly participate and become an active part of the community. The more quickly you can get them to post a message or comment or complete profile data, the better.

3. Train for various roles. Consider the major categories of people who will use your ESN, why they are motivated to use it, and then prepare helpful material and live sessions to help those audiences succeed in their ESN use. For example, I hold monthly training sessions for several groups of people: those who serve as group admins, those who use it for project management, those using it for idea challenges, and those using it for dated/timed town halls. I’ve also held occasional sessions with leaders in groups or one-on-one to discuss how they can benefit themselves and those who report to them through effective use. Particular business areas would do well to train their people on ways specific to their areas and how use can benefit their work processes and outcomes. A combo of live sessions and readily available documentation is needed here.

4. Train for different levels of expertise. As long as people continue to come and go from your company, you’ll have an ongoing need to train newbies in the tool, both in the “why” and the “how.” Introductory training shouldn’t attempt to cover everything because that’s too overwhelming. Break up the subject matter into reasonable chunks than people can digest before moving on to more advanced uses when they are ready. A good community manager will want to replicate himself/herself as many times over in the enterprise as possible, so building the community management skills of your greatest users, advocates and enthusiasts will help scale growth far more effectively than hoarding the leadership role by oneself.

5. Use a variety of methods. We have readily available for our ESN users quick reference sheets, longer documentation, short videos, recordings of longer training webinars, live virtual sessions once or twice a week, one-to-one mentoring as needed, tips included in weekly broadcasts sent to all users, instructor-led classroom sessions upon request, booths at major events, and of course many eyes looking at questions asked on the ESN throughout the day to answer random questions posed by users. People don’t magically know how to use your ESN just because you made it available or because you did one or two things once upon a time to train them. The need is ongoing and people have different preferences for how they learn. Recognize that fact and attempt to meet the need from whatever angle the user may approach whenever they may be ready. And don’t get discouraged when, after all your attempts, you occasionally hear someone say “It’s too hard to use” to “I don’t know how to .” After four years, 35,000+ users, over a million ESN posts and countless training opportunities, I still hear comments like those every month without fail.

6. Publish a calendar of live training and links to on-demand resources. I always have the next few weeks’ live training calendar prominently displayed on our ESN home page right above a number of additional clearly labeled links to on-demand resources. I record and keep links in that same place to the most recent live webinars so anyone can view at their leisure any of the training we do. I publish in a weekly broadcast details of the training opportunities scheduled for the next week. I post details in an ESN broadcast message about each and every training session as soon as it is scheduled. For those sessions, I make attendance as easy as possible by not requiring anyone to register in advance and by intentionally not using the company’s learning management system (LMS) to host or track completions.

7. Be an advocate for informal, social learning over formal. Formal learning teams in many companies – especially large companies – still tend to think they need to control access to learning behind an LMS. I don’t know if that’s in part to be able to justify their existence by documenting how many completions they see, or through unnecessarily extending the corporate need to track some learning (such as annual compliance training) to all learning. Regardless, I just want people to learn and to be able to do so in the easiest manner possible with as few barriers as possible between them and the information they seek. The sooner companies jump on board the informal, social learning bandwagon to develop the knowledge and skills of their users, the better off everyone will be. As far as I’m concerned, learning management systems can die today and the world will be a better place because of it. Long live informal, social learning! It’s how most learning happens, anyway, and it always has been. Just ask any caveman.

So there you have my take on some considerations regarding the ongoing need for your people to know why and how to use your ESN. Be versatile. Accommodate user preferences for style, time commitment and specific needs based on role or current expertise. Always look for gaps in knowledge and be creative in finding ways to fill those gaps.

Never forget tip #10: Train, train, train.


See the following posts for previous tips in this series:

Tip9ForSuccessfulESNIt’s time for tip #9 in my 12-part series on my best advice for building a successful enterprise social network (ESN). This one is related to tip #8 which is “Integrate your ESN where people do their work.” However, that tip focused on the applications and workflow to which people are accustomed. This tip is more about a combo of the behind-the-scenes ease of access as well as the mobility of it. Tips 1-8 are listed at the bottom of this post. Here is tip #9:

Make it easy to access.

Of course the integration into other apps discussed in tip #8 is an important part of making the ESN easy to access, but here I want to mention a couple of other specifics that aren’t related to particular applications people may use.

First, ease of access is affected by the simplicity of the login process. Assuming workers have to log in to their work environment, there is really no good excuse for making them continue to log in to additional work-related destinations throughout the day. Few things irritate employees more than having to spend time logging in again and again throughout the day into various systems and applications – especially when nearly all of them are securely behind the company’s firewall in the first place. Such additional logins are considered a gross waste of time.

Therefore, go through whatever effort is required to implement single sign-on processes between your ESN and other internal systems. Work with vendors as needed to do so. If you have not yet decided on an ESN for your company, save yourself some pain and eliminate from consideration those that do not allow for signing in to their product by virtue of a single sign-on process which knows and uses the person’s network or other defined credentials. If the ESN is to be used throughout the enterprise, embedded into numerous systems for the sake of access and workflow, then you must eliminate the burdensome hassle of requiring the user to log in multiple times and places in order to use the ESN.

Another major means of making the ESN easy to access is to enable mobile access from the user’s personal and work-issued mobile devices. I realize that there are many types of businesses that are hesitant to enable mobile access to internal resources as a matter of protecting information, but with an increasingly mobile workforce, it is unreasonable to work in 2014 by 20th century practices and standards. Do you want your executives or other workers who are always on the go to be a part of your ESN? (You should – see tip #3.) Then you must have mobile access to your ESN. Do you want to take advantage of flexible work hours and locations expected by today’s workforce? Then meet their expectation that they will be able to get to the resources they need to do their work on the personal devices they carry with them at all times.

Many companies have the luxury of less stringent rules and laws protecting data, and those types of businesses may have a hard time understanding why other companies don’t just open things up and let their people work anytime, anywhere on devices of their choice. But for those of us in highly regulated industries, we know that it’s no small decision or process to enable mobile access to data. That means you’ll have to bring together people from the right business areas, IT, legal and elsewhere to make sure constraints are known and reasonable compromises are made in order to reach the necessary outcome of mobile access. It may take a while to implement, but it can be done securely and in a manner that maintains a good user experience. Anyone who claims otherwise just isn’t willing to see anyone’s view but their own.

So tip #9 is really an extension of tip #8. Making ESN access easy combines the integration of tip #8 with additional access issues of tip #9 such as reducing logins via single sign-on and especially allowing mobile access on personal as well as business-issued devices.

Tip #9 is Make it easy to access.


See the following posts for previous tips in this series:

Tip8ForSuccessfulESNThis is part 8 of a 12-part series on tips for building a successful enterprise social network (ESN) at your business. Links to the previous 7 tips are at the bottom of this post.

Tip #8 is an extremely important one if your ESN is to really make a difference in how your company gets work done. Here’s the tip:

Integrate your ESN where people do their work.

There are two aspects of this integration to consider – (1) integration into the software and tools people use daily in their work, and (2) integration into the processes by which that work occurs. First, let’s consider integration into other software and tools.

It’s likely that most workers in businesses prior to the launch of an ESN have established places online where work happens – software applications, email inboxes, intranet resources and more that they switch between during the course of the day to perform their various tasks. If an ESN is introduced as a completely separate destination which they must go to outside the workflow to which they are accustomed, then there is likely little motivation – much less need – to go there. If I can still accomplish everything that is expected of me at a level of proficiency acceptable to my manager and myself without using the ESN, then why should I bother unless there are other non-work advantages to going to that destination?

If an ESN is being sold, for example, on its merits of improving communication or simplifying processes, then it needs to be readily available where I’m doing my work and not something that takes me away from my primary applications in order to use it effectively. That is why it’s vital to integrate the ESN into places like the intranet landing page that users see multiple times daily, or into those internal sites where teams store documents and manage lists throughout the day (such as SharePoint), or embedded into other specific applications where ESN communication can serve a purpose like user assistance or approval processes, or even integrated into the long list of email inbox folders for those still holding on to the inbox and the way of managing their work.

At my company, we currently have over 200 integrations of our ESN into other sites and tools where people do their work. It is deeply embedded into our intranet landing page – a giant leap forward in ESN exposure which doubled the rate of growth that existed prior to that integration. Every article on the intranet has a corresponding discussion thread in the ESN along with icons to like or comment on the article from the intranet home page. A recent question by our CEO in one of those articles resulted in over 100 comments in the corresponding ESN discussion within a day. The link to the ESN main application is the very first work-related site link on the Intranet home menu. In addition, we have over 200 SharePoint sites that have embedded discussion streams from the ESN, mostly tied to particular interest groups created on the ESN, although sometimes based on hashtags used or the posts of specific people. We have two other major web-based internal applications used by thousands that embed the relevant user group ESN stream into those products so that users can ask their questions and get live assistance directly from within those applications. Anyone who wishes to have their ESN groups and streams embedded into their email inbox folders can also open a help desk ticket and get that added (although I don’t push that since I think we’re too email dominated in our environment as it is).

The point is that you don’t want use of the ESN to be available only as another destination, although many companies (mine included) will still see the bulk of their activity from those separate ESN web apps. So the first and a very important aspect of integration which must be planned and continuously executed and improved upon is embedding those discussions into where people are already doing their work daily.

The second aspect of integration has to do with processes. This is where we change our ways of working to intentionally use the ESN in processes in place of previous ways of doing things. For example, instead of those ungodly reply-all email chains that clog up inboxes, are hard to find when you need them, and waste the time of so many who don’t need to be on the recipient list, why not post the question or discussion topic on the ESN? That way you can share the discussion link with stakeholders so they can participate in the discussion if they wish, and then you have at most one email that goes out – none if you do the notification solely via the ESN. Those who want to participate in the discussion can do so without clogging up the inbox of others not interested.

For another example, consider the various approval processes that occur with different work tasks. How complicated do those tend to be? How many tools are involved? How many emails are involved? Why not have a simple discussion in an ESN – private if it must be – where stakeholders can easily discuss and document their approval without unnecessarily complex, time-consuming sequences taking place elsewhere?

Of course, ESNs are a natural for leaders who are progressive, open, transparent, and who want to lead their people to be aligned around a common purpose, values and strategy, engaging in two-way conversation regularly with employees at all levels of the organization. You can’t do that reasonably via email or top-down, controlled communications. You can only accomplish that in live, in-person settings or the online equivalent of those via ESNs, virtual town halls, etc. Leaders who make good use of an ESN to change the tone and process of communication will have a strong, lasting impact on the satisfaction of employees and their consequent success together as a team.

If you have not yet invested in an ESN solution with a vendor, then make sure any solution you consider provides flexible ways of being integrated into many other kinds of applications where people do their work. It will be critical for adoption and for making the ESN pervasive throughout the organization. Always keep working to find more places, more business areas, more tools and applications where the ESN can be embedded so that its use becomes an expected, normal part of daily work life.

In terms of processes, keep your eye out for opportunities to improve the way work happens by changing archaic, complex, confusing, time-consuming processes into simpler discussions that happen in one easily accessed place via the ESN. Don’t just tack on the ESN to existing ways of working. Take advantage of its functionality to replace and improve the way work happens.

Unlike some of the other tips in this series, tip #8 is one you will continuously need to have in mind and work toward. You will never completely arrive and be done with this process. There will always be room for improvement, but being the advocate and change agent around this effort at integration will leave a significant mark on the organization as work is accomplished by people throughout the company more efficiently and effectively.

Tip #8 is Integrate your ESN where people do their work.


See the following posts for previous tips in this series: