The pursuit of the Enterprise 2.0 utopia promised, described and promoted across the web has attracted the committed, the curious and the cautious. As we move further up the adoption curve the amount of success as well as failures increase. This is the second in a short, three part series about the common mistakes in Enterprise 2.0 strategies and how to avoid them.
The three common mistakes of E20 are:
1. Technology treated as an ends rather than a means.
2. IT as leading the business rather than supporting the business.
3. Information architecture that is walled and gated when there is no good reason for it to be that way.
Let’s continue to take these one by one.
Mistake 3. Information architecture that is walled and gated
Despite the previous caricature of “BSTech”, many specialized web and enterprise 2.0 systems are very good at what they do. Those that are suffer from another, more insidious problem. When BSTech is well made and highly utilized it produces lots of sequestered information. This yields a somewhat counter-intuitive result. The enterprise becomes a victim of its own success. More use and more adoption produces more, good information. But as that information becomes more desirable, its ability to 1) be found and 2) be accessed is decreased.
walled and gated garden
Content “walled gardens” are the individual information stores of separate systems. All organizations have them. Very few are required for legal, regulatory or intellectual property reasons. Most exist because nearly every system comes with one. CRM data is stored in the CRM system. Web analytics reports are stored in the analytics system. Accounts Payable information is stored in the AP system. Content is in the CMS. Let’s be honest for a moment. There would be no market for SOA systems, enterprise search and integration platforms if systems could natively share information with each other. So this is a reality of the world in which we live. But isn’t all the information the Organization’s information? Ask yourself this: if the system-imposed information sequestering was not there, might I be able to access information that is highly relevant to me that I am otherwise allowed to see ? It is because of a fractured enterprise information architecture that many employees are prevented from accessing highly relevant content. So they are left either re-inventing the information, jumping through efficiency-killing access request hoops, or lobbing requests for “something you think might help” to other people who have no stake or incentive in helping.
For all the vaunted benefits of a network effect where BSTechnology is concerned, the benefits only accrue only when there is actually a (…wait for it…) network. Lots of user adoption is not the ticket to success. It is a part of the success formula, but it is not complete by itself. Unfortunately, the focus for many in the enterprise 2.0 and next generation workplace discussions has been on user adoption. Make no mistake, adoption is necessary to success but it is not sufficient. So if network effects (which state that the value of the system grows the more it is used) require a network, then the concept of a host of walled gardens and sequestered information stores is fundamentally antithetical to enterprise 2.0 technology goals.
Facebook Social Network Slice - Billy Cripe via Facebook
Social networks require that people use them, engage with others through them and share ideas with them. If all the ideas and users have to be created within the system in order to use it, they would suffer. So we see social tools for the business able to integrate with corporate Identity management (e.g. LDAP and Active Directory) systems. The ability to hyperlink to other content is among the most basic of expectations. The advantage of Portals would be substantially diminished if your portal server could only bring together pages, code and content that were created within that portal server. Enterprise content management systems that only allow specific, invited people to consume content that would otherwise be available for a much wider audience are fundamentally flawed. This is because those kinds of systems put artificial constraints and limits on the network – the ability to connect, access and consume information. They create many walled gardens of information. Admittedly they often do a great job of creating that content. It is rich, desirable, relevant and usable. But it is not available to the network. It is available only to those few who were originally invited into the walled garden. The organization suffers as a result.
So what is an organization to do?
Answer to Mistake 3. Except where required for legal, regulatory or intellectual property purposes, consolidate your information stores. Now before the IT readers have a heart attack, understand this: consolidation does not necessarily mean migration into a single physical system. Consolidation means bringing content and information into a single logical (not necessarily physical) information hub. The aforementioned SOA capabilities, enterprise search indexes, and integration APIs are wonderful tools (means – not ends!) with which to get a handle on organizational knowledge. This is a critical step in preventing enterprise 2.0 goals from becoming merely department 2.0 realities.
Once IT has a handle on the information out there, they can start to help bring it together in meaningful and predictive ways. What makes a meaningful way? Look at the solution to mistake 2: focusing on the business problem, the stake holder, and crafting a solution to that problem is what makes a solution meaningful. Composite applications are one way to do this. Compositing simply means bringing two or more different things together. Think of it this way: today we can bring together people in a social network. That social network, whether your Facebook profile or LinkedIn group or Fishbowl’s CollabPoint team is treated as a single entity. It is the team, the friends list, the group. That group is a composite of many different bits of information that combine to create something all together different and exciting and useful. Composite business applications are very similar.
Think of the customer care process. It is made up of many smaller processes, applications, tools and technology. Before they are customers they are prospects.
They may have attended an event, or sent you an email or visited your store (responding to a media based ad like a blog or your website or a television commercial – 1).
Some contact was made (phone, email, in person visit – 2).
They were probably added to a marketing list (excel or database or list – 3).
Eventually they responded to some invitation and received a visit from sales (sales tracking or CRM system – 4).
They became a “lead”. Sales has its own processes of presentation, demonstration, test-drives, samples etc (scheduling system, calendar, technology demo system – 5).
Eventually the lead becomes a deal and the contact becomes a customer (conversion of lead to customer or migration into a new Sales Automation system and Entry created in an Accounts Payable system – 6 and 7).
The technology used up to this point was probably a combination of 7 or more separate systems. And the “process” has not even advanced to the invoicing, collections, support, call center and ERP (for restocking etc.) systems.
Is it any wonder that the drive and call for process efficiency and system compositing is growing? Any compositing, any combination of any of these steps in the process yields efficiency and delivers additional revenue (or cuts cost). When portals are used to not just show side-by-side glimpses of still separate systems but rather to bring together information from separate systems into a single content object efficiency is gained. When ECM systems are used to house a single piece of content that can be delivered to several different systems without copying, speed and intelligence are boosted. When support and call center complaints are trend-mapped and delivered to product management problems can be spotted and handled early – before they get out of control. When the sales force is proactively given access to the marketing team’s campaign materials rather than only giving it to them if and when they ask, better messaging and coordination can take place. This provides mutual reinforcement of the overall message or campaign you are delivering and adds credibility through consistency. It means that each sales rep can tap into the collective power of the marketing team and all the trend and market research they’ve done rather than spending precious cycles trying to discover what the next big thing is going to be.
These are just examples of how the next generation workplace ought to function. I’m interested in your stories of where you have seen or are starting to see these kinds of incremental successes. Add your thoughts below.
applications and mentioned that to implement this functionality you call the UCM services directly over HTTP. This is a great way to do it and makes the integration very straightforward, however, the customers where we have implemented the Fishbowl Portlets were using their portal technology to present a public facing site. In this instance the UCM server that is serving the content was always behind a firewall where the client’s browser could not access it on port 80 or 443. Opening a secure socket connection between servers ended up being a much easier sell to IT Security.
