As part of my career in software design, I used to run A/B testing and usability tests. This meant sitting with users and watching them use the software. Since IUE (initial user experience) was very important, this often included inexperienced users.
The data was absolutely worth it, and definitely improved my designs, but it took a lot of patience to watch people struggle and fail without intervening or saying anything that would affect the results. It was rewarding, but sometimes excruciating.
Care to share some tips? I feel I’m getting there, trying to navigate old ERP interfaces, new web interfaces, and AI interfaces, and a mix of boomers, millennials, Gen Z as user base.
I think two major things are understanding platform standards and that what users say they want is often not what they need or what will work best for them.
Innovation is fine, but IUE and usability are often better served by following common platform standards (for general apps on the OS, not necessarily trying to match existing and often shitty enterprise software).
Also, it’s important to look for root causes when people ask for a specific feature. Many users focus on specific UI elements when they’re having issues, and in a complex system, it’s easy to wind up with bloat by solving the wrong problem. This is often how enterprise software becomes so unwieldy, with options and elements seemingly vomited all over the UI. What users think they want and what they need can be very different things.
Sorry if this is too general or basic. It’s hard to design a system that works for beginners and experts, and A/B testing a mix of users early with lofi prototypes helps a lot. For existing software, just watching users interact with it is massively helpful.
Is this what you meant? Happy to be more specific if I missed the mark.
Nothing that techy. I did include power users in tests, but their requests were usually for specific hotkeys or to have their favourite (and lesser used by most users) feature front and centre.
It can be difficult to balance a UI for inexperienced and power users, but watching them interact with prototypes and the actual software does help.
As part of my career in software design, I used to run A/B testing and usability tests. This meant sitting with users and watching them use the software. Since IUE (initial user experience) was very important, this often included inexperienced users.
The data was absolutely worth it, and definitely improved my designs, but it took a lot of patience to watch people struggle and fail without intervening or saying anything that would affect the results. It was rewarding, but sometimes excruciating.
How did you manage not to strangle anyone, nor jump out of the window?
maybe a high enough salary
They’d probably have to put me behind glass or just make me watch a tape like it’s an old handegg practice session.
Nah, they’ll just lock you in a cuck cage
I’ve watched pups escape from those more times than you’d think, so I’m not worried.
You did what?
edit: I misread cuck cage.
Yeah, sometimes it really hurt.
Care to share some tips? I feel I’m getting there, trying to navigate old ERP interfaces, new web interfaces, and AI interfaces, and a mix of boomers, millennials, Gen Z as user base.
I think two major things are understanding platform standards and that what users say they want is often not what they need or what will work best for them.
Innovation is fine, but IUE and usability are often better served by following common platform standards (for general apps on the OS, not necessarily trying to match existing and often shitty enterprise software).
Also, it’s important to look for root causes when people ask for a specific feature. Many users focus on specific UI elements when they’re having issues, and in a complex system, it’s easy to wind up with bloat by solving the wrong problem. This is often how enterprise software becomes so unwieldy, with options and elements seemingly vomited all over the UI. What users think they want and what they need can be very different things.
Sorry if this is too general or basic. It’s hard to design a system that works for beginners and experts, and A/B testing a mix of users early with lofi prototypes helps a lot. For existing software, just watching users interact with it is massively helpful.
Is this what you meant? Happy to be more specific if I missed the mark.
Did you ever get any power users who raged at the lack of command line switches or something like that?
Nothing that techy. I did include power users in tests, but their requests were usually for specific hotkeys or to have their favourite (and lesser used by most users) feature front and centre.
It can be difficult to balance a UI for inexperienced and power users, but watching them interact with prototypes and the actual software does help.