February 10, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
Sandy Kemsley
Column 2
The archive of Sandy Kemsley's blog on business process management, enterprise architecture, business intelligence and technology in business.

« May 2006 | Main | July 2006 »

June 29, 2006
links for 2006-06-29

Posted by Sandy Kemsley at 07:22 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


Gartner BPMS Magic Quadrant 2006

I just saw the new Gartner Magic Quadrant for BPMS, published yesterday, and although I haven't had time to review the entire 19-page report, here's the MQ:


Graphic removed at the request of Gartner, who seem to be missing the point that I'm actually encouraging people to read the entire 19-page report in context, not just look at the single graphic that I excerpted.

Good way to alienate the blogosphere by stomping all over the notion of fair use, guys.

The most recent point of comparison from Gartner is their June 2004 MQ for pure-play BPM, which included many of these same vendors. They see BPMS as the second generation of this market, and note that many of the former leaders no longer meet the requirements.

Some interesting notes:

  • Three of the four vendors in the leaders quadrant are new arrivals as I discussed in my History of BPM posts.
  • Fuego (now BEA) and Lombardi have moved from the visionaries quadrant to leaders, relative to the Pure-Play BPM quadrant that Gartner published in 2004. Interestingly, their relative "completeness of vision" dropped as their "ability to execute" increased.
  • Savvion and Pegasystems both retained their place in the leaders quadrant, but both also dropped in relative "completeness of vision".
  • Two long-time players in this space, FileNet and TIBCO (Staffware) have been bumped out of the leaders quadrant: FileNet for less completeness of vision (a point that I readily agree with lately) and TIBCO for less ability to execute. As I said in the afore-mentioned BPM History post, many of the larger vendors are lagging badly in implementing new features, and look a little tired these days in comparison to the shiny bright newcomers.

Tons of good detailed information in the report, worth reading.

Posted by Sandy Kemsley at 05:15 PM in BPM | Permalink | TrackBacks (0) | Add to del.icio.us


Bluespring does it in style

This is the foie gras of eating your own dogfood: I registered online for a product demo webinar with Bluespring today, and here's what I saw after I filled in the form:

After a few minutes, I clicked the refresh button; the process status changed to "Temporarily Delayed" and the upper part of the process map changed:

The URL included the process ID so that I could bookmark the page and can go back at any time and see where my process is, in real time; the registration confirmation email also contained the URL back to my process plus a vCalendar file to add the webinar to my calendar. It would be even more cool if they customized the vCalendar file to include the URL of my registration process, so that I could toss the registration email after the item is on my calendar without having to add the URL to the calendar entry myself, but that's a minor quibble.

All the BPM vendors say that they can do processes that cross the firewall and keep the external participants informed, but how many of them actually do it on their public website?

Posted by Sandy Kemsley at 12:20 PM in BPM | Permalink | TrackBacks (0) | Add to del.icio.us

June 27, 2006
links for 2006-06-27

Posted by Sandy Kemsley at 07:20 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


Plans for Mashup Camp 2.0

Okay, I'm joking about the 2.0 nonsense, but I am headed for the second edition of Mashup Camp in two weeks to continue my investigations into using mashup methods and technologies to make enterprise integration more agile and less weighty. If you're going to be there, look me up.

Posted by Sandy Kemsley at 01:36 AM in mashupcamp | Permalink | Comments (2) | TrackBacks (0) | Add to del.icio.us

June 26, 2006
SOA anti-patterns

This is brilliant: Steve Jones on SOA anti-patterns. I was going to just do my usual del.icio.us link/auto-post, but it's inspired me to an entire post.

A few months back, I wrote an article for AIIM E-DOC Magazine on BPM Implementation Pitfalls that described my three favourite ways to screw up a BPM project: over-customization, allowing the business to design the solution, and applying the wrong BPM tool. Jones' article on SOA anti-patterns is more formal treatment along the same lines that addresses the following burning issue:

A lot of emphasis has been placed on implementing Service Oriented Software according to best practices and principles. But how about the worst practices?

He rigourously lays out several SOA anti-patterns that had me laughing out loud, including "The Shiny Nickel" (used to incorporate the latest technology buzz within your SOA for the sake of telling people about it) and "IT2B" (creating "business" services based on the belief that IT understands the business results in services that meet neither IT nor business goals).

Posted by Sandy Kemsley at 08:14 PM in SOA | Permalink | TrackBacks (2) | Add to del.icio.us


links for 2006-06-26

Posted by Sandy Kemsley at 07:21 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


Savvion's ProcessXChange

I had a chance late last week to talk to Shawn Price (CEO) and Pat Morrissey (SVP Marketing) of Savvion about the news that they're releasing this week. It's always flattering to hear the CEO of a BPM vendor start a sentence with "Having read your blog...", and there's some interesting things that they're announcing that are aligned with what I write about, including their "Show us your models" contest announced shortly after I wrote "Show me your process models". Their call to see your process models is their new ProcessXChange, a forum to share process models, discuss best practices and other topics related to process improvement: more ambitious than what I was suggesting, which was just a library of process models, but at the same time, more restrictive since it is limited to process models developed in the Savvion Process Modeler. I applaud their efforts to start a collaborative community around process improvement, but a vendor-specific walled garden isn't going to cut it in the long run.

Savvion is also launching a new version of their BusinessManager product this week that attempts to increase the range of BPM participants within an organization in an effort to speed the deployment of process automation: Shawn's comment was that an organization must deploy its first application within 90 days in order to be successful at BPM, and allow for ongoing changes to processes two more times every 90 days. I found that comment tremendously interesting, considering that many of my more conservative customers spend three or four times as long to deploy their first application, and end up being not all that succesful because the business has changed during that time and there's been too much over-customization to make the solution agile enough to adapt. I always push for a simpler application deployed sooner, but many customers are sold (usually by a large SI) on the notion of an all-singing, all-dancing "solution" that takes a year to develop and deploy, and ends up solving nothing, in the end.

A cornerstone of Savvion's plan to push BPM out into the organization is their free, downloadable Process Modeler, on the premise that if everyone has a process modeling tool on their desktop, they're more likely to participate in the process improvement efforts. They've also added simulation capabilities to allow an application to be previewed before deployment and improved their BAM capabilities. I've never done an in-depth on their product so I'm not in a position to say how much of an improvement that these things are over previous versions.

One recommendation that I made to them, which I've made to other vendors as well, is the addition of a zero-footprint AJAX-based process modeler, if you're really serious about having this used throughout an organization. Many companies lock down the user desktops so that software can't be installed, and applications requiring installation may take weeks of testing by a central IT group before they are approved for use on a desktop. Move this completely to the web with no download, and the usage rate will shoot up. One thing that I do like about their modeler is that it models in BPMN directly, whereas many other vendors are relying on third-party modeling products such as the Zynium add-on to Visio that exports to XPDL, then imports into their process modeler.

One last thing that we discussed is the role of BPM as an enabler for BPO by allowing for collaboration between an organization and their outsourcer: if the "home office" can model their processes and have those process be implemented elsewhere without re-translation of the models between tools, then use the same set of tools to monitor processes or collaborate on changes to the processes, business process outsourcing would get a lot less painful. Also, the addition of automation to the outsourced processes is becoming a necessity in places such as India where the wages are creeping up and the all-manual methods are becoming less cost effective. Savvion is busy making deals with a number of Indian BPO firms with exactly these ends in mind.

Posted by Sandy Kemsley at 01:20 PM in BPMBPMN | Permalink | Comments (2) | TrackBacks (0) | Add to del.icio.us

June 21, 2006
links for 2006-06-21

Posted by Sandy Kemsley at 07:21 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us

June 19, 2006
links for 2006-06-19
  • A repository for workflow modeling patterns, often referred to when evaluating process standards and product.
    (tags: bpm bpmn)

Posted by Sandy Kemsley at 07:25 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


FileNet Toronto user group meeting tomorrow

A bit late notice, but if you're a FileNet customer or partner in the Toronto area, you can attend a UserNet (user group) meeting tomorrow at 9am at FileNet's offices, 191 The West Mall, Suite 1010 in Toronto's west end.

Posted by Sandy Kemsley at 04:45 PM in BPM | Permalink | TrackBacks (0) | Add to del.icio.us

June 16, 2006
links for 2006-06-16

Posted by Sandy Kemsley at 07:20 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us

June 15, 2006
links for 2006-06-15

Posted by Sandy Kemsley at 07:22 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


A Short History of BPM, Part 8

Continued from Part 7.

Part 8 (the last): The Current State of BPM. Every analyst, vendor and customer defines BPM differently, because the current definition of BPM is very broad, and there are many vendors jostling for position within it. EAI/ESB-type vendors call their products BPM, but the products may contain only rudimentary human-facing functionality. Workflow-type vendors, also labelling themselves as BPM, lack the necessary infrastructure for integration, and often handle automated steps poorly. Some pure integration products call themselves workflow, just to confuse things further. There’s a lot of complementary products, such as process analytics and simulation, and business rules engines: BPM vendors will either tell you that a particular capability must be part of the base BPM product (if their product has it), or should never be part of the base BPM product (if their product doesn’t have it). And now there’s the whole SOA wild card thrown into the mix.

