• Andrew C, over 1 year ago

    Suganth hit the nail on the head: your answer is in proving your usability concerns w research.

    Get 3-5 existing users to perform the key tasks of your app (ideally survey or pull data ahead of time so you know what tasks to ask about). Record them with Zoom or Silver back. Time how long it takes them to complete, how many interaction errors they have, and how many fail to complete. You can ask them to try a prototype of the new features your team is exploring as well. This may help illuminate how a new feature may impact existing users. Keep that separate from the initial task though.

    You can make a flowchart based on each step you see them take (hopefully you discover steps even before users start your service).

    Next get 3-5 prospects who reasonably simulate your users but have no experience with your UI. Run the same test as above.

    If new users are able to successfully navigate your app then you don't need to fix it. But the new feature probably won't be as valuable if your core tasks aren't great. Companies get more bang for their buck fixing existing issues in well established flows than adding new flows altogether.

    Show the results with a few videos SHOWING how painful using the app is. The video artifacts are key.

    Make the changes and see how much better your new designs perform. Set an objective. Aim for 100% task completion and an 80% error-free. You can even try and get the time to complete tasks down if you're really ahead of the game (be careful though, not all tasks are improved by going quicker).

    Hope this helps. I started at a startup as designer 2 and had a similar challenge. You shouldn't have to measure every decision you make but if you need to align your product team showing user pain is much better than nagging to deaf ears.

    Good luck!

    1 point