Reporting & Analytics System
- Role
- Sr. Product Designer
- Core activities
- AnalyticsDashboardsWidget Builder
- Period
- 2025
- Product Tags
- ScomplerDashboardsAnalytics
Context
Scompler's reporting experience was fragmented and low-trust. Users needed to understand content performance, compare segments and communicate results, but the product offered rigid widgets and disconnected analytics surfaces.
Product Landscape
Scompler / 2025
Reporting & Analytics System connected product strategy, user workflows and implementation constraints. The work needed to support the immediate feature scope while leaving the product easier to extend.
Scalable analytics system with report boards, filters and a Widget Builder.
- Analytics scope
- Dashboards scope
- Widget Builder scope
- SaaS scope
Challenges
The work started with a set of product, workflow and system constraints that had to be resolved without slowing delivery.
- The legacy reporting model had low adoption and forced users into Excel or external BI tools.
- Data relationships across Articles, Stories and Social Signals were hard to expose clearly.
- Different roles needed different reporting questions without duplicating the entire system.
Approach
Design process
I translated the product problem into reusable UX structures, validated the direction with stakeholders and prepared implementation-ready design specifications.
- Reframed reporting around user questions, datasets, dimensions, metrics, filters and chart types.
- Defined a shared widget grammar for reports, dashboards, comparison logic and summary states.
- Designed role-based premade widgets for General, Social and Community reporting.
- Added a Custom Widget Builder as the advanced flexibility layer.
Outcome
The result was a clearer product experience, stronger delivery alignment and a more scalable foundation for future work.
- Created a unified widget system across reports and dashboards.
- Improved trust through clearer filtering, preview and comparison behavior.
- Reduced dependency on external reporting tools by bringing analysis and communication into the product.
- Established a scalable foundation for future analytics work.
Reflection
General experience
Good system work is less about perfect component inventory and more about creating repeatable agreement between product, design, and engineering.
The most useful artifacts were the ones teams could apply immediately in delivery: decision rules, naming conventions, reusable states, and practical examples.
Featured Projects
My product design cases from the last few years.
