It is true that we have First Degree and Fourth Degree Taekwondo Black Belts on staff at Corevist (yours truly and Master Ray Mannion respectively). It is also true that Black Belts have been known to hit people and break boards under crazy conditions. But I assure you that we’re not a violent company. However, as part of our Agile evolution, last week we did decide that we are going to HIT each other as part of our daily standup routine.
I don’t want to beat around the bush. I simply can’t live with you anymore. It’s nothing that you did, or didn’t do, that got us here. It’s me. I’ve changed.
I just came across this article over at practicalcommerce.com entitled “12 Key Job Roles for B-to-B eCommerce Success”. What amazed me most was that we have several clients who have achieved unquestionable success with their B2B eCommerce initiatives with only one of those roles on staff. What’s even more fascinating is that they aren’t even dedicated full time to working on their SAP Integrated B2B eCommerce website.
Which role do they have and how can that be? Read on.
Enough acronyms for you? Let me spell them out.
Last week I wrote about EDI transactions falling well short of their vision of transferring “…structured data, by agreed message standards, from one computer system to another without human intervention” (sic). According to this Supply Chain Insights survey, fully two thirds of all EDI transactions sent to Suppliers have to be fixed by human beings. That, in turn, delays the fulfillment of those orders by a factor of two! Today I’d like to discuss how an SAP Integrated B2B eCommerce website can actually improve the hands-free throughput of those EDI sales order transactions, improve your order fulfillment performance and ultimately increase your customer satisfaction ratings. Read the rest of this entry »
Electronic Data Interchange (EDI) is the “The Workhorse of the Value Chain” according to a recently published Supply Chain Insights report. In late 2013, they surveyed 79 Manufacturers/Distributors/Retailers, each generating over $250M in annual revenue, and inquired about their use of EDI. Here are some of the survey’s highlights:
A few weeks ago I had the pleasure of kicking off an SAP Integrated B2B eCommerce project for our newest client. (They’re staying anonymous for now since they don’t want to tip off their competitors). This isn’t going to be one of our simpler projects for several reasons, not the least of which is that they are in a regulated industry and we’ll have to validate our work (yet again) against FDA 21 CFR Part 11. Yet I’m really confident that this project will be one of our best. Why? Because they’ve been thinking and planning for this project for the better part of a year.
A few weeks ago we launched yet another successful SAP Integrated B2B eCommerce website project. This project was uniquely challenging in that before we could go into production, the system had to be validated to adhere to the US Federal Drug Administration’s (FDA) 21 CFR Part 11 Regulations for electronic records and signatures. Culturally, FDA validation is about as far away from our Agile DNA as you can get, so we had a lot to learn and adjust to.
While not explicitly written for a hybris, Magento or Shopify integration to SAP, I just came across this project description on Freelancer.com that really jolted me:
“Hello, can anyone my WordPress Webshop connecting with a SAP/ERP System?” (sic).
As of this writing there are 18 bidders, with bids ranging from $144 to $777…with no clarifying questions asked!
My first reaction was “this is nonsense”, which quickly escalated to an outraged “who are these Freelancer.com guys anyway?“. (For the record, they are an Australian publicly traded company valued at over $500M. They generated close to $20M in revenue last year, (nice 25X valuation huh?) and posted over 5M projects). After a little while I settled in on rationalizing that the person posting that poorly specified project was probably getting what he/she deserved…maybe a single hyperlink from a WordPress page navigating to an SAP ERP login page. Could that be what “connecting” actually meant?
And then I got to thinking.
The story about Avon’s $125M write off of their B2B eCommerce project in Canada was all over the press last month as 2013 was coming to a close. It’s a beastly ending to a project that got started in 2009.
For me, the Avon story started in May of 2011 at the SAPPHIRE show in Orlando. I was one of 100,000 people who saw Bill McDermott, SAP co-CEO, proudly strut on stage with an iPad in hand to lavish praise on Avon’s vision. His key message was that mobile access to SAP would dramatically transform Avon’s business model. (Little did he know how prescient he was…but not in a positive way).
As SAPInsider Dave Hannon reported, Bill demoed a world where:
“…when the Avon lady rings your bell, she’s going to be holding a tablet computer to show you the vivid colors of their products on screen and placing orders and showing you delivery dates. It really is an effective business case. It blows your mind!”
I was sitting there having just signed our fourth client, Office Relief, and laboring to launch our first SAP/Magento integrated B2B eCommerce website with them. Bill’s demo simultaneously validated our market and proclaimed that SAP was vigorously pursuing it.
I felt like David must have felt in the presence of Goliath. (We all know how that turned out :-0)
Fast forward 31 months to December of 2013 and the Wall Street Journal prints the news that Avon was canceling their SAP eCommerce rollout.
The final project scorecard? A $125M write-off and about 16,000 Canadian Avon reps quit.
Ouch! Big ouch.
According to InformationWeek, it was a beautiful website, but it simply couldn’t get the job done. It was unusable.
- You couldn’t login reliably.
- You couldn’t get real time inventory information.
- You couldn’t place real time orders that reserved your inventory.
- It did not support both low and high volume ordering sales reps.
Why didn’t it work?
All the signs were pointing to a mismanaged project with an overly complex architecture.
SAP seems to have upheld their end of the bargain. The SAP implementation appears to be working fine and is able to manage the Avon business well. But Avon decided to bolt on a custom IBM Websphere based eCommerce front end that turned out to be the boat anchor that sank the ship. If you’re not going to go after SAP information in real time, EVERYTHING has to be duplicated in the front end. EVERYTHING. Customer, product, pricing, inventory, delivery, payment rules and data all have to be replicated. EVERYTHING.
That’s complicated. $125M worth of complicated. 16K lost customers complicated. 55 months complicated. How many people got fired complicated?
This project also clearly suffered from a classic case of IT hubris. The project team believed that they knew better than their users…who were hinting at the fact that the website was unusable just as the pressure to launch was mounting. One senior Avon representative was quoted as saying “…the head office kept insisting that the system was working, but it was not. The sales leaders here in Canada feel that Avon is trying to portray the representatives as too stupid to use the technology.”
Bill McDermott was right in 2011. B2B eCommerce websites do indeed have an “effective business case”. Mobile access clearly has its place for certain business scenarios. But one thing is for sure. If a website is launched and no one uses it, you really don’t have a website.
The moral of the story?
Vision is nothing without execution.
There are thousands of SAP ERP implementations all over the world that are ready for B2B eCommerce. I hope they learn from the Avon experience and look for solutions that:
- leverage their SAP investments,
- don’t inject unnecessary technical risk into their projects with complicated (duplicating data and rules) architectures,
- listen to user feedback that is gathered early and often,
- solve real business problems for real business users…don’t just look flashy,
- get into production quickly…3 months versus 55 months, and
- save millions and millions and millions of dollars by eliminating the need for complicated and expensive software and armies of consultants
Hmmmm. I wonder who can offer them that?