3 ms·
I don’t think it’s solely a dev responsibility, but having worked in a UX role on a project that merged two systems with user accounts and millions of users, we
by nkrisc 4y ago
I don’t think it’s solely a dev responsibility, but having worked in a UX role on a project that merged two systems with user accounts and millions of users, we (UX, dev, product) spent a lot of time thinking of scenarios exactly like this.
You’re right, this was a support failure, but it was also a failure of the team(s) that performed the merge.
- chefandy 4y agoAnd who knows how many other scenarios they considered? The reason it's a lot of work to ferret these situations out is because there are a ton of things that can go wrong. Who knows how many other situations were considered? For this to be a development failure, we'd need to see a pattern. One instance doesn't make a pattern.
- npteljes 4y ago1. How would you know about the users that were missed? Just because they haven't complained, it doesn't mean that everything was alright. 2. Why do you think that B/A haven't spent a lot of time thinking of scenarios like this?