Should your library decide to use a consultant for a project, it might be tempting to hire the first one you hear about. After all, who has time to interview an endless list of candidates? But the first consultant who offers to help you is not necessarily the best choice. Would you trust the first shoe salesman who says he has just your style? Finding a consultant you have a good working relationship with is crucial. You are going to be investing significant time and money in this; it's best to shop around and interview several candidates. An in-person interview is the best way to find out if the consultant is someone you want to work with. But if you have only a small, well-defined project, a phone interview may be enough. Things to find out in the interview: Does the consultant's technical experience match your needs? Does the consultant understand the hardware, operating system, and software that your library uses or is likely to use? Has the consultant worked on similar projects before? Look at the consultant's educational background and work history. Does the consultant understand how libraries work? A consultant who has experience working with libraries is always preferable, but library-specific technical consultants can be hard to find. If you use consultants who work mainly with businesses, make sure they understand the library world. See the article Working with Corporate Volunteers and Consultants for ideas on how to orient corporate consultants so that they take your needs and limitations into account. If the work involves discussion and negotiation, make sure the consultant's values are compatible with yours and with what is needed to do the job well. How well does their solution fit? Talk through your needs as you see them. Ask them what solution they would propose. Can they articulate how the solution would address your needs? Can they justify why it is the least expensive solution that will work well? Do they explain things in a way you can understand? Consultants who make fancy speeches about what you need and use jargon you don't understand are not doing their job. You should never have to listen silently and feel ignorant. When the consultants use technical terms, do they explain what they mean? Do they clarify what you need to understand, so you can see how it will impact your work? Do you feel comfortable asking "dumb" questions? Are they trying to push one specific product? Some consultants have a special relationship with certain vendors, and will recommend their products even if they are not what you need. Others may recommend something simply because they are more familiar with it. Make sure the consultant does not represent any software or hardware companies. How busy is the consultant? Can the consultant commit to finishing the project in the time frame you want? Is the consultant clear about the responsibilities of the project? Ask any consultants to articulate what their role will be and what specific tasks they will have to accomplish. Find out how busy they will be with other things while they work on your project. The best way to find out how much they have thought it through is to request a proposed work plan from them What fee structure does the consultant use? Some consultants charge by the hour and some charge for the whole project. Are they willing to break the project down into stages, with an estimated fee for each stage? Watch out for pat answers about how much things will cost. For instance, a consultant who always charges the same to make Web sites probably makes them according to a formula that may not give you what you want. The bottom line, of course, is whether you can afford their rates or get them to negotiate. If the interview gives you a good impression, it's still best to check the consultant's references carefully. CompassPoint Nonprofit Services offers a great article on checking references. Request a work plan or proposal The final step in making a decision about a consultant is to see a concrete proposal for the project. You can ask a potential consultant to come up with a work plan for the project. If you decide to go with that consultant, you can incorporate the work plan into the contract you write. If the consultant comes up with a work plan that is extremely technical, don't assume it is fine. Ask for an explanation in terms you understand. You can also research it by running it by people in your library who know enough to tell if it sounds right. Once you have interviewed the consultants, checked their references, and seen their proposals, the bottom line is how you feel about them. Who can you work best with? By carefully evaluating several candidates, you can be more confident that your consultant will be the best one for your library. By spending a little extra time in the selection process, you can help avoid a world of trouble later on.
Documents
| Choose the Right Consultant |
Why and how you should invest the time to evaluate a potential partner.
|
|
Contribute to this topic
Do you have an article, presentation, or other content to share on this topic?
You can post it on this topic page. Find out more about submitting documents in the Member Center.
Ratings You must be signed in to rate this item
|
Average (0 Votes)
![]() ![]() ![]() ![]()
|
Comments
