I had intents to go through with it, fully knowing that my teammates were unreliable and hard to get to work. I had things sorted out that we would log hours – and everything had to be approved by me (Project Leader). I was prepared to do most of the work alone.

What changed was that I increasingly became aware that I *really* didn’t want to bear all this burden, plus have to chase after my coworkers. I already work full time hours – and I was beginning to doubt I could pull myself and team members together to deliver a quality product, and still have any time for other things (like, chores, socialization, recreation).

The other two members don’t have jobs, and so aren’t limited. I had begun to see that even once school was completed, they weren’t that into doing any work. And I became even more doubtful about the possibility of doing the project. I envisioned bug upon bug, and not being able to rely on my coworkers to do what they’re supposed to do reliably.

So I told them I was out. The clients (if they decide to go on with the project) are expecting I’m part of it – but I’m pretty sure they’re already informed I’ve left the group. I didn’t want to do this if it was going to be a poor quality job, and hurt my reputation (especially since the client was a Municipality).

I know the oppurtunity was perhaps a good one, and maybe in different circumstances I would’ve gone through will it, and it could’ve worked. I do feel bad about the sudden and late change, but it was something I had to do – I had already given up on it, and the biggest reason was exactly what you wrote about, reputation, and especially first impression. Your first big job could really mean a lot, so I think it’s important you start out with small, high-quality, low-risk work.