Skip to content

{ Category Archives } Web 2.0

Architecture & Process: Pat Cappelaere

For my last session — I have to leave for the airport around the time that the roundtables start — I sat in on Pat Cappelaere of Vightel discussing workflows, Identity 2.0 and delegated authority using REST.

He showed how lightweight protocols like ATOM — rather than SOAP — can be used to allow the quick mashup of information in near real time. He spent quite a bit of time on the advantages of a RESTful approach (summary: it’s easier), and the nature of the basic commands (post, get, put, delete) for managing web-based resources.

Where identity comes into all this is that some resources that might contribute to a mashup could be behind some type of access control, and the source system can’t manage the identities of all of the people who might want to access the end product. Identity 2.0 allows for the delegation of authentication to a trusted provider, i.e., using your OpenID (from Yahoo or other providers) on other sites instead of creating a user account on that site directly. That looks after basic authentication, but there also needs to be some authorization or pre-approval of transactions, which is what OAuth has been created for.

He’s using the term workflow to mean (I believe) the steps to assemble and process various resources and services into a web application: a service orchestration of various resources on the web using lightweight protocols. To implement this, they’ve created a RESTful version of the workflow bindings defined by WfMC as WfXML.

This was interesting, but I’m not at all clear what it was doing at this conference.

IT360: Web 2.0 - Now and its future for business

Mike Fox of Brightlights, a recruiter serving small and medium-sized software companies, is giving a talk on Web 2.0 and business; I started out unsure of why a recruiter is talking to us about Web 2.0, and ended up pretty much of the same mind.

He started with some very basic concepts, like the original Web 2.0 meme map and the themes it contains, and discussed some well-known (and well-worn) Web 2.0 case studies, such as Proctor&Gamble’s crowdsourcing of research, and Barack Obama’s online campaign presence. He asked questions like "has anyone heard of the $100 laptop?", "have you ever seen Slideshare?" and "has anyone heard of the ‘long tail’?", which I think you’d have to have been living under a rock not to know about, but maybe I’ve been drinking too much of the Koolaid.

He moved on to talk about Web 2.0 in the recruiting world, including the use of information aggregation tools such as ZoomInfo. He spent some time talking about using LinkedIn as both a recruiting tool and a job search tool, although I tend to think that this audience is probably pretty aware of what LinkedIn does. He mentioned some other recruitment-focused search sites like Jigsaw, and then stepped us through how to use Google Advanced Search for finding more information about companies and individuals — again, a bit basic, particularly (I think) for this audience.

He went through how to apply Web 2.0 thinking to business, based on the different goals and expectations for different generations of workers. He’s definitely been reading too much Tapscott. He did look at how to apply Web 2.0 to some fundamentals of adding value to a business, such as SaaS as both a cost reduction technique and a channel for offering products to customers.

He considers sending a monthly PDF newsletter by email and using Skype for long distance to be part of how he incorporates Web 2.0 into his business, which is a bit sad, although he does use a SaaS recruitment management system. There’s so much more that could be done with Web 2.0 in recruitment for a small recruiter like him: collaboration on resumes and job postings via Google Docs; blogging to show thought leadership in recruitment and engage the audience instead of a static monthly newsletter in PDF; publishing job postings listed on his site via RSS; hosting a discussion forum for job applicants.

That’s it for my coverage of IT360; I have to get back to some real work for the rest of the day. The Google talk was definitely the highlight for me, although I did really enjoy making the Director General of Industry Canada squirm yesterday, too.

IT360: Social Networking for Business

I’m dropping in on a few sessions at the IT360 conference being held in Toronto this week — nice to be able to walk a conference for a change — and attended John Reid of CATA Alliance talking about the value of social networking for business. He’s a stand-in-the-audience sort of guy, and is standing about 4 feet from me, so I’m here for the duration. :)

He started with some pretty mainstream stats and information about social networks, such as a new blog being created every 2 seconds, then moved on to discuss the degree of risk that comes from publication and dissemination of information, starting with a bit of an obscure story about being threatened with a lawsuit for some information that he distributed in a spammy sort of fax operation several years ago up to how some companies are starting to ban Facebook access from inside the firewall.

He’s doing the presentation almost completely with audience participation; having first done an audience poll on whether we fell that social networks had high, medium or low value for business, he’s selecting people from each of the respondent categories to say why they feel the way that they do about social networking. We’re hearing about how social networks can be used to get closer to your customer, although this is dependent on the industry, the target audience and the company’s corporate culture. There’s a lot of old-school types in the audience, those who raised their hand for "low/no value"; more than one person said that they use no social networks at all, and these were people who appear to be considerably younger than me. One of them even referred to "this blogging thing" in a somewhat derisive tone. This is not, as Don Tapscott proposes, an issue of age; it’s an issue of culture and position. In fact, the most vocal supporter of social networking from the audience declared himself to be 59. There are a lot of self-declared skeptics in the audience who say that they’re going to wait and see what the value is; one person said that he could spend the 8-10 hours per week that he believes is necessary to maintain a Facebook presence; he has 70 contacts on LinkedIn but it’s never really come to anything; and he wonders what happens to all those blogs that have a lot of effort put into them but no one reads them. Get real: if you put effort into blogging about something that’s of interest to someone and put some effort into being a good citizen in the blogosphere, people will read it. This blog is proof.

