How to Infuriate your WebGuy for $500, Alex
So, I get an email from a client sent to both me, and my boss's boss, informing boss's boss of the mythical "completed" status of a job that was, indeed, 80% or more complete, but the last 20% was driving me crazy. Not only had said client announced the "completed" status to boss's boss, but the final product had already been marketed fully and promised to client's customers, without being greenlighted by me or my offices.
That was step one in "how to infuriate your web guy."
Next, add to that an uncommunicative subordinate of said client, who hasn't gotten you even the first taste of her information for aforementioned site. Nevermind the fact that it will be presented to you completely differently from the other functionally-matched piece, which you've had weeks to work on. (And no, I still don't have it.)
Thirdly, (Thirdly? There's more?) add Scope Creep to the mix. (FYI, scope creep is when a project somehow finds a way out of the bounds of its original scope. You need it to do this, but you only told us about this this and this... so we built it one way and you need more, so you find a way to make us do it. Yesterday.) Additional functionality requested after the functioning product is turned over and after the client has had plenty of time to review it as-is.
Fourthly, (good lord!) while working to fix the problem, using an utterly foreign concept called a "development server" (as opposed to a "live, production server") we figured out the problem which was the final 20%. The client was contacted and told which parameter they would have to change on their end. Only, when they did, they expected to see it on their live site, when all you were doing was final testing in development. So, then, when they didnt see a change, they changed five other parameters, thus breaking the current, 80% working in-production software. AND THEN (Oh, God, and then...) when told about the issue, the client then argued WHY IT SHOULD STILL WORK rather than accepting the fact that we'd spent 3 days (THREE DAYS) trying to fix it the same way they ended up breaking it.
When we finally got on the same page, everything was peachy, right? Wrong. The client still was toying with the parameters on their end. A little nudge here, a little tug there... BAM. Broke the live site again. "STOP IT," I shouted. And finally, a little voice of reason decided I meant it.
And then, I fixed the final 20%. Out of nowhere. The single good thing this Friday had to offer.
But we still don't have part 2 from the client's subordinate lackey. She can't even create a directory in Winblows using a step by step guide. I gave up.