Paul Greenberg initiated a very interesting discussion. It is an excellent read in it’s entirety, but I will quote just a part of it here:

the contemporary empowered customer is enmeshed in some way with a network of peers, their expectations are dramatically changed. They are straightforward changes, though. They expect that they can interact with a company the same way that they interact with a friend or a peer who they can trust. That means that they expect a personal relationship to the company, not just to a person in the company, though that may be how the relationship manifests itself a larger number of times. That also means that they expect that the attributes, the characteristics of that deeply personal connection they have to a peer is part of the way that the company interacts with them. That means that trust and transparency have to permeate the company’s DNA. That means that the company has to have something distinct about them. That means that the customer is expecting the company to converse with them, not push corporate hype at them. It’s why you see contemporary marketing so geared toward buzz and word of mouth and engaging customers in conversation through use of social media like blogs, or engaging internal customers in a valued conversation through a wiki.

I also feel very passionately about the possibility of a “real” relationship between the institution and the individual, but I am less optimistic about achieving this state within the life expectancy of CRM 2.0.  There are three major obstacles in our way which imho would take much longer time to overcome:

1. Authenticity - many, if not most, institutions see the customer from the next quarter sales forecast point of view and no technology can change that. There is an opinion that the institution has no social conscience, only individuals that are part of the institution have it, so until there is a very clear, undisputable connection between authenticity and profitability it would be a long time before we see any meaningful change. I know there are exemptions and we all can name one or two institutions which have demonstratively got it, but we need much more - even now the truly successful implementations of CRM 1.0 are still only a relatively small minority relative to the number of attempts. Watch this video for experiencing an example of current institutional authenticity

2. Asymmetry - it is too common of an experience that an institution has a much louder voice than the individual. I can see great promise in current technology to change that, but the model has yet to emerge to the best of my knowledge.

3. Execution - it takes time to earn trust in a relationship, whether it is between people or institutions, time to observe a certain consistency in behavior and authenticity of intent, which I covered above. We all have experienced dealing with individuals who represented their institution in an exceptional way, but building processes and organizational changes to provide such experience consistently, across an institution, is still a huge challenge which is not a technology issue but a cultural one.

All these aside I do believe that change is the only constant and technology is a great tool to accelerate change.

Ben Worthen of WSJ Business Technology Blog reported about adoption problem experienced by SureScripts.

Doctors are reluctant to change the way they’ve always done things, Rick Ratliff, SureScripts CEO, tells the Business Technology Blog. That’s why more than 26,000 pharmacies across the country — including major chains like CVS, Walgreens and Wal-Mart – are now marketing the e-prescription program directly to consumers. The hope is that enough patients will ask their doctors about the programs that doctors will be forced to use them.

This story illustrates a cost of ignoring cardinal law of holistic application design - WIITFM (What Is It For Me). Considering that the appeal of SureScripts for the pharmacies is no-brainer (shifting a burden of data entry to doctors), what would motivate the doctors to change the way they do things?

Many business applications project investments were written off because of this failure. CRM initiatives are probably the hardest hit segment. However the attempts to correct this by bullying people into adoption, as Mr. Ratcliff is quoted to suggest, will likely produce even more waste and anguish. Perhaps honest and creative review of the system would produce an improvement, which would motivate doctors to use the e-prescriptions because it save time for them - like allowing them to dictate a prescription.

“Win-Win” is a popular phrase for Sales motivational trainers, but it is probably even more important concept in “Design for Adoption”  business.

Michael Krigsman, who’s blog I subscribe to, posted an interview with the SAP CTO, Vishal Sikka who is quoted:

Lines of business know the what and IT knows the how.

Mr. Sikka does not stop there and proceeds to talk about how this relationship should be managed. However this thought is very commonly used as a dogma which I would like to challenge.

If this is true, how can we explain all the projects delivered out of time and budget constrains, all the unsatisfied business communities, and low rates of adoption we read about in Michael’s blog? Perhaps these lines of business do not tell what they need? Or perhaps IT doesn’t have the know-how to install enterprise software or to maintain infrastructure?Â

I would like to propose that the above mentioned wisdom falls into a category of truthiness and the lines of business do not know exactly what their requirements are, as well as IT often does not have the know-how and political clout to provide thought leadership required to articulate and negotiate these requirements. The what is often in a realm of notions and wishes, which are impossible to act upon. The requirements are expressed in a form of functions and features which have very remote connections to the economic reasoning for the project. The lack of this knowledge is greatly discounted and misunderstood. The "what" needs to be figured out, challenged and probed until a set of specific business requirements is distilled which communicates why it is economically necessary to invest and how the change adoption will be managed. Perhaps lines of business have to accept ownership, responsibility and leadership for success or failure of the organizational transformation initiatives rather than "outsourcing" this responsibility to IT.