• All Posts
  • Application Development
  • Customer Success
  • Enterprise 2.0
  • News & Events
  • Product Updates
  • Tips & Tricks
  • October 2010

    Transparency, Access and Focus: Getting the Most From Enterprise Social Software

    I recently had a series of conversations with customers to get their input on some upcoming capabilities. The conversations included a variety of stakeholders and participants in each organization. Each conversation triggered thoughtful reflection and lively debate among participants about how their organization should use social software for the right mix of transparency, focus, and security.

    I’ll tell the story, do some analysis, and talk about what it means for how your organization can get the most out of Enterprise 2.0.

    South Australia Office of the Premier

    At the South Australian Department of the Premier and Cabinet, the discussion was about whether to hold conversations among a larger group, or within smaller enclaves. They use Socialtext Signals heavily for Q&A to tap into the expertise of a broad range of employees and to share resources that are valuable across the organization.

    Several managers advocated in favor of holding and keeping the conversations in smaller groups, while others pushed for more enterprise wide discussions. A member of the risk management group raised concerns about security. A project manager gave a counter-example, talking about value she sees in asking questions and getting answers from the larger group.

    Eventually, the manager weighed in. He said that the goal they were striving for in their use of social software was increased transparency. Part of the goal was to move the culture toward greater openness and transparency. Sure, there is the possibility that someone might make a mistake. But people use email every day and make decisions about what information to share with whom. It’s better to share the goals and trust people’s judgement.

    Getty Images

    At Getty Images, the conversation took the opposite direction. Getty Images is a major distributor of digital images and stock photography. They are using Socialtext broadly among their sales, marketing and service professionals.

    At Getty Images, people are using Signals to ask questions about the broad range of products and services the company offers. They are also using it to promote new campaigns, share reports and good news. A sales manager boasted that “we rocked the Emmies last night.” But people were starting to feel like the discussion in the larger group was too much information. At Getty Images, they are starting to steer people to hold some discussions in smaller groups. The reason is not security, but to improve signal to noise.

    Also, the Getty Images team is finding that brand new users sometimes share things that other people find to be irrelevant and trivial right when they get started. But then they see what others do, and learn from others’ practices, and adapt to the norms of sharing what people feel is relevant.

    GT Nexus

    GT Nexus is a company that makes software for the shipping and transportation industry. At GT Nexus, there was a lively debate among representatives of IT, engineering, product management, design and customer support about the need to share enterprise wide versus in smaller groups. On one hand, some product management and design team members were collaborating in private groups. Meanwhile, an engineering manager was encouraging them to post more publicly across groups.

    The debate didn’t conclude during that meeting. But GT Nexus will be able to use self-join groups and workspaces where they can collaborate in smaller groups without disturbing others, while valuable information is still being to others via browsing and search.

    Analysis and recommendations

    In all of these situations, the ability to share both broadly and narrowly, more publicly and more privately, set up a lively internal discussion about how broadly and narrowly to share different sorts of things. Each organization needed to think through its own culture and information needs, and come up with guidelines and heuristics about what to share with whom. Also in all of these cases, adoption timeline comes into play. People’s initial impulse is to share “too much” or “too little”, and the adoption process is about settling on the norms and accommodating people’s behavior to these norms.

    Overall, the value of enterprise social software comes from increasing transparency, so that more people in the organization have access to the people and information they need. Transparency is tempered by two different factors – the need for security, and the need for focus. If too much information broadly shared, and too much is said out loud, everyone drowns in the noise.

    Enterprise social software needs to enable organizations to manage, focus, and access along both of these axes:

    1. Security is provided through private groups that are visible to members only
    2. Focus is provided by small groups where activity can be easily discovered, and interested parties can join

    It is business decisions and cultures, not features, that enable organizations to gain the benefits of appropriate transparency and access. People need to decide, and develop shared culture, about when to share and ask publicly, and when to refrain from distracting their colleagues. Employees need to understand what information must be kept confidential, and what problems would benefit from increased insight and collaboration from a broader audience.

    The implementation of social software catalyzes important conversations and requires important decisions about transparency, access, and focus in your organization. There is no one right answer, and getting it right takes key decisions about what’s right for your organization, and tools that let you tune for your company’s goals.

    Video Interview: General Motors R&D Utilizes Social Software to Drive Product Innovation

    GM has researchers from Asia to Detroit to Palo Alto that have been using Socialtext to share expertise and ideas about what’s going to be next big breakthrough in the automotive industry. Recently, I sat down with John Suh, a staff researcher at GM who has been helping drive the effort. In this video, he breaks down how social software has facilitated more open communication between researchers at GM, and what benefits he’s seeing internally as a result.

    The Social Software Grassroots Myth

    Call me crazy, but I’m going to attack another another social software orthodoxy: the Grassroots Myth.

    The Grassroots Myth is my name for the notion that the most effective way to bring a new social software platform into an enterprise is through bottoms-up, viral introduction.

    There’s something very right about the Grassroots myth, but also something very mistaken.

    Like all good myths, this is based on a heroic legend. The details of the story vary from one company to the next, but the central elements are almost universal. It all begins with a single, junior-level employee. I’ll call him Joe, after Joe the Plumber, the “common man” immortalized by a

    Joe the Plumber, Grassroots Myth Icon Extraordinaire (Credit http://www.flickr.com/photos/38729188@N00/2987725752)

    bizarre moment in John McCain’s presidential campaign. Joe is hard at work on a project or task that requires exchanging lots of ideas and content with colleagues across the organization. Joe sports an iPad and reads Tech Crunch daily. He’s tech-savvy, but doesn’t actually work in the IT department. Late one night it occurs to him that some sort of Facebook-, Wikipedia-, or Twitter-like collaboration tool could really help. So Joe does a little Internet research, finds a cheap or free hosted service, and –Voila!– that very night he is up and running. He posts some content and invites a few colleagues. Then, as the commercial goes, he tells two friends … and they tell two friends, and so on, and so on. Six months later, the whole company has adopted the tools and Joe is a hero.

    It’s a wonderful story: the little guy who transforms his company through the power of a great idea.

    It’s not quite that simple.

    There are certainly Grassroots success stories out there, but they’re the exception not the rule. The more common experience is less rosy. Joe is working on his project, finds and sets up some collaboration software, and invites his colleagues on the project. His colleagues use the software to collaborate, and really like it. They tell a couple friends, but the friends are busy and not as tech-friendly as Joe. They like the concept, but can’t quite visualize it. They ask Joe to show them, but somehow the meeting keeps getting postponed. Joe launches the tool with another project he’s working on, and the same thing happens: the tool works great for the project, but goes no further. Joe demos the collaboration tool for his manager, Jane. Jane loves it and invites Joe to demo for the entire department. A few people ask Joe to set up accounts for them, but after a few days they misplace the login information and never go back. Joe continues to push the tool for his projects, and people continue to like it … as long as Joe is leading the charge. IT gets wind of the project and expresses concern that company data is being hosted externally by an unapproved vendor. Joe gets accepted to Harvard Business School (having impressed the Admissions Committee with his essay on collaboration). Joe leaves, and the company settles back into its (inefficient) email-based collaboration habits.

    What happened to Joe, and why do so many social software innovators cling to his myth in the face of real-world experience?

    I said before that there’s something very right about the Grassroots myth. That’s the content part. What you really want inside the enterprise is what I call “Content Grassroots.” This is distributed content creation from the ground up. This is the community that spontaneously forms around a shared interest in pediatric medicine, the engineering team that decides a wiki workspace is the best place to manage project deliverables, the sales manager who posts a photo in order to show a new demo booth to colleagues in other regions, the virtual conference that attracts hundreds of colleagues to a real-time brainstorming “tweet-up” on improving the customer experience. This is social software in action. This is where Joe really shines.

    A lot of people confuse Content Grassroots with another type of Grassroots effort which is less benign: Technology Grassroots. Sourcing a new technology, platform, tool, or application via the Grassroots is an exercise in confusion and frustration. You end up with multiple solutions, all competing for attention. End users are sent to lots of different destinations, apparently for no good reason. There’s little or no integration with existing applications or data flows. Users don’t know which tools will survive and which will die. IT is concerned about security, performance, and stability. Organizational silos are reinforced, not diminished. Worst of all from a social networks standpoint, the company’s attention is fragmented across multiple tools, each of which struggles to achieve critical mass.

    That’s where our mythical Joe usually fails in reality. When it comes to social software, your technology can’t be driven from the grassroots.

    The most effective way to empower your Content Grassroots activity is to provide a single, unified, integrated technology. Invite everyone in. Integrate with company Directory and Single Sign-On. Integrate with other enterprise applications. Make sure everyone knows that it’s secure and it’s not going away.

    Then let them blast away.

    Here’s one way to put it: Content grassroots good, technology grassroots bad.

    Here’s an even simpler way to say it: IT owns IT, and content owners own content.

    Crazy? Obvious? Accurate? Stupid? Tell me what you think…

    Sharing Links Via Enterprise Microblogging

    One of the main tenets of social software is sharing information with your peers, and one of the most popular ways of doing that is by sharing links.  These links could point to breaking news from a popular web site, a press release from one of your competitors, a question from a customer or important business content your authoring with your team. Regardless of the topic, Socialtext makes link sharing easy, by providing a variety of tools that integrate sharing into the flow of the way you work.

    Workspace Pages

    When you’re reading a Socialtext workspace page that you want to share, just click the “Signal This!” action in the page’s toolbar. This will display a dialog box where you can enter any additional text that you’d like to include (ex: “Team, here is a great page about…”), choose the group you’d like to share it with and add additional attachments or tags.  When you click Post, a message will be created in the Signals stream with a link back to the workspace page.

    signal this workspace page

    Web Pages

    So what if you’re reading a web page that is not in Socialtext?  Using the “Signal This!” bookmarklet, sharing a link to any web page via Socialtext Signals is a snap, or well a click. Just like with the Signal This! feature mentioned above, you can post the signal to everyone or to a specific Socialtext group.

    To install the “Signal This!” action on your toolbar, first go to the Signals page of your Socialtext account.  Next, scroll down to the bottom of the Signals stream.  There you will see “Use the Signal This! bookmarklet to share any page on the web via Signals.“  Click on the link and follow the instructions for your browser.

    Notify Colleagues About Comments or Edits

    The two examples above are about sharing links to something you’re reading.  But what about a Socialtext page you’re contributing to? Well, Socialtext makes it just as easy to let people know when you’re editing a page or adding comments.  In either case, before you hit save, just click on the checkbox to “Signal this edit/comment”, choose the group you’d like to notify, and when the page is saved Socialtext will automatically post a signal with a link back to the page.



    Enterprise Microblogging is a great way to share information with your team.  As you can see above, with Socialtext there is no need to copy and paste URLs or move back and forth between different tools. Sharing a link is always just a click away.  So start right now. Go on and share a link to this article with your colleagues and show them just how easy it is.

    Social Software Adoption: When Good Companies Do Bad Things

    Why do good companies do bad things to social software adoption?

    In my previous post, I listed 6 things that companies can do to stimulate adoption of enterprise social software.

    • Make it your Intranet
    • Make it the primary destination for must-have information
    • Integrate with your company directory and, ideally, Single Sign-On (SSO)
    • Integrate with enterprise sear
    • Integrate with existing enterprise applications
    • Launch to your whole company (i.e., skip the pilot)

    This advice ain’t exactly rocket science. And yet, few companies do them–even companies that are working very, very hard to stimulate social software adoption. Why is that?

    One thing I learned as a McKinsey consultant is that organizational dysfunction is most frequently what causes good companies do bad things. So in order to understand why companies aren’t doing the most basic things to stimulate social software adoption, I went looking for an organizational explanation.

    I didn’t have to look very far. I have met the enemy and, once again, he is us.

    Looking across  identified three fundamental organizational failures that explain why companies are sabotaging their own efforts to roll out social software.

    1) Technology under-investment. Many companies got into enterprise social software with cheap or free wikis, blogs, or other social software thingies that were thin on functionality, integration capabilities, and administrative tools. “This isn’t about the technology,” people told themselves, “it’s about organizational behavior.” That’s true…but only up to a point. If you’re rolling out to more than a hundred people, you need technology that can stand up to the needs of your organization. I don’t mean just the “social” needs of the organization, but the business, administrative, and usability needs as well. That includes a comprehensive feature set like blogs, wikis, microblogging, corporate directories, groups, and social networking. It also includes back-end stuff like Directory and Single Sign-On integration, data security, technical scalability, and reporting metrics. Isolated point solutions without deep integration capabilities may be cool and fun to launch, but they won’t take you far.

    2) IT-Business Misalignment. With the trend towards Software as a Service (SaaS) and hosted solutions, many line executives think they can do this “without IT”. I’ve even seen examples where an individual department or business unit launched a “secret” social software project that they kept hidden from IT. That may help “the business” get up and running quickly, but it’s a sure path to adoption failure. You can’t integrate with LDAP, make social software your Intranet, integrate with enterprise apps, or integrate with search without bringing IT to the table. Try to hide social software from IT, and you’ll end up hiding it from your end users, too–no matter how hard you try to promote it on the down-low. Even if IT isn’t driving the effort–even if IT isn’t managing the service–they still need to be at the table, and committed to the project’s success.

    3) Innovation Marginalization. Because social software is innovative, companies sometimes think and talk about it in ways which marginalize it as a mere experiment. “This is a cool, crazy experiment. We’re just going to put it out there and see what happens. In a few months we’ll decide what to do with it.” This messaging appeals to innovators and early adopters, but it turns off everyone else. Why should they invest time learning a system that might not stick around? Why should they build content and processes around something that could be gone next quarter? When you position social software as a core part of your company’s technology capabilities, that’s when your colleagues in the mainstream will pay attention and start to use it.

    Taken as a group these organizational factors explain why companies set themselves up for social software failure. Are you having trouble achieving social software adoption? If so, take a page from Pogo‘s book. Look hard look in the mirror. Which of these organizational failures apply to you and your company? What can you do to address them?

    Socialtext CEO Eugene Lee to Speak at E-Summit for International Association of Software Architects (IASA) Today

    As enterprises integrate their traditional enterprise systems with social software, we have spent a lot of time thinking about how this should be done from an architectural perspective. So today, we’re thrilled that our CEO, Eugene Lee, will be speaking at the International Association of Software Architects (IASA) e-summit, sponsored by our friends at Cisco. His talk will take place at 11:30 a.m. eastern time (register here).

    Back in June, we launched Socialtext Connect, an offering that utilizes open web standards behind the firewall to integrate traditional systems of record (such as CRM, ERP and document management) with social software. Connect builds what we call a “social layer” in the enterprise that enables employees to see the critical events happening across their company from both colleagues and the systems they work from, and then easily collaborate and take action on those events with flexible social software tools.

    As Eugene’s talk will illustrate, we want to eliminate information silos that prevent employees from serving customers efficiently, responding to change, and accelerating their company’s overall business performance.

    We hope to see as many of you as possible. If you can’t make it, please check out our whitepaper on ReadWriteWeb that shows how technologies (like Socialtext Connect) that are built on a web-oriented architecture can make it easy for you to bridge your existing applications with your social software.

    About This Blog

    Weblog on gaining business results from social software.

    On this blog, Socialtext staffers and customers explore how companies can gain the most business value from their use of enterprise social software, including microblogging, social networking, filtered activity streams, widget-based dashboards, blogs and wikis.

    Search

    Find us on Facebook

    Read blogs from our team members:

    Archives

    Recent Posts

    What’s Next for Online Piracy

    Eugene Lee, January 26, 2012


    Enterprise 2.0: It’s not just for knowledge workers anymore

    Michael Idinopulos, December 9, 2011


    Turning Serendipity into Probability

    Michael Idinopulos, December 1, 2011


    Why Socialtext 360 = Success

    Mark Sylvester, November 15, 2011


    Social Training for Social Software

    Michael Idinopulos, November 1, 2011


    Socialtext 5.0

    Alan Lepofsky, October 3, 2011


    Socialtext introduces Socialtext 5 – welcome to the power, the ease and the flow of the future!

    Sarah Dulak, September 28, 2011


    CIO Insight Interview with Eugene Lee

    Britta Meyer, September 22, 2011


    Learn How the DAU Is Improving Collaboration and Education

    Alan Lepofsky, August 15, 2011


    Eugene Lee Discusses Socialtext with TMC

    Alan Lepofsky, August 11, 2011


    Recent Tweets


    Blue Man Group Webinar

    Recording Coming Soon

    Learn how Blue Man Group uses Socialtext to foster creativity among its 500 employees, how groups are working better and more effectively together and why they’ve seen an over 80% adoption rate since implementation.

    Integration: The Next Frontier For Enterprise Social Software

    Recorded Webcast

    Integrating "social features" with your organizations core business processes (CRM, ERP, CMS, HR, Financial, etc) makes it easy for your staff to use the new social features "in-the-flow" of their daily tasks. This recording provides examples of how Socialtext customers are benefiting from this type of integration.