We didn't just want to create another social media platform. Our goal was to build something special, where young people aged 12 to 19 could join in-person activities and earn rewards to support their studies and future careers. We aimed to make it engaging, rewarding, and tailored to their needs.
Research & Benchmark
I researched various competitors and conducted a comprehensive analysis that delves into their design, pricing, user ratings, strengths, weaknesses, and potential areas for improvement. Based on this analysis, I've developed strategic suggestions to differentiate our product in the market and address unmet needs among our target audience.
Information Architecture
Since our product is entirely new and covers all aspects, I've developed a Information Architecture. This helps us understand how users will explore features and engage with content. It's like drawing a map for them, ensuring they can easily find what they need and make the most of our product.
Design System:
Designing the DS for Zaahah posed a significant challenge, not only because it started from scratch but also because this Design System would be utilized across other products of the company, such as the aHa Wallet and the website. Therefore, it was crucial to define the visual identity and create consistent components.
Leading Multiprojects
As the principal designer, I led a small team of junior designers who were concurrently engaged in other projects. Therefore, I was responsible for reviewing and approving their ideas. To facilitate this process, we established daily meetings and maintained constant communication.
CMS & Administrator Mode
This SaaS product required an administrator mode and a CMS capable of visually presenting data about users who were registering and utilizing our platform. Additionally, I spearheaded this project while simultaneously developing new features.
Native Android & IOs
This project was designed and developed for web responsiveness and native mobile applications, ensuring they can be downloaded from both app stores or accessed online.
For this project, we decided to create only low-fidelity wireframes for mobile since we adopted a mobile-first approach. This allowed us to explore numerous ideas and conduct testing. We also discarded options that could potentially be harmful to the user, such as the "swiping right" feature, and opted to retain the infinite scroll. We chose this approach because it is simpler, easier to understand, and provides a full-screen view, enhancing the quality of posts or pictures.
Mobile
Starting with the mobile-first approach was intriguing because we aimed for a product that stood out from what was already in the market. This approach enabled us to experiment with iconography, various types of cards, and delve into gradients or colors that would capture the attention of teenagers
Web
The website presented an even greater challenge as we experimented with various types of navigation. We divided it into three panels: the right panel contained the menu and some options, the middle panel displayed the content and feeds, and the left panel housed the virtual wallet and chat. This approach was highly creative and explorative, breaking away from the common conventions.
Outcomes & Metrics
After I delivered the designs, this project took an additional year to be coded and delivered to the market. During this phase, I was no longer working for the company. However, I maintained a good relationship with the owner. He expressed gratitude on several occasions and informed me that everything was progressing well. He mentioned that the product was being used in many schools across the United States. I am truly happy for him and grateful for the opportunity to have worked together.
What we did well
Communication throughout the project was excellent, and as a result, we were able to deliver a successful product. I want to commend the quality of the team I worked with. Despite not being in the same country, we managed communication effectively. They were receptive to feedback and understanding of the project flows. Additionally, my team demonstrated a willingness to refine and evolve initial ideas, which greatly contributed to our success.
What I would improve
No specific methodology was established for this project. Therefore, I led the design efforts and directly collaborated with the developers. Despite the project's completion in just four months, it entailed a significant amount of work. One area for improvement would be time management and planning. I would recommend incorporating methodologies such as Scrum and involving a product or business analyst. This would facilitate working with more realistic timelines and enhance overall project efficiency.
