Usability feedback loop of web-based software
We run plenty of usability studies here at Ronin. We run them so commonly, that we think of them as taste tests - it’s only any good if it fits the palettes of the everyday user. A certain magic happens when you combine the rich feedback mechanism that is usability studies with the instant gratification medium of the web applications.
Everytime we conduct a study, we walk away with plenty of improvement ideas. Then, we sort them in priority (including bonus points for biggest-bang-for-buck features) and we add them into the product, usually within one or two days. Simple as that. While that may seem mundane, it’s really only possible with the appliction distribution model of web-based applications. Instead of building and compiling the next version of software as an incremental release that our users have to download, we can ship it to them without them even knowing.
Case in point, after the last round of usability studies, we’ve made the following improvements, all of which were released Sunday evening, waiting for use on Monday morning:
- The ‘amount’ field during adding of payments is automatically filled out with the remaining balance of the invoice. This is so often the case, and it’s a big win for efficiency.
- Removed requirement that a ‘note’ be filled out during payment creation.
- Added two links to edit “from address” (and other additional informational fields, like tax ID) and “to address” right in the invoice interface. The most common case of client creation is during the invoice creation flow and additional address information is usually a necessary addition afterwards.
- Change the invoice summary section to read “Total Due” instead of “Remaining Balance” when there haven’t been any payments, partial or whole. Removed unnecessary tax information from the invoice summary when the invoice is taxless.
- Improved the invoice comments UI by moving up next to payments as a column. We noticed a lot of users mentally filtered out the comments section because it was so low and hidden on the page.
This is just one set of improvements we’ve made, but changes like this happen almost on a daily basis. Sometimes they’re big, sometimes they’re small, but they’re hopefully always a step in the right direction.
