Rohit Chauhan
Team Lead SAP IS Auto VMS
Tata Technologies Ltd.
Rohit Chauhan is a member of:
Could you tell us briefly about your family background?
I am son of a Government employee. My father got retired as a Class I officer in UPSRTC. I am married to a Biotech Engineer. I got a younger brother, who is currently pursuing MCA and a younger sister, who is married to a CA.
Most Important Decisions
The most important decision was to work for 3 years with Lucas-TVS before joining the full-time MBA course. Working with corporate taught me many things which got honed in the MBA course.
Most Important Lessons
The most important lesson is to keep learning new things. There should be a hunger to learn always. Secondly, there is no room for excuses, there is always a way out to get the things done. You need to find that way, that's your job.
Plans for the Future
I see myself as a Project Lead, managing a team/project all by myself.
Points of inflection
None, everything was an opportunity.
The Journey So Far
It has been great so far. I am happy the way it is turning out. Its good learning so far and has made me a better person, professionally and personally.
Role Model
Stephen Hawking. First answer to 'WHY' is because of his fighting spirit. He was diagnosed with a fatal disease (ALS) and told by doctors that he doesn't have much time to live, yet he is alive after 50 years and still rattling the world of Physics with his equations.
A Fine Balance:
Its simple. Isolate both of them. Full focus on work when at work, and full focus on personal life when at home. I don't mix them until and unless necessary. And above everything, if one enjoys the work he does, the balance comes automatically.
Current and Previous Responsibilities
I am responsible for the delivery to the client on some WBS elements of the project. I take care of the end to end delivery for those WBS, right from Business Requirements Gathering to testing to implementation. I am responsible for the client satisfaction for those deliverables.
Essential Advice
Know the process from the business/practical point of view. Systems view comes later. Also try to understand the viewpoint of the User, who is actually going to use the process/application.