BPM is definitely a case where the whole is greater than the sum of the parts. It’s not just workflow plus EAI plus B2Bi plus business rules, plus plus plus: it’s the near-seamless integration of all of these tools into a single suite that provides an organization with the ability to do things that they could never do before. That doesn’t mean that all the tools have to be from the same vendor, but it’s essential to deliver all of the BPM functionality in a single environment of closed-loop process improvement.

Smith and Fingar’s book Business Process Management, The Third Wave describes this "third wave" as providing the ability to create a single definition of a business process from which different views of that process can be rendered and new information systems can be built. This allows different people with different skills -- business manager, business analyst, regular old user, programmer -- to view and manipulate the same process in a representation suitable for them and derived from the same source. They make a great analogy with HTML, where a business user may use a high-level tool like FrontPage to view and edit HTML, whereas a developer may edit the HTML code directly, but they’re still working from the same source. Round-tripping between a business analyst's modelling tool and a developer runtime environment is one way to do this, although it violates the "same source" in the purest sense, but we definitely have to get rid of the strictly one-way paths from business analysis to implementation that exist now in many organizations.

Furthermore, Smith and Fingar point out that in the world of BPM, the ability to change is far more prized than the ability to create in the first place, and that BPM has the potential to actually remove application development from the cycle -- the "zero code" Holy Grail that gets a lot of press these days. They make an analogy with VisiCalc, which took customized data analysis out of the hands of the IT department and put it in the hands of the business users, thereby taking software development off the critical path for achieving results.

Getting back to the point of this post, what is the current state of BPM?

First of all, we have several companies from the pure-play BPM/BPM suites market: they provide excellent human-facing BPM and at least adequate integration capabilities, with some providing outstanding integration. At the Gartner BPM summit earlier this year, they listed three "major players" in this category who had revenues upwards of $100M -- FileNet, Pegasystems and Global 360 -- and five "up and comers" with revenues above $30M -- Appian, Lombardi, Savvion, Metastorm and Ultimus -- while ignoring anything smaller than that. All eight of these vendors hit into the right zones in the Gartner and Forrester charts, which means that they either have the necessary functionality or are partnered with someone to provide it.

Second, we have a couple of integration-focussed BPM vendors who have purchased pure-play BPM vendors to create the complete range of functionality. The two highest-profile examples are the TIBCO acquisition of Staffware in 2004, and the BEA acquisition of Fuego earlier this year. In both cases, there seems to be a reasonable fit, but my concern is that the human-facing BPM side is going to become weaker since the main focus of these companies is on integration.

Third, we have the large software companies that have developed (or acquired) a BPM product: IBM, Microsoft and Fujitsu all spring to mind. In many cases, such as IBM and Microsoft, their BPM products are primiarly integration-focussed without a lot of human-facing support, and likely started as a "would you like fries with that" sort of offering for customers who were already committed to their architecture. IBM's MQ Series messaging is probably still the most commonly used piece of integration middleware in financial services, although I think that they call it (and everything else) "WebSphere" these days, and IBM rightly has it as a cornerstone of their BPM strategy. Fujitsu is the odd one out here, with what appears to be a fully-functional BPMS; unfortunately, they've been marketing it in stealth mode and most people are completely unaware of it: as I said in one of my posts about the Gartner BPM summit, "who knew that Fujitsu did BPM?"

We'll continue to see most of the business functionality envelope being pushed by the vendors in the first category as they seek better ways to integrate business rules, analytics, performance management and other capabilities into BPM; in fact, the most innovation seems to be coming from the smaller vendors in this category because of the lack of baggage that I discussed in part 7.

Because of the current focus on process improvement in all organizations, I don't think that there's any great risk of any of the vendors that I've listed here going out of the BPM business any time soon. However, the integration vendors will acquire some of the smaller BPM suite vendors to round out their portfolios, and the large software companies will acquire some of everything, in a continuing Darwinian cycle.

Before you vendors start adding self-promoting comments to this post, keep in mind that this is not intended to be a comprehensive list or review of BPMS vendors, and I know that you're all very special in your own way. :)

Posted by Sandy Kemsley at 02:00 PM in BPMBPMhistoryBREESB | Permalink | Comments (3) | TrackBacks (1) | Add to del.icio.us


Show me your process models!

I had a couple of emails recently from people looking for public-domain process models, related but slightly different. The first was looking for generic process models for those processes that are the same in most businesses:


