Client has hired an idiot

[Zero Fuchs]

I've recently taken on a job for a client, which is to support a project and the engineer working on it. It took me all of 5 minutes to work out this guy doesn't know what he's talking about, but talks like he knows everything.

I've only been on this job a week and have already corrected so many rudimentary errors, some of which my client is aware of and some not. The ones he's aware of are due to him, not me, as I'm not an asshole. I'm trying my best to fix his errors discreetly but he seems to be hanging himself. The trouble is, my PO is relatively short but left alone, this guy is going to wreck the project.

I guess my question is what do I do? I did some work for this client a few years ago and he's a really nice guy. He took on this engineer after I last did some work for him and it's clear this engineer has oversold his CV. I can see this project is going to go to st so do I say something or not. If I do, how do I navigate it without looking like a tt or I want more work, which I don't, but just don't want his project to fail badly.

[TGCOTF-dewey]

Having been in this situation several times, you have options.

The direct approach - just explain the errors to the client. Avoid getting personal as THEY hired them so will be invested and likely feel it reflects on them.

Indirect - introduce gated reviews into the process where the errors will get caught and attributed. That way you're out of the direct firing line.

[Mr Pointy]

Just take the direct approach - book a meeting with the client & go through all the issues with him. Explain that you don't care about the politics as you are only on a short contract but you don't want to see the project cause problems for the client. It's then his decision about what to do, but you've been open & given him the information & it's not down to you if the project fails.

You need to protect your reputation.

[ARHarh]

Be honest open and respectful to all involved. Bring this concern up with the client, do not cast blame, just point out the issues you have found, and how you have or might solve them. Let the client work out where the problems were created. Keep on top of the issues and report any that come up in future discussions.

If you go in blaming this other guy for all the issues it will come across as just a personality clash and will not look good.

[MadCaptainJack]

Start documenting everything. You don't want to end up taking the blame if the whole project goes titsup.

[Zero Fuchs]

Thanks for the replies/advice.

Fortunately the times when he's outed himself have been when the boss was cc'd on his email asking for help, or asking me to review something. I've then been as tactful as possible when responding.

My client is also an engineer so suspect he knows full well but is being very quiet about it. It's leading me to think he might be family or connected somehow. Hence my reservation but I could be wide of the mark.

[Peterpetrole]

Would help to know the subject we are talking about

[aproctor1]

Peterpetrole said:

Would help to know the subject we are talking about

I'm not sure it's relevant at all, the OP seems to be a decent bloke trying to protect his client.

OP, if the client is aware, the suggestion to make some suggestions of how to manage the project is probably the most tactful way to approach this and leave them to it.

[Jag_NE]

How could you do anything but air your concerns?

[Collectingbrass]

Mr Pointy said:

Just take the direct approach - book a meeting with the client & go through all the issues with him. Explain that you don't care about the politics as you are only on a short contract but you don't want to see the project cause problems for the client. It's then his decision about what to do, but you've been open & given him the information & it's not down to you if the project fails.

You need to protect your reputation.

This, and not just with the client but in your wider circle of contacts too. You need an early sit down with the client, identify your concerns about the project and agree an action plan. As a client in a similar positions I'd expect it anyway after the first week, usually it's called the discovery phase. You've discoved a can of worms and no mistake, but it needs addressing now while all 3 of you can course correct.

[Peter911]

You have to point out the errors as soon as possible to the client. You are managing the project and it’s not going to go well. It sounds like if you continue with the engineer it will fail, be over budget or need remedial work.
You are the project manager. Sort it. That’s what your paid for.

[Zero Fuchs]

Jag_NE said:

How could you do anything but air your concerns?

That's a fair comment and I should perhaps put my big boy pants on.

But I don't take the possibility of getting someone sacked lightly, irrespective of their inability to do a job. He could probably be a good engineer but the solution would be for my client to spend more money and hire someone to train/guide him.

It's something I could do but just don't have the time, due to having other clients.

The consensus seems to be to have a chat though, so will do that. Thanks again to all for the advice.