DCMN · Dashboard Design · Data Visualization
Eliminating 400 Hours of Monthly Reporting Waste
400 hours of manual Excel reporting every month — error-prone, inconsistent, and consuming the strategists most capable of turning data into insight.
Orchestrated 6 months of facilitated workshops and user research — standardizing 50 client accounts onto a single live platform and reclaiming 400 hours of monthly strategist capacity from manual Excel work.
400 hrs/month eliminated. 40 adopters across 5 teams. One standardized report, company-wide. Excel templates are gone.
30+ Hours
per strategist, per month. No longer wasted.
At the start of each month, I had five reports due. Each one could take a full day.
Role
Strategic Designer
Timeline
6 Months
Impact
400 hrs/mo
I orchestrated the full transformation — co-creation strategy sessions across 5 teams, a unified data model, and a live dashboard that replaced 400 hours of monthly manual work across 50 client accounts. 40 adopters. The Excel templates are gone.
01 — Context & Constraints
400 Hours Wasted Before a Single Insight Reached a Client
The organization
DCMN is a performance marketing agency specializing in offline channels — TV, audio, out-of-home — for growth-stage companies. Monthly client reporting was the primary mechanism for demonstrating channel performance. The process was broken.
The target user
Janine — a senior marketing strategist — put it plainly: a single client report could consume a full working day, and at the start of each month she had up to five clients expecting reports simultaneously.
The real constraints
8 hours per report, 50 clients
Up to 8 hours of manual Excel work per report — data entry, formatting, export. Across 50 clients: 400 error-prone hours every month before a single insight reached a client.
Inconsistent templates across the company
No single report standard. Each account manager's own Excel file, their own structure. Clients received different-looking reports depending on who handled their account.
No live data connection
Data pulled manually from ad platforms and pasted into spreadsheets. No API integration, no version control, no audit trail. A single copy-paste error could silently corrupt a client's numbers.
Reporting consumed strategist capacity
The people most capable of turning data into insight were spending their month on data entry. The reporting process was cannibalizing the work the reports were supposed to enable.
02 — The Efficiency Map
From Excel Slog to Live Dashboard
Every step below represents time that was no longer available for the work that matters. The left column shows what the team was losing every month. The right column is what replaced it.
Before — Excel Process
Time lost per client
8+ hours
× 50 clients = 400 hrs/mo
After — Live Dashboard
Time per client
~2 minutes
30+ hours reclaimed per strategist / mo
03 — Discovery & Research
Building Consensus Before Building Anything
Co-creation strategy sessions as the engine
Weekly co-creation sessions via Miro throughout the engagement — not status meetings, but structured alignment sessions where we audited existing reports, synthesized competing views on what data mattered, and built consensus on the information architecture before a single component was designed.
Auditing what existed — before designing anything new
I audited existing reports and catalogued data points across all client accounts. Roughly 70% of content was consistent — the inconsistency was in structure, not substance. Standardization was viable. The data model could be implemented before the UI was designed.
The previous process (left) and workshop artifacts (right)
04 — Stakeholder Management
The Hard Part
The resistance, the prototype that missed, and the political KPI negotiations that shaped the final system.
The resistance
Some team members quietly ran the old Excel process in parallel — comparing numbers until they trusted the data. We let the dashboard prove itself instead of forcing a cutover. That dual-use period became a validation phase. When numbers matched consistently over three cycles, adoption accelerated on its own.
The prototype that looked "too familiar"
My first prototype was functionally correct but looked too much like the old Excel report — same visual language, same cognitive pattern. We had redesigned the data model but not the experience. The second round addressed layout, color system, and navigation before it went to client testing.
The KPI negotiation
Every team had a different opinion on which metrics belonged on each view. The workshop process surfaced the underlying disagreement about what "performance" meant across channels. Once that conversation happened explicitly, KPI prioritization became a product decision rather than a political one.
05 — The Dashboard System
Three Views Built Around How Strategists Actually Think
The final dashboard split reporting into three distinct views aligned to how strategists actually communicate performance — not how the data happened to be structured in the source systems.
Funnel Overview
5-step marketing funnel, budget breakdown by day, key KPI metrics benchmarked against the previous month and the same month of the previous year, adjustable reporting period and campaign filter.
Channel Performance
Toggle between KPIs via dropdown, clear visual distinction between channel types (Awareness, Volume, Frequency), tooltip showing exact values on hover.
Daypart & Timing
Toggle between daypart and weekday breakdowns, timeline view showing how budget and conversions fluctuated throughout the day, splits for key KPIs by time segment.
Interactive prototype — click the tabs to explore Overview and Channels views
Design Principle: Shareable by Default
Every view was designed to be shared live — directly in a client call, not as a static export. This changed the interaction model from "we prepare, they receive" to "we explore together." Strategists reported that client conversations became materially more productive once the data was live in the room.
06 — Business Impact
30+ hours reclaimed
Per strategist, per month — returned to campaign strategy, client storytelling, and the analysis the reports were supposed to enable.
400 hrs/mo — eliminated
Four hundred hours of manual Excel work removed from the monthly cycle across 50 clients. Now billable capacity.
40 adopters across 5 teams
Rolled out across 5 internal teams starting with 3 beta testers. Steep adoption curve once the parallel validation period resolved — no mandate required.
One report, company-wide
A single standardized template replaced the inconsistent Excel patchwork. Every client receives the same structure and quality floor regardless of account manager.
Reactive → proactive
Real-time shareable reports shifted the team from reactive data entry to proactive storytelling — pulling a live view during a client call rather than scheduling a reporting cycle.
Second-Order Outcome
The standardized report structure implemented for this engagement became the template for how DCMN onboarded new clients — institutional alignment that outlasted the project and became operational infrastructure. That's the marker I use to distinguish design that sticks from design that gets replaced.
07 — What I'd Do Differently
I would have built the parallel validation period into the rollout plan intentionally rather than stumbling into it. Letting teams self-verify accelerates adoption more than a hard cutover — that insight was real, but we discovered it emergently. A planned transition protocol would have been faster and less anxious for the team.
I would also have pushed earlier for a client-facing version. The shareable reporting capability was partially retrofitted — but the client interaction model (exploring data live in a call) was the most valuable shift in the whole project. It deserved to be a design brief from the start.