rather always do what she wants. I am not going to discuss why you should follow this, and a couple of case studies. The name of the company and individuals have changed to protect the privacy.
It is important to follow the BOSS. Everybody wants loyal people who she can rely on. But to be reliable one sometimes needs to out smart her boss, as boss might not have all the information that she has. I am providing a couple of case studies where following the boss did harm the employer AND/OR not following the boss worked.
CASE STUDY 1: Sam and Sonia worked at a IT service company and had a tough American customer. They were good in application programming and technology, but did not know the Investment banking. Because of their lack of domain knowledge and Indian ascent they were facing problem in handling costumer during post production support. Their Manager learned about the project and gave a short term and a long term solution. He asked them to enroll for Investment Banking 101 and spoken English in US ascent course as a long term solution and asked to twist the tongue so that it will be more US like ascent and read more about portfolio and equity (as their project is based on Portfolio) for short term resolution. Sam followed his Boss's advice religiously with
little success. Sonia did not do what exactly her boss said, but customer called their boss and asked only Sonia to be their point of contact. In return Sonia got a good appraisal and promotion. What did Sonia do? She discovered that customer was able to understand the English of Raj, who is deputed at customer location. She found out that it is not their ascent but speed which is causing the communication gap. So she tried to speak slowly where as Sam tried to speak in an unknown ascent (twisting tongue). Sam was busy reading about portfolio where as Sonia mastered the flow of the application and what exactly is bothering customer. She found out customer was unhappy because the page takes 30 seconds to load the page when an user logs in and what can be done to reduce it when Sam was reading about Equity Portfolio etc. She was able to understand customer and her requirement. So she was able to provide resolution.
So she got good appraisal, hike and a promotion.
Case study 2: Sam was deputed to customer place in London. In one of the REAL TIME trading application response time was more than 2 minutes at sometimes and mostly within 2 seconds. The requirements signed by client and service provider claims it to be 2 seconds. SLA claims any such problem in production must be resolved in 15 minutes, and in case it does not get resolved, it gets escalated and reaches VP level within 24 hours. The application was working fine at development and UAT environment but did take more time during production. Level 1 support was unable to solve the problem in 15 minutes, so the management called Sam and Harry who is known for their technical brilliance to resolve it. Their manager asked them to tune the queries what might be the most probable reason for the problem. Harry tuned the queries so the response time is within 1 second most of the time but close to 2 minutes during peak load time. Sam instead of tuning the queries checked the application log and did some profiling using the tools available. He figured out that JVM was actually not tuned for their requirement. So GC sometimes takes a long pause during peak load, and there are some physical memory leaks, which affects performance during peak load. He tuned the JVM parameters and asked for a hot fix for the memory leak. This happened in 2007 when software market was good, and market started slowing down in 2008, so client wanted only one person at London, and they have asked for Sam though Harry is senior to Sam.
Monday, 21 September 2009
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment