In last post Customer is the king... and more!, I wrote about inevitable customer dependency and how sellers may take advantage of it.
Dependency should not create a sense of 'being locked' with the product or service. Some ways by which customer gets 'locked' are:
Dependency should not create a sense of 'being locked' with the product or service. Some ways by which customer gets 'locked' are:
- Proprietary data format and ways to read / write it
- Custom components to do trivial jobs
- User accounts, loyalty programs
- Restrictive licensing
- Artificial compatibility between hardware and software components of same seller
What are the ways to reduce - if cannot entirely remove - customer's dependencies on sellers and their products? Some ways are:
- Increase standardization, use minimal standards
- Increase generalization, reduce specialization
- Make product flawless
- Make product stateless
- Educate customer to help himself
- Make system customizable / soft coded
- Provide compatible components and let customer assemble it to suit his purpose
- Make interaction transactional
Above ways still do not guarantee unlocking the customer from product. (except may be the last one?).
I thought of more ways that could help unlock customer from product:
- Provide easy exchange with other systems. So that customer can easily switch between systems of his choice. A good example is a wiki site being viewed and edited in different browsers of user's choice. On the contrary, word documents can be edited using only Microsoft office or at the most Apache Open Office.
- Provide easy way out! Unnecessarily locking customer in your product / system is unacceptable to customer, and in long run to the seller as well. Giving an easy way out of your product / service is a good solution. Some examples are: Storing a data in simple ASCII text or XML form instead of proprietary format so that any other system can consume it.
Am I insane? am I allowing customer to walk away from my product? Customer is always going to be dependent, but attempt should be made not to lock him for longer than necessary! No matter what, customer never likes to be 'locked' with a system he is using.
He may choose to remain engaged, with a possibility of easy disengagement.
We should aim for a situation where, in spite of having a way to walk out of your product, customer chooses to remain engaged with you and your product. This is the best state of customer relationship.
Code not made available is one more reason to get locked
ReplyDeleteThat would be locking before delivery or insufficient delivery. Even after successful and complete delivery, customer still remains locked. We need to remove that locking.
ReplyDelete