Symphony Analytics

Unified enterprise analytics workspace for investigation, collaboration, and reporting.

Symphony is an enterprise analytics workspace built on top of tools such as Power BI and Tableau. I led UX/UI strategy and implemented key Vue front-end experiences for investigation, collaboration, and reporting workflows.

The goal was to keep teams inside one connected workflow, using saved views, in-context collaboration, and storytelling to reduce screenshot handoffs and manual reporting loops.

Impact

60+

Reusable design-system components

100+

Prototype and workflow screens

-60%

Manual reporting loop time

5M+

Daily records handled

Snapshot

Company

Berkeley Research Group (BRG)

Work Type

Full-time Employee

Industry

Enterprise Analytics / B2B SaaS

Sectors

Finance / Government / Healthcare

Role

Lead UX/UI Designer / Front-End Developer / Product Designer

Scope

UX Strategy / Design System / Vue Front-End

Core Stack

Vue.js / Tailwind CSS / Bootstrap CSS / JavaScript

Tools

Figma / ECharts / Power BI / Tableau

Duration

2019-2025

The Outcome

Symphony connected embedded analytics, bookmarks, collaboration, and storytelling so teams could move from insight to output without losing context.

A unified layer for analytics, collaboration, and reporting on top of existing BI tools.

What shipped

  • Embedded analytics workspace across existing BI tools
  • Bookmarks to save and share live analysis states
  • In-context collaboration tied to analytics views
  • Storytelling layer for client-ready outputs

Embedded Analytics

Symphony sits on top of existing analytics tools, giving teams one workspace to access dashboards, save views, and keep investigation context visible across review.

Symphony analytics dashboard showing report context, high-level metrics, and enterprise workspace navigation
Symphony create-bookmark flow used to save a filtered investigation state inside the analytics workspace
Symphony bookmark panel used to reopen a saved analytics view and restore its investigation context
Symphony analytics table filtered through a saved bookmark to keep review states consistent across teams

Collaboration Layer

Collaboration stays in context: saved assets, shared states, and feedback remain attached to live analytics instead of moving into screenshots or email threads.

Symphony collaboration workspace showing analytics assets filtered by saved bookmarks for structured review
Symphony collaboration panel listing saved analytics assets and related review items
Symphony collaboration view with a saved bookmark applied to preserve the analysis state during review
Symphony in-context messaging flow used to send feedback on live analytics content

Story Module

The story workflow turns analysis into client-ready outputs, letting teams select assets, shape narrative, and prepare delivery without leaving the product.

Symphony story module showing template selection for a new narrative or report output
Symphony story builder with analytics assets applied into a structured narrative layout
Symphony story editor with layout and styling controls for report composition
Symphony story workflow used to select analytics assets for a client-facing output

Problem

Once an insight mattered, teams left analytics tools and moved into screenshots, decks, and email threads. That broke context, slowed review, and created rework across builders, leaders, and decision-makers.

The dashboard was not the problem; the handoff after it was.

Main Issues

  1. 01Insight context was lost during review
  2. 02Feedback lived across screenshots, decks, and email
  3. 03Client-ready outputs required too much manual work
  4. 04Traceability weakened across handoffs

Research & Insights

Across sectors, teams already had tools such as Power BI and Tableau. The missing layer was how builders, leaders, analysts, and decision-makers shared, reviewed, and delivered insights without leaving context.

Research showed the real gap was collaboration after insight discovery.

What shaped the product

  • Builders needed feedback on live analysis states
  • Leaders needed reuse, governance, and scalable delivery
  • Decision-makers needed narrative without losing context
  • Workflows mattered more than demographic personas

Design Process

The work started with the steps around an insight: access, save, discuss, refine, and deliver. From there I moved into wireframes, prototypes, and reusable UI patterns, validating critical flows before implementation.

I mapped the workflow around analytics before designing screens.

Workflow Mapping

This slot should show how the team mapped the path around an insight, from access and saved states to review, refinement, and final delivery.

Placeholder for future Symphony workflow mapping image

Wireframes & Prototypes

This slot should show early screens for bookmarks, collaboration states, and story setup that were used to validate the workflow before implementation.

Placeholder for future Symphony wireframe or prototype image

Component Patterns

This slot should show how repeated interactions were turned into reusable UI patterns across analytics, collaboration, and storytelling modules.

Placeholder for future Symphony component pattern image

Key Features

Instead of optimizing single screens in isolation, Symphony focused on keeping investigation state, collaboration, and reporting connected. That made the product more usable for teams and more scalable for delivery.

The strongest product choices were the ones that protected context across the whole workflow.

Core Decisions

  1. 01Build on top of existing analytics tools rather than replace them
  2. 02Preserve context through saved views and bookmarks
  3. 03Keep collaboration attached to live analytics states
  4. 04Treat reporting as part of the product workflow, not an external handoff