Risk & Compliance
Operations Dashboard

Overview

Paystack's risk and compliance teams were working across 4–5 disconnected tools — spreadsheets, third-party dashboards, email threads, and a partially-built internal tool that had grown organically. The result was slow case resolution, difficulty meeting reporting deadlines, and no single source of truth for transaction risk signals.

I led the end-to-end product design of a unified internal SaaS platform: from research and service blueprint through information architecture, hi-fi design, component specification, and implementation support.

Problem

Risk analysts had to context-switch constantly — pulling data from one tool, cross-referencing in another, then documenting findings somewhere else. The lack of shared state between tools meant case notes were often lost, decision trails were incomplete, and regulatory reports required significant manual assembly.

The platform needed to serve three distinct user groups — each with different workflows and access requirements — within one coherent system.

Process

I ran structured stakeholder interviews with risk analysts, compliance leads, and ops managers to document the actual workflow — what tools were being used, where handoffs broke down, and what data was most critical at each decision point.

From the research I produced a full service blueprint mapping frontstage actions, backstage systems, and support processes across 5 swimlanes. This became the shared reference for the whole design process.

• Stakeholder interviews across 3 user groups
• 5-swimlane service blueprint
• Information architecture for case management, transaction monitoring, and reporting modules
• Lo-fi wireframes → hi-fi Figma designs with full component library
• Accessibility review (WCAG AA)
• Developer handoff with annotated specs

Design Decisions

The dashboard needed to surface risk signals clearly without overwhelming analysts with noise. I introduced a severity-tiered alert system — green, amber, red — that let teams triage by urgency at a glance. Case cards showed the full decision trail in a single view, eliminating the need to reference other tools.

For the reporting module, I prioritised configurability — compliance leads could define reporting windows, thresholds, and export formats without engineering involvement. This moved report generation from a 2-day process to under 20 minutes.