Top 5 client mistakes dealing with consultants.
Top 5 Client mistakes when dealing with SAP consultants (thoughts from the creators of ERPandi.com):
Symptom: Job requirement written poorly. Ask for “unrelated” skills in a single resume.
Risk: Recruiters will pass on good resumes because they do not find half the technologies from job requirement. “You”, as SAP clients/customers, will loose good candidates. And end with a cooked up resume tailored to fit your job requirement.
Symptom: Rely completely on big brand implementors with too little validation.
Risk: Implementation partners are a two edged sword. Make sure you are plugged into their process and implementation every step of the way. It may be their show, but it is your money.
Symptom: Too many levels of subcontractors. (Related: reduce the levels)
Risk: The consultant delivering your product is under paid. Going by you-get-what-you-pay-for, the system works against you. Emphasize on not more than two levels of sub-contractors.
Symptom: Misplaced trust on a consultant to deliver. Interview is an imperfect screening process. So conciously validate a consultant’s performance early in the project engagement. Do not wait three months before looking for a replacement.
Risk: A project that is way behind schedule and out of funds.
Symptom: In awe of pretty ppt and long, well-formatted word documents. Communication is good but do not over rate it. Often end-clients encourage talkers & email monsters and crap on the guy who delivers.
Risk: Sets a bad tone and affects morale. Productive people are going to loose interest in the gig. Creates a gap between you and the hands-on guy who implements.
Hind sight 20/20, in this case, has two certainties:
i. A Not-So-Successful project
ii. A consultant and/or primary vendor who already has cashed in their chips.
These are just few client mistakes we experience on a daily basis.
Please share your experiences. Remember, each successful implementation is a big win for the consulting community as a whole.
Check out similar blogs @ ERPandi.com/blog