ArBitra

Objective

1. Produce the Immediate view of market-reflective price forecast for deals decision-making for business commodities focusing on the price only.

2. Real-time insights on market movements to provide intel to decision-makers.

Problem Statement

1. Slower Analysis: Due to a lack of real-time updates and delayed data can hinder decision-making and affect trading opportunities.

2. Manual Processes: The chart is not comprehensive enough to do all the functionalities. Takes a lot of time to create basic charts and manual tasks such as exporting charts and importing data, can be time-consuming and prone to errors.

3. User's Difficulty in Understanding the Data: The charts are difficult to understand and require time to digest. Required additional filter to understand.

Impact Solving the Problem

1. Improve the speed and accuracy of data analysis.

2. Reduce the manual effort involved in data handling.

3. Enable better decision-making through real-time updates and clear visualizations.

User Persona

Based on our research, we recognized that there were 2 key user types that our product tried to solve problems. We decided to focus on Persona 1 since their need was greatest.

Persona 1: Analyst

Persona 2: Trader

Defining the MVP

I conducted workshops and sketching sessions with the team to map out the user flow and come up with a storyboard to capture the MVP. We identified the following key features:

1. To improve the overall user experience and customer satisfaction by enhancing data visualization and simplifying navigation.

2. To provide real-time data availability as it is updated from the sources for immediate decision-making.

3. To create a centralized, one-stop dashboard for all trading-related activities, allowing for effective market analysis and trade execution.

Working with Developers

I worked closely with a team of 5 engineers to develop the designs for ArBitra. I scoped out tickets for the front-end engineers with user stories and product requirements. I also encouraged the team to look into using a third-party component library to quicken the implementation process and spend less time worrying about the component interactions.



As part of the future vision, I created an Information Architecture of the platform to help engineers understand how the overall site architecture worked.

Results and Takeaways

Working on this project was an extremely steep learning curve. It was an eye-opening experience that taught me a lot about being lean and knowing when and where to focus your energy and efforts.

Some key takeaways from this project are:

1. Focus on building an MVP: There is only so much time and effort that you can invest so it's important to focus on the features that can deliver the highest value for your users.

2. Don't worry too much about the details: Earlier in my journey, I made the mistake of worrying about the look of the UI. Taking a step back and reassessing the user flows helped me to reprioritize the UX.

3. Focus on the problem: At the end of the day, it is your user's pains that you will be solving for so keeping that front of mind is important as it's easy to lose sight of this when you're bogged down in the day-to-day.