Conventional wisdom on CRM requirements doesn't work
The final major flaw with the functionality led approach to CRM requirements gathering is the Rumsfeldian notion of the unknown unknowns. Users, who invariably haven’t used CRM technology before, are expected to articulate a complete vision of what they want from a system, and invariably are only able to produce a handful of bullet points.
Even those who have been exposed to CRM technology before, generally because the system they used wasn’t well set up, and/or the deterioration of memory over time, and/or their exposure to a limited sub-set of functionality, tend to struggle to produce meaningful requirements.
On the other extreme, this approach does occasionally produce users who can create a very detailed but ultimately Frankenstein-esque vision of a system out of all context with what’s deliverable from conventional CRM technology.
The implications of the above are that:
The stated requirements are so limited that most packages in the market can meet them, and so the meaningful comparison is nigh on impossible.
Key functional requirements are missed which increases the risk of purchasing a CRM package that doesn’t meet the ‘real’ needs. For example I’ve seen a lot of organisations with very sensitive data security needs fail to document any data security related requirements.
Or in the ‘Frankenstein-esque’ situation the stated requirements are so ‘unusual’ that vendors are discouraged from bidding, and those that are received have huge price tags. I know of several expensive CRM tendering exercises that produced no responses at all, with all invited vendors deciding to ‘no bid’.
Anyway, that rounds out why the functionality led approach to requirements gathering doesn’t work, next time I’ll try and articulate a better way…
Even those who have been exposed to CRM technology before, generally because the system they used wasn’t well set up, and/or the deterioration of memory over time, and/or their exposure to a limited sub-set of functionality, tend to struggle to produce meaningful requirements.
On the other extreme, this approach does occasionally produce users who can create a very detailed but ultimately Frankenstein-esque vision of a system out of all context with what’s deliverable from conventional CRM technology.
The implications of the above are that:
The stated requirements are so limited that most packages in the market can meet them, and so the meaningful comparison is nigh on impossible.
Key functional requirements are missed which increases the risk of purchasing a CRM package that doesn’t meet the ‘real’ needs. For example I’ve seen a lot of organisations with very sensitive data security needs fail to document any data security related requirements.
Or in the ‘Frankenstein-esque’ situation the stated requirements are so ‘unusual’ that vendors are discouraged from bidding, and those that are received have huge price tags. I know of several expensive CRM tendering exercises that produced no responses at all, with all invited vendors deciding to ‘no bid’.
Anyway, that rounds out why the functionality led approach to requirements gathering doesn’t work, next time I’ll try and articulate a better way…
Related APEX Wiki Articles
Devil’s Dictionary for High Tech - Part 1
The Devil’s dictionary is a book created in the early 20th century by American Ambrose Bierce containing sarcastic, ironic and witty re-definitions of words. e.g
PAINTING, n. The art of protecting flat surfaces from the weather and exposing them...
Read more about Devil’s Dictionary for High Tech - Part 1...
Aurora: Writing the Script
Writing the script for Aurora turned out to be a tricky balancing act. We wanted to illustrate the interesting design solutions we had come up with, but we also had to provide enough context to make the solutions meaningful. We needed the movie to...
Read more about Aurora: Writing the Script...