Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Is your CRM implementation architecture or interior design?

David Taber | June 26, 2014
Just because your CRM project involves software, infrastructure and the cloud doesn't mean it's just an engineering project. There's some design work involved, too -- and, as any homeowner can tell you, sometimes the window dressing costs more than the window.

I've recently done some serious house construction projects, both remodeling and ground-up building. Like any good engineer, I have no problem working with the architect, the civil engineer, the construction guys and even the inspector. I might object to the total bill, but I can understand all the components and cost drivers.

Interior designers, however, drive me nuts. As far as I'm concerned, they might as well be Feng Shui witch-doctors. While individual interior designers clearly have their own methods, if you compare them, there seems to be almost no consistency in the inputs, outputs or sequence of actions. In other words, they don't follow a business process. In the immortal words of W. Edwards Deming, "If you can't describe what you're doing as a process, you don't know what you're doing."

When it comes to costs, interior designers just don't seem to understand the meaning of the word "budget." They never see an overrun that they don't like, endlessly pointing to wondrous things that would make the Sultan of Brunei blush - and you just know that, 18 months from now, you'll have to throw much of it away when it's hopelessly "out of style." You'll be endlessly replacing all those Great Ideas.

CRM More Drapery and Duvets Than Ducts and Dormers
Uh-oh. I just realized I'm an interior designer.

Not really, of course. But looking at CRM implementation from the client's perspective, I see too many eerie parallels:

  • CRM requirements seem to vacillate and be totally subjective. There are no specs, just "stories" under the influence of users emotions. What's important this week? Only the users know. What'll be important next month? We'll just have to see. Worse still, all the details of what's being delivered are hammered out in real-time, below the radar of accountability.
  • Even if every sprint completes on schedule and on budget, the client doesn't know exactly what it's going to get in any one sprint. All it gets is the vague idea that each release train will have "the most important things for the business that can be delivered with quality." Inmates run the asylum.
  • In a most uncomfortable way, there's no way to know when the CRM system will be done, so it can be frozen into a production configuration for a couple of years. Instead, the only assurance you get is that the business requirements will continue to evolve, so the system will be in a state of continuous overhaul until the day it's decommissioned. Guaranteed lifetime employment for your CRM consultants.
  • Due to that continuous evolution of your systems and integrations, there's anything but a guarantee of data quality. Without continuous attention from people and process designers, CRM data tends to degrade faster than any other database. In some industries, the email field alone can degrade as much as 10 percent per month. Plus, your CRM may hold the enterprise's most expensive data in the first place. This is like cleaning luxurious silk drapes every time you want to use them.
  • Financial and operational professionals want a set of specs, a systematic project plan and a spend plan that they can examine and compare against reality throughout the life of the project. Instead, agile teams look like artist colonies, with ephemeral "card walls" and plans that don't seem to extend beyond the current week. There's only the assurance that money will be spent, not that you'll get anything for it. Understanding what the scrum team is up to requires too much attention and careful listening, and even then the team may seem evasive.

 

1  2  Next Page 

Sign up for Computerworld eNewsletters.