Hacker News new | past | comments | ask | show | jobs | submit
I've often found this is a mistake WAY too many people make. A successful team has a failure. Often, the reaction is restructuring, big changes, ...

I try to tell people that. "You're a 10 person team. You've had some 50 successful projects before this failure. That means this justifies at most a 2% change. A 2% change in the team is about half a day change, once per month, NOT more than that".

Invariably, the whole team is changed entirely, randomly, or going with the political winds, usually with much worse quality as a result. And afterwards they do see it didn't work.

And then they respond differently: they'll no longer admit failure, because they do see that the changes were a disaster, but you apparently fix that by refusing to admit anything ever goes wrong ...

I'm different. I think every project is a failure, it's just a matter of degree. You don't succeed in projects, you minimize how bad they are. Drives people up the wall though.

loading story #42065297