The digital company – freedom to collaborate

I am closing down some of the open tabs, cleaning up draft versions and stuff I always wanted to blog about. Not all drafts stand the test of time, but some do. On the topic of good organization the report Digital company 2013: Freedom to collaborate written by Kim Thomas for the Economist Intelligence Unit stays interesting. Some of the key themes explored by the report are

  • Technology knowledge will permeate the enterprise.
  • Social networks will be common in the workplace, like it or not.
  • Beware information paralysis.
  • Digital tools will democratise access to information.
  • Digital tools provide employees with greater control over the information they can access.
  • IT will also need to loosen the reins.
  • Ceding technology control will be good medicine.

And they note that in order to realise the benefits of improved collaboration business leaders must come to terms with autonomy: “for employees, in how they access information and spend their work time; and for business units, in what technologies they purchase and how they use them. Above all, it will require from executives a great deal of courage—to allow technology to bring customers and other third parties into the company’s operations—and trust in their employees to access and use information freely.”

In Auto industry and Enterprise 2.0 Andrew McAfee speculated what he would do if appointed “Detroit CIO”. While the set of 10 principles he’s applying is good, I am not too convinced that technology, i.e. rolling out emergent social software platforms (ESSPs) to all employees of the company, starting internal CXO blogs etc. would do the trick. The car industry is a heavy user of IT already, adding to the pile of tools won’t help in overcoming resistance. And that’s where the rub is: implementing Enterprise 2.0 concepts must cope with the people, processes and the tools they employ in these processes (I specifically doubt that Six Sigma or Lean Production processes can benefit much from Enterprise 2.0 concepts, these are repeatbale and highly automated processes, i.e. they don’t need no flexibility, adaptivity or emergence). But some other advanced (knowledge work) processes might benefit a lot – hey, collaboration and social software might even help in turning around a basically flawed business model, so Andrew’s thought experiment is very welcome.

Then, IBM Research is looking at adoption, usage patterns, motivations, and overall impact of Social Software in the Workplace (pdf). The paper focuses on the internal usage of social networking (Beehive) and examines the individual goals people have when utilizing these platforms (like interacting with colleagues, career advancement, convincing and informing others about ideas and projects).

Via Stewart I found Gerard Tellis & Ashish Sood‘s article “How to Back the Right Technology” in the Wall Street Journals and MIT Sloan’s Business Insight – dealing with mistakes organizations often make when choosing which technologies to adopt:

  • They fail to distinguish among different levels of technology, with the result that they focus too much on one level and get tripped up by changes in another level.
  • They assume technological performance follows a standard path — from innovation to obsolescence. It often doesn’t.
  • They fail to recognize that technological innovations shape consumers’ tastes, not mere whims.

Good advice included, like e.g. try multiple things at once and don’t bet too heavily on one choice, on picking a winner:

  • […] Technologies, and the competition among them, evolve in more-complex ways than conventional wisdom suggests. To make the right choices, managers need to understand these patterns of evolution.
  • [so that] executives can avoid some common mistakes: missing a market-changing technological breakthrough, embracing a hot technology too eagerly or abandoning another one too quickly, and underestimating the effect of new technologies on consumers’ tastes.

And if you’re in doubt what technologies to evaluate for 2009 EDS’ Charlie Bess gives you something to think about, see his predictions for 2009 (granted, a mixed bag of IT technologies and/or approaches). To me, most important and most interesting is his starting point:

In this [financial et al. crisis] situation, the investments in technology can actually have more impact than at any other time, since your competitors may be in a purely cost cutting mode. In 2009 organizations must maintain a balance between the new/strategic and the immediate return, between operational cost-cutting and operational excellence. Anytime there is this level of conflict, the situation is ripe for innovation

Well, basically looks like a good situation for social software in the enterprise aka Enterprise 2.0 …

Outlook on collaboration in 2009

Besides playing experimenting with some new (sometimes cloudy) collaboration services and technologies (and I didn’t even make it halfway here), battling a nasty cold and family time I’ve been reading my share of Enterprise 2.0 outlooks for 2009 lately, starting off with Gil Yehuda of Forrester (“Predicting the battle over collaboration infrastructure in 2009“) who answers short questions with good long analysis.

