CRM projects done right mean business process changes

By David Taber, CIO |  IT Management, CRM

Think about an accounting, ERP or even HR application. Making them work means some using pretty tight business rules and user practices. Most of the time, users have been fully indoctrinated by their professions and have no problem adopting generally accepted accounting principles ( GAAP) or the more flexible ERP II.

Now think about the typical outbound marketing person or sales rep. There's professionalism, yes, but there's also a deeply held belief that what they do is a sort of artistry based on unique personal skills. The amount of CRM-oriented processes baked into most sales and marketing departments could fit in a couple of tea cups.

Commentary: Before You Invest in CRM Software, Assess Your Needs

I'm not just being snarky here. That's coming from a 20-year veteran of the revenue generation business process. The shallowness and incoherence of marketing and sales processes is a major impediment to the effectiveness of CRM efforts and the adoption of the systems by users.

The bottom line is this: Successful CRM projects depend on the refinement and deepening of the relevant business processes. That can make CRM projects a taller order.

5 Business Process Issues Associated With CRM Projects

In the early stages of any significant CRM effort, you need to look for symptoms of business process disconnects and incentive misalignments across various parts of sales and marketing. Unifying and automating non-integrated business processes will only expose or exaggerate contradictions.

The place to look for these disconnects is in job descriptions, territory maps, sales channel rules of engagement, marketing programs, lead nurturing campaigns and other PowerPoint, Visio and Word documents. Here are five major problem areas.

Unclear or undifferentiated processes. Do the job descriptions in marketing (particularly the outbound side) and sales (particularly field marketing and pre-sales) reflect highly differentiated process roles, or are the responsibilities only vaguely stated? You want to see unique ownership of goals that can be independently achieved. You're looking for specific descriptions of cogs in a machine, not vague statements about teamwork.

Pay close attention to service level agreements, especially those that involve the following parties:


Originally published on CIO |  Click here to read the original story.
Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Answers - Powered by ITworld

Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Ask a Question
randomness