|
|
|
What is a Senior Consultant ?
Did you ever thought about what a senior consultant
is, when ever you needed one?
I thought many times about it, when I needed a professional expert
behalf on my side.
But how is it possible, that young and dynamic university graduates are already
called and sold as seniors after 2 years of working in a consulting company? Our understanding of a senior consultant: a senior is able to listen and is able to understand the specific requirement of his/her customers. The senior is a fair (sparring) partner of the customer, has a clear opinion in the area of his/her competence and stands for it also in inconvenient situations. A senior is self-confident and honestly as well to inform the customer immediately in cases of risks and gaps. A senior consultant is always self-motivated to achieve the best possible solution. Why we have to pay more attention to your satisfaction?
Did you
ever thought about why a self employed consultant,
must pay much more attention
on customer satisfaction than an employee on the payroll of a consulting company
must do? I am thinking on it around the clock, because we all earn our money
directly by satisfaction of customer needs on a contract basis and not by a
fixed salary. No contract, no money! It is just simple as that! How SAP R/3 Projects could become more successfully? Did you ever thought, how SAP R/3 projects could become more successfully? We always thing on it! Some of the small hints we like to give you already here are: Have a long term master plan for your IT-Projects. Think about your key success factors of your business and clarify what you want to control for what purpose! Clarify your reporting requirements based on these factors already at the end of your rough design phase and highlight them for your project team members over all modules! Establish formal problem escalation and decision meetings with interdisciplinary team members; provide a fixed agenda at least one week ahead to all participants. Start never a meeting without a moderator and time schedule. Document the results of your meetings already in the meeting with choosing the right media visible for all. Try not to use high sophisticated project management tools! Try to make a detailed table of content for your end-user-documentations (simply a word document by module) at the very beginning of the detailed design phase of your project. This document can also help you to measure your team progress. If you can not close a chapter or a topic by fixing it in the documentation, then it seams to be an open topic to be clarified! Do not accept changes on agreed and committed business processes after rough and/or detailed design phases. There might be some exceptions in the case of obvious errors in business process flows which have to go over your problem escalation and decision making teams! Try not to accept own developments and programming requests by the user departments, if they do not sign up as responsible for the development and as well for the maintenance cost for the whole live time of the system! Every needed own development should be formally requested and confirmed. Integrate one or two people of your IT-maintenance department in project work and train your IT maintenance people as they where key users at the end of your project. The process know how they will get will be enormous valuable for your company. Do never the mistake to buy extra consultancy capacity for end-user trainings at the end of a project only. Nobody can train your organization at the end of a project without knowing your business your processes and your project history? The provided training can only be a general one.
Usually the implementation of any ERP
software is forcing a higher degree of integration of your business
processes. With the introduction of a system you are obligated to rethink your
business processes and their integration aspects and impacts to your business
and organization. However there are some business process groups, which usually do not appear important in the first
view.
Last but not least, if possible do not start with the last available release of any ERP software. It is the same as with all new products. They have a lot of errors and mistakes at the beginning. With "one step behind strategy" you can minimize efforts and save time and money. or Let us introduce some of our consultants
|
|
Stand: 07. November 2008 |