Case
Intelie Live

Dashboards are one of the most important tools in the Live platform because of their extensive application and personalization.  At the moment, advanced users with an administrator-level of permission do the task of building dashboards and configuring widgets.  Sometimes those customized widgets and charts can cause performance issues. The product team became aware of this issue through the users' feedback channels and reached me to help with the solution.

To help the team build an adequate solution, I had to learn more about the users of that specific task of building and managing dashboards. With the help of my team, I went after more information about who they were inside some of our main clients and also who they were inside our own company. After that, I reached out to some of those who were available so I could get more insights into how they approached the problem at that moment.

According to users, performance issues were caused by a combination of technical difficulties that the system could go through while reading, writing, and rendering data from the storage.  A solution relies on identifying and labeling those issues in a way that the user understands. We knew by then that our job would be to empower users to identify the causes of the problems and give them tools to act on them or to share key information with the person who could.

As we gettered from the user's journey, general users identify performance issues when assessing a specific dashboard, so I started by designing an area of that specific dashboard option where the performance information would be shown to the user. The idea is to keep an agile mindset, so since we've already collected some info and insights, we were fine-tuning within the team and some internal users the minimum viable solution so we could test it quickly but not far from success.

That's the moment where it all ends, right? No, it's starting. After delivering the prototypes, I kept working with the front and back end developers, helping out with any doubts about the user flow, interactions, and visual interface.

The feature is working in the test environment, and now we can pull its buttons. I am one of those responsible for helping with the quality assurance document. There were minor issues—mostly visual corrections, and the feature is ready for the next release.

Since its rollout, the feature has received lots of good feedback from users, and we're already looking into expanding its sharing options.