The business owners who are speaking up really seem to be in command-and-control mode: one stated that they’re blocking Facebook because they’re concerned that employees will put confidential information on it; doesn’t he know that if he hires untrustworthy people, they’ll do that from their home computer, so that blocking Facebook at work doesn’t solve that problem? He also said that people will spend too much time on sites like this if they’re allowed to do so, but you have to consider that people do have to take breaks sometimes, and allowing them to read their personal email or check Facebook while they’re on a break is no different than allowing them to make a personal phone call on their break. If you have sufficient technology to block specific sites, then you likely have the ability to monitor the usage and raise flags if people appear to be abusing the privilege rather than just blocking things outright.

Keith Parsonage from Industry Canada (who is speaking later today) popped up and admitted that he can’t access Facebook or a personal email service like Gmail from his office, but that the federal government is on a campaign to hire young people. This is definitely going to come back and bite them, since people who expect to be able to access sites like Facebook and Gmail while on their break at work aren’t going to be happy in an old-school corporate environment where they’re treated like irresponsible and unprofessional children.

Reid is really trying to get to the key points of how to incorporate social networking into business in terms of outward-facing communications, such as blogs; it’s unfortunate that this turned into too much of a discussion of who does and doesn’t use Facebook, and whether they’re allowed to do so at work.

Unfortunately, there’s no free wifi at the convention centre; in fact, the only available wifi is that geared for exhibitors and priced at an extortionate $395 for access for a single computer. I grabbed a couple of 30-minutes online passes in the press room, but I’m tempted to boycott it just so that MTCC doesn’t get the conference organizer’s money for this.

Tagged

Webinar: Applying Web 2.0 to your business challenges

A bit late notice: today at 1pm Eastern, there’s a webinar on applying Web 2.0 to your business challenges, featuring Don Tapscott, Jeremiah Owyang and Robert Scoble.

This is sponsored by Cisco, and will include a demo of their new WebEx Connect collaboration workspace. From the event description:

Traditional models for management and problem solving are changing. Thanks to the advent of wikis, blogs, social networks, and other Web 2.0 tools, the ways organizations foster collaboration and promote innovation are undergoing profound change.

This 60-minute video Webcast explores the new paradigm created by the Web 2.0 phenomenon and shows you how this model can be applied to virtually any business process. Learn how you can use Web 2.0 applications to solve technical challenges, promote business innovation, uncover new product or market opportunities, and make employees much more productive.

There will be interactive Q&A with the participants during the webinar.

Should connecting on a social network = signing up for marketing blasts?

When I connect to someone on a social network such as LinkedIn or Facebook, I expect to be connected to them personally, not to their company’s marketing machine. Yes, I know, it’s common to farm our online contact lists for potential customers, but I found this recent email to be a bit over the top:

As a Linked In connection to Dion Hinchcliffe, you are probably aware of Dion’s internationally acknowledged thought leadership on Service Oriented Architecture (SOA), Web-Oriented Architecture (WOA) , and Web Services.  Given the growing demand for his subject matter expertise, Dion felt it important that Hinchcliffe & Company’s expand its capabilities to include world class consulting on these subjects.  To that end, Dion has assembled a team of highly skilled technical architects, personally educating them on his own strategic and operational methods for successful delivery of SOA/WOA and Web Services Solutions.

On behalf of Dion, I am writing to announce the formal launch of Hinchcliffe & Company’s SOA/WOA and Web Services Practice.  I will be following up with you by phone . . . but in the meantime, if you have an immediate need for this type of expertise, feel free to contact me directly.  We have talented, fully trained people ready to go.

I have never heard of the person who wrote this letter (although apparently she works for Dion), and although when I connected to Dion I assumed that I would likely be put on some of his mailing lists, but I never expected one of his people to explicitly admit that she breached the privacy of one of his social networks in order to feed the marketing machine.

Forrester Day 1: Rob Koplowitz

Lots of choice in the breakout sessions, but I’ve decided on Rob Koplowitz (who works with Connie Moore) on Web 2.0 and Social Computing in the Enterprise. The official statement:

Enterprise Web 2.0 can drive new efficiencies, but it needs to be approached like any new technology coming into the enterprise.

He had a good slide on how Web 2.0 changes group dynamics, from reviewed repository (predefined contributors and reviewers with a central point of communication) to facilitated community (clusters of communications with a facilitator in each cluster) to social networks (unstructured peer-to-peer communications).

He made a distinction of four types of social networking technologies: “listen to me” (blogs), “listen to us” (wikis), “find people like me” (tagging, profiles, social networks, virtual worlds) and “find stuff I need” (tagging, RSS feeds). He then went on to discuss which of these adds the most value within an enterprise based on research that they’ve done; after instant messaging, which was really just added in as a benchmark, RSS feeds came in as next most useful, which doesn’t really surprise me give what I’ve been seeing in the past months in the Enterprise 2.0 space. What happens, then, is a combined environment of a corporate information workplace with external sources of information, mashed up using various tools to provide value to users.

He referred to RSS as a lightweight integration fabric within organizations, which is a great characterization, and showed it on a spectrum of enablers that also included mashups, SOA and BPM.

Koplowitz then looked at the risks of Web 2.0 technologies within the enterprise, such as privacy and security; note that he’s talking about using consumer Web 2.0 technologies that are available via SaaS on the public internet, whereas there’s a ton of new Enterprise 2.0 solutions that are sold as on-premise, inside-the-firewall solutions rather than risk an improperly-hosted solution. There’s also many reputable Web 2.0 vendors who don’t do risky things with your data, or not any more risky than your own data center does now. He gave a scary-sounding example using Quechup, a recently social networking disaster that decided to spam your entire address book without permission and was quickly outed and shamed on the internet; this information came out with a few short days of this starting, and if the person involved had just been a bit more careful about watching the internet buzz on Quechup rather than jumping right in with their corporate address book exposed, then this would have been a non-story.

