My Harvard colleague Larry Bouthillier commented on my previous post, which discussed the corporate Facebook application WorkBook recently released by WorkLight.
"Facebook integration like this is less scary than it may look at first glance. At the risk of getting a little too geeky
, let me explain.
Facebook allows application developers to create their own apps that live inside an “iframe” within the Facebook site. Whatever a company does within that iframed space is entirely their own secure environment, and can even have its own intranet login process just like the company portal.
For example, in the application my team built for Harvard students to see and interact with their course schedules and classmates in Facebook, that application uses the standard Harvard intranet login process, runs on a secure (SSL/https) connection, interacts securely with the Harvard directory services (LDAP) and email services, and Facebook never sees any Harvard-specific data about the users whatsoever.
So, our app looks like Facebook’s screens—same styles, same way to display lists of people, same Facebook photos of users. But it’s all generated by us to look that way.
I suspect that WorkBook does something similar. The application does not live *inside* Facebook, it just appears that way. It just happens to sit inside a Facebook iframe, and uses a few handy conveniences Facebook makes available (such as access to Facebook photos, friend lists, and messaging).
Ultimately, it can be as secure (or insecure) as any other intranet application. "
Larry’s explanation is extremely helpful and illuminating. It also brings up two larger points that deserve emphasis. First is the distinction between technology deployments that are advanced and those that are powerful. As Larry points out, WorkBook is not terribly advanced; it’s not near the cutting edge of what can be done with Web applications, or any other aspect of IT.
For some, this makes it uninteresting. Lots of people who study technology are perennially attracted to that cutting edge: the fastest chip, the most complex algorithm, the largest cloud or grid of interlinked computers, the biggest simulation, the coolest use of AJAX, etc. These advances are often important and always newsworthy.
But from the perspective of an executive trying to run and improve a company, are they the most powerful ones? Put another way, how many pressing business problems can only be solved by the application of cutting edge computing? There are some such problems, to be sure, but my guess is that they’re confined to small parts of relatively few companies in a small number of industries. Most of the jobs, business processes, and organizations I know well wouldn’t benefit tremendously if all their computers suddenly became twice as fast. They’d gain a lot more from basic data standardization, systems integration, workflow, or social networking.
Let’s make this more concrete with a thought experiment. From which technology deployment would Merck benefit more: Facebook and WorkBook to all employees, or the most sophisticated hardware and software for drug discovery across all its labs? I don’t raise this question to dismiss it as a no-brainer — a good argument could be made for either choice.
But my money’s on the unsophisticated digital social glue. I think it’s telling that despite the huge amounts of money pharma and biotech companies have poured into advanced computing in recent years, big pharma’s drug pipeline is in the worst shape in recent memory. As James Surowiecki points out in a recent New Yorker column, "The number of “new molecular entities”—drugs not yet introduced in the United States in any form—approved annually by the F.D.A. has fallen by sixty per cent since 1996, and new drug applications have dropped nearly forty per cent." It’s naive to think that Enterprise 2.0 tools and approaches alone will open up the floodgates — Surowiecki states that" ‘diseconomies’ of scale: inertia, bureaucracy, risk aversion, clock-watching, [and] office politics" are the major factors drying up the pipeline — but I think these simple but powerful technologies would have a larger impact than all the new workstations money can buy. Do you agree?
The second point arising from Larry’s comment is the ever-increasing ease of integrating applications and data. There are many labels associated with this trend, including ‘mashups,’ ‘Service-Oriented Architecture,’ ‘Web Services,’ etc., but they’re all describing the same happy process: the fact that it’s getting easier and faster over time to combine two or more formerly separate systems to yield something valuable.
I was talking the other day John Bruce and Eric Shurr of the enterprise social media company Awareness Networks (I have no financial interest of any kind in Awareness, and have had no commercial dealings with the company). They said that it now takes Awareness a matter of weeks to fully deploy their hosted platform at a customer, and to integrate it with whatever security and authentication infrastructure is already in place. I asked them how long it would have taken them to do the same work five or six years ago. John, who worked extensively in security before joining Awareness, told me it would have required several months.
Some foresee that the day will soon come when it’s so easy to integrate systems that the systems will do it themselves. This is part of some visions of the ‘Semantic Web.’ I have grave doubts that this will ever happen outside labs and other tightly controlled environments, but that’s a topic for another post. For now, it suffices to highlight and applaud the fact that it’s getting much easier to get computers to talk to each other. As the examples of WorkBook and the scads of other Facebook applications show, this delivers benefits to all of us IT consumers.
{ 8 comments… read them below or add one }
Andrew,
I saw your last blog post and wanted to address some of the points raised by your colleague. First all, the technical onesÂ…As your colleague correctly points out, putting a gadget or widget in an iFrame within Facebook is simple to do. I agree with him that this is a very low technical barrier. On the other hand, it is quite difficult to producing an application like Workbook, for the following reasons:
•Tapping into the native authentication and access control mechanisms in order to know which information should be served to whom (for Q&A, search, sharing news, building friends lists, etc.) is not simple. The prospect of building a new security layer and a new access control system is a non-starter.
•WorkBook is part of an Enterprise 2.0 operating system called WorkLight, which is also able to incorporate application data from apps like the corporate directory, CRM, HR and other employee-related applications and use it within the WorkBook/Facebook application. Therefore, WorkBook is more than a gadget running in an iFrame, it is a complete application that solves the following key enterprise challenges:
oSecurity –There is a plethora of security challenges that are unique to the world of Enterprise 2.0. Some of these include the following:
Authentication/access control using native systems. How do you make sure only the appropriate people can see snippets of protected enterprise data?
Keeping data from leaving the enterprise while appearing to come from public Web 2.0 tools like Facebook.
A whole new set of threats inherent in Web 2.0 technologies like AJAX and RSS. These have not yet been addressed by customers or vendors, but they have been addressed by WorkBook.
oIntegration – WorkBook comes out of the box with adapters to applications (like CRM, HR, and other apps) and security infrastructure (like SSO systems and LDAP directories), so implementation is quick and simple. We have already solved these problems – creating this from scratch is not trivial, to say the least.
oSelf-service – WorkBook/WorkLight comes with tools that allow organizations to customize and evolve without having to code new changes. Many of the changes can be done by non-technical people.
In short, there are many more pieces involved to making an enterprise Facebook application than just putting a gadget in an iFrame. Some of these are part of WorkLight’s patent-pending intellectual property. Large security-conscience organizations who have “tried to build” their own solutions have come to the conclusion that WorkLight/WorkBook is the right solution once they understood all the issues at hand. We would be happy to spend time with Larry and explain these in detail, if he so desires.
As for the social aspects, we have found that more than a few organizations have tried to build their own Facebook-like applications, and have failed, not because they couldn’t develop the features. They failed because they could not get employees to adopt the new application. And that is where the ‘social glue’ comes in. People are already on Facebook. Why reinvent the wheel if you can make Facebook itself safe to use within the enterprise? This is the realization that our customers and many others are coming to see. And this is where WorkBook provides enormous value to the organization.
Andrew,
Mostly a note to express how much I enjoy and value your blog. I’ve passed it along to dozens of people in my company, and posted it on my FB page. We are going down the E2.0/social path to explore how we might leverage them to improve the adoption of some enterprise and developer products we have. It’s fascinating, mostly a morbid fascination at this point – that is, how hard IT will block efforts at unstructured IT deployments.
Also, your links in this post to WorkLight are broken.
David
It’s not that “not interesting”. At least I got myself to finish reading it!
Actually, I did find it interesting. One of the questions I frequently see being asked (and usually slapped down) by CIO/CTO types is “how much do we leave open”, and “how much do we leave them (the users) play about with it (our beautiful platform;)”. Its sometimes hard for the CIO/CTO to figure out HOW to let people play with the system, and how this can be managed (sic).
We all know how PHP is vulnerable to attacks and Facebook uses PHP. Other then the benefits integration with other applications exposes us to hacks and attacks.
Max
First, Andrew thanks for your leadership on Enterprise 2.0 (E2.0). I’m an Enterprise Architect (EA) in Washington. DC with a background in complex systems. I hope E2.0 becomes an effective mechanism to bring what we’ve learned from complex systems theory into the mainstream and answer a few lingering questions currently facing EA practitioners on which we somehow seem stuck.
Second, and maybe some interesting stuff. Without additional information and as a reductionist, my view is that the debate here reveals an E2.0 anti-pattern. What is the relationship between E2.0 and EA ? What’s implicit in the debate centers around how cohorts arrive at HBS with not only branding and identity beliefs, but high expectations of what Larry and the folks in Cotting House can deliver. This is where EA can be a pretty good help in keeping Cotting House from becoming so cannibalized that Larry’s maintenance costs become unsustainable. One issue that should emerge in the follow up debate is how to develop a transition strategy and sequencing plan for E2.0 to EA technology adoption at HBS. This is a hard questions and HBS is in the best position to lead us all towards the answers. I’d like to hear how things go because if E2.0 does make it in DC more broadly than ONDI, we’ll be facing the same issues soon enough.
Third, your intuition regarding the Semantic Web (SW) well founded. Ironically, the SW is about the best chance we’ve had in years to improve mainstream information sharing for many of the same reasons E2.0 is so good. Unfortunately, its much less than what we need. That being said, hats off to Tim-BL & Co. We need to keep pushing that rock up the hill no matter how steep the incline. The crest of the hill is probably not a good target for E2.0 as much as an effective public policy with targeted private sector investment and public sector adoption as the Markle Foundation recommended a few years back. For the short term, we’ll see a swarm of very smart, creative and energetic folks form around this long standing and much loved (by me) issue.
Anyway, thanks again for your leadership on E2.0 !
“There are six defining characteristics of the work “place”- how clearly are they reflected in business software solutions today?
* A vision that defines the meaning of work;
* Actors : the managers, employees, partners and customers that produce work;
* Interactions : the events in which we sell and purchase products, ideas and services;
* Outcomes: the generated revenue stream
* Gateways : communication channels that integrate the workspace into local context, culture and organization ”
http://leeschlenker.wordpress.com/
Andrew -
First, I really enjoy your blog and always learn something by reading it. This post is really helpful as we are wrestling with how to handle our employees’ interest in FB in parallel with our concerns about information security. I will give this technology a look. Keep up the great work with your E2.0 leadership.
Ken