Cautionary Tales: Enterprise Software Edition
A few weeks ago, I was talking about CRM (Customer Relationship Management) software. Essentially, CRM should help a company (as Dennis Howlett – business software blogger put it), “sell more stuff.”
I don’t have a problem with that result. We can argue all day long abo really “needed” as opposed to “pushed”. That’s a philosophical debate, indeed, it’s a MORALISTIC debate. In Obama’s address to the USA (re: BP oil sands) he prayed for a “hand to guide us.” Was he talking about the hand of god, or the invisible hand? … But I digress.
My point about CRM was much less lofty. CRM systems are simply about attempting to know your customer. How much data can we collate and analyze in order to maximize our value proposition? Or, if you’re a cynic – how can we, as Homer Simpson would say, “cram one more salty treat into America’s already bloated snack hole?”
Sidenote: Back in the heyday of the SUV craze, there was a great interview on 60 Minutes with some analyst/pundit who described the motivation that seemed to underlie the populating of these beasts. He described it as “reptilian.” The term stuck with me and I find it helpful to think about in around any purchasing decision of consequence. A well executed CRM can create a veritable “Jurassic Park” of suckers if that is what one is so inclined to create. Although, it doesn’t have to be that way. It doesn’t have to be evil.
My point this week though is less about CRM per se and more about what happens when an enterprise software implementation goes awry. A different kind of evil. There have been two big stories recently detailing lawsuits being leveled against firms who had been contracted to install an enterprise system and had allegedly failed to deliver on the contract.
In one case, EDS (now owned by Hewlett Packard) just agreed to pay British Sky Broadcasting $460 million for a failed CRM implementation. This was from a project undertaken in the year 2000 and abandoned two years later. The settlement is four times the value of the budgeted project cost.
In a second case, Marin County, CA is suing Deloitte Consulting for an alleged failure in rolling out an ERP (Enterprise Resource Planning) system. Marin County is seeking $30 million. Their contention is that Deloitte didn’t have the technical skills on the software in question. That’s an important point. This type of technical skill is of the “use it or lose it” variety.
So, is that the answer? When a software implementation goes awry, you sue everyone? Well, sometimes.
You see, buying an enterprise software system isn’t like buying a vehicle. You can’t just hand the wheel over to your reptilian brain and pray for the invisible hand to hook up financing and you’re on your way.
There’s work involved, normally a third party, that is paid to configure the software and integrate it into your organization’s existing infrastructure. In a complex business model, the process of defining and integrating all the business rules, data flows, and connections can be daunting… sometimes, impossible. Failure, unfortunately, is always an option.
These recent examples deal with alleged failures on the part of the third party implementers, but failures can occur anywhere within “hell’s half-acre.”
I’ve seen examples where it was clearly a management failure to provide project leadership that created an implementation failure. The example I am thinking about resulted in the company taking a $2 million dollar charge then having to start over. When I went to see them, it looked like they were heading right back down the same road. Making the same mistakes. Me? I can’t help someone who doesn’t want to be helped.
Some folks point to Saas products as a way to alleviate these nightmare scenarios. If only it was that easy. Wherever a business has an existing IT architecture, there is the possibility of an integration problem (assuming you want integrated systems which I have to believe that you’ll want). There is another company I can think of who, when I met them, had been working for at least 6 months on an integration with a Saas ERP system and their back office. For a number of reasons, it really just didn’t seem like it was going to work. And the red flag for me was that the CFO and the Director of Finance had vastly different views as to how the project was going.
These are just a couple examples I can name from my own experiences and I’m not even in the software implementation game!
The moral of the story is know the statement of work inside out. Understand the terms of the contract. Technical skills are finite. Be very clear on the desired outcomes.
And beware of the reptilian brain.
Geoff Devereux as been active in Vancouver’s technology start-up community for the past 5 years. Prior to getting lured into tech start-ups, Geoff worked in various fields including a 5 year stint in a tax accounting firm. You can see more of his posts for GC here.
Customer Relationship Management – Know Your Customer, Know Yourself
The first rule of business is “know your customer.” So, how do you do that?
This is the question that brings you into the field of CRM (Customer Relationship Management). I remember working in a tax firm back in the early 2000s and all client correspondence was hardcopy in the file. Our “CRM system” was rows of filing cabinets.
A sales forecast? rked at a company where the sales forecast was an excel spreadsheet that physically gave me vertigo just looking at it. Updating that thing was like a game of Tetris.
A “real” CRM system consolidates all of your company’s customer interactions and sales activities into one database. It enables sales and marketing to detail the entire sales process from Lead to Close. And now it’s the difference between “knowing your customer” and living in the dark ages.
I only started seeing these systems spring up in mid-sized businesses a few years ago. How much are you guys seeing CRM out there now? Does your CRM system integrate with your other business systems? Or is it more of a Contact Manager?
For example, I have seen an instance where the CRM software operated as its own sphere of information. Then, we had the company financial information as its own separate sphere. To connect the sales pipeline info (from the CRM) to the financial results was a manual task.
I’m throwing it out there because my own experience with CRM in the SMB/SME space is limited to using Salesforce.com. I spoke about them briefly when I introduced Saas and Cloud Computing a few weeks ago. I must sound like a Salesforce salesperson but I’m not. I just found that Salesforce 1) put CRM on the radar for the SME I was working for at the time and 2) was inexpensive and easy to deploy.
The other main Saas CRM play is Sugar CRM. Both Salesforce and Sugar CRM have free versions. A very small business could probably operate on the free version for ever. Most mid-sized businesses could use the free version to test the fit of the product’s process flows before committing to rolling it out throughout the business.
In large enterprise, the CRM is probably big enough to just be called “the system”. Let’s say you are working for a bank or an insurance company. “The system” knows things. Next time you are speaking to a call center representative, ask for a summary of your own history. You might be surprised what details are lurking within the system. These can be simply contact histories or can also incorporate decision-making capabilities (i.e. loan or credit card approvals).
Retailers capitalize on this technology through the use of Loyalty Programs.
The real power behind CRM, for those not currently using this type of software, is the ability to clarify the sales pipeline and to consolidate customer interaction. You can detail right from Cold Call to Close and you can get the analytics to visualize the process too.
We’re right on the cusp of even bigger innovations in this field. Just look at some of the things Google is doing right now with respect to data and data visualizations (Google Trends – Google public data – Google Analytics). Sentiment analysis is appearing to gain traction as well. To blow all that out into the CRM realm means really powerful insight into customer behavior.
The success or failure of the CRM is linked directly to the quality of data in the system. This is where the “know yourself” bit comes into play. Where you can automate, do so. Trusting a salesperson to voluntarily do data entry is like trusting your road-trip navigation to a poet. Not good. Again, great strides continue to be made here. Between the increasing migration of transactions and activities online, and the tools allowing for Salesforce Automation (SFA), the direct maintenance on this type of system can be minimized.
For those of you unfamiliar with CRM technology, maybe you’re working in smaller companies or companies with a legacy of paper-based CRM, Saas solutions like Salesforce and Sugar CRM are worth checking out. It’s a place to start. And it’s free to start.
We would really like to hear from you on this issue as well. What has your experience been with CRM?
Geoff Devereux as been active in Vancouver’s technology start-up community for the past 5 years. Prior to getting lured into tech start-ups, Geoff worked in various fields including a 5 year stint in a tax accounting firm. You can see more of his posts for GC here.
Mario Armstrong: Cloud Computing, SaaS, Social Media Are Tools for All Small Businesses to Consider
Earlier this week we got the chance to speak with Mario Armstrong, on-air tech contributor for NPR’s Morning Edition and tech contributor to CNN. We discussed several technology issues, including SaaS and social media, for small businesses to consider to mark National Small Business Week.
There you have it! Cloud solutions, SaaS, social media. They’re all important tools for small business owners. You can spend your weekend boning up.
Cloudsplitting: Recognizing the Tech and Business Cloud Narratives
Cloud Computing can be an intimidating subject area simply due to the sheer number of articles, blogs, conferences, and information on the matter. My goal in this post is to split the discussion based on the perspective of the writer.
While researching this post on “Cloudsplitting”, I became formally acquainted to the concept of an unreliable narrator:
“a narrator, whether in literature, film, or theatre, whose credibility has been seriously compromised.”
The nature of the narrator may be immediately clear or it may be revealed later in the story. Sometimes it is revealed at the very end, at which point you find out your narrator has been totally unreliable! This makes yo story… which you should…. the guy was unreliable.
I think it’s a great concept! The first example that jumps to mind would be Kevin Spacey’s character in The Usual Suspects (Warning: Swears… Gonzalez sized swears).
I stumbled on the concept, the actual term, thanks to Cloudsplitter, the book. It’s a fictional retelling of Harper’s Ferry from the FICTIONALIZED point of view of John Brown’s son.
The author, Russell Banks, creates new context around the real events through his imagining of what Owen Brown’s views might have been. In this case, John Brown comes off as a lot less crazy than he may have come off otherwise.
(It’s also a hill in upstate NY near Bank’s home – ‘Tahawus‘ is the native Algonquin name for Mt. Marcy – the highest peak in the Adirondacks. It translates to ‘Cloudsplitter.’)
Emotional attachment and years of hermit-like isolation warp the perspective of our fictional version of Owen Brown. Unreliable. Quite frankly, I’ve seen the same in business.
I don’t want to fall for the same mistake.
We’re not hermits holed up in a cabin somewhere living on bottled water and beef jerky.
That’s one of the biggest differences between the introduction of Cloud technology and the introduction of previous computing technology. This time around information abounds. Whereas in the past, information about new technology was carried through very limited channels. And even then, it may have traveled indirect routes.
With our proliferation of information, it’s more important than ever to consider the source of the information. After all, the greatest trick the narrator ever pulled was convincing the world he didn’t exist…. or something.
Be it me and my Cloud Computing story or the guy at your office who waves his arms and decries this “parlour trick” technology.
Where is your information coming from?
I’ll point you to a few resources in a minute that, hopefully, will pass the narrator reliability test. First, if I may, I want to take the opportunity to split Cloud Computing into two separate camps.
In one camp, we’ll have Techie Cloud. In the other, we’ll have Business Cloud.
Techie Cloud:
This is the stuff relating to the functioning of a cloud environment. What’s the architecture? Where’s the data? How do I manage it?
It’s the kind of stuff your Systems Administrators and DBAs and IT Managers would want to know. For instance, I want to play around with Amazon Web Services to create a new computing environment. Do I need any special tools to work there?
Yes, there’s a front-end tool called Rightscale that makes creating a computing environment easy.
While interesting from an academic perspective, your average business user will probably get limited value from seeking out tonnes of information about Techie Cloud. Recognize it when you see it.
Business Cloud:
This is the stuff relating to using cloud-based software. The business user who is looking for a “consumerized” web experience. What does it do? Is it easy to learn? What’s the cost? How do I sign up?
It’s the kind of stuff the accountants, marketers, and salespeople would want to know. For instance, I want to find a way to manage my team’s projects. Can I get going with something quickly?
Yes, try Basecamp.
And Business Cloud is separate from the business of cloud which we’ll get into later.
The reason I am going around Cloudsplitting is because the content I’ve been finding lately doesn’t discriminate with respect to audience. You are as likely to jump into an article that’s geared toward IT as you are to find an article for a Business User’s perspective.
Forward the Techie Cloud articles on to your IT departments. There’s a view out there that Cloud is going to make IT deparments obsolete. I disagree. I think Cloud will free up IT from the mundane custodial services of server maintenance becoming a more strategic partner with management. I’ve written before about accountants being the dishwashers of business. We’re the dishwashers and IT are the custodians (or janitors if you want to be unkind about it).
And remember:
Evaluate the reliability of the source. Evaluate for audience.
Techie Cloud
8 Tips for Getting Started in Cloud Computing (by Rackspace)
What Does the Future Hold for IT? (Bloomberg)
Cloudcamp – formed to provide a common ground for the introduction and advancement of cloud computing
Business Cloud
ICPA Trusted Business Solutions (CPA2Biz) – all of these are Saas offerings
Tourist in Techie Land: Reporting from Cloudcamp Vancouver (me)
IBM CTO at Interop: Consumerization of IT is a Driving Force (ZDNet)
Geoff Devereux works in a marketing/social media role with Indicee, a Saas Business Intelligence company, bringing B.I. to mere mortals. You can see more of his posts for GC here. H/t to Jesse from Cloudsplitter Mountain Guides for the translation and Greg_Smith for the pic.
It Was a Dark and Stormy Night…or: Cloud Computing and SaaS Briefly Explained
Figuring out how to sum up Cloud Computing and Software as a service (SaaS) in the space of ~800 words would absolutely require the biggest, puffiest, most cumulus metaphor that ever precipitated understanding over the dry, barren plains of ignorance EVER! Something like….