Skip to main content

7 dirty consultant tricks (InfoWorld)

InfoWorld had a neat article a few days back called
7 dirty consultant tricks (and how to avoid them)

Those of us who are consultants should know that these are being done and should be pretty angry about it. Most of the practices listed here are the reasons why the right consultants (that would be us) don't get the jobs we bid on.

Those who run consulting firms should know about these and know that they are the best way to stay in business.

I wrote an response to this on my own web site more but thought I would share some of the immediate takeaways here:


1.  If you (as a client) aren't starting your project with a measurable result by a specific date, then you need to break your project INTO those results first. Otherwise, assemble an internal team and maybe ask for some guidance but keep the deliverables in mind at all times. If you don't, it becomes a money pit.

2. I often look at my work as a consultant as being similar to a good plumber: if you want me to fix a problem, I'll do it as quickly as possible so I can move onto the next problem. If you want me to re-design or identify possible improvements to your plumbing system, it will take longer but I'll do it right.

3. Best thing to do is MEET with the actual team who will be doing the work.

4. When dealing with fixed prices,
I always think it's in the best interest of the client to look at per-diems but with a cap. It allows the consultant their opportunity to shine through but also limits the company's exposure.
We once had our floors done by a company who looked at the floor and said "about $1600 labour based on x/day". By the end of the project, it was over $3400 because they didn't account for it right. This was a per-diem project and I should have thought first to put a cap on it. At the end, they still tried to weasel out of finishing the work and left us with a half-ass job.

It's an interesting article - typical of InfoWorld who often target consultants in their columns but it's also an opportunity for consultants to identify and address them head-on, especially when dealing with new clients (who may read InfoWorld).

Comments

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…