His recommendation is not to stop people from using social networking site, but to be cautious and appropriate about what they put out there, and to audit their behavior to ensure that they’re not violating corporate confidentiality. As he points out, Gen Y’s (18-26 years old) are the target hiring market for many companies these days, and they’re using these tools as creators of content as well as participants. However, the higher-level management in most companies, smack in the middle of the boomer years, are much less likely to participate and hence less likely to fund any related efforts.

Forrester will be publishing some research very shortly about vendors in the Enterprise Web 2.0 space, although he didn’t give us much of a sneak preview except to name a few vendors both in the Web 2.0 space and the enterprise space (BEA, Microsoft, SAP, IBM, Oracle), and predicting a collision. Traditional vendors are following the old-style release and adoption cycles, which may not play very well with the faster iterations that will come from the SaaS offerings from the Web 2.0 space; however, those traditional vendors are also in the position to just start bundling their Enterprise 2.0 offerings into their standard offerings (WebSphere Portal as a mashup platform, anyone?) to encourage adoption with their existing customers. There’s a new breed of vendors, however, that have deep enterprise roots and the agility of the hair-on-fire Web 2.0 vendors, that are likely to give the big guys a run for their money. Most likely, any organization is going to use a combination of vendors, both traditional enterprise vendors (who will be favored in the long run, based on history) and the new vendors (who are likely to be acquired by the big vendors). You’ll also see a combination of technologies, for example, ad hoc processes in a wiki with more structured processes in a BPM system linked to that.

His summary:

  • Enterprise Web 2.0 is part of the Information Workplace fabric
  • Corporations are getting value today from Enterprise Web 2.0
  • Users are getting social without appropriate guidance
  • Process and content need to be managed
  • The investment decision includes change management.
  • The vendors are colliding in this space.

There was an interesting discussion during the Q&A on the place of Google in the environment (Koplowitz thinks they have to solve their security issues first, such as not transmitting data to and from Google spreadsheets in clear text).

He points out that for many organizations that have a significant portion of younger workers, especially in technology-heavy industries, there is no way to put this genie back in the bottle; organizations have to deal with this, and “just say no” isn’t an alternative.

Web apps are great, until you get on a 9-hour flight

From Dion Hinchcliffe’s Facebook updates earlier today:

Dion Hinchcliffe is getting on a plane from Europe to SFO. He’s really starting to feel the need for Web apps that run offline.

As someone with over 35,000 flight miles on the clock so far this year, I feel your pain.

Enterprise 2.0 Camp: Anthony Williams

I’m at Enterprise 2.0 Camp today, and Anthony Williams is the first breakfast speaker. He’s giving the Wikinomics lesson in short — how we’re undergoing an economic transformation because of the collaborative nature of value creation that’s happening due to both Web 2.0 internet applications and social networking principles being introduced into the enterprise. He covers the four basic principles: peering, openness, sharing and acting globally; since I read the book fairly recently, this is all still pretty fresh in my mind and it’s great to hear it from the author.

I like his discussion of openness, where he shows the move from companies hiring all their own talent internally, to outsourcing of some business processes, to a true open market for talent. This is a critical area of overlap between BPM and Enterprise 2.0, since BPM has been enabling business process outsourcing and will continue to be a key technology for supporting an open market: if you can find a grope outside your organization, whether local or a half a world away, that has superior skills to deliver some aspect of your business process, you need to be able to easily include them in your value chain. He also talks about organizations creating an ecosystem for others to add value to their base products: everything from SalesForce.com’s AppExchange to Facebook’s new application platform. In some cases, there’s a more active collaboration with other companies; in others, it’s the prosumer doing their own thing and giving it back to the community.

He talked about Science 2.0 in the context of sharing, with the Human Genome Project and other similar projects pooling data and computing power. Open source development also falls under the sharing part of wikinomics, with companies like IBM contributing developers to Linux development that is turned back to the community. It’s not completely altruistic: a more robust Linux community benefits IBM because they sell more hardware and services to run it on, and the amount that they contribute to Linux development is about 1/10 of what they would spend developing and maintaining an equivalent proprietary operating system (say, OS/400).

Williams described how to get started with Enterprise 2.0 internally, through the use of internal blogs and wikis, which put me in mind of the Avenue A|Razorfish intranet wiki that I heard about last week at the PCC conference. It’s a good way to get people used to the concepts, while at the same time working out the governance issues before any of this information is exposed on the public internet.

Tom Purves put today together mostly as an unconference, with a few minor changes: first, there’s some “name” speakers at breakfast, and second, we all had to pitch in $50 for the day, but we’re at the Toronto Convention Centre so I wouldn’t expect that we’d be getting everything for free. Still a great deal, and I’m looking forward to the rest of the day.

Shared Insights PCC: RSS in the Enterprise

My session on the changing face of BPM went pretty well, except for one guy who said that I was wrong about pretty much everything :)

Today finishes early, so I’m at the last breakout session, Colin White discussing using RSS in the enterprise, and the broader subject of using web syndication to deliver content to users. It’s a bit distracting because he has exactly the same English accent as someone on my wine club board; I keep looking up and expecting to see my friend Bernard (who doesn’t even know how to spell RSS) at the front of the room.

