Lagoon - 'DaaS' Desktop Dashboard
A 2-month Hack-a-thon Design. Uncovered the blind spots in our flow and enrich it with new recommendations and drove the development and communication of clear design guidelines, patterns, libraries, and assets.
Overview
Lagoon is a no-code data intelligence platform for professional investors (DaaS). Lagoon uses predictive analytics and explainable AI to deliver actionable insights, faster and more affordable than ever before. Uncover the blind spots in your research and enrich it with new sources of data.
Built something from nothing in few weeks
As the Startup Lagoon was a 1 months design Hack-a-thon since I integrate the team later on, and our investors expected results in a few days/weeks. We made a tight schedule including, a journey map, problem definition, brainstorm, prototype, business model, and pitch preparation.
Due to the time limitation, we did not get the chance to conduct the usability tests and iterate, but we would definitely include those processes in future steps.
“Weaponizing an ocean of data to deliver unprecedented returns”
Lagoon
Understanding the product and the problem
When I first integrated the team I knew that I had to do quick learning around investment in stocks and how it works since I had no previous experience in the field.
I also conducted brainstorming workshops with the team to uncover the pains felt by individuals.
The process included multiple key questions that I asked the team that would help me build my user stories, my KPIs (Key Performance indicator), and later on the flow.
-
How might we provide an experience that is engaging and valuable to our users?
-
What differentiates us from the other popular and outstanding stocks platforms such as Wall Street, Google, or Yahoo?
-
What are the needs of our users?
-
What problems would they like solved?
-
What features are most important to them and why?
-
What initial questions do they have about your product?
-
What information needs to be provided in order for them to effortlessly interact with your product?
Once I understood the full scope and deliverables for the project, I was able to develop estimates for how long it will take me/our team to deliver it fully.
Design Guidelines & Components
When creating a design system, it’s important to stay organized and to be in constant collaboration with the development team and as needed, continuously be updating the component libraries/design system to ensure changes and new components aligned with the existing design language. For example, using tools such as Zeplin, improved collaboration, and communication between the Designers and the Developers on our team.
Current Design Analysis
The biggest concern that I identified when joining the team was the information architecture of the platform. One prominent frustration was the confusion caused by poor navigation and features scattered all over the app. I visualized the current information architecture to see what was going on:
Main Pain Points:
-
Finding Relevant data.
-
Analyzing the data.
-
Creating a Competitive Edge.
-
Understanding the data.
User KPIs:
-
Found data and enrichment (relevant data).
-
Create the spider graph to bring differentiation between the project on the dashboard menu (User case- having twice the same company).
-
Create research based on multiple data sources.
-
Create a project (easier way to create a project).
-
'Easy to use' platform (Compare between the data and companies easily).
Prototyping
Now that we’ve established our user flow, we can look into the next steps.
Working as the only designer in the team, I designed and prototyped starting from paper to high fid. digital prototype.
When prototyping, I love creating real interactive prototypes to help the team and/or the user understand how it will actually look upon completion (High Fidelity Prototype). Creating prototypes also helps the developers through the dev process.
To ensure that I can create the best user experience for users, I make sure to read and stay up-to-date on the latest best practices and trends.