I am trying to convince [a small healthcare company] that their business is no different than many other service businesses providing service to customers. I am having a very hard time finding a reference model for just a generic enterprise, one that would include all of the standard functions such as Finance, Strategy and Planning.

The second was looking for some real-world examples of BPMN:

I'm looking for a good source for real examples of BPDs that are compliant with the BPMN spec. I've spent ~3 hours surfing for information on BPMN when I came across your blog and decided you might know what you're talking about. I'll admit to being uncompromising when it comes to adherence to the BPMN spec, but I don't have a lot of support. So far, we've generated a whole bunch of examples of how not to draw models, do you know of any good sources?

Aside from not being sure whether to be flattered or not over the comment that I might know what I'm talking about, it's really the same issue: the need for publicly available templates or samples of business processes. Think of it as design patterns for business processes, something that's far more useful than the standard "employee expense approval" flow that seems to ship with every process modelling tool. The biggest problem, of course, is that many companies consider this to be part of their intellectual property, even if the particular process is not part of their competitive differentiation, and don't allow those process models to be shared. What's funny is that every customer I work with thinks that their processes are completely unique, but it usually boils down to something very similar to what I've seen at other customers in the same industry, or even across industries. I think that the attitude that "our business is unique" might be preventing more standardized modelling of business processes.

Anyone out there know of any libraries of real business process models available online, whether generic or industry-specific? Any that use BPMN? Does anyone have process models that they'd like to contribute to an "open source" library? Tim Vojta, the author of the first email above, has kicked things off by creating a Business Process Reference Model after our discussions and publishing it under a Creative Commons licence (yeah!), although it covers only a fairly high-level functional view of the enterprise.

Posted by Sandy Kemsley at 08:26 AM in BPABPMN | Permalink | Comments (4) | TrackBacks (0) | Add to del.icio.us

June 14, 2006
links for 2006-06-14
  • The public beta release of Flock, a Mozilla-based brower that adds some nice features above Firefox.
    (tags: web2.0)

Posted by Sandy Kemsley at 07:22 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


Acronyms

I had lunch with a (relatively) non-technical friend last week, and she commented that she read my blog but sometimes doesn't understand the alphabet soup of acroyms. Instead of having some sort of glossary that you could go to, then search for a specific term, I'm going to try to be more diligent about including pop-up definitions (using the HTML acronym tag) -- just float the pointer over anything with a dotted underline to see the pop-up definition. Since I'm basically lazy and can't spell acronum acromyn acronym half the time, I wrote a bit of Javascript that I've installed as a Bookmarklet on Firefox and Flock:

Acronym Bookmarklet

To try it out, click on the link and a window will pop up prompting you for the acronym/abbreviation. Click OK (or press enter), and a second prompt will prompt you for the definition phrase. Click OK again, and a third prompt appears containing the tagged text, pre-selected so you just have to hit the copy command, and it's ready to paste into your blog entry or other HTML page. If you want to use this on Firefox/Flock, just drag the link onto your Bookmarks (Firefox) or Favorites (Flock) toolbar.

Posted by Sandy Kemsley at 06:26 PM in Blogging | Permalink | Comments (1) | TrackBacks (0) | Add to del.icio.us


Flock first look

I downloaded Flock last night, about 12 minutes after the public beta was released, and I've been playing with it on and off since then. Some good stuff, some things that seem good but aren't so useful for me. Flock is based on the same code base as Firefox, so there's lots of similarities and it can even import everything from Firefox in its initial setup, including saved web form data.

Some unique Flock features and how well they work for me:

  • Flickr or Photobucket integration right along the top edge, allowing photos to be dragged onto that area to upload it to the photo service. I'm not using Flickr much; I still create photo galleries using JAlbum and publish them for various websites, so this feature isn't as useful for me as it would be for a dedicated Flickr fan. I'm sure that will change as soon as I buy a pocket-sized digital camera and start snapping photos every day.
  • RSS feed functionality built in. This is a non-starter for me, since I need a subset of my RSS subscriptions to drive my blog roll directly, which is what Bloglines does for me.
  • Integration from the Favorites directly to del.icio.us. This is another non-starter for me, since it doesn't put me far enough into the del.icio.us environment to show me my del.icio.us tags, so I end up accidentally creating a bunch of new tags and have to clean them up later. However, the "add to del.icio.us" bookmarklet that I had in Firefox works just fine.
  • Built-in blog posting tool. I'm using this now, and have even figured out how to post to both Movable Type (for this blog) and Blogger (for my wine club blog) although errors are occuring on the MT posting that I haven't resolved yet. It keeps the blog post window on top of all other Flock windows, which is a bit inconvenient since I often flip back and forth to the browser window during blogging to look things up. There's no obvious hot key to pop up the links window, which is annoying. It generates some extra tags in the source, and I'm a sucker for clean source. Otherwise, I like it.