White is looking at this from an architectural rather than implementation viewpoint, and focussing on enterprise rather than internet data sources: a standardized and lightweight XML-based integration protocol. He spent an undue amount of time explaining generically what RSS feeds are and how internet syndication works in various RSS readers; is there anyone in this fairly technical portal-savvy audience who doesn’t already know all this? He then moved on to the differences between RSS and Atom and the specific tags used in an RSS feed; 30 minutes into the presentation, we still haven’t yet seen anything to do with RSS in the enterprise.

Eventually he does get to enterprise uses of RSS; no surprise, one big use is to have it integrated into a business portal, although the XML can also be consumed by various search tools, including ETL to capture the data and load it into a data warehouse or content management system — something that I hadn’t thought about previously, but can be done with tools like Microsoft Integration Services. He points out how RSS is one piece in the integration puzzle, which is essentially what I’ve been saying with respect to using RSS feeds of process execution data as one way of providing visibility into processes.

White covers the different types of feed servers: external, internal, and hosted SaaS. Interestingly, NewsGator is now in all three areas, with both an enterprise server and an on-demand solution that can aggregate and syndicate internal as well as external content, as well as their well-known external internet version. That gives a variety of ways that a feed server can fit into an enterprise environment: either an external feed server providing only the external feeds, or an internal/hosted feed server that can handle both internal and external feeds. This has the advantage of reducing network traffic, since the feed server caches the feeds, as well as providing filtering and monitoring of content that is consumed.

I’m really aware of a push to give PCC a very Enterprise 2.0 flavour; having not been at any of the previous PCC conferences, or even the first half of this one, I don’t know if this is a new bandwagon that they’re leaping on, or something that’s a logical progression of where this conference has been in the past.

Shared Insights PCC: AvenueA|Razorfish intranet wiki

I skipped this morning’s taxonomy/folksonomy smackdown featuring Seth Earley and Zach Wahl — I just wasn’t up for that much testosterone this early in the morning – and went to the best practices track to hear about how AvenueA|Razorfish implemented their internal wiki. I’m speaking next, so if this session isn’t sufficiently riveting, I’ll duck out early to review my notes.

Donna Jensen, their senior technical architect, took us through how they use a wiki as an intranet portal. She spent some amount of time first defining wikis and discussing benefits and challenges, particularly when used inside the firewall. She made a crack about how Ph.D. dissertations will be written on many of these points, which isn’t that far from the truth: things like encouraging active versus passive behaviour. And, although she claims that they’re breaking down behaviours tied to organizational silos, she admitted that no one can comment on the CEO’s blog although all others are open territory. At some point, even the top level executives have to learn that if they’re going to commit to Enterprise 2.0, it has to permeate to all levels of the organization: no one should be exempt.

The platform that they used was MediaWiki (the software used to create Wikipedia) on a standard LAMP stack, giving them a completely open source base. They also use WordPress for internal blogs, maintaining the commitment to open source. Although they did do some customization, particularly in terms of creating templates such as project pages, they took advantage of many freely-available third-party extensions for functionality such as tag clouds, calendaring and skins. They use Active Directory for security, and allow access only internal or VPN access: no external access or applications.

AA|RF put in the wiki with only a technical VP and a part-time intern, pretty much out of the box, and found that it wasn’t adopted. They did another cut with Jensen as technical architect (part-time) and a couple more interns, and arrived at their current state: no project management oversight, no content management system, and no creative designer, with the whole thing implemented in about 2,000 person-hours. As a web technology consulting company (although with little Web 2.0 experience), they can get away with this, but you may not want to try this one at home. They used agile scheduling, and eventually brought in some rigorous QA. Jensen feels that their only real mistake was not bringing in a create designer earlier, since the wiki is apparently pretty technical looking. They haven’t yet put a WYSIWYG editor so everyone still needs to work in WikiText, which is likely a bit of a barrier for the non-techies.

Jensen talked about a few byproducts of the wiki adoption, such as the incremental upgrade model that tends to come with open source or SaaS products, rather than the monolithic (and often disruptive) upgrades of proprietary software. She also talked about how many IT departments won’t use open source because it makes them unable to turn to someone who is compelled to help them — in other words, they have to take on the responsibility of finding a solution themselves. Another byproduct is the shift towards open source, and the savings that they can expect by replacing some of their current software platforms and their hefty maintenance fees with open source alternatives.

In their wiki environment, any kind of file can be uploaded, all pages (except the home page) are editable by everyone, and any content except client-confidential information can reside there. I really have to wonder how this would work if they upload a massive number of files: at what point do you need to add a content management system, and how painful is it going to be to do that later? Their wiki home page shows del.icio.us and Flickr feeds, internal blog feeds, Digg items and recent uploaded documents. One audience member asked if that meant that if anyone in the company tagged a public web page, that it would be included on the home page; there was general shock around the room and wonderment that you could do this without having some centralized body approving such content before it was surfaced to the rest of the company. I tried not to laugh out loud; is this such a radical idea? Obviously, the last year of being immersed in Web 2.0 has changed me, and I start wondering which of these things that I would adopt if I were still running a 40-person consulting company. As the session goes on, the same question about how user tagging on the internet drives their intranet home page keeps coming up from the audience over and over.

