[pvg]

I think at 5 out 8 it's not a mere firing, it's a bloodbath. If you've built any kind of team cohesion, you'd be throwing it all away. Obviously, if they're all critically detrimental to your business, fire the lot and eat the hit. Have you considered firing maybe 1 or 2 and seeing if it improves the performance, overall?

[firingtest]

Actually I wasn't considering this but you and many others in here pointed out mass firing would be very bad with very good reasons. Now I changed my mind about this, even if I finalize my decision on firing it'll be worst to better in every 2 months (unless they change in the middle).

[Goladus]

I actually think dragging it out over several months would be even worse. I wouldn't fire more than 2 that way. Your good employees will be wondering if they are next and if they should be polishing their resume (which they'll do instead of work you need done)

[neilk]

Do not do this. One firing is bad. Multiple firings drawn out over time make people feel like the project is doomed.

Even if the people deserve to be fired, then people will be blaming you for hiring the wrong people or being indecisive.