Rapid implementation solutions in 2012. Limited value at best?

Closing out a year on a bit of controversy is always fun and 2011 does not disappoint. Mike Krigsman's rapid implementation solutions predictions post caused a bit of a stir among colleagues yesterday.

Vijay Vijayasankar threw the whole argument under the bus relegating it to minor importance in 2012. (Disclosure: Vijay is a regular JD-OD.com panelist and a senior IBM'er. We have no commercial relationship but we're good buddies.)

During the slightly tongue in cheek conversation we had yesterday (see video above), Vijay points to the basic problem that most if not all ERP projects are going to be judged a 'failure' because it is almost impossible to define the whole project scope at the outset. I chose not to challenge that as it is a diversion from the topic but understand why he would make that assessment.  Others will vehemently disagree with this position saying it self serves the SI position as implementers who gain significant economic advantage.

The real question is whether rapid implementation is the right solution to that problem and whether there are alternatives. Vijay makes two crucial points:

1. What happens after implementation as that is only a fraction of the problem? What about post implementation topics like integration, deployment etc?
2. If vendors are taking more responsibility for implementation, as seems to be the case through this approach, then why not go the whole way and build out for cloud/SaaS deployments?

I am on the fence about this one for the moment. I've not seen enough evidence to persuade me in any particular direction although I would favor cloud approaches if they exist. However I take note of the fact that Krigsman's piece did not include a single customer reference. My view here is that predictions without any practical evidence are at best precarious. On the other hand, Jarret Pazahanick, an SAP HCM consultant is convinced this concept is a dud:

One size fits all approach to #SAP often doesnt fit anyone except very small customers. Market for #RDS isnt as large as believed.

@mkrigsman@micdoane ->What makes #SAP the expert in knowing how to run successful rapid implementations (#RDS) for customers.

Pazahanick's position is equally understandable although Vijay notes that Pazahanick claims to have run the numbers for a like-for-like HCM solution using traditional techniques and says he can undercut SAP pricing. I'll await the evidence before commenting further.

I noted that John Appleby, another JD-OD panelist and business development director at Bluefin Solutions (Disclosure: I am developing a small piece of content for Bluefin) had not jumped into the discussion. I am aware his company is something of a fan of this type of solution. Appleby must be the sensible one, enjoying a well deserved vacation. Instead, Mark Chalfen, SAP finance Capability Lead at Bluefin added nuance:

@SAP_Jarret#RDS will create a good platform for most clients and they can enhance from the core solution.

@SAP_Jarret with over 100 #RDS in 2012 some will be better adopted than others and have different restrictions. Add on market will be big.

This is a discussion that will not go away anytime soon but it is worth bearing in mind that:

1. Supporters among the vendor community view this as a way of delivering early value - essentially giving them an implementation get out of jail free card for past mis-steps.
2. At least one and likely more large SIs believe the 2012-2015 timeframe will bring much more important projects stemming from planned M&A plus the impact of macro economic conditions.
3. Tier 2 SI customers may see benefit from this approach.

Who will be proved right? We cannot know and I for one am not going to make any predictions.

Note - The video quality isn't that great, the audio is better. We recorded the conversation over Skype across some 5,000 miles distance.

UPDATE: Dave Hull of Disney (@sapdba) added his personal view:

@dahowlett speaking from experience, large SIs will overly complicate implementations, to the detriment of smaller customers @vijayasankarv

@dahowlett And as SAP have yet hardly tapped SME market, and that market may be >= large cust market, #RDS is worthwhile @vijayasankarv

@dahowlett I agree w @vijayasankarv when it comes to large complex impl, but #RDS is necessary for smaller cust/less experienced SIs