Less time reporting.
Clearer ownership.
Weekly reporting effort fell from 20–30 team hours to approximately 6. The work consolidated a process spread across multiple users and teams into individual ownership, with shared visibility.
The problem I worked on
Reporting involved multiple people and teams. The opportunity was to reduce the effort needed to produce stakeholder-ready reporting while bringing ownership and visibility together.
My role
Reporting Data Analyst Lead. I developed commercial dashboards and reporting foundations spanning media planning through post-campaign analysis and coordinated the people and requirements involved in delivery.
The business outcome
A measured reduction in weekly reporting effort and clearer accountability across teams. This result describes operational efficiency; it does not establish incremental revenue or a campaign-performance uplift.
What the work involved
- Bring the reporting inputs together.Consolidate datasets and reporting requirements so the same reporting process can serve stakeholder needs.
- Check definitions and data quality.Use validation, reconciliation and clear metric definitions to resolve discrepancies before the report is shared.
- Build reporting around the decision.Connect commercial dashboards with the questions being asked from the media plan through post-campaign analysis.
- Make ownership visible.Bring the reporting work under a clear owner while giving the wider teams visibility of progress and outputs.
How the result is measured
Measurement boundary
The recorded reporting times cover the workflow from receiving data to exporting it to stakeholders. The before figure combines work across multiple users and teams; the after figure reflects consolidated ownership. Figures are expressed as weekly reporting effort.
The calculation
At the lower baseline: (20 − 6) ÷ 20 = 70%. At the upper baseline: (30 − 6) ÷ 30 = 80%. The difference is 14–24 team hours a week. This is time released for other work, not a claim of cash savings or headcount reduction.
Based on measured timings reported by Sibusiso Malunga. Client data and identifying operational detail are omitted. The observation window, workload volumes and a formal like-for-like comparison are not published; the result should not be read as a controlled causal evaluation.
What a similar engagement could deliver
A review of the current reporting process, a consolidated model and dashboard, agreed QA checks and a plan for ownership and handover. Scope and success measures would be agreed against your reporting workload.
A separate illustrative reporting design shows a dashboard concept. Its synthetic visuals are not evidence for the measured result above.
Explore the architecture behind the approach
A separate demonstration connects media planning, file validation, dashboard snapshots and a proposed invoice reconciliation branch. Built tools and synthetic examples make each responsibility visible.
Explore the reporting system ↗This illustration is separate from the measured employment result above.