Snibble
Dashboards
Problem & Overview
Snibble had a content process issue. It relied only on code, which took up a lot of developers' time and affected the platform's quality. Content partners and advertisers wanted portals to manage their content and check stats, while the team needed tools and metrics to help manage the app as it grew.
As part of my work in Snibble I joined the other designer and developers to create tools for internal team to manage the platform and analytics for advertisers and content partners.
Role
Product Designer
Platform
Web
Year
2022 - 2023
Industry
Entertainment
Target Users
This dashboard has 3 versions for 3 different groups: content managers & stakeholders and advertisers.
To structure all the data, I spent several weeks interviewing stakeholders, developers and other designers, gathering documentation about the processes and what can be changed and improved. Provided info helped define what each user category expected from the Dashboards.
Content managers & stakeholders
100% functionality, the ability to change / add content and view statistics
Length
Content partners
Limited version - content statistics and some management
Competitor
Research
Solution & IA
After gathering research insights, I developed the dashboard's architecture, focusing on a flow curated to different user types. Instead of designing multiple portals we decided to create one Dashboard that partially changes depending on the user type. After several iterations, we reached a solution that the developers supported.
We also took this opportunity to standardize the vocabulary, addressing inconsistencies in naming conventions which differed between product team and stakeholders.
Wireframes
With access to stakeholders throughout this project, I prioritized creating high-fidelity wireframes to quickly iterate and gain approval on ideas. I developed wireframes for key layouts, so the developers can start working on working on both the UI and backend.
Final Design: Admin Panel
Admin panel lets internal team manage content and its categorization on a platform and reduces the load on back-end developers who prior had to do content management platform manually through code.
Analytics
In order to better understand user and content behaviour on the platform we designed internal analytics with focus on tracking social engagement with platform features and content.
Monetization
Being primarily ad driven platform, monetization tracking was also included as part of the project. Although there are good third party tools that lets you track revenue we decided to design our own that can be used by a company and its partners.
End Product
QA
In the final phase of this project, I conducted thorough QA sessions on a weekly basis. The goal of my QA sessions was to iron out critical bugs and make sure the web app works in different desktop browsers and tablet devices. Given dashboards were working with a lot of data considerable portion of QA I spent considerable amount of time on UI testing.
Outcomes
Content managers
Accelerated content management speed by 80%. The number was extracted by comparing the time it takes for developers to link new content to the dashboard and for content managers to curate and publish it on the app.
Developers
Developers can allocate more time towards platform improvements instead of having to manually maintain and manage the content.
Stakeholders & users
With new data coming in, we can make better propositions for design and development.
Next Project
Faind
