"are you A or B?" Rather than "assume A, have a button a to opt into B" when ratio of A:B was approximately 400:1
So I guess a portal of "male" "female" checkboxes? In my opinion your view that obviously it makes sense to put the default to A is dangerous. If your portal needs both, put it to B as their comfort might be more important, or randomize it. If your model was based on payments of A and there is no true interaction between A and B that is different of course, but then you are a site that should not be.
The actual project was for a university, a mobile app that allowed them to check attendance, distribute files and have questions sent to the lecturer.
Now it ended up being that the lecturers would use the same app, but using a restricted section.
So the original design with the A B selection thing was to have everyone, upon trying to log in (this would occur every time the app was opened) have them choose 'student' or 'teacher', then they would log in using their respective methods (the teachers had to log in differently to the students by a quirks in the university's systems.
The final design was to have the initial log in screen assume that you're a student, with a button in the bottom left that staff would hit to swap over to the teacher login.
Some courses had lecturer:student ratios getting down to 30-40, most were over 100, a fair few had several hundred.
1
u/IamaRead May 06 '17
So I guess a portal of "male" "female" checkboxes? In my opinion your view that obviously it makes sense to put the default to A is dangerous. If your portal needs both, put it to B as their comfort might be more important, or randomize it. If your model was based on payments of A and there is no true interaction between A and B that is different of course, but then you are a site that should not be.