Overall, the experience is quite a bit like Firefox, only slower since I suspect that there's some amount of test/debug code in here still. Given that the only extra that I might use is the offline blogging tool, there may not be enough to keep me here if it proves annoyingly slower than Firefox.

Posted by Sandy Kemsley at 11:01 AM in BloggingWeb2.0 | Permalink | Comments (1) | TrackBacks (0) | Add to del.icio.us


Sun/PwC webinar today

Today at noon Eastern, I'm moderating a webinar called "SOA: Architecture, Methodology, or Millstone for Financial Technology Organizations?" featuring Sun Microsystems and PricewaterhouseCoopers. Tune in live, or use the same link to listen to the replay later.

Posted by Sandy Kemsley at 08:33 AM in SOA | Permalink | TrackBacks (0) | Add to del.icio.us


BPM tough love

This story makes me want to drive out to Oakville (which is just east of Toronto) and buy Neil Montgomery a beer. In summary, Davis Controls, a 50-person manufacturing firm in Oakville headed by Montgomery, put in a BPMS from Exact back in 2001 to handle business processes ranging from sales orders to vacation requests. They now have 25% higher revenues with the same number of staff, and have reduced administrative headcount to 1/3 of its pre-BPM number.

That success was not without some rocks along the road. As with every BPMS installation that I've ever seen, there was some amount of push-back from the employees, who continued to circumvent the BPMS using email. Montgomery did everything possible to convince the team to use the system, to the point of having to mandate its use, but a half dozen empl0yees still used email instead. So he cut off their email accounts, which is pretty much the most drastic thing that I've heard of anyone doing to get people to use BPM, until I read on that two of the employees, including the CTO, still resisted (are they stupid, or what?), and he gave them the boot.

This man deserves a medal, although I'm sure that some of the people who work for him, or used to work for him, might disagree. BPM is one of those technologies that fundamentally changes the way that people do a lot of everyday tasks, and those people can put up a surprising amount of resistance to change, even though they accept logically that the new technology and methods make them more productive. As John Maynard Keynes said, the greatest difficulty lies not in persuading people to accept new ideas, but in persuading them to abandon old ones.

Posted by Sandy Kemsley at 08:08 AM in BPM | Permalink | Comments (1) | TrackBacks (0) | Add to del.icio.us

June 13, 2006
SaaS: Mean time to fix security holes

I hadn't looked at the news feed from Information Week for a few days, so when I checked it today there was a really interesting story told by way of headlines:

Yahoo Mail Worm Harvesting Addresses: The "Yamanner" worm exploits a JavaScript vulnerability in Yahoo's Web mail client. Users should watch out for messages with a "From" address of av3@yahoo.com and the subject line, "New Graphic Site." Posted on: Mon, Jun 12 2006 11:41 AM

Yahoo Quashes Mail Bug: Yahoo says it has patched a bug that was letting attackers hijack systems through a flaw in the portal's free Web-based e-mail service. Posted on: Tue, Jun 13 2006 1:23 PM

Yahoo Mail Worm May Be First Of Many As Ajax Proliferates: The Yamanner worm that hit Yahoo Mail shows how increasingly popular techniques like Ajax and Javascript that make Web-based software perform well also could make it vulnerable. Posted on: Tue, Jun 13 2006 4:00 PM

As alarming as this might sound, think about the timeline for a minute. Late Monday morning, the problem hits the news. Early Tuesday afternoon, the security hole is fixed; because there's no software installed on any desktops, the fix is effectively distributed everywhere instantaneously. By late Tuesday afternoon, they're already into the post-game analysis since there's nothing else to talk about.

Quite different from applications that run on your desktop or your servers: this is the reality of web-based SaaS.

Posted by Sandy Kemsley at 09:27 PM in SaaS | Permalink | TrackBacks (1) | Add to del.icio.us


links for 2006-06-13

Posted by Sandy Kemsley at 07:21 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


A Short History of BPM, Part 7

Continued from Part 6.

