10 Unwritten Rules for a Consultant to Live By

by Volker Weber

  1. You work for the client, not the consulting firm. No matter who cuts the payroll check, the client is the one paying for your services. Do the right thing for the client, not the consulting firm (or anyone else).
  2. Your network of consultants is your most important asset.
  3. Consultants should keep a blacklist of firms and other consultants that should be avoided, and why. Share this list with your network of consultants but not to the general public.
  4. Do not make negative comments about another consultant within ear shot of an employee of a client, and especially around the sales and marketing people of a consulting firm. Negative comments are fine between consultants, but, keep it "in the family". But, never break rule # 1. When dealing with non-consultants, do like your mom always told you, "if you don 't have anything nice to say about someone, don't say anything at all".
  5. When your consulting firm takes you out to lunch, remember, you are really the one buying lunch. It is coming out of the consulting firm's cut out of your rate, so just pretend you are picking up the check. Would you really want to pay to have lunch with this person? The same thing holds true for all events and gifts you may get from the consulting firm.
  6. Avoid giving consulting firms information on possible leads without first getting everything in writing (especially your commission). And even then, the contract usually isn't worth the paper it is written on. Don't expect to get any money for info on leads, so be careful who you give them out to.
  7. When referring another consultant to a consulting firm, expect a finder's fee. $2 per hour is the minimum that they should offer. Flat fees typically benefit the consulting firm not you, so try to avoid them. Remember, your finder's fee is coming out of the consultant's pocket. So if the consultant is part of your network, you should waive the fee. Your network keeps you employed.
  8. If you didn't negotiate your rate starting at the consulting firms billing rate to the client don 't try to find out what it is, unless you are prepared for the consequences. That knowledge will usually just make you disgruntled.
  9. Never tell the client what the consulting firm is paying you. If they need to know, it is up to the firm to disclose that info (see rules #1 and #8).
  10. Avoid professional days. You don't bill for hours you don't work, so you shouldn't work for hours that you don 't bill. A good project plan, with a budget to match it, is a must. Unless of course you created the project plan, then you should live with the mess that you created.

[DonXML via jimmiz]

Comments


This is an excellent set of rules. I've never tried to really codify my personal ethics code, but I doubt it would be much different.

Surely different, but not at its core.

I can also say that those times (fortunately much earlier in my career) where I ran into trouble I'd say most could be traced to a poorly or downright not followed one of these tenats.

--Andrew

Ou...especially #1 is most important and useful for some consultants from the big 5 Agencys.

cheers
Ingo

I'm glad to see that people are reading the list. Now, we all just need to remember to follow them (it isn't always easy).

Don

I asked Don for clarification what "professional days" are. Here is what he said:

Here, in the States, some companies want to pay based on a professional day. Basically, you will only get paid for 8 hours work, even if you work 10, as a professional courtesy. It is a holdover from fulltime employee world, where there are hourly employees and salaried employees, and the salaried employees are considered "professionals" and don't get paid for working more than a normal day (8 hours), but get "paid" a yearly bonus. Some clients and/or consulting firms try to get the consultants to do this too. I know of consulting firms that do this to their consultants, but still bill the client for the extra hours.

Thanks, Don, that has made it perfectly clear now.

One particular extension to rule #1 that deserves a note:
What, if your client is itself a consultancy? What, if these guys hire you to work at their own client's sites? This is the situation I regularly face. Anyway, if you employ rule #1, you inevitably come to acknowledge that your client's client is -NOT YOUR- client. The rest follows straightforward: What is good for your consultancy is good for you. What is good for your consultancy's client is good for you -if and only if- it is also good for your consultancy-client. That's the extension to rule #1: subcontractor's benefit rule.

It does not matter whether you are a subcontractor or an employee of the consultant. Rule #1 is trivial if there is no conflict of interest.

I like this list, but I would maybe refine #1 a little to include: "Make sure the customer understands what s/he is buying", meaning, you (the consultant) need to articulate at some point what you are and are not willing to do as part of the gig.

Examples:
"I will tell you the truth as I see it, whether it's what you want to hear or not"

"I will not reveal secret stuff I might know about what your compeitors are doing. I will afford you the same confidentiality"

"I will not spy on your employees for you"

Post a comment











Shall I remember this for you?




Use your full name and a working email address. Unless you want your comment to be removed. No kidding.



Recent comments

Tim Vogel on Apple Airport Express dropping off the network at 12:06
Ed Brill on Five days, three countries, three taxis at 01:37
Stephan H. Wissel on Bathtub with a view at 12:21
Nick Daisley on Five days, three countries, three taxis at 12:16
Dominic Bennett on iPhone OS 3.1.3 brings back Internet Tethering to unlocked iPhones at 12:04
Stephan H. Wissel on Snacks at 12:04
Stephan H. Wissel on Five days, three countries, three taxis at 12:02
Andy Mell on Five days, three countries, three taxis at 11:23
Armin Roth on Five days, three countries, three taxis at 11:22
Rob McDonagh on Unintended Acceleration at 23:44
Volker Weber on Unintended Acceleration at 19:39
Charles Robinson on The Future of Publishing at 21:36
Charles Robinson on Unintended Acceleration at 21:31
Rob McDonagh on Unintended Acceleration at 15:28
Asi Christo on iPhone OS 3.1.3 brings back Internet Tethering to unlocked iPhones at 12:49
Ken Bisconti on Bathtub with a view at 10:33
Nick Daisley on Unintended Acceleration at 07:57
Asi Christo on iPhone OS 3.1.3 brings back Internet Tethering to unlocked iPhones at 05:58
Harald Geiger on Bathtub with a view at 01:41
Lars Olufsen on The Future of Publishing at 23:44
Joerg Michael on Relocating your business? You'll keep only the dead wood. at 22:59
Kevan Emmott on Relocating your business? You'll keep only the dead wood. at 21:50
Samuel Orsenne on Relocating your business? You'll keep only the dead wood. at 21:01
Ragnar Schierholz on Bathtub with a view at 20:51
Nick Daisley on The Future of Publishing at 20:18

Ceci n'est pas un blog

vowe.net is a personal website published by Volker Weber a.k.a. vowe. I am an author, consultant and systems architect based in Darmstadt, Germany.

rss Click here to subscribe

Hello

About me
Contact
Publications
Certificates
Frequently asked questions
Join the network

Twitter Updates

More >

Local time is 19:52

visitors.gif
176 visitors online

News

Other sources of news, imported into my own format to make them more accessible:

Schlagzeilen
Weather

Archives

As most of my articles roll off the front page rather quickly, I am making an archive of previous posts available here. You can also use the handy search box at the top of the page if you are looking for something particular.

Last 30 days
More archives

Got the T-shirt?

Got the T-shirt?

Systems Architecture

This site runs on an Apache web server on top of the Linux operating system. The content is managed with MovableType which is implemented in Perl. Last but not least the HTML code your browser sees is put together with PHP.

© 1992-2010 Volker Weber.
All Rights Reserved.

Impressum