cpdeol
← Back to Projects
Data Engineering + Analytics

Real-time Analytics & BI Dashboard

Eliminated 30-minute data lag so operations and trading teams could detect and respond to incidents in under 30 seconds.

<1s

dashboard query latency

30s

incident detection (was 30 min)

40%

faster operational decisions

100+

concurrent users at <200ms

Role

Lead Technical Business Analyst — BI & Reporting

Timeline

Q1–Q2 2021 · 4 months

Delivery context

Power BITableauSQLSalesforceCapital Markets

The Problem

Legacy reporting dashboards had 30+ minute data latency. Reports were generated hourly via batch jobs. Operations and trading teams couldn't react to real-time issues — every decision was based on stale data. Business units had divergent definitions of key metrics, making cross-team reporting unreliable.

My Contribution

I defined the reporting requirements and KPI framework for this real-time analytics overhaul at a capital markets firm. I facilitated sessions with trading desk leads, operations managers, and compliance stakeholders to document exactly what data they needed, at what latency, and in what form. I standardized metric definitions across four business units, translated those requirements into technical specifications for the data engineering team, validated the data models against source system schemas, and ran structured UAT across all business units before cutover. I also designed the custom dashboards and reports to deliver actionable insights for investment banking operations.

The Solution

Requirements-led analytics: stakeholder workshops to define KPI taxonomy, metric standardization across business units, technical specification for pipeline and dashboard teams, source-to-target validation, and phased rollout with structured UAT.

Results

  • Sub-second query latency on 1M+ events/sec
  • 100+ concurrent users with <200ms updates
  • Incident detection time: 30 minutes → 30 seconds
  • Operations team decisions 40% faster
  • $20B+ daily transaction volume handled
Key learning
Metric standardization was the hidden prerequisite. Four business units had four different definitions of 'active client' — reconciling that ambiguity in requirements workshops, before any pipeline was built, was what made the dashboards trustworthy enough to actually change decision-making behavior.

Tech Stack

BI Tools

TableauPower BISalesforce Reports

Data

SQLSSMSExcelETL

Tools

JIRAConfluenceVisio

Methodology

Agile/ScrumUATBRDData Modeling

Related

How this project connects to the rest of my work.