Self-Serve Reporting That Replaced an Analyst-Dependent Workflow

Self-Service Client Reporting Dashboard

OVERVIEW

Designed a self-service reporting tool that gave Account Managers direct control to build and publish client-facing performance reports — replacing a manual workflow that stitched together three disconnected tools (raw platform data, Google Sheets for formatting, Tableau for visualization) and required analyst involvement for every client report. Before this, every client report required routing through internal resources, creating bottlenecks that slowed client relationship cycles. I led the design end to end, building it in phases and validating with a beta group of AMs over several months before company-wide rollout.

WHAT MADE IT MORE THAN A REPORTING TOOL

The surface-level ask was a reporting dashboard. The underlying problem was one of dependency and confidence — Account Managers didn't have the tools to do work that was fundamentally theirs to own, which meant internal analysts were constantly context-switching to handle requests that didn't require their expertise. The design challenge was building something flexible enough to serve varied client reporting needs while remaining simple enough that Account Managers with no analytics background could use it confidently and independently. Getting that balance right — powerful enough to replace the old workflow, approachable enough to eliminate the need for hand-holding — was the core design problem.

IMPACT

Achieved 85% user satisfaction with 90% of Account Managers finding the tool easy to use independently, with no analyst support required. Adoption extended beyond internal use — AMs began presenting the dashboard directly in client meetings, and client reception was strong enough that clients started asking for direct access themselves.

Following rollout, at least 10 AM-managed client accounts were granted access, a number that continued growing after I transitioned to another team. That external pull — clients actively requesting the tool rather than being asked to adopt it — was the clearest signal that the self-service model had solved a problem on both sides of the relationship, not just an internal one.

Decision Alternatives / options Why Trade-off
1 Pivot table as the core model
  • Fixed report templates
  • Spreadsheet-style grid (your early wireframe)
  • Pre-built dashboards per vertical
Every AM's client needed a different story. Only pivoting could flex to all of them. Flexibility vs. simplicity: more power meant a steeper learning curve for non-analyst AMs.
2 Table as the single source of truth; charts and metrics built from it
  • Separate chart builder with its own data selection
  • Charts as standalone widgets (Tableau-style)
One dataset means the numbers never disagree, which matters a lot once clients see them. Consistency vs. freedom: users couldn't build a chart from data that wasn't in the table.
3 Story hierarchy: Headline Metrics → Charts → Table
  • Freeform canvas / grid layout
  • Table-only view with export
  • Tabbed views
It mirrors how an AM tells a performance story: what happened, then the trend, then the detail. Guided structure vs. layout freedom: there's less customization, but every report reads the same way.
4 Right-side drawer editor
  • Full-page edit mode
  • Modal wizard
  • Inline editing on the chart or table
Users see the result update live while they edit, without losing context. Context vs. space: the drawer squeezes the canvas, and it can feel intimidating as a starting point.
5 Draft → Published states
  • Auto-save, always live
  • Export-only (PDF or Slides)
  • Approval workflow
AMs can experiment safely, and only deliberate versions reach clients. Speed vs. safety: there's an extra step, but it protects client trust.