Gil, do you think companies will cut back on Enterprise Web 2.0 in light of the economy?

First reaction – it depends. I’m an analyst, that’s always our first answer. […]

That’s not all for sure, he goes on to ponder what lies behind all this, i.e. he delves into the relation between IT department and business units, diagnoses an increased need for collaboration functionality as a result of “layoffs, mergers, and deepening external partnerships (requiring new infrastructure to collaborate outside the firewall with trusted, external partners)”, and sees a slowdown of IT-driven collaboration projects in 2009 compensated by more business-driven collaboration projects. A good read.

More general are FastCompany’s predictions that 8 experts have for Web 2.0 in 2009, even with Charlene Li among them who holds

“[that] the biggest innovation will be the opening of social networks so that they can exchange profiles, social relationships, and applications. As such, companies need to think about how they will “open” up their businesses.”

Read-write web compiles a list of enterprise-focused web products that are already doing well and are poised success in 2009, nice that there’s a subcategory of Wiki++ (oh, this geeky humour):

We added “++” to “wiki” because the leading vendors are rapidly incorporating micro-blogging, social networking, forums, and other collaboration tools. Integration is key, so we see this market moving towards suites, but with wiki at the core.

Yes, said that before, think “middleware for humans” – one might even argue that wikis are archetypical infrastructure, and being flexible enough to cater for diverse and changing needs.

Then Craig Roth of the Burton Group presents their views of the 2009 landscape for communication, collaboration and content and warns

It’s also important to note the cyclical nature of organizational dynamics, which underlies everything we talk about related to communication, collaboration, and content.  Rather than just disappearing, terms like “knowledge management” fade from view only to be rediscovered when their time is right.  Governance has been on the tip of the tongue for at least five years now in our space, but it may fade only to be rediscovered under a new name ten years from now.

That is why it is so important to understand the basic concepts and dynamics behind communication, collaboration, and content before delving into the specifics of any specific technology.  If you don’t understand your history, for example, social networking can be felled by the same issues that caused collaborative workspaces to fail before them.

Craig also blogged about the implications of the tough economic conditions on the collaboration (and IT) market, something on which I will post a follow-up soon as well. Actually I think that the economic crisis might even turn out good for collaboration initiatives, open source and Enterprise 2.0 …:

Companies that come out of recessions in a stronger position than they went in are those that judiciously invest in technology and related processes that let more work get done with less resources as well as reducing costly delays and red herrings when making decisions. And when the market downturn ends – and it will – opportunistic organizations will be in a better position to succeed than those that had hunkered down during the recession.

Some more quotes and notables:

– Mike Gotta thinks about some acquisition possibilities (or dangers) in the Enterprise 2.0 market, triggered by an article in CIO magazine “Web 2.0, Social Networks in ’09: The Year of Consolidation, Not Innovation” that puts Lotus Connections and Sharepoint in perspective (btw, I don’t buy the article’s argument that consolidation in the enterprise Web 2.0 market could hamper innovation around those tools, I guess the innovators in this space have set high standards already, plus the real issues aren’t with nifty tools et al.). Yet, the triggered reasoning by Mike on “strategic fits” is good, and I can’t help wondering if some of these M&As might turn reality in 2009. Besides he’s done a great rundown of various Enterprise 2.0 issues too …

– Robert Scoble sees a fight coming between the collaborative web and Microsoft, besides being busy talking to Socialtext and Jive Software (during his Enterprise disruption week), while  David Coleman examines the underlying thinking (in “The Evolution of Collaboration Technologies“): “Most of these organizations are betwixt and between. It is safer to go with what you know (IBM or Microsoft) but also can be expensive in a recessionary period. Or phase out the aging collaborative infrastructure for something a bit more up to date, with more collaborative functionality. So far most of them seem to be playing it safe, a few are looking for new tools that will meet their collaborative needs both today (with the Millenials) and tomorrow.” and Kevin Mullins offers some Technology Predictions for 2009 (“I see Web 2.0 and Enterprise 2.0 becoming feature sets in new products and services in the Enterprise, however they will not become feature sets in all Enterprise products”). Well, fair chance and clever arguing 😉

