What makes a good IT consultant?

What do you think are the key values and skills that a good software consultant should have? How do you think they should act? What do you think the 10 basic rules of a good software consultant should be?

The reason I ask is because I so often hear about bad consultants and consultancy firms failing to deliver products up to standard, on time and within budget. I am going to give my basic 10 tips for becoming a good software consultant based on the failures I have seen in consultants and consultancy firms of the past. Feel free to add your own and build on those that I have suggested and recommended.

1. Always turn up on time, fit into your working environment and have a professional working attitude.
2. Ensure that you know what it is that you need to deliver. Get a specification that is UNAMBIGUOUS agreed and signed up against by both yourself as a consultant and also with the management so that you both know what it is that you have to deliver.
3. Ensure that an accurate and reasonable deliverable time scale is agreed upon between the contractor and the company and that it is absolutely clear what is delivered, i.e. whether it is just the source code, a complete and tested system etc.
4. If there are bugs (if... try to avoid these where possible!) in the system do your best as a consultant to minimise the impact of these to your client and their customers. If it is a major bug, fix them as quickly as you can and make sure that they are fully tested so that you can be sure that you haven't introduced any further issues into the software.
5. Ensure that your work processes are clear and suitable for the task at hand.
6. If the scope of the work suddenly changes, ensure that the client knows what has happened and let them understand the impact of this change in terms of time to completion, cost and project management.
7. If you find a problem with the work or don't think you will be able to deliver a complete solution yourself let the client know that. Don't just work around it or leave the problems unchecked until the delivery date, this leads to bad client relations and you want repeat business from them if you can manage it, and rememer that by not delivering you make all consultants look bad. It reduces trust in the consultancy business as a whole!
8. Only take on work that you have the correct skills set for. Steep learning curves slow projects down and create an element of risk that the contract may not be honoured.
9. You are expected to deliver all or part of a complete solution. Make sure you deliver it and that your client is happy with what has been delivered.
10. Make sure that you have excellent communications channels between yourself and your client. A breakdown of these could be the difference between the success and failure of a working relationship!

I am absolutely certain that there are many more pieces of advice that could be given on this subject so I look forward to hearing a few of them from consultants and clients to consultants out there. Maybe we can build up a strong set of rules for consultants to follow... maybe the "Rules of the Consultant" or something like that.

posted @ Wednesday, February 01, 2006 7:56 AM

Print

Comments on this entry:

# re: What makes a good IT consultant?

Left by Venus Geek Admirer at 2/4/2006 12:23 PM
Gravatar
I suggest the reality is more like this-


1. You need to keep several irons in the fire. If you end up late for a meeting once in a while your customer will probably forgive you and forget it sooner or later.

2. A perfect specification would be great but don't cause too much fuss if there are some holes in it. Chances are your client doesn't know exactly what they want. If they do now, they will probably discover they need to make some changes as soon as you have started to make progress.

3. Agree to whatever time frame your customer desires. If you don't take the work on someone else will. By the time your customer realises you can't deliver on time they won't be able swap to one of your competitors. If you are late you can always blame it on the poor specification or late changes.

4. All software has bugs. Bug fixing means more work which means more money.

5. It is important to present an air of professionalism at all times to your client. Even if you work in a disorganised manner and your coding seems to be a little less than perfectly structured make sure your presentation is slick.

6. Scope changes are a great excuse for the project over-running which means you can bill for the extra work.

7. Show initiative and try to work round problems. No one wants a consultancy that keeps pointing out problems with the specification or the system their software will go into.

8. If you don't think you will be able to deliver a complete solution yourself, keep quiet. Once you have the work you can either learn the skills or take on someone who does for a while.

9. Deliver what you can. All customers will accept a few tweaks as they have no alternative by the time you reach the deadline.

10. Know who signs your cheques in your customer's organisation. They are the one to keep happy and it's unlikely they will know diddly squat about software.

# re: What makes a good IT consultant?

Left by Alberto Cueto at 8/20/2008 3:48 AM
Gravatar
Well, Venus Geek Admirer, I think, that yeah, reality might be like that, but the question was: What makes a good IT consultant? I mean, the stuff you are pointing like: "I don't know how to do it now, but let's stay quite, I mean, maybe i will be able to do it later..." it is actually like the oposite to being a good IT consultant, consultants are supposed to be experts who give you advice, an expert is this person that knows about it, tha has the "know how", not someone who accepts every project and tries to keep the "big fish" happy. Deliver what you can? Come on!

Your comment:



 (will not be displayed)


 
 
 
Please add 8 and 3 and type the answer here:
 

Live Comment Preview:

 
«November»
SunMonTueWedThuFriSat
2627282930311
2345678
9101112131415
16171819202122
23242526272829
30123456