A Design System That Earns Its Keep in a Risk Platform

When you're the solo designer across five surfaces of a banking risk-intelligence platform, a design system isn't a nice-to-have — it's how you stay sane and how engineering stays fast. On BlackSwan I built the system in parallel with the surfaces themselves: Explore triage, the Entity page, the monitoring Dashboard, Horizon Scanning, and the Risk Engine all draw from one shared library of tokens, components, and patterns. The payoff your team feels is consistency without coordination overhead. A status pill that means 'flagged' looks and behaves identically whether an analyst sees it in a triage list or an investigator sees it on an entity. That predictability is what lets you ship a new surface without renegotiating every interaction from scratch. For a CTO, the real ROI is maintainability: when a threshold display or a data-density rule changes, it changes in one place and propagates everywhere. I treated the system as a contract between design and engineering — documented states, defined edge cases, named tokens — so the handoff was unambiguous. In a regulated domain where auditability matters, that single source of truth isn't just tidy. It's defensible.