Report Theme Panel Redesign
A global styling control panel inside a cloud-based data visualization tool - Web Report Editor - for creating interactive repot dashboards
Outcome
100% User Satisfaction | 80% Faster Report Formatting | Reduced Onboarding Time | Higher Adoption Rate
"I can now find controls and apply them more confidently."
My role: Led the project from initial problem definition and user research, through information architecture, visual design, prototyping, and final implementation hand-off to engineering
Team: Data analysts, Software Engineers, CEO
Employer: Megaputer Intelligence
Year & Duration: 2025, 3 weeks
Introduction
PolyAnalyst’s Web Report Editor (WRE) is a browser-based enterprise BI tool used by data analysts to build interactive reports, guided dashboards, and data visualizations at scale.
The Report Theme Panel inside WRE is a critical control surface for global formatting, enabling users to set the visual style of reports across all pages and components.
Problem Scope
The Report Theme Panel had become:
-
unintuitive
-
overloaded with ungrouped and unclear controls
-
misaligned with analyst workflows
This led to slow report creation, inconsistent themes across sheets, and high onboarding friction for new analysts.
Business Goals
Enhance analyst productivity, eliminate formatting inconsistencies, and boost adoption of report authoring features without changing the underlying architecture
Understanding Data Analysts (Primary Users) & Their Workflows
I synthesized data from 8 internal user interviews and conducted a quantitative card sort with 5 data analysts to identify semantic gaps. Data analysts use the Report Editor to:
design dashboards for internal stakeholders
apply themes consistently across multiple sheets
fine-tune visual configurations
maintain readability and brand alignment
Key Workflow Insights
Analysts think in terms of global→sheet→visual hierarchy, but the interface was built around back-end components, causing friction and errors.
User's Pain Points
#1 Cognitive Overload
Controls were grouped by engineering logic, not tasks. Users struggled to:
-
find controls due to having too many options
-
achieve efficiency because of the lengthy customization process
-
distinguish global vs local formatting
#2 Uncategorized Report Controls
-
Lack of meaningful categorization for report controls leads to confusion
-
Users struggle to find specific controls, harming productivity
#3 Visual Misalignment and Crowded Interface
The interface suffers from visual misalignment, resulting in a cluttered appearance.
#4 The Central Conflict & Trade-off
Pit the business need (feature scalability/customization for enterprise customers) directly against the user need (simplicity/cognitive load reduction)
Project Constraints
Design around system architecture
Engineering required:
- Minimal back-end refactoring
- No new APIs
- No new theme propagates logic
.png)
I couldn't touch how the system worked (no interaction design), so I focused on how it communicated the information and its functionality.
I could only surface, clarify, and reinforce the current architecture.
What are My Design Goals?
Design a modular, scalable, token-based panel architecture that:
works within legacy constraints, reduces cognitive load, and mirrors the analyst's mental model & workflow.
Research Synthesis & Defining Design Strategies
From research and architecture limitations, I defined principles to guide the redesign:
Align with Analyst's Mental Models
Group controls by workflow stages, not code structure.
Make Theme Hierarchy Predictable
Clarify global vs sheet-level formatting to prevent accidental overrides.
Reduce Cognitive Load
Prioritize high-frequency actions; hide rarely used ones under Advanced Options.
Provide Immediate Feedback
Ensure that every change is reflected instantly on the canvas.
Support Scalability
Use a token-based structure aligned with the design system for future extensibility.
Information Architecture Redesign
Card sorting surfaced unclear feature semantics, misaligned taxonomy, and duplicate controls, resulting in elevated cognitive overhead and inefficient task flows. I re-grouped all controls into more intuitive categories by workflow stages and software propagation logic instead of code structure.
Diagnosing Prior Redesign Failure through Usability Testing and KPI Analysis
Previous designers had developed a solution before; however the beta redesign showed poor performance across key metrics (e.g., satisfaction, time on task, adoption), driven by several critical UX misalignments:
Misaligned grouping broke mental models. Misplacement of low-level styling (e.g., Border) under unrelated sections (e.g., Theme Colors) forces users to search unnecessarily, as they expect these properties to be grouped independently.
Visual Clutter: The redesign is "too busy," leading to poor scannability and focus.
Interaction Cost: Collapsible sections create frustrating, extra steps for adjustments.
Before & After: Transforming Complexity into Clarity
Before
After
-
Added a global "Restore Default" control at the top, enabling instant rollback to system or saved theme settings, reducing recovery time and reinforcing expected “undo” patterns.
-
Surface "template configuration" first, as it sets the styling baseline for dependent settings. Placing it early aligns with system logic and avoids rework from late overrides.
-
Moved Color Palette into “Component Style” as it relates to the component's color (e.g., charts). Aligning terminology with user expectations reduced search friction and improved control discoverability.
-
Renamed “Report Theme” to “Report Style” and expanded its scope to include related formatting options, improving information scent and hierarchy clarity.
-
Replaced a two-step dropdown (On/Off) with a native toggle switch, reducing interaction and aligning with platform UI.
-
Renamed "Report Header" to “Report Title” and used progressive disclosure, showing options only when activated to reduce interface noise and guide user intent.
-
Repositioned this control under “Report Style”, removing an isolated category that increased cognitive overload.
-
Realigned control placement by moving component settings from "Report Style" to "Component Style", improving the structure and reducing errors.
-
Enhanced visual hierarchy by introducing clearer groupings, not just padding, for better quick scanning.
-
Consolidated “Header Font" from multiple sections into Sheet Style to simplify decision flow.
-
Used standard icons for familiar settings to decrease cognitive load and improve recognition
1. Users saw sheet-related settings as global controls, so I merged them under “Report Style” to match their mental model and avoid hierarchy fragmentation. Creating a separate “Sheet Style” would have been redundant and increased cognitive load.
The only outlier was “Header Font,” applied at the component level. I moved it under component-specific settings to match actual behavior and prevent misconfiguration.
2. To balance scalability with precision, I introduced sheet-level overrides, enabling users to localize changes without affecting the entire report, reducing errors and improving styling accuracy.
To reduce cognitive load and declutter the primary editing panel, I migrated the long list of low-usage settings into an “Advanced settings” section. These controls are now grouped into meaningful clusters, balancing discoverability with interface simplicity.
Interaction Design & Component Systems
I created reusable components:
-
collapsible sections
-
token-based spacing
-
consistent input components
-
multi-sheet theme preview
-
global→sheet inheritance logic indicators
-
local override “warning” states
This modernized the UI without touching the underlying logic, reducing engineering effort.
Conflict Resolution & Override Logic
Override alerts and confirmation modals to increase user awareness when a sheet-level setting overrides the global theme.
This prevents unintentional inconsistencies and gives analysts control over the propagation of themes.
Impacts
The usability testing results demonstrated significant improvements in efficiency and satisfaction in the post-lunch evaluation.
+ 80% Faster Report Formatting
Analysts completed formatting tasks significantly faster, saving hours per week
2X Improvements in User Satisfaction
Analysts rated the panel as clearer, more predictable, and more enjoyable to use
Reduced Onboarding Time
New users reported understanding global vs sheet formatting immediately, instead of after trial and error
Higher Feature Adoption
More analysts used global themes and applied consistent branding across reports
Reflection
-
Users' Mental Models
-
Established Conventions
-
Clear Labels
These elements directly influence usability and decision-making and are crucial factors to a product’s success. One of the core challenges was balancing simplicity with functionality, ensuring the interface remained clear and approachable while still offering access to advanced features for experienced users
