|
|
|
|
|
by wildrhythms
1298 days ago
|
|
So 1 person to design, prototype, and test the thing? The design has to go thru many iterations, feedback sessions, approvals by managers and their managers, approvals from the design system folks, approval from the engineers who have to implement the thing. Then the prototyping- should a designer also know Java and the Android SDK to build a prototype? And should they commit the code into production and set up an experiment for A/B testing? (Whole set of data collection and bias concerns and approvals needed here) Or if they build a prototype in, let's say, Figma, is that high fidelity enough? (More internal feedback and managers required) Then the testing: building a research plan that avoids bias, asks the right questions, defines how success is measured, yeah the feedback might be subjective but the process needs to be empirical. And then gathering all of this data and compiling a whole set of research findings and suggestions so the manager-of-manager whoever is in charge can feel comfortable with going ahead and actually building the thing. (I work in UX, and there is a lot of bullshit like this) |
|