post

Romulan Attack Because of Microsoft Office

The Romulans attack the Federation for they can’t read the Peace Treaty sent to them in Word 2307 format… they only have Word 2303. A hilarious cartoon by Geek and Poke. Joke? Perhaps … or not.

Yesterday I attended a (so-called) Enterprise 3.0 event hosted by the MIT Club of Northern California. So-called, as nobody really used the term, other than the moderator, Sramana Mitra. The panelists politely put the title on their slides, and then distanced themselves from the concept, Google’s Jonathan Rochelle being most outspoken: “we did not even get to Enterprise 2.0, why 3.0 now?” (Update: read JR’s follow-up post).

That said, it was an interesting event, clearly focused on Software as a Service (SaaS). 3 of the 4 presenters came with PowerPoint decks – kudos to Microsoft’s Cliff Reeves who only had 1 slide. In the spirit of eating one’s own dogfood JR’s “presentation” was a public Google Spreadsheet.

Next came Captain Picard Sramana: her slides suffered the same faith the Federation’s Peace Treaty did: they were created in a different version, and could not be opened on the presenters’s laptop. Host Nicolas Saint-Arnaud made a heroic effort trying to download a converter, but failed, so Sramana could not show her presentation. This happened in a room discussing SaaS where at least two (well, one and a half) online presentation tools were represented: Google’s future presentation app by Jonathan, and the existing Zoho Show by Sridhar. With a Web 2.0 tool, there s no dependency on having the correct software version on your machine, there are no updates, patches (in fact there are, managed behind-the-scenes by the service provider) – your slides (data) are instantly available anywhere, anytime.

I somewhat wonder if this was an intentional ploy on Sramana’s behalf: after all we can talk all we want about the benefits of working on the Web, nothing delivers a punchline as forcefully as a publicly failed download/patch… or the Romulan nukes, for that matter. (Will they still use nukes in the 24th Century?)

(Side-note to anyone delivering presentations: don’t ever try to download and apply an upgrade publicly, on a projection screen. Murphy’s Law will apply)

Update: See Sramana’s Nuggets from the event, including the slides. She says it was not a ploy… (but I may just have given her an idea 😉 )

post

Enterprise 3.0: Where Is It Headed? – Interesting Panel with the Wrong Title

I’m not a big fan of the whole 2.0 /3.0 theme, but I have to accept the fact that Web 2.0 and related concepts have become commonplace, everyday terms that today we’re taking for granted. Enterprise 2.0, on the other hand is far more debated. Definitions range from loosely saying “Web 2.0 tools in the Enterprise” through Harvard Prof Andrew McAfee’s “Use of emergent social software platforms within companies, or between companies and their partners or customers” to MR Rangaswami’s much broader synergy of a new set of technologies , development models and delivery methods that are used to develop business software and deliver it to users.” Then we have a set of attempts to simply “get to the point”, without long academic debate, like lightweight software, or Meet Charlie, a simple yet effective slideshow that personalizes the story.

One thing there is agreement about is that there is no agreement – in terms of a definition, that is… but that does not prevent us from attending conferences like Enterprise 2.0 or Office 2.0, and more importantly, businesses from embracing Enterprise 2.0 to varying degrees. It is happening, whether we have a “final” definition or not.

However, I really don’t think we’re ready for Enterprise 3.0 – not now, not ever. There are quite a few articles on the subject, but they all come from the same author, Sramana Mitra (except for two old ZDNet articles quoting Shai Agassi and JP Rangaswami). Sramana has certainly “cornered” the market – except there really is no “market” if she’s the only one using the term. Her definition: Enterprise 3.0 = SaaS + EE. What’s EE? Extended Enterprise:

The modern enterprise is no longer one, monolithic organization. Customers, Partners, Suppliers, Outsourcers, Distributors, Resellers, … all kinds of entities extend and expand the boundaries of the enterprise, and make “collaboration” and “sharing” important.

Let’s take some examples. The Salesforce needs to share leads with distributors and resellers. The Product Design team needs to share CAD files with parts suppliers. Customers and Vendors need to share workspace often. Consultants, Contractors, Outsourcers often need to seamlessly participate in the workflow of a project, share files, upload information. All this, across a secure, seamlessly authenticated system.

Sounds familiar? Of course, back in the 90’s this is what we called (Extended) Supply Chain. I’m not sure we need to create another label just yet. But if and when something is so significant that it deserves a new name, let’s get a bit more creative … I’m with fellow Enterprise Irregular Thomas Otter, who humorously ranted:

  • The car isn’t called horse 2.0.
  • The lightbulb isn’t called candle 2.0
  • Fax (Facsimile) isn’t called letter 2.0

If we are so innovative in the 21st century, the least we can do is to think of some new terms that inspire. Think ROBOT, Television, Velcro, Radio, even scuba (Self-Contained Underwater-Breathing Apparatus) … If this stuff is really that innovative then it deserves a proper word.

Back to Sramana and “Enterprise 3.0”: next week she will be moderating a panel discussion of the MIT Club of Northern California, with the ambitious title: Enterprise 3.0: Where Is It Headed?. Excerpt from the event description:

