The Challenge: The "Dropdown Abyss"
The legacy reporting system was a victim of its own success. Over years of layered development, it had devolved into a single, unstructured dropdown containing hundreds of reports with zero hierarchy.
The Operational Bottlenecks:
• Discovery Friction: Fortune 500 analysts struggled to find specific reports, often resorting to manual data extracts because the "correct" report was buried.
• High Support Tax: Client services teams were overwhelmed with requests to "find" or "explain" data, as there was no central knowledge base for calculation logic.
• Low Automation Adoption: Advanced features like scheduling and subscriptions were underutilized because the interface made them too difficult to configure.
• Information Silos: Without a searchable or categorized system, new users faced a steep learning curve, leading to inconsistent data interpretation across teams.
The Strategic Mandate: Re-Architecting for Discovery
As the Principal Product Designer, my goal was to move the platform from a "report extraction" tool to a proactive automation engine. This required a dual focus on Information Architecture (IA) to solve the discovery problem and Workflow Engineering to drive automation.
Showing empty state for unselected report
The Solution: A Tiered Reporting Ecosystem
1. Scalable Information Architecture
I replaced the single-dropdown model with a searchable, categorized library.
• Search-as-you-type Filtering: Implemented a high-performance search engine that allows users to find reports by name, category, or keyword in real-time.
• Multi-Tiered Categorization: Balanced stakeholder pressure for client-specific customization with a standardized, scalable IA that works across the entire multi-tenant platform.
2. Customization & Power-User Presets
To reduce manual rework, I designed a robust parameter engine.
• Saved Presets: Enabled users to save their specific filter configurations (date ranges, vendor IDs, compliance tiers) as "Saved Presets," reducing the time-to-report from minutes to seconds.
• Contextual Knowledge Base: Embedded definitions and calculation logic directly into the UI, ensuring that users understand the "Why" behind the data without leaving the workflow.
3. Closing the Loop with Automation
I moved reporting from a "manual task" to a "background service".
• Subscriptions & Scheduling: Designed an intuitive automation suite where users can schedule reports to be delivered via email or SFTP on a recurring basis.
• Team-Level Governance: Added "Team Subscriptions," allowing leads to automate reporting for their entire department, ensuring everyone is working from the same daily dataset.
The Technical Foundation: Implementation Fidelity
To ensure the new IA was buildable and performant, I worked closely with Engineering and QA.
• Empty State Strategy: Designed "zero-state" UI components that guide users through the discovery process when no report is selected.
• Scalable Component Logic: Codified the new reporting patterns—search inputs, parameter cards, and scheduling modals—into the production-aligned design system.
Strategic Outcomes & Business Value
The modernized reporting engine successfully transformed a legacy bottleneck into a high-adoption feature.
The Wins
• Accelerated Decision-Making: Users reported significantly faster discovery times and a reduction in "data anxiety".
• Reduced Support Volume: Centralizing definitions and logic led to a measurable decrease in "how-to" tickets for the client services team.
• Increased Product Value: Higher adoption of automated scheduling and team subscriptions directly increased the "stickiness" of the platform for executive stakeholders.
• Future-Proofed IA: Established a foundational structure that allows the organization to add hundreds of new reports without re-introducing discovery debt.