Today's post is written by guest blogger, Phil Simon, an independent systems consultant and author of the excellent book Why New Systems Fail.
Although consultants make easy scapegoats when projects go wrong, there are definitely times when you should replace the incumbent.
Here are five good reasons to get rid of your system integrator:
Client-consultant relationships rarely sour over a single isolated incident. More often, a pervasive pattern of suboptimal performance and poor communication leads to a gradual deterioration of the union.
Although replacing your SI is the sometimes the right move, changing consultants mid-stream can be expensive and disruptive. Ideally, address relationship with your SI while there's still time to repair the damage. Hoping things will magically improve significantly increases organizational risk and only prolongs the agony. Don't let dissatisfaction with a partner linger for a long time; it's far better to address the situation directly and early.
Before making a change, perform thorough due diligence on the replacement. Otherwise, you may find the new SI is worse than one you just fired.
While it's tempting to blame the system integrator for all project hassles and differences of opinion, introspection is also worthwhile. Before pulling the plug, evaluate your own role in creating the problems you experience. The more accurately you understand each party's contribution to the negative situation, the better you can solve the problem.
Firing your system integrator is a last resort, but sometimes it is indeed the first step toward getting a troubled project back on track.
[Image via iStockphoto.]