Skip to main content

What you get when you visit customer

A warm welcome and hot coffee.!... no no no. that is not enough. You get to see a whole lot of different world.

You get to see how your customer looks

Do you have some idea about your customer? Do you think he is great, rich, technically enabled? He knows everything and anything? no. Customer is just like us. he also has limited resources, cost implications and techincal problems. If you can understand this, it will reflect in the solution you provide. You will consider his problems, and use your skills most effectively to benefit the customer.

You get to see how your customer works

Customer has his own problems to solve. He has different soup in his plate. He is trying to reduce his problems by seeking solution from us. If we create more problems by our solution, it adds to his problems. You also get to see what ideas he implements to solve his problems. you can pick some idea in your solution. That will enable the customer to solve his problem in better manner. You also get to see what principles he follows to solve his problems. You can make use of them in your solution. When you visit the customer, you can identify actual problems to tackle and modify your solution accordingly.

You get to see what are his needs

 Does customer need a jazzy, grand looking solution? no. He needs a solution which solves his problem. It can be an independent application, customization of available application, or just a small script. But if even that small script solves his major problem, he is more than happy.

You get to know how he thinks

Customer's thinking style can be totally different than you think. You can incorporate his thinking in your solution. We work in a different domain. Our thinking style is acustomed to our domain. When you visit customer, you come to know his domain, how he thinks in his domain. You can also identify differences in your and his thinking and tailor the solution.

You get to see how much he needs your support

Customer is a user of particular technology but does not understand internals of it. You are the expert in that technology and you know the internals. You can guide customer in obtaining solutions with that knowledge of internals. Such guidance is also considered part of the solution. Customer will be happy to know internals of the technology he is using, to some extent.

You get to see where you stand

Customer's problems come in a lot of variety. you may not be able to cater to each and every need. But it still gives you a chance to judge where you stand. You can be far behind his needs or may have a far advanced technology. Matching your solutions with customner's needs is the key. If you are far advanced, you can quickly provide the solution. If you are behind, it gives you a food for thought and opportunity for business. Yeh dil maange more!

You get to see where you lack

Even if we think we have best solutions available, it is still in our own little world. You may also lack in the quality of solution that  you already have. Customer may ask for more. Customer may want to see quickly, how your technology works. He wants a quick demo, or a quick prototype. You may lack in quality of service provided.

You get to see what all you can do

what all we can offer. During a meeting with customer, it is a good exercise to try to match his needs with our solutions, and our capabilities. You get to see a whole lot of new world where you can use your capabilities, and areas where you can offer solutions.

You also get to see customer's happiness

...and sometimes rage as well! It is a great time when you go to install the functionality at the customer's place. Customer is anxious to see the new baby... what he has paid for! If he sees good results he is happy. He will call for a dinner party, site seeing trip, otherwise hot coffe can be on the your face instead of in the mouth!
 

Comments

  1. Put your legs in customer's shoe to feel his actual pain \ his needs & as you said, solution should be very simple :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Pune-Goa-Pune Motorcycle solo ride: A ride that was many things!

  Part 1: We decided to ride "Let's go Goa!" College group of friends and families announced the yearly Goa trip. Some said: We are flying.  Some said: We will take train.  Some said: We will drive. Shree (my friend) and I: (our wives not coming because of prior commitments) let's ride our RE Meteors! That's how we decided to ride. And a plethora of things started. Route search, Road condition R&D, riding schedule, packing list, load distribution, checking on safety gear, rain preparations, pre-ride maintenance and so many. We searched a lot on the web. read a lot of articles, blogs, updates and finalized on Pune-Karad-Anuskura-Rajapur-Goa route. While preparations were in full swing, Shree caught Chikungunya infection and was down with high fever! There was no possibility of him riding! However, I decided to ride solo and complete the trip. With Solo riding decision, few things changed. Non-stop one-way ride changed to a break journey. I d

A short ride to Kondane caves

This time it was a combined Trek and Ride experience. Motorcycle ride for 3 hrs. from Pune to Kondane caves base, Mini-trek of 45 min. to Kondane caves and ride back home.  My younger son Chinmay was my partner. He likes to ride with me once in a while, and definitely likes to trek :-)

Forcing to lock, Choosing to engage...

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: 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 Some of th