Bernardo Braga Leader and full-stack developer
Jefferson Domingos Product Designer
Ruan Ramos Full-stack developer
Intelie Live is a platform that offers real-time data analytics. It also offers management and operational intelligence for companies in different sectors.
As part of the company's future strategy, we had the challenge to encourage users to create, and consume more annotations over data.
Intelie Live is a platform fed by lots of data so specialists can interpret and make good use of it. Besides showing data and information, Live keeps evolving into an Augmented Intelligence solution. It's starting to give recommendations, predictions, and automatization of technical analysis and processes. One of the main ingredients for all that power is annotated information, created by users. Those annotations over data are shared between users that work together and need each other's insights, but it's also a key component for the AI model's training and development.
As part of the recently created Augmented Intelligence team, I've partnered up with the team leader in an effort to discover the Design role on AI solutions and also to understand how the market has tackled similar challenges. That's when we've identified that our starting point on that journey would be to empower and encourage annotations throughout the platform.
I've started an internal investigation of what was already been made and collected in the form of annotations and where could we act to bring the outcomes we needed, which in that case was more and better annotations. We've started by making questions like: "What already exists? What is missing? What can be improved?"
We've started by understanding the user flow when creating and consuming an annotation within the platform and gathered some valuable information and started finding points of improvement.
Live is an almost 12 years old platform that is in constant iteration but of course, it has lot's of legacy codes and features. This adds up to the challenge since that specific feature is used on a daily basis by our users and besides having flaws, they're used to the current user flow. We've decided to go for an improvement of the current way to find and consume annotations so we have to take extra attention to the legacy of this feature.
Now that we know the goal, which is to increase annotations usage, and we're fueled with information about constraints, stakeholders views and the current state of the feature, it's time to ideate. Since the complexity of the feature is high and I've acknowledged that there were lots of different views on how we could approach the problem solution, I've decided to start on really low fidelity wireframes. The main purpose was to avoid discussions about the visual aspects during presentations, and keep the focus on information architecture at first.
We've discussed and collaborated a lot during the design process. I was the one with the hands-on at this phase but my developer colleagues were always following my proposals and giving insightful feedback. Internal users were also included in the loop by participating in presentation meetings and user testing.
We've come out with a sollution that adds a new and isolated area inside the platform to list annotations. The list experience was quite close to what the users were used to but the fact that it now has it's own place minimizes confusion and the main improvement was on the search and filter functionalities that were added.
I can say that it went well, but if you're really interested in knowing in-depth details about this or any other project that I've worked on, let's arrange a meeting! I'll be happy to share with you the details of my work and maybe in a near future, we could use my approach and experience to improve your product and strengthen your team.