What I found interesting (and I’m probably blowing their whole game by publishing this), is that they’re using public Web 2.0 tools to feed part of the home page: if something is tagged AARF on del.icio.us or Flickr, it shows up there. For Digg, however, you have to be a friend of AARF to have your items show up. Jensen said that she’ll be changing the AARF tag to something unguessable, although if you know how to track items and users through del.icio.us or Flickr, it wouldn’t be that difficult to figure out their new tag. She also said that they had run some analytics on whether these tags gave away any secrets about what they’re currently researching, and found that the mix is too varied for any patterns to emerge.

The wiki is a portal in a very real sense, which was a bit of a revelation to me: I didn’t previously think of wikis as portals. Everyone has their own people page which they can format and populate as they wish, and which can include their recent file uploads and blog postings. On any page, adding a “portlet” is just a matter of copying and pasting a snippet of PHP code, including copying snippets of code such as the <embed> code provided by YouTube for every video on its site.

They’ve done some cool things with blogs as well, such as having mailing lists corresponding to blogs, and sending an email to that mailing list will auto-post it as a blog entry on the corresponding blog.

Jensen had some great ideas for wiki adoption, often centred around “wikivangelists” getting out there and helping people. I especially like the idea of the “days of wine and wikis” events. :)  And they’re getting some great adoption rates.

I had to leave just before the end: she was running 7 minutes overtime and I had only 15 minutes between sessions to get to my own room to set up. It was hard to tear myself away, however; I found both Jensen’s presentation and the audience feedback to be riveting.

Shared Insights: Two-Day Wrap-Up

Apparently there was no wrap-up session yesterday, so the last session today wrapped up the past two days. Colin White, who has been running this conference for 8 years, was joined by three of his regular presenters: Shawn Shell of Consejo, Tony Byrne of CMS Watch, and Zach Wahl of Project Performance. The discussion was pretty open; I’ll try to attribute to the correct person as I document it.

In looking at what has changed at the conference recently, White found that 2/3 of attendees were building external-facing rather than internal-facing, which he feels to be influenced by Web 2.0. Shell found the audience to be more technical and tactical, and very focussed on building portals to connect with customers and employees. Byrne commented on how layered that portals are becoming, sometimes with several portal products being used simultaneously, and how the sheer diversity of integration technologies is making a more complex portal ecosystem. He feels that many organizations are out-growing some of the lightweight tools provided by portals, such as document management, and thinks that traditional portal vendors are having problems figuring out how to do Web 2.0 in their products. Wahl mentioned a higher caliber audience (by which it appears that he means “more technical”, however frightening the implications of that statement), and sees that the outward-facing portals that are being developed provide a stronger tie-in to ROI.

They then moved on to audience questions, and I can’t attribute the responses to any of the four participants.

Q: How are organizations using blogs?

