Quote Originally Posted by Foraet View Post
Do you mean a team of designers that probably discussed this ad nauseam before it was sent to multiple leads who inevitably rejected it a few times until it finally got approval only to be kicked back multiple times by QA until finally getting pushed to release? Only to be torn apart by thousands up thousands of hardcore users using the software in every way possible way? With complaints about ANY change or lack of change regardless of what you do.

I mean that's software development for you, but I'm always amused by this picture that there's one guy that's randomly coding stuff.
It actually wouldn't surprise me at all if each of the job kits were owned by a single designer - it wouldn't even surprise me if that single designer owned more than 1 job's kit design.

It also wouldn't surprise me if it didn't get "kicked back multiple times by QA" - I've never heard of a QA team that had the power to veto design decisions they don't like.

It's completely conceivable that a single person thought this was a good idea and Yoshida, reluctantly or not, went along with it despite playtesting [hopefully] including negative feedback.

Every one of their excuses for why they removed Kaiten falls apart under the slightest scrutiny - my bet is that it was done specifically to dumb-down the job, and if so, mission accomplished, working as intended.