PROJECT OVERVIEW

CLIENT

Canomiks is the first technology company using Genomics, Bioinformatics, and an AI-based technology platform to test and certify the biological efficacy and safety of ingredients and formulations. Canomiks has built exclusive IP and groundbreaking technology that is transforming the functional food and dietary supplement industry. We worked with Leena Pradhan-Nabzdyk, founder of Canomiks, and Ashley Moya, Marketing & Operations Manager.

Our goal was to create a multi-user dashboard prototype for Canomiks. This dashboard will demonstrate both the front-end and back-end user experience.

MY ROLE

This was a remote collaborative project where I could serve in many roles. I contacted the client and their own clients to set up research interviews. I facilitated interview sessions with users and then synthesized the data. I ideated features and created some low/mid-fidelity and high-fidelity web screens. I also help move the current state journey map forward. I completed this project by working and creating the presentation keynote to wrap up all our key findings.

METHODS

  • Stakeholder Interview

  • Comparative Analysis

  • Moderated Remote Interviews

  • Kano Survey

  • Information Architect

  • Journey Mapping

  • Wireframing

  • Prototyping

TOOLS

Figma, Zoom, Keynote, Google Docs, Pencil and paper sketching

DELIVERABLES

Comparative Analysis,

Screen Shot 2021-02-15 at 3.35.02 PM.png

Stakeholder Interview.

Goals: To gain a better understanding of the stakeholder needs, pain points, and opportunities for this multi-use Dashboard.

Insights: I learned the client was very passionate with a strong concept and was not very far along in the process of building the platform, they had a few wireframes mocked up but by no means was this what our dashboard had to look like. This gave us the exciting opportunity to build this dashboard completely from the ground up.

 Key Takeaways

  • Clean and simple should be the solution. Easy to see and easy to use.

  • Forgiveness on the customer not understanding something and having alerts set in to help them.

  • Option to customize how the dashboard can look like for each user.

Screen+Shot+2021-03-11+at+10.41.21+AM.jpg

Comparative Analysis.

Goals: Comparator dashboards were examined to determine what conventions are in place for a science data-driven platform to succeed.

Insights: We found great and intuitive ways to showcase science-heavy driven documents into a more everyday user-friendly world.

Screen Shot 2021-03-11 at 11.25.28 AM.png

Feature Ideation with Dot voting and Kano Survey.

Goals: After conducting user interviews we all had an idea of what key feature screen a user would want or need on a dashboard. To help us stay focused on the key users at hand we took this ideations and created a Kano Survey to help us back up our research with user results.

Canomiks - IA.jpeg

Architecture Diagram.

Goals: After choosing our key features, we set to create an architecture diagram for the dashboard so we could decide which user flows were the top priority for high fidelity prototyping.

Screen+Shot+2021-03-11+at+2.38.07+PM.jpg

Low-Fi to Mid-fi sketching.

Insights: We started with low-fi to mid sketching to ideate our ideas from our research into the Dashboard prototype of Canomiks.

High-fi wireframes done by me

 
 

Client presentation

(Click for keynote)

As a team, we remotely presented our research, findings, design process, and final product in the form of interactive prototypes to our client. Figuring out how to present a deck and a prototype with five people over Zoom took some strategy and practice, so I was very fortunate to be on a team with such incredibly talented and capable UX designers.

Conclusion

A big challenge for this project was navigating the new science-heavy field Canomiks handles and clearly communicating that on a dashboard. The team took extra care in hearing what the users were communicating to us, while also keeping in mind what the Stakeholders gave us to find a cohesive harmony of a dashboard.

During work hours my team would be on Zoom together so we could have conversations about the project, and we used Slack to communicate in the off-hours. This was a great way to collaborate because we were able to accommodate each team member’s preferred working habits. We also took the time to talk through communication problems and push each other onto the finish line to give this client an amazing, thoughtful end product.

Previous
Previous

goodreads mobile

Next
Next

stakeholder design