A:

  • Attend the Razorfish session tomorrow for a case study. [I did]
  • It’s still a “cautious” activity for organizations, and is often still a top-down corporate communications “fake blog” from C-level executives rather than true blogs.
  • Blogs are useful for technical organizations [I scratched my head over that one, although I admit that one of the most successful organizations that I've seen using blogs internally is IBM]
  • Many people inside corporations “don’t have anything to say that’s universally consumable”. [This statement made me cringe; it totally misses the point of blogs]
  • A corporate ethos of content sharing can provide the right environment for blogging.

My conclusion: half of the 4 speakers don’t get blogging.

Q: How much of Web 2.0 is hype versus reality for the enterprise?

A: “There’s some organizations for which this isn’t going to work”. [The speaker quite erroneously equated Web 2.0 in the enterprise with publishing corporate content on the public internet]

Q: What are the future directions in PCC?

A:

  • There’s an increasing diversity of products rather than consolidation in the market, leading to more competition.
  • Major vendors, such as Oracle and BEA, are leapfrogging technologies to meet new standards and stay competitive.
  • The dynamism in PCC right now is in the add-ons, such as BPM, rather than the underlying portal technology. [This resulted in a specific discussion about how BEA's BPM is driving portal sales, although I'm not sure that's true]
  • Portal vendors are moving into the add-on market to take more of the enterprise pie.

There was also a discussion about getting started with search and taxonomy: for example, using the Google search appliance as a starter for search/taxonomy, and the need for a simple start to taxonomy in particular. We finished with a brief discussion about the perceived dilemma of SharePoint proliferation: is it out of control or a necessary state of departmental document collaboration?

TUCON: Technology Buzz Panel

Next up in the general session is the technology buzz panel, where “journalists, analysts, and industry experts square off on buzzwords of the day”. The moderator was Gary Beach of CIO Magazine, with panelists Frank Kenney of Gartner, Jason Maynard of Credit Suisse, Rob Strickland of T-Mobile USA, and Aaron Ricadela of BusinessWeek. Their initial goal is to eliminate four tech buzzwords (one per panelist):

  • Maynard picked “Web 2.0″, apparently not only because he thinks that it’s a bad term but because he doesn’t like social networking. There was discussion around the stage: Kenney railed against the term Web 2.0 but then used the ever-overused “paradigm shift”; Strickland said that he thinks there’s too many bugs in Web 2.0 and he’s waiting for 2.0.1; Ricadela commented on the new business models coming out of this, although he didn’t use the term “Bubble 2.0″.
  • Strickland picked “the business”, in the context of the dichotomy between IT and the business; as a CIO, he sees himself as an integral part of the business. I wonder if T-Mobile’s business users feel the same way; Maynard said that he felt that his IT department was actually a detriment to productivity sometimes, and admitted to using his own MacBook Pro and Gmail (interestingly enough, a Web 2.0 application) because IT wasn’t focussed on some of the business requirements. Kenney and Ricadela both talked about aligning IT and business, which of course just points out that the divide does exist.
  • Ricadela picked “business process management”, because he believes that it’s become a catch-all term for anything to do with business improvements enabled by technology. He blames the analysts and vendors for the confusion: given that Gartner helped to promote this term in its infancy and created a tremendously confusing landscape that in turn allowed vendors to promote everything as BPM, I’d have to agree to a certain extent. Kenney feels that the term BPM is overused but should still exist; Maynard doesn’t appear to understand the distinction between BPM and packaged applications.
  • Kenney picked “enterprise”, saying that it’s not used consistently and is often just applied as a marketing buzzword: sometimes it means “within the four walls of a company”, sometimes it relates to scalability or other features of a system. Maynard points out that adding the word “enterprise”  to a software product allows vendors to charge more it, and thinks that it applies only to large companies.
  • Beach finished up by picking “virtualization”, which I identified yesterday as potentially just being an overused buzzword, so I’d have to agree.

They moved on to a discussion of several magazine headlines: “Is your company fast enough”; “No future in tech?” (which veered sharply into American protectionist rhetoric); various open source headlines (Maynard pointed out that open source is fundamentally changing the software industry, even those companies that are not open source); software as a service (nothing new here); and finally, can you trust analysts’ opinions given that they’re all sleeping with the vendors.

They finished with a lightening round with 30-second opinions on Web 2.0, gigabit everywhere, SOA, AJAX, and the future of enterprise applications.

All in all, a more entertaining panel than I’ve seen for a while.

The New Software Industry: Investment Opportunities Panel

Jason Maynard of Credit Suisse moderated a panel on investment opportunities in the new software industry, which included Bill Burnham of Inductive Capital, Scott Russell (who was with two different venture capital firms but doesn’t appear to be with one at this time, although his title is listed as “venture capitalist”), and Ann Winblad of Hummer Winblad Venture Partners.

This was more of an open Q&A between the moderator and the panel with no presentation by each of them, so again, difficult to blog about since the conversation wandered around and there were no visual aids.

Winblad made a comment early on about how content management and predictive analytics are all part of the collaboration infrastructure; I think that her point is that there’s growth potential in both of those areas as Web 2.0 and Enterprise 2.0 applications mature.

There was a lengthy discussion about open source, how it generates revenue and whether it’s worth investing in; Burnham and Russell are against investing in open source, although Winblad is quite bullish on it but believes that you can’t just lump all open source opportunities together. Like any other market sector, there’s going to be winners and losers here. They all seem to agree, however, that many startups are benefiting from open source components even though they are not offering an open source solution themselves, and that there are great advantages to be had by bootstrapping startup development using open source. So although they might not invest in open source, they’d certainly invest in a startup that used open source to accelerate their development process and reduce development costs.

Russell feels that there are a number of great opportunities in companies where the value of the company is based on content or knowledge rather than the value of their software.

SaaS startups create a whole new wrinkle in venture: the working capital management is much trickier due to the delay in revenue recognition since payments tend to trickle in rather than be paid up front, even though the SaaS company needs to invest in infrastructure. Of course, I’m seeing some SaaS companies that are using hosted infrastructure rather than buying their own; Winblad discussed these sort of rented environments, and other ways to reduce startup costs such as using virtualization to create different testing environments. There are still a lot of the same old problems however, such as sales models. She advises keeping low to the ground, getting something out to a customer in less than a year, getting a partner to help bring the product to market in less than two years. As she put it, frugality counts; the days of spending megabucks on unnecessary expenses went away in 2000 when the first bubble burst, and VCs are understandably nervous about investing in startups that exhibit that same sort of profligate spending.

Maynard challenged them each to name one public company to invest in for the next five years, and why:

  • Russell: China and other emerging markets require banking and other financial data, which companies like Reuters and Bloomberg (more favoured) will be able to serve. He later made comments about how there are plenty of opportunities in niche markets for companies that own and provide data/information rather than software.
  • Burnham: mapping/GPS software like Tele Atlas, that have both valuable data and good software. He would not invest in the existing middleware market, and specifically suggested shorting TIBCO and BEA (unless they are bought by HP) — the two companies whose user conferences that I’m attending this week and next.
  • Winblad: although she focusses on private rather than public investments, she makes Amazon is a good bet since they are expanding their range of services to serve bigger markets, and have a huge amount of data about their customers that allows them to . She thinks that Bezos has a good vision of where to take the company. She recommends shorting companies like CA, because they’re in the old data, infrastructure and services business.

Audience questions following that discussion focussed a lot on asking the VCs opinions on various public companies, such as Yahoo. Burnham feels that Yahoo is now in the entertainment industry, not the software industry, so is not a real competitor to Google. He feels that Google versus Microsoft is the most interesting battle to come. Russell thinks that Yahoo is a keeper, nonetheless.

Questions about investments in mobile produced a pretty fuzzy answer: at some point, someone will get the interface right, and it will be a huge success; it’s very hard for startups to get involved since it involves them doing long negotiations with the big providers.

Burnham had some interesting comments about investing in the consumer versus the business space, and how the metrics are completely different because marketing, distribution and other factors differ so much. Winblad added that it’s very difficult to build a consumer destination site now, like MySpace or YouTube. Not only are they getting into a crowded market, but many of the startups in this area have no idea how to answer basic questions about the details of an advertising revenue model, for example.

Burnham had a great comment about what type of Web 2.0 companies not to invest in: triple-A’s, that is, AdSense, AJAX and arrogance.

Winblad feels that there’s still a lot of the virtualization story to unfold, since it is seriously changing the value chain in data centres. Although VMware has become the big success story in this market, there are a number of other niches that have plenty of room for new players. She also thinks that companies providing specialized analytics — her example was basically about improving financial services sales by analyzing what worked in the past — can provide a great deal of revenue enhancement for their customers. As a final point on that theme, Maynard suggested checking out Swivel, which provides some cool data mashups.

Okay, now I am starting to get paranoid…

After several weeks of receiving emails saying “Good news! We expect to have your account activated within the week.”, I received this:

Blueprint declined again

Is there something that Lombardi doesn’t want me to see?

BPM and Enterprise 2.0 — what a blast!

I just had a great time hosting the BPM and Enterprise 2.0 panel with Phil, Phil and Ismael. These three have some radically different viewpoints, which made for a lively discussion (insert graphic of me dressed as a lion tamer, complete with whip and chair).

My favourite quote from the panel, from Phil Larson when speaking about mashing up BPM data: “BPM *is* a mashup”.

And from Phil Gilbert, in an email note afterwards: “Awesome… most fun I’ve ever had on a webinar.  OK, OK, that’s a low bar, I guess… BUT it was fun.”

The replay should be available soon at the same link if you missed the live version.

More on the Enterprise 2.0 conference

I’m now confirmed to head to Boston in June for the Enterprise 2.0 conference, where I’ll be doing my usual live-blogging coverage under this tag. More on this as we get closer to the event.

BPM in Action panel

If you enjoyed the free-for-all discussion at the end of the webinar that I moderated with Colin Teubner and Jim Rudden a few weeks back, you’re going to love the panel that I’m hosting next week on BPM and Enterprise 2.0 as part of the BPM in Action series. It’s not sponsored by a vendor, so I was able to pick whoever I wanted on the panel, and there will be no vendor product pitches or slides — just an interactive discussion between the four of us. Get over there and sign up.

Here’s the description that I wrote for it:

As Web 2.0 technologies and concepts advance in the consumer world, they are also impacting enterprise software as users change their expectations of how software should behave. This “Enterprise 2.0″ movement is impacting BPM software in a variety of ways ranging from platforms to user functionality to integration. This panel will explore the following:

  • How Web 2.0 is becoming Enterprise 2.0
  • BPM platform changes: the impact of browser-based tools and software as a service
  • New tools and techniques for improving user participation in process design and execution
  • New ways of “mashing up” BPM data with internal and external data

I picked three people to join me whose opinions I value and who I think will be interesting in this format: Phil Gilbert of Lombardi, Phil Larson of Appian, and Ismael Ghalimi of Intalio. They’re all very opinionated and all have a stake in the Web 2.0/Enterprise 2.0 space: Lombardi’s very cool Web 2.0 Blueprint release for widespread collaboration, Appian’s kick-butt browser-based process designer for serious Enterprise 2.0 work in a browser, and Ismael’s involvement in radical office 2.0 and BPM 2.0 ideas.

We only have 45 minutes so I’m going to have to keep a tight rein on the conversation to cover off our proposed subject areas, which could be difficult because I inadvertently invited two Phils to the panel (”Phil, pipe down! No, not you Phil, the other Phil!”). No “call me Ishmael” jokes, I’ve heard them already.

By the way, congratulations to Ismael and his wife on their new arrival. No wonder he wasn’t at the Gartner conference.

Waiting for Blueprint

In the world of Web 2.0, there’s always some hot new service that you have to be invited to join, then you get on a waiting list, then (after a while) you finally get an account. Remember when Gmail was launched, for example? This is a brilliant idea from a marketing standpoint, because it creates a lot of buzz around the service, with everyone who gets an account bragging about it, and everyone who doesn’t, wishing that they did. From a support standpoint, it also makes sense: you can’t just put 10 million people on your service the first day of beta, because it will crash, and you’ll look bad.

The current hot Web 2.0 account to have is Joost, an interactive online TV service brought to you by the two wunderkids who created Skype — I see requests for Joost invitations, which apparently only come from those already on Joost, flying around the Toronto tech community.

The second hottest new Web 2.0 account to have is Lombardi’s Blueprint (okay, maybe I’m exaggerating slightly), and I’m still in that unhappy “waiting list” phase. However, their bot still remembers my name, because it sent me an email this morning to tell me that it expects to complete my account setup soon…

Enterprise 2.0 conference in Boston

CMP’s Enterprise 2.0 conference in Boston on June 18-21 has opened up for registration. Topics include the changing role of IT (presumably as it becomes more commoditized and outsourced), creating a culture of collaboration, consumerization of the enterprise and others. Andrew McAfee (inventor of the term “Enterprise 2.0″), David Weinberger (co-author of The Cluetrain Manifesto) and Don Tapscott (co-author of Wikinomics) are all keynote speakers.

I’m very interested to see how Web 2.0 extensions to enterprise applications (like Blueprint) are covered in the conference, as opposed to the use of social software such as blogs and wikis within the enterprise: the two faces of Enterprise 2.0.

Naked Process Modelling with Lombardi

“Naked blogging” is a term that’s applied to living your life transparently on the web through your blog and other social media, like Flickr, del.icio.us, Skype, LinkedIn, Library Thing and Facebook. Most of my friends around my age (which, as you can tell from many of my online profiles, is 46) are appalled at the amount of information that I expose out there, although the younger crowd that I hang with at TorCamp see it as perfectly normal, and I truly believe that if you’re going to get benefit from the network effects of Web 2.0, you need to contribute every bit as much as you expect to get back.

Two weeks ago, when I had a chance for a preview of Lombardi’s new Blueprint Web 2.0-like, software-as-a-service process modeller, my first reaction was “Cool! Naked process modelling!” After all, if you could model your processes online and invite people from within or outside your organization to collaborate on the design of those processes, wouldn’t you expect to see some benefit from that collaboration?

Blueprint addresses some of the issues seen in current process modelling tools: too much complexity for the casual user, and too little ability to collaborate. They call it “process discovery” rather than process modelling, host it as software-as-a-service, and let you get started with a free version (limited to one process and two users) to try it out before you spring for the monthly subscription. Just go to the site, start sketching out your process, then invite others to participate in the design. Like a wiki, everyone who you invite to collaborate on your process can make edits, and you’ll see their edits right away — a true shared whiteboard paradigm. Last September, I used the term “process wiki” in a post and at a couple of conferences where I was speaking, and that’s pretty much what Lombardi has done here.

They’ve also integrated presence into the application using the Google Talk instant messaging client: you can see if your process collaborators are online (notice the “4 Other Users Viewing” indicator in the top right of the first screenshot below), and chat with them through Google Talk. You can also use your Google Talk buddy list to invite people to join the collaboration. As a big Skype user, I’m hoping that they add other IM clients eventually.

Given what I’ve been doing lately around Enterprise 2.0, and seeing how Web 2.0 impacts BPM, this is one of the most exciting things that I’ve seen in BPM for quite a while. I must disclose that Lombardi is a client of mine, but I’d be saying the same thing even if they weren’t.

The visual paradigm is that of outlining a process by specifying the main high-level activities, then the sub-activities within each activity. In fact, you see both the flow diagram and the outline view:

Blueprint outline view

Notice anything weird about this screenshot? That’s right, it’s taken on a Mac. In fact, the Lombardi product manager who gave me the demo came into the meeting room toting his MacBook, which was not something that I was expecting to see. I’ve also seen it on Firefox on Windows. What better way to demonstrate platform independence? The Web 2.0 style interface is very slick, and there won’t be much of a learning curve for anyone who is comfortable with other web-based applications.

You can then specify a lot more detail for the process, including participants, inputs and outputs, impact analysis information such as potential failure points and likelihood of occurrence (very Six Sigma-like), and documentation.

You can also drill down into a more detailed BPMN view of the process for detailed workflow modelling:

Blueprint BPMN view

You can generate a PowerPoint presentation from the process model, which includes all of the additional parameters specified, for presenting the business case of the process further up the management chain. The demo that I saw generated a 60-page PowerPoint presentation with every possible bit of detail; I think that the problem would be cutting it down to size rather than the usual problem of having to find information to add to the presentation.

Once the collaboration has gone as far as it can, the process model can be exported to Lombardi’s TeamWorks, using (soon-to-be-released) BPDM as the serialization format — with Lombardi’s CTO chairing the BPMI steering committee at OMG, which oversees the BPDM standards, this isn’t a big surprise. You can even round-trip the processes from TeamWorks back to Blueprint when they need another round of collaborative design.

I think that their pricing is too high — $500/month for 10 users, whereas Salesforce.com is around $165/month for a 10-user team, and is currently discounted to half of that — but that will sort itself out in the marketplace. I suggested that their free version be ad-supported, much like the freemium business models of other Web 2.0 applications like Flickr and LinkedIn; I got a few weird looks from around the table at that point, but who knows, I may have put a bug in someone’s ear.

They are almost certainly going to have requests from companies to host the application on internal servers rather than Lombardi’s software as a service, although the success of Salesforce.com (especially in maintaining privacy of data) means that there’s a lot of companies out there are that starting to trust the SaaS model. Looking in a completely different direction, I would love to see Lombardi make Blueprint open source, which would drive collaborative process modelling into places that they never imagined. Although it could negatively impact Blueprint revenue — it’s still possible to have revenue-generating open source, it just requires a bit more imagination — it could serve to drive more business to Lombardi’s core products.

In a year-end emerging trends article in December, I predicted both “modelling for the masses” and “Web 2.0 hits BPM”. Lombardi’s Blueprint delivers on both of these, and I look forward to seeing how they take it forward from here. If it’s like all other good Web 2.0 software, it will adhere to the principle of constant improvement rather than monolithic release cycles.

There’s a lot more to it than what I’ve discussed here, and if you’re interested, check out the webinar that I’m hosting tomorrow entitled Are You Ready for On-Demand BPM with Colin Teubner of Forrester Research and Jim Rudden of Lombardi, in which Jim talks a lot more about Blueprint. You can also sign up for the beta program if you want to try it out for yourself; as of the end of April, it will be available to everyone. I signed up this morning, but received the following email back from Lombardi a short while later:

Dear Sandy,

Thank you for your interest in Lombardi Blueprint. Unfortunately, due to the overwhelming number of requests for Blueprint accounts, we are unable to activate your account at this time.

We will keep your registration information in our database and will contact you when we can provide you with an account.

I’m hoping to be able to pull some strings and get in the beta program sometime soon. :)

For those of you who did manage to get a beta account, go on, get out there and expose your processes!