Can tech industry learn from car industry?

Can tech industry learn from car industry?

Summary: Ever heard about the one involving a consultant and the sheep farmer? I had my own encounter.


Ever heard about the one involving a consultant and the sheep farmer? I had my own encounter.

I recently sent my car (the one I was raving about) in for its regular servicing. I mentioned to the service technician that at the last servicing, the previous service technician told me the car battery was weakening and would be due for a change soon. So the service technician said he would check it out. As expected, he informed me that the car battery was weak and he would proceed to change it.

What was puzzling was that when the bill was issued, it mentioned three separate charges related to changing the battery. I quizzed the service technician and his answer was even more startling--the first charge was to ascertain whether the car battery needed changing, second was to change the car battery, and the third was to confirm the change was correctly performed. In terms of services performed, the ratio of charges came up to 3:4:2.

I have no beef with the second charge and I guess I can understand the third one, even though most people would consider it part of the second task. What baffled me was the first charge, given that I was the one who told the service technician of the need to carry out the work.

If you are providing software support, do you charge your clients for telling you of their problems that they encounter? I think you should--after all you spend time listening to them. Then, after you fix the problem, do you charge for checking the fix was proper (that is, performing the acceptance test)? It all now makes sense--afterall, the mechanics have been doing that.

Topics: Outsourcing, Emerging Tech, Hardware, Legal, Software, Tech Industry

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


1 comment
Log in or register to join the discussion
  • Though there will definitely be apprehension in accepting this mindset, it makes perfect sense especially when applied in the software development.

    There have been several times in my previous experiences that a client consults with me, spending hours, even days, and costly parking fees and coffee to discuss their problems and dreams. These encounters often end up in solid ideas and laid out plans and diagrams of how to solve their problems.

    And not going into too much detail with this rant, you turn around with a promise that you'd be the one to help implement the project, only to find that the client has gone ahead and implemented your free advice.

    I need not elaborate how much that encounter cost the consultant in time and money...