“Algorithmic trading made easy for everyone”
In the world of trading, Algorithms are computer programs that allow traders to execute trading activities automatically; i.e without the need for human interference. This attribute makes algorithms much faster in taking decisions and executing trades than the normal human ever could. [Pls note “algo” is just a shortened form of algorithms and I will be using algo throughout this casestudy]
Since the advent of trading algorithms in the 1980s, they have been a welcome development, but over the years traders began to point out some underlying issues restricting wide adoption. Some of these roadblocks include:
Algopear is a startup dedicated to eliminating these and all the other unlisted barriers of entry into algorithmic trading. Algopear’s product is a platform that connects investors and traders to a library of ready-to-use algorithms that they could use to automate their trading activities.
When I joined the team at Algopear for this project, the company wasn’t called Algopear then. It was called Pushstash and the change of name to Algopear was a direct result of this massive overhaul I and the team executed and shipped over the course of approximately 6 months.
–
–
Besides Algopear there were other companies who were headed in similar directions and if Algopear was to dominate the industry and also stand the test of time as planned, then a solid design foundation was necessary. The challenge was to come up with efficient scale-able solutions to the identified problems and then translate these solutions into exciting easy-to-use interfaces and experiences. I also needed to create a design system that was scale-able and would be capable of accommodating new features in the future.
–
Solo product designer
–
Me [Designer], Bennie [Head of marketing], Lakeisha [Lead dev who’s also the co-founder], Ronnie [Founder], and about eight [8] other developers.
–
For this project, I employed my four-step design process.
–
Tools used:
Figma, Miro, Photoshop, Adobe illustrator, Google docs,Overflow.io, Xmind, Raindrop.io, and quite a few others.
–
“At the outset of the project, we didn’t really have a clear direction for the Algopear experience.”
In the old app, we simply sent users stock alerts on their preferred stocks and allowed them to monitor the performance of their favorite stocks. But in this new version, we wanted to do way more.
–
Instead of trying to figure out from the start what new features to add, I ensured we first answered questions like,
–
Hypothesis statements — I started by working to identify all the things the team held as truths, especially the ones that hadn’t been confirmed through research. This was so I could work towards proving or disproving these opinions during research. Some of the hypothesis we held were:
–
Demographics — In collaboration with the marketing lead, I identified the three major demographic categories our existing and potential user base would fall under. I named them D1, D2, and D3.
D1: Investment savvy people, high-risk appetite, very financially capable and experienced folks. High risk – High rewards kind of traders.
D2: Average experience with high financial capability. Averagely experienced with average financial capability. Mid risk – Mid rewards kind of trader. Average risk appetite too.
D3: Low-risk appetite, little to no experience. Very unwilling to lose money. Not as financially capable as the other categories.
–
Business goals — From the meetings and discussions we had, I was also able to deduce some business goals. This part of the process is essential because keeping these in mind help inform certain decisions to be taken later on in the design process
Short-term:-
Mid-term:-
Long-term:-
KPIs — The major KPI was an increase in user base on both the algo maker and trader side.
–
User research recruitment — For interviews, I was looking for people who fit our three different demographics. I sent out initial questions via a questionnaire and then I reached out to users with interesting responses to gain further insight. Further discussions allowed me to uncover new insights and also invalidate some of the hypotheses we held.
User research findings — After hearing from and discussing with potential users, Some common themes began to emerge. While some of our hypotheses were confirmed, I also discovered many things we were missing.
–
My research also birthed some “How might we” statements like
–
Testing results
Deliverables
Results & Impact