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...

Tips for a long ride

 A long ride on a Motorcycle is a thing filled with thrill and excitement. How much long is 'long'? Should it be defined by distance, time taken, number of breaks or the difficulty level? I think its a combination of all. Depends on how much time you spend and how much stress you are subjected to. None-the-less, here are some tips I scribbled. Before the ride: Research the route. thoroughly. For road conditions, stops, fuel bunks, service and emergency support etc. Estimate timings. Plan the short stops and overnight stay if need be. Book in advance. Research the weather. and prepare for it. Prepare the travel kit. Plan on type of luggage. Plan the weight distribution. Make sure it will be well balanced when on bike. Plan the luggage according to Cabin/check-in concept. Practice some maintenace if you can. e.g. Chain cleaning and lube, puncture removal, minor adjustments and settings. etc. Go for multiple short rides to get used to your bike. You must get used to extended sitt...

Classification of long rides

  The perception of long ride varies greatly among motorcycle riders. Especially new ones (does not mean young ones). Some call 400km ride a long ride, some call 1000km ride a medium one. Not that I am an expert on motorcycle riding, but I thought of putting the method to this madness. I jotted down my thoughts about classification of rides. I thought of 3 key parameters viz. Distance traveled, Time taken, and Effort put. Based on these I came up with following categories By Distance: 1. 400-1000 km. A ride should at least be 400km to think of it as a long ride. 2. > 1000 km. These rides really require a lot of preparation, stamina and experience. By time: 1. 2-3 days: Have more than one day, and you can reach longer distances which is essential for long ride. Exceptions exist, but yeah. they are exceptions. 2. week-long: Week long ride requires good planning, carrying of enough luggage and  tough mind. It should not just be a rote ride. Some sight-seeing, adventure, experi...