I think, to be honest, it is this post which could do to be delivering more value.I am an implementations consultant. The reason why I am happy with my title? Because I consult. Perhaps you are surprised that implementation consultants consult? Fair enough - but I think that belies a lack of understanding of our professional - which I agree is not completely one-sided.Let us take the example of a large ERP system. Your post, Bob, implies that we simply take this solution and implement it. Simple. No problems. No consulting. However broaden your view of consulting to outside the boardroom. It is sometimes equally, if not more, challenging, to go into a factory (staffed by people who are reticent, if not fearful, to change / technology and the thought of a consulting firm becoming deeply involved in their entrenched processes), analyse their needs and their requirements, then tailor the solution around them. More often than not, the solution we implement doesn't initially appear to fit their requirements so we talk to them, think creatively about how we can utilise the functionality of the system, apply change management techniques - to come up with a solution.If this is not consulting - then I don't know what is? I would also argue that implementations consultants get more exposure to the key drivers of the business - which are, in anyone's book, it's people.