Part 7: The New Arrivals. In the years following the dot-com bust in 2000, a number of new BPM vendors came into being, mostly in the coveted pure-play space. (Funnily enough, "pure-play BPM" is now not the desirable place to be, having been replaced by the "BPM suites" space that, according to some large analysts' research, seems to have nearly identical functionality to pure-play BPM.) In many cases, these were started by those who were bounced out of their previous positions during the bursting of the bubble, so there was a lot of experience being put to the task of starting this new generation of BPM vendors.

The big advantage that a new vendor has in any industry is the lack of baggage, and nowhere was this truer than in BPM: they could start designing the next generation of BPM without having to reuse their existing technology or support their installed base, because they had neither. The BPM market needed to be reinvented, and these upstart young companies were the only ones who could shake things up enough to do it. I'm not going to credit the new arrivals with all the innovation in BPM during that time, but they certainly lit a fire under the old guard. Suddenly, we had BPM calling web services, or being called as a web service, in order to speed integration (and eventually become part of the SOA ecosystem). We had BAM, or at least some half-decent process monitoring and analytics for a change. We had simulation and optimization. We had integration with third-party modelling tools. We had business rule integration.

The startup environment during that time wasn't the best -- not a lot of venture funding around for technology, the perception that this was just a rehashing of the well-established workflow market -- but a few of the vendors have become successful and many others are still straggling in their wake.

Meanwhile, the established BPM vendors had a big challenge on their hands: although few of the upstarts were challenging them directly for sales, the new guys were changing the perception of what the BPM market should be, forcing the big guys to follow suit as Gartner and the other large analysts published lists of must-have features that included this new functionality. Many of the larger vendors lagged badly in implementing new features, and look a little tired these days in comparison to the shiny bright newcomers. In some very conservative industries, such as financial services and insurance where most of my clients are, this hasn't been a problem because they'd rather pick a vendor with a longer track record and the proven ability to process hundreds of thousands of items per day. However, this is where many of the dinosaur-like CIOs are fighting the losing battle against the push for emerging technology, and eventually the new kids will prove themselves scalable and stable enough for even the most conservative industries.

Even if none of the post-2000 vendors survive the upcoming bout of acquisitions, they have to be credited with not just injecting new life into BPM, but helping to reinvent it.

Next: The Current State

Posted by Sandy Kemsley at 12:32 PM in BPMhistory | Permalink | Comments (5) | TrackBacks (0) | Add to del.icio.us


The Eight -- er, Four -- Misperceptions of Outsourcing

I was catching up on some older Gartner podcasts recently -- they're not really time-sensitive, so fine to listen to them weeks or months later, and some of them do contain some good tidbits of information. There was one good one called The Eight Misperceptions of Outsourcing: Part I, in which Linda Cohen starts by listing these eight misperceptions:

  • the myth of sourcing independence;
  • the myth of service autonomy (this was particularly interesting since it touched on the subject of the interdependence of services due to SOA and BPM);
  • the myth of economies of scale;
  • the myth of service management as self-management;
  • the myth of the enemy;
  • the myth of procurement;
  • the myth of steady state; and
  • the myth of sourcing competency.

She then went on to discuss the first four in detail, whetting my appetite for Part II, which was to contain the second four. I checked my iPod: not there. I checked the iTunes directory: ditto. I checked the Gartner podcast page: Part II just doesn't exist. Okay, it's only been four months since Part I, maybe I'm being a bit impatient, but bring on the second four myths, already!

Of course, I'm not one to be throwing stones here: I posted the first six episodes of my Short History of BPM over a month ago, and haven't completed the last two. Now that JC has caught up with translating them to French on his blog, however, I need to get moving on this.

Posted by Sandy Kemsley at 11:49 AM in BPMSOASaaS | Permalink | Comments (1) | TrackBacks (0) | Add to del.icio.us

June 12, 2006
links for 2006-06-12

Posted by Sandy Kemsley at 07:24 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


Start page heaven

For years, I've been using My Yahoo! as my start page. It has lots of great modules available, I use a free Yahoo! account as my "web form" address (instead of Hotmail), and I use Yahoo! groups, all of which has made it pretty functional. When they added the ability to add any RSS feed instead of just their own modules, I was convinced that I'd never switch.

Today, I tried out Netvibes, and I've already switched my start page over. There's a few things that I'm missing (such as the movie times for my local theatre), but there other things that I find to be useful enough to make the switch.

  • First of all, a to do list. That sounds like a small thing, and there are a ton of other apps that will do that for me, but to have it integrated into my start page so that it stares me in the face every time I open my browser is a big help.
  • Secondly, and more significant, is access into my POP mail account so that the last 5 (number configurable) email subject lines are displayed. It doesn't provide click-through access to my email, but gives me a heads-up about anything that might need my attention. Since I have a bookmarks module containing a link to my webmail immediately below that, I effectively have one-click access to my email anyway, which is one click less than it takes to access it via MyYahoo. I spend almost my entire day with multiple tabs open in Firefox, but without Outlook open because it can be a real resource hog, so I sometimes just handle email directly through the webmail client. The really ironic part is that Yahoo! hosts my email (my real paid account as well as my free one), yet I can't do this with MyYahoo: it will only provide a count of the number of messages in my free Yahoo! account on the MyYahoo page, and nothing related to my real account.
  • Third is the interface: sleek, easy to use, and advertising-free (for now). I suppose that they'll have to monetize this through advertising at some point, but right now it's beautifully unadorned.
  • Last, I just figured out how to add an iCal feed from my upcoming.org calendar - cool! And there are a ton of independently-created add-ins, such as the Google maps module which provides the functionality that is missing natively.

Just to summarize, here's what I have on my NetVibes start page:
  • Left column: Upcoming.org (viewable as agenda/week/month); BBC news headlines; CBC news headlines
  • Centre column: POP mail (last 6 email senders/subjects); bookmarks (imported from my Firefox bookmarks, organized in folders)
  • Right column: To do list (with "done" checkboxes); Toronto weather; Google map search form; Mountain View weather (I'm headed there soon for Mashup Camp; also shows the current date/time there)

Posted by Sandy Kemsley at 04:18 PM in Web2.0 | Permalink | Comments (5) | TrackBacks (0) | Add to del.icio.us


Weekend of not blogging

Heads down on a couple of client projects, plus a home project to completely disassemble a Compaq Armada M700 in order to resolder the power connector, which is conveniently located on the underside of the motherboard where you can't get at it without at least 45 minutes of disassembly. This is just one of the reasons that I keep an electrical engineer around the house -- my degree in systems design engineering qualifies me to correctly identify a soldering gun, but not actually do anything with it. However, since I'm the software guru of the household, I'll be installing SQL Server later this week as payback.

I also went out yesterday for my first sail of the season with my friend Ingrid, who owns a 25' C&C and is completely tolerant of my inability to learn much about sailing except how not to fall off the boat. She started a blog several months ago on my urging, and is now at the "so what now?" stage of business blogging. We talked about a number of issues with regards to getting customers -- especially somewhat technology-challenged ones -- to read her blog, and it's given me some great ideas for topics for BlogHerNorth when we get it kicked off.

Back to work...

Posted by Sandy Kemsley at 12:42 PM in Blogging | Permalink | TrackBacks (0) | Add to del.icio.us

June 08, 2006
links for 2006-06-08

Posted by Sandy Kemsley at 07:23 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


Appian/Zynium webinar

If you haven't had the chance to see Zynium's Byzio product in action yet, Appian is hosting a webinar on June 21st that will show off how Byzio works with their BPMS. As I discussed previously, Byzio lets you draw your process map in Visio, then export it to XPDL as a standard BPMN map for importing into a BPMS for execution. I expect that a lot of the webinar will not be specific to Appian, so if you want to get a look at Byzio this should be a good forum.

Posted by Sandy Kemsley at 11:21 AM in BPMBPMN | Permalink | TrackBacks (0) | Add to del.icio.us

June 07, 2006
links for 2006-06-07
  • Nicholas Carr's post from last year on why process matters, in response to Ross Mayfield's "The End of Process" post.
    (tags: bpm)
  • An association for people in Spain who are interested in BPM.
    (tags: bpm)
  • James Taylor on how to tell that a service (or process) is ideal for automation using business rules.
  • A great post by Muli Koppel from last year (it was hanging around in my bookmarks) on why SOA is a fundamental paradigm shift that will change our lives. Be sure to check out the two sequel posts linked at the end of this post.
    (tags: soa)
  • A project for a rainy day.
  • Microformats.org wiki pages on the various released and in-progress microformats, including hCard and hCalendar.
  • Cool mashup of the day: mashes up Google Maps, Google Search, Flickr, and hostip.info. Locates you based on your IP, then shows you on Google maps with Flickr photos tagged with your location. Strangely, AdSense ads in German.
    (tags: mashups)
  • Ismail Ghalimi with a BPM vs SOA viewpoint that I can agree with: "BPM and SOA are the two sides of the same BPM 2.0 coin. BPM is SOA’s killer application, while SOA is BPM’s enabling infrastructure."
    (tags: bpm soa)

Posted by Sandy Kemsley at 07:22 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


CIO as dinosaur

From Baseline/CIO Insight, a report on emerging technologies; specifically, a survey of CIOs of what technologies that they're actually using. Some results that I find to show the incredible short-sightedness of many corporate CIOs is the percentage who find the following technologies "of no interest/not on the radar":

  • SaaS, 32%. How could this number of CIOs possibly have no interest in SaaS? Only one answer comes to mind: empire building.
  • SOA, 30%. The percentage of CIOs who prefer to remain mired in legacy linguine.
  • AJAX, 46% and RSS, 38%. How to they plan to deliver information, both interactively and via publication, in the future? This isn't just an externally-facing issue; in large organizations, these technologies are equally important for serving it up to internal users.
  • Social networking, including tagging, 51%. Although other things were mentioned in this category, I see tagging as the key contributor to a corporate environment here. How long will it be before all ECM systems have tagging as a standard feature? When will CIOs stop characterizing this as "allowing the lunatics to run the asylum" and just put the right categorization tools in the hands of their users?
  • Wikis, 46%. Okay, I get why a lot of companies are still uncomfortable with blogs. But wikis for collaboration make a lot more sense than clogging up everyone's email with multiple out-of-date copies of a Word file that everyone is trying to update at the same time. It's only a matter of time before Microsoft adds wiki capabilities to SharePoint (if they haven't already), at which time everyone will be using wikis below the CIO's radar. David Berlind posted yesterday about how many IT leaders have never even heard of wikis, which is likely where the "not on the radar" is really coming from.

There are a lot of other equally shocking stats about just how far behind corporate CIOs are in their thinking. Many of my clients are large financial institutions, so I suppose that I shouldn't be that shocked: if I polled them directly about these same issues, I'd likely get similar results. Unfortunately, that doesn't give me much hope that these organizations are going to become a lot more efficient or offer better services to their customers any time soon.

On the BPM front, only 21% show as "deployed", 19% "testing/piloting", 27% "evaluating/tracking" and 32% "no interest/not on the radar".

Update: I just saw this post on why AJAX and RSS matter for in-house user interfaces, particularly for BPM.

Update: Robert Scoble reports that wikis will, indeed, be in Sharepoint 2007. The meteor has landed, you guys can all just head for the tar pits.

Posted by Sandy Kemsley at 08:58 AM in BPMSOASaaSWeb2.0 | Permalink | Comments (6) | TrackBacks (2) | Add to del.icio.us

June 06, 2006
Webinar on supply-chain integration

Although supply-chain integration is definitely not my key area of expertise, I've been asked to moderate an ebizQ webinar this Thursday featuring Extol. I'll do the introduction up front, then ask the questions that the audience sends in at the end. You'll be able to watch a replay of the webinar shortly after it finishes using the same link.

Posted by Sandy Kemsley at 08:30 PM in BPM | Permalink | Comments (2) | TrackBacks (0) | Add to del.icio.us


links for 2006-06-06

Posted by Sandy Kemsley at 07:23 PM in Links | Permalink | TrackBacks (0) | Add to del.icio.us


Social networking surprises

Sometimes the whole social networking phenomena still manages to surprise me. Last week was DemoCamp6, put on by my friend and neighbour David Crow. I missed it due to a bad head cold, but emailed him on Saturday to get some information and he sent the info with the comment "Sorry I missed you at DemoCamp, I had a bad day (a very bad day)." I figured that his "bad day" was just logistics problems with DemoCamp, but found out differently when I read his blog yesterday about how he had a heart attack while setting up for DemoCamp. I immediately emailed him to say that reading about it in his blog was weird (to say the least), and he responded "Welcome to web 2.0... it seemed like a perfectly useful way to diseminate the information." My best wishes are with Dave, and I'll pop upstairs to see him as soon as my cold is gone, but I have to admit that reading about it in his blog makes me laugh -- he even has shots of his angiogram on Flickr.

On a separate social networking note, thanks to all of you who left comments for my 83-year-old blogging mom on her birthday last week. Some friends and family, but lots of complete strangers who just read about it here and decide to make her day. She declared it "amazing". It's not too late to go over there and leave a happy birthday comment if you're so inclined.

My last surprise came from Assaf of co.mments, a free conversation-tracking service that I mentioned last week. He added a comment to my post thanking me for the link, and I commented back that I had found that the service didn't work with https URLs. Less than eight hours later, he responded that he could do that, and an hour after that, tracking of https URLs became part of co.mments. Now that's Web 2.0! If only David Sifry over at Technorati could be so responsive in fixing the problem with redirected URLs not combining their count with the URL to which they are redirected...

Posted by Sandy Kemsley at 06:18 PM in