Collaboration, wikis, blogs and social networking are new tools igniting the enterprise market. Service based models are emerging as alternates to desktop software and enterprise servers. In March 2007, Cisco acquired WebEx for $3.2 billion, stepping in with a splash in the enterprise collaboration space. Meanwhile, Google has assembled a whole suite of word processing, presentation, and spreadsheet tools and just acquired Postini, an email management company. Microsoft has been adding collaboration and knowledge management capabilities to its Windows Platform and just announced plans to offer Web-based versions of its applications. Then, there are exciting startups that are offering alternatives.

This panel will explore the impact of Web 2.0 on the prosumer i.e. the individual user in the enterprise and the evolution and integration of office tools, communication and collaboration technologies.

Sounds vintage Enterprise 2.0, if you ask me.smile_wink That said, I think it’s an exciting subject, and they will certainly have a first-rate panel:

  • Tom Cole, General Partner, Trinity Ventures
  • Cliff Reeves, GM, Emerging Business Unit Team, Microsoft
  • Jonathan Rochelle, Product Manager, Google Docs and Spreadsheets
  • Sridhar Vembu, Founder, CEO, Zoho / Adventnet last minute change: the event site now lists Tim Harvey, VP Planning, Webex, Cisco Systems instead of Sridhar Vembu.

Whatever we call it, I plan to be there. If you are reading this blog, chances are you’re also interested in these subjects, so if you happen to be in the Bay Area Wednesday evening, perhaps I’ll see you there. Here’s the registration page. (Warning: the form is way too long, asking for way too much information – vintage 1.0 stylesmile_omg)

Additional reading: Open Gardens, Portals and KM, Anne Zelenka, Luis Suarez, the FASTForward Blog, Read/WriteWeb, Chris Pirillo, Fake Steve Jobs smile_tongue , just to name a few…

Update (8/21): as much as I hate this 2.0-3.0 labeling, I like Don Dodge’s new formula: Web 2.0 = web app + 2 founders + 0 revenue

post

Web 2.0 in the Enterprise – Round …n.. (I can’t keep track)

Stowe Boyd picks up where Ben Metcalfe left off in Web 2.0 doesn’t work in the mothership, but… essentially recommending that Web 2.0 is best introduced in the Enterprise “in a satellite operation at arms length from the rest of your operation

While this is often the easy solution, I think a case can be made for the seamless mashup of process- and workflow-centric enterprise applications and the more creative, unstructured, collaborative tools like wikis.  Case in point is JotSpot’s integration with Salesforce.com based on the Appexhange. Granted their target is not the largest of enterprises, but another example I heard of at SAP’s annual conference is the SAP Help Desk wiki by  Socialtext targeting the entire SAP ecosystem.  In any case, I agree that spontaneous, project-focused use is how wikis will become adopted in the Enterprise, but at the same time I believe they should be a logical extension of any Enterprise system – SAP, Salesforce.com are starting to recognize, and I think the day when we’ll have both top-down (enterprise sale as part of the large package) and bottom-up (departmental initiative) penetration is not that far.

But then Stowe goes one step further, and this is where the trouble starts:

…the larger question — whether the enterprise would be more agile, more adaptive, and more of a survivor is it could somehow break away from the need for slow-to-change applications that span the needs of many departments, beholden to many but satisfying none — has not really been addressed by Ben or the others I am interviewing on the on ramp to CTC 2006….
My gut says yes. Enterprises would be better off if their IT departments could move to small, low cost, web-based apps that satisfy local needs — a project group, one campus in Denver, the marketing department in Japan — without having to subordinate local needs to corporate controls. The benefits of enterprise standardization are measured in the IT budget, but the true costs are distributed thoughout the enterprise: less collaboration in the research team leads to slower innovation, a less-thatn-intuitive UI for the sale staff in France leads to lowered sale numbers, and a heavyweight finance solution that slows down invoicing costs serious bank in collection time
.”

Oh, boy. When we’re talking about large multinational corporations, as Stowe does in his example, the primary benefit of standardization and integration is NOT measured in the IT budget. The key benefit is competitiveness, simply being able to conduct business.  Here’s a case study from my “previous life” when I was implementing SAP systems in exactly these types of companies: The Client, a major test and measurement equipment manufacturer had no real-time visibility of their available-to-promise inventory throughout their own plants accross the US and several countries in Asia and Europe.  It typically took them 3 weeks to be able to promise a delivery date to customers. Needless to stay they started to lose business. After the SAP implementation customers could receive the promised delivery date in real-time. For this company the implementation of the standard system was not an option, or driven by IT savings, it was the only way to stay in business.

As a matter of fact, prior to standardizing on SAP the individual plants operated exactly according to Stowe’s ideal model: each doing whatever they wanted, picking their own systems that simply did not talk to each other.

Web 2.0, collaboration is great, it has it’s place in the Enterprise, but so do those “ugly complex” transactional systems.  Don’t try to run your supply chain on a wiki

Update , more than three years later: Would You Manage CRM with a Wiki?

Tags: , , , , , , , , , , , , ,