Getting Value From Consulting
I’ve been a consultant for the last two decades, most of that time running my own firm. So it should be one of the easier topics to write about, right? But it’s actually very difficult. It’s hard to be completely objective about something that has been my livelihood for most of my career, and something that I am heavily engaged in on a continuous basis.
I’ve decided to embrace that perspective, to acknowledge up front that I may not have the most objective views, but to share with you my thoughts and beliefs around consulting in the project arena. I want to start with some basics and look at what consulting is (and isn’t), and how it should drive value for everyone involved with it.
Consulting is different from contracting
For many people, “contractor” and “consultant” are used interchangeably, but they are very different. Contracting is associated with the execution of a piece of work; consulting is about helping an organization to change (improve) how they work. An individual may spend some of their time contracting—managing a project in exchange for a fixed fee or an hourly rate, for example—and some of their time consulting.
With contracting, organizations should have no expectation that their ability to deliver work in the future will improve. That may happen—I know of many project managers
Please log in or sign up below to read the rest of the article.
|
"It is best to keep your mouth shut and be presumed ignorant than to open it and remove all doubt." - Mark Twain |




