BT 2.0 case study (12/11/07)
(I wrote the below article as a case study of BT’s experiences to date with the adoption of social media tools – it was published in the November 07 edition of Employee Engagement Today magazine)
Taking the ‘social’ out of social media
The power of social software is undeniable in the free, anarchic world of the global internet. But what happens when you bring these tools into the constrained, policy-driven, risk-averse world of the corporate intranet where the user population is small, where expressing oneself as an individual and on a personal level can feel threatening, and where management is watching your every move? Well, that’s just what one of the world’s leading providers of communications solutions, BT, has chosen to do. Richard Dennison, BT’s Internal Programme Manager, tells the story.
It was inevitable that the unprecedented and explosive growth of social media tools on the internet would eventually start to seep through firewalls onto corporate intranets. However, reading the increasingly negative stories in the media about employees ‘wasting time’ on social media sites such as Facebook, one could be forgiven for thinking that they are an evil to be resisted at all costs, transforming focussed and highly productive employees into a morass of lazy, good-for-nothings who spend their days competing with one another to collect the most cyber-friends. At BT, we take a different view.
While some companies begin the impossible task of shutting out social media tools, at BT we have just completed a web ‘liberalisation’ project to make sure all our employees can access social media sites. Why? Because we see social media tools as a huge opportunity to transform the way our employees interact with each other, with ‘the company’, and with our customers, partners and suppliers. When over 4,000 of your employees voluntarily join a Facebook group called ‘BT’, it’s time to take note.
Winning over the policy makers
Having taken the ‘philosophical’ decision that we should use these tools internally and externally, the first step was to persuade the HR, security and legal policy makers that we weren’t about to open a can of worms for them. That’s where we made our first mistake. Initially, caught up in the hype surrounding these tools, we began shouting from the rooftops that the world was about to change, that these new tools would effect a seismic shift in everything we did. Unsurprisingly, the policy makers ran a mile! Being the people in the business who are often left to pick up the pieces, HR, legal and security policy makers are understandably cautious.
Having calmed ourselves, we took a different and probably more realistic approach. In reality, these tools are not actually ‘new’. They are, in essence, simple content management systems. What makes them different from their predecessors is that they are intuitive, simple, offer no technical barriers to participation, reflect social behaviour rather than try to distort it, and crucially have become incredibly fashionable.
So, we went back to the policy makers and explained this more clear-headed perspective on what we wanted to do. Together we looked through our existing policies around use and abuse of the internet and intranet and found that the use of these tools was actually pretty well covered by existing policies already. This went a long way to confirming our suspicions that these tools were not as new as the hype suggested and gave the policy people much more confidence. The final reassurance was that we agreed that all tools that allowed user-generated content would be behind our single-sign-on application to prevent any anonymous publishing. The ethos we would engender was one of allowing BT people to say anything they want, in the knowledge that they would be held accountable for what they say.
The final policy hurdle was persuading the BT Communications Council, made up of the directors of internal and external communications from around the business, that letting BT people say what they want internally and externally was a good idea. In August 2006, approval was given for all internal activity, but the main stumbling block was whether or not to let BT people blog externally about the company and their work. Initially, the proposal was rejected outright. We agreed to a nine-point action plan that involved things like: reviewing who in BT was already blogging; what the blogosphere had to say about BT; and what peer organisations were doing.
In January 2007, we returned to the Communications Council with our findings and the external blogging proposal received a warmer reception. The balance was finally tipped by Ben Verwaayan, BT’s chief executive, who expressed publicly his support for the more liberal approach. The policy was approved.
Introducing the technology
In parallel with negotiations around policy, we released some pilot social media tools quietly on the intranet. We didn’t publicise their existence but let people find them and the news of their presence spread virally. The tools were based on a single platform, called JotBox, which was cheap to buy and easy to customise. Our view was that these tools would take off or wither away based on how useful they were to BT people. Whatever the outcome, we would have succeeded or failed quickly and cheaply.
The tools we launched initially were an enterprise-wide wiki called BTpedia (see figure 1), based on the concept of Wikipedia, which allows any BT person to publish articles or edit articles published by others. We also launched a blogging tool. Both were well received and within a matter of weeks we had several hundred articles in BTpedia and around 300 blogs.
Figure 1 – BTpedia
However, the ‘killer application’ was a social networking tool we called ‘MyPages’. MyPages (see figure 2) provided every BT person with a place on the intranet to call their own. In it they could: create web pages and allow others to edit them (wiki pages); set up photo sharing pages and file stores; set up wiki calendars; create as many blogs as they wished; and connect themselves with other people in the organisation through ‘friends’ type functionality. The fact that individuals could manage all this functionality through a single ‘portal’ was incredibly powerful and sent adoption rates through the roof. With only viral marketing, within a couple of weeks over 1,500 people had activated their MyPages. Activity and traffic on this tool was so heavy that it sent the JotBox into meltdown and all our social media services disappeared overnight!
Figure 2 – MyPages
Technology in a twist
It’s ironic that the thing that social media is best known for, namely simple and cheap technology, is the one thing that we have struggled with most. We had to switch off MyPages to keep BTpedia and the blogging tool open. The company that created the JotBox was bought by Google, who announced they would no longer offer it in the way in which we were using it, effectively making it a legacy product overnight. And, because the JotBox was brought into BT ‘under the wire’ without following correct IT procedures, we couldn’t buy the extended capacity we needed to keep it going on a sustainable basis.
For the last six months we have been through a process known in social media circles as: ‘throwing technology at the wall to see what sticks’! A significant change in policy by our IT department to embrace OpenSource technologies threw open the flood gates of technology options open to us. Consequently, we will be migrating information off the JotBox into a number of different tools ranging from WordPress, Mediawiki, and Confluence to SharePoint 2007 over the coming months.
It seems inevitable that there will always be a degree of friction between the need for robust IT processes to safeguard customer and business data and to effectively manage IT spending in a global corporation like BT, with the need for technical agility and to support the concept of the perpetual beta in which you try out quickly and cheaply often competing technologies and let users iterate and adopt as they see fit – ultimately, letting the users write the business case for adopting a particular option. Trying to reconcile these often competing needs is a tricky and ongoing process within BT.
Impact on corporate environment
So what impact has the introduction of these tools had on our intranet? The impact has been significant in some areas, subtle in others and in some cases has had no impact at all. Some of the major changes are outlined below.
Our internal communications consultants have had to accept that in some cases they will have to relinquish control of messages which become subject to community ownership and community editorial control. They are also increasingly having to conduct their business in channels they don’t own and cannot control, such as employee blogs. Communications is becoming a ‘conversation’ rather than a managed activity which requires a different type of engagement by those traditionally responsible for communications activity.
Intranet responsibilities are subtly shifting between those responsible for intranet management and intranet users (see figure 3). For example, six months ago information retention policy was a relatively simple policy to enforce. Content was owned by individuals and those individuals were responsible for managing that content through its lifecycle. Today, more and more content is produced and owned collaboratively. With no clear ownership, who manages a piece of community-owned content through its lifecycle and ensures it is deleted or archived appropriately? In addition, what information governance model do you apply to organic, user-generated content.
Figure 3 – Responsibilities on a social media enabled intranet
Information consumption behaviours on the intranet are changing too. With increasing amounts of unstructured user-generated content appearing in disparate channels on the intranet, the challenge for users in finding and extracting value from that content increases exponentially. To help users find and keep up to date with new content, we are using a combination of ‘tagging’, where publishers and users attach key words to content which are then searchable by others, and Really Simple Syndication (RSS), where content is published into appropriate feeds to which users can subscribe for updates via a feed reader client on their PC or via an RSS server. Without RSS, the value of social media content would be very limited indeed. However, this does require both publishers, whose target audience may never actually visit their site but read content in their feed readers, and users, who are used to viewing structured content on the sites upon which it is published, to behave in very different ways.
Perhaps one of the most positive impacts has been in the area of accountability. Management and communications teams are having to be much more end user focussed as the employee channels provide a perfect platform to hold them accountable for what they say. Contrary to popular opinion, these channels are being used in a constructive and positive way. To date, BT people have responded responsibly to being trusted with channels into which they can publish anything they like. By and large, BT people enjoy their jobs and are not prone to throwing them away gratuitously for the sake of it!
We’ve learnt a lot on the bumpy social media ride to date and have bruises and accolades in equal measure to prove it. A key lesson is to focus on the value social media tools can deliver rather than the risks. If you dwell too much on the risks, you’ll never leave the starting gates. There are risks, but the potential benefits are huge. Many believe that trying to stop social media tools seeping onto intranets is a futile activity anyway, so it is better to introduce them on your terms in a managed way.
Our experience suggests that it is better to start small with simple and cheap tools with limited functionality. Let users dictate the direction and speed of adoption. Allow users to dictate how they are going to derive value from new tools and don’t be afraid to shut down applications that are withering on the vine. Let users play with new tools as soon as possible, warts and all. We positioned all our social media tools are ‘beta’ applications when they were first released to set the right user expectations.
Engage the policy makers as early as possible. Emphasise that these tools represent an evolution rather than a revolution in the use of the web. After all, it’s just another form of content management.
Finally, have realistic expectations about what you can achieve – the intranet and the internet are different beasts. Much of what makes social media successful on the internet does not directly translate to the corporate environment. For example, a cornerstone of social media on the internet is the concept of the ‘wisdom of crowds’ – i.e. if you have a large enough body of people collaborating on a single topic, you will distil the ‘truth’ from them. Does the wisdom of crowds work with a smaller population of people, or will the result be unbalanced opinion rather than ‘truth’?
The demand for social media tools by employees to support their work is growing apace. While it is too early to measure the impact of introducing these tools into a corporate environment, our experience to date has been very positive.
As well as meeting the needs of today’s workforce, we are mindful of the needs of those entering the workforce over the coming years – so called Generation Y – for whom this technology is second nature and an important part of how they interact and manage their time. The extent to which a company adopts user generated tools is bound to become a barometer of company culture for those looking for suitable employment in the future.