– At last, CBC had a feature interview with Clay Shirky on the pros and cons of social media, new online business models online, and how big change comes from human motivation, not shiny new technologies. Well, yes, don’t blame the web intranet when it’s filter failure, yes, the ability to pay attention in the Web 2.0 age is the “work smarter, not harder” version 2.0

    So now I wish all my readers, friends, colleagues, partners and clients a happy and successful 2009. I hope you all had time and rest to enjoy some quiet days with friends and family before the rat race starts again. Oh, again it’s making-fun-of-rats-time – I really must look out lest this turns out a standard operating procedure …?

    A mixed bag of tabs …

    … with some interesting stuff I found but can’t really blog about, at least not yet, I will see how much time I get next week when LeWeb is in full swing …

    • Wharton says what we should do when the times are getting rough: innovate. Well, yes, no point in playing safe these days, rather use the downturn to trigger serious change. A good idea (like supporting more efficient collaboration and teamwork with enterprise social software solutions) stays a good idea after all. A sense of urgency may just be what is needed to overcome some of the remaining resistance …
    • Kathy Harris of Gartner collects some thoughts on principles and actions to foster and increase creativity, like rapid knowledge and idea sharing, effective information management, listening to the customer, visualizing concepts and information relationships and to develop deep analysis and analytical skills (good list, competing on analytics gets missed upon too often).
    • Bruce adds some words of wisdom and a reality check warning the overly collaboration optimists, and while I agree that participation inequality is no real problem, I am more optimistic for enterprise wikis that have a clear goal and that support a dedicated group of people. That’s what gets wikis flying – a group of people that care and invest themselves into wiki gardening, motivating and educating (yet, wikis can do a great job as information platform even when “most people contribute nothing”, but that’s not the best they can do).
    • Ted Schadler blogs about extranet collaboration platforms, collects some (infra-)structural problems that must be solved and proposes in the comments his “working model for an extranet collaboration platform toolkit”. Seems like a pretty complete offering to me, at least in “advanced mode”. Well, I think that these are good and valid elements of an (extranet) collaboration toolbox, but I doubt that all of them will and must be used in parallel. Individual tool usage in Enterprises is highly dependant of the context, and “tool inflation” won’t help. It’s changed methods and practices of collaboration that do the trick, not tool A vs. tool B. Shines a little light on the “best of breed” vs. “integrated suite” debate too I guess.

    Zusammenfassungen …

    … meiner Recherchen und Analysen u.a. zu Themen wie Cloud Computing, SaaS, Enterprise Microsharing, ECM, MOSS 2007 und Sharepoint sind normale (und tägliche) (Beratungs-)Arbeit. Nicht alles wird hier (oder als Bookmark bei delicious) öffentlich geteilt. Anderes durchaus, ein paar Notizen und Anmerkungen zu Fundstücken der letzten Zeit

    Mit dem Google Search Wiki (gefunden via TQU und netzwertig) können angemeldete Benutzer die Reihenfolge ihrer Suchergebnisse für eine bestimmte Suchanfrage verschieben, löschen, hinzufügen und Ergebnisseiten mit Notizen versehen können (ähnlich wie es Wikia und Mahalo mit Social Search anstreben). Interessant – kollaborative Entdeckung und Empfehlung (digg-like) als erweiterte Suche? Ja, analog wird auch für RSS mehr Personalisierung gefordert:

    As Web content becomes more granular, compositional, and personalizable (not to mention more perishable), subscribability becomes a design consideration. Users want to be able to opt into dynamic content. […] it’s no longer enough just to let users save queries; they now need to be able to subscribe to their queries (or the content generated by them).

    Via Stewart Mader habe ich den neuesten Forrester Report zu Enterprise 2.0 (Enterprise Web 2.0) gefunden. Die vollständige Analyse ist umfangreich und kostenpflichtig (ja, wie oben gesagt) – aber einen wichtigen Punkt fasst Stewart schon ganz gut zusammen: “wikis are transforming collaboration“:

    […] One of the more promising of the Web 2.0 technologies for the enterprise, wikis show good evidence of helping transform collaboration in the enterprise. Users report success with many wiki endeavors when they’re sponsored by business leaders and connected to business processes.

    Und um wieder mit Forrester zu argumentieren: Verteilte Teams profitieren besonders von (Real-Time) Collaboration Tools – auch wenn sicher nicht alle Kommunikation in real-time geschehen muss. Aber die Unterstützung reichhaltiger, kontextgerechter Interaktionen (Ted Schadler spricht von pervasiveness, aus meiner Sicht bestehen zudem weitere Anknüpfungspunkte wie “reach” und “ambient intimacy”) ergänzt die Zusammenarbeit in Wikis ideal. Es ist also schlüssig dass Micro-Sharing und -Blogging, sowie “federated, cloud-based collaboration platforms” wie Forrester schreibt an Interesse gewinnen.

    Teaming up for innovation (and integration) …

    Via Oliver Marks I found an article (free download at nGenera) who appeared in the November issue of Harvard Business Review (“Teaming Up to Crack Innovation and Enterprise Integration”) by Robert Morison of nGenera (yes, Don Tapscott is involved …), James Cash and Michael Earl of Oxford and Harvard respectively.

    Picture to the left by Idris Motee who understands the need for interdisciplinary creative thinkers

    Morison et al.s “idea in brief”:

    Your company is continuously creating new generations of products, services, and business processes. These innovations require seamless collaboration across your firm’s different parts. But in most large corporations, innovation and integration are unnatural acts. Resistance stifles new ideas, and silos block cross-functional cooperation.

    […] explore how some companies are overcoming these boundaries […] establishing two new types of cross-organizational teams:

    Distributed innovation groups (DIGs) – foster innovation throughout the company.
    For example, they deploy intranet based forums and wikis to scout for promising ideas.

    Enterprise integration groups (EIGs) – establish the architecture and management practices essential for business integration. For instance, they identify
    integration opportunities, channel resources to them, and reconfigure Enterprise Resource Planning (ERP) systems to support ever-tighter crossbusiness collaboration.

    To establish each of these groups, select a small number of talented people who combine broad business knowledge, technology expertise, and the social skills needed to build relationships both within and outside your company.

    Yes, establishing tools and protocols is only the start. People and their skills (that includes leadership, being trustworthy and good at team building) are essential, especially when dealing with innovative tasks. And it’s more challenging when dealing with scattered (or even rivaling) business units.

    So I liked the sound strategic thinking Oliver added – namely what separates the successful collaborative enterprise from those that aren’t – even more as he pointed out usage arenas like business intelligence, internal and external environmental scanning. These are memes worth expanding upon: one of the often overlooked benefits of Enterprise Social Software like wikis is that it both puts real time information to the front-lines of a corporation and collects the wisdom that is spread at the “edges” of the company:

    […] DIG’s could include, as examples, scouting for new ideas and untapped potential in current technologies, scanning the external environment for emerging technologies, Facilitating participation in idea forums, acting as an innovation expertise center, serving as an incubator for promising innovations and publicizing promising innovations and funds.

    and

    […] why there are so many sparsely populated wikis and blogs slowly twisting in the wind in the corporate world – because they were set up as tentative trial balloons with no clear utility or guidelines for expected use. It’s trivial to set up a blog or a wiki from a technical perspective – you could do it in the time it took to read this article – setting up the internal use case to ’scout for promising ideas’, for example, takes a great deal more thought and planning.

    The real challenge is in finding the key people […] these are the core resources that will drive innovation, adoption of associated methodologies and their enabling technologies and the successful execution of usage models.

    People issues again, but it also reminded me of this (old) article by Rob Cross, Andrew Hargadon et al. (“Together We Innovate“) on the MIT Sloan Management website (and it isn’t about scouting for ideas inside the organization alone, right). It claims “How can companies come up with new ideas? By getting employees working with one another”,

    […] problems that stifle innovation. They share a couple of common themes: the failure to effectively leverage the expertise of employees (or their peers in partner organizations) and the failure to react effectively when new ideas do arise. But we’ve also found five steps companies can take to clear those barriers and start producing big ideas.

    Cross, Hargadon et al. collect some network problems (and wrangle some ideas on how to solve them too):

    1. No Communication […] the structure of the company keeps people apart […]
    2. Bad Gatekeepers […]
    3. Insularity […]

    Check out the proposed “solution takes” – and see that these are about people and leadership in the beginning but include as well adaptivity & agility, connectivity and emergence (well, they don’t name it but it’s shinig all through, like when arguing that we need systems that allow for easy collaboration, in my book that means systems that can be personalized and tweaked to my very own needs).

    Collaboration Techniques that really work – Lisa Reichelt @ Web 2.0 Expo Europe

    Some notes on the first session at the Tuesday workshop session at Web 2.0 Expo Europe: “Collaboration Techniques that really work” with Leisa Reichelt. I really enjoyed the workshop, it was both easy going and immensely interesting. I went there to learn about new working patterns and methods, and learn about how to adopt these to my consulting practice.

    We started off with all participants presenting themselves, at a minimum three tags were said. I got the impression of a pretty mixed crowd, i.e. there were developers, journalists, designer, start-uppers, business developers – and even one or two big Co guys too – mainly with an european background.

    OK, here we go:

    • Collaboration = working together, especially with the enemy 😉
    • Collaboration ain’t inviting a bunch of people to a meeting at the beginning of a project
    • Collaboration ain’t working separately on the same project, yes, it’s all about the „actually working together“, not just contributing bits to a pot

    Well, we all agreed that good collaboration is rare, it’s percveived as somehow fluffy, even when the benefits are so obvious. Some reasons:

    • good for team building & morale
    • good for communication
    • support and build up cross disciplinary skills and insight
    • more heads, eyes, perspectives enrich our work
    • we build up team & shareholder buy in
    • it’s fun too, yes, fully acknowledge this – people are social animals, we like it to be together with people we like, and with people that have energy and commitment (for the project)

    If we do it right we can

    • turn stakeholders or customers into collaborative partners
    • build collaboration into project methodology – i.e. collaborate regularly with your project team
    • collaborate with your peers & invite other expert perspectives – Leisa offered us this good idea of inviting “wildcard collaborators” from the outside, they help us to think tangentially and integrate new perspectives

    Ok, then, when to collaborate?

    • at the beginning of a project, but not JUST at the beginning
    • when you’re stuck, i.e. for trouble shooting and problem solving (this is collaborating with a narrow focus)
    • when you’re looking for inspiration (yes, wide focus)
    • regularly, well, it must be trained …

    What kind of tools make sense?

    • people (the right ones!), i.e. people that like to collaborate
    • sticky notes & pens, whiteboards/ flip charts
    • fun stuff as stimuli
    • sugar in the afternoon (sic!, give them sweets to keep them alert and productive)
    • an objective (well, I know this is not exactly a tool, but close enough in Leisa’s line of arguing, agreed)

    Later on we ventured into techniques that make brainstorming work, i.e. right people, preparation, „the rules“, the tools and the environment. Some noteworthy points are the Importance of a good facilitator and the aligning along useful rules, like e.g.

    • what is the problem / question?
    • we need to appoint a facilitator & a scribe
    • listen more than you talk (this can be really hard, it’s easy to dominate the group when you’re outspoken and have a deep interest in the ideas)
    • listen for your own ideas, but also add value to other peoples ideas
    • suspend judgement

    One very important rule is “NO QUESTIONS”, good one but nothing new here. I actually liked the second “lifehack”, i.e. demand that any of the contributed  ideas must start with the words: „I wish …“ or „how to …“ as this is helping in going from an idea to a story. Giving you a roundup of our group experience, dealing with ideas for a pizza restaurant is rather hard, so it pass on this one.

    Well, second part of the workshop dealt with the KJ method for consensus, i.e.

    1. determine the focus question
    2. get „opinions“ / „ideas“ onto sticky notes
    3. affinity sort into groups (likeness, clustering)
    4. name groups
    5. vote on group importance (three votes)
    6. rank groups (two by two)

    Some hints: a) if nobody votes for a group throw it away, you can get there later if you want b) rank them via counts of votes, then put the winner group besides the second group and discuss which is better (well, you basically apply some kind of bubble sort to this, finally you reach a list sorted by perceived importance) and c) in the voting stage it’s basically about discussing these things out, even when in the end it can be necessary to resolve deadlocks by voting again.

    In the discussion we shortly talked about whether we can do this online. Well, yes, sort of an issue. But I agree that it’s hard to do this with offshore teams (I guess that is not so much about distance, than about cultural differences), so while technically speaking you can do it, it’s never going to be like the F2F-situation. Moreover, the hassle involved in getting the people together is so much worth it (side benefits like connectedness, understanding, team building, …) and basically making it a lot easier later on to do more on technical platforms and with online tools.

    By the way, the room was packed with people I know and dig, let me see: Peter Bihr, Stefan Nitzsche, Jodi Church-Wagner, Christian Heller, Johannes, Hans Dorsch, Jan Tißler, Igor Schwarzmann and Henning Grote. Johannes did some live-blogging, as well as Jodi, but I guess that there will be more write-ups soon. Moreover there’s the Twitter Backchannel with the tag w2eb_ux and w2eb respectively, check out e.g. Twemes. And Leisa said that she’s going to put her slides up on Slideshare, probably in a Web 2.0 Expo group  …

    Web 2.0 Expo Europe 2008

    Communication (and coordination?) in complex organizations

    Stumbled upon this Harvard working knowledge paper by Adam Kleinbaum, Toby Stuart, and Michael Tushman via Mike Gotta who highlighted the opening quote:

    “The social system is an organization, like the individual, that is bound together by a system of communication.” − Norbert Wiener (1948, p. 24)

    The paper asks which groups are most likely to communicate with others in a large organization, regardless of social-and physical-boundaries and finds that category-spanning communication patterns are demonstrated primarily by women, mid- to high-level executives, and members of the executive management, sales and marketing functions.

    It is available for free download as a pdf. Here’s the abstract:

    This is a descriptive study of the structure of communications in a modern organization. We analyze a dataset with millions of electronic mail messages, calendar meetings and teleconferences for many thousands of employees of a single, multidivisional firm during a three-month period in calendar 2006. The basic question we explore asks, what is the role of observable (to us) boundaries between individuals in structuring communications inside the firm? We measure three general types of boundaries: organizational boundaries (strategic business unit and function memberships), spatial boundaries (office locations and inter-office distances), and social categories (gender, tenure within the firm). In dyad-level models of the probability that pairs of individuals communicate, we find very large effects of formal organization structure and spatial collocation on the rate of communication. Homophily effects based on sociodemographic categories are much weaker. In individual-level regressions of engagement in category-spanning communication patterns, we find that women, mid- to high-level executives, and members of the executive management, sales and marketing functions are most likely to participate in cross-group communications. In effect, these individuals bridge the lacunae between distant groups in the company’s social structure.

    I like the approach, and the systematization of the three types of boundaries. Moreover the results reminded me of McAfee’s empty quarter thoughts, esp. if we understand that building bridges is one thing that may emerge with the adoption of social software in the enterprise. Yes, to achieve the boundaryless organization, putting social web elements to use is a good idea – especially to support lateral, cross-division, cross-function and cross-rank communication patterns. Yet, I guess that breaking up the silos all the way, i.e. to achieve and leverage “cross-division, cross-function and cross-rank” cooperation and collaboration, will be a lot harder. Connectbeam‘s Hutch Carpenter highlights the status quo and the real issues to deal with, i.e. integrating the user experience and adding layers that do more than mere enterprise search:

    Adding social computing features to existing enterprise silos certainly helps, but fails to connect the larger organization. […]

    We have not yet seen the emergence of a full-suite vendor that addresses the different needs of the market. Expect to see enterprises with multiple social computing apps for the foreseeable future.