Regulated finance.
This is my domain.
Nearly five years designing financial products inside regulated environments — compliance UI architecture, enterprise design systems, and institutional-grade data visualisation across ASIC, FCA, FINRA and ESMA jurisdictions. Not a domain you learn in a workshop — a set of hard constraints that only become legible after you've designed something that almost violated them.
finance
live systems
held
→ rebuilds
Three things nearly five years actually taught me.
Regulated finance is a set of hard constraints — disclosure hierarchy, audit-trail requirements, risk-prominence rules — that only become legible after you've shipped inside them. That builds a different kind of judgment.
Compliance is architecture, not annotation
Data density is a feature, not a failure mode
Senior means changing how the org makes decisions
What I've shipped — and why it scales up.
Each row: what I built in production, why it matters at institutional scale, and where to verify it.
A global trading platform across 40+ countries, thousands of concurrent users during market hours.
Institutional platforms serve fewer users but at higher data density. Scaling to 100K users proves I can carry institutional 1K-user workloads with heavier data requirements.
150+ pre-tested compliance UI components. No design-related regulatory violations over 2+ years across jurisdictions.
Institutional firms carry serious regulatory risk. I design audit-ready surfaces where every interaction generates a compliant event log — regulations treated as design specs, not afterthoughts.
Cross-timezone operations, multi-currency support, region-specific compliance variations.
Global institutions face the same problems — regional compliance, timezone-aware UX, multi-currency risk reporting. 40+ countries is direct evidence of readiness for global institutional products.
Algorithmic strategy distribution. Risk visualisation (Sharpe, max drawdown, win rate) for retail investors.
Institutional wealth platforms face the same challenge — translating quantitative strategy into investor-friendly UX. TradingCup shows progressive disclosure for complex financial products.
Designed for traders processing 1,000+ data points daily. Roughly 40% faster market analysis via IA redesign (usability testing, n=15).
Professional terminals demand synchronised multi-monitor displays. I architect dense information layouts (1,200+ data points) that stay manageable — using BroadcastChannel / SharedWorkers for instant cross-desk sync.
150+ components, one visual language across web, mobile and trading terminals. ~30–40% faster engineering implementation.
Major institutions run dozens of products needing one design language. Scaling a system across 5 products with 3 engineering teams is direct multi-product design-system evidence.
IPS constraint modeling (Risk, Return, Time Horizon, Tax, Legal/Regulatory), Asset-Liability Matching (ALM) visualization, and behavioral bias adaptation (BFMI).
Institutional portfolio management requires strict adherence to binding IPS constraints and risk budgets. I design interfaces that explicitly surface funding status, duration matching, and explainable AI handoffs without cognitive friction.
Strategic partner on capital-markets and investor materials and investor presentations. Translated design impact into CFO-ready ROI language.
Institutional roles require understanding order flow. I've designed B2B API systems that turn market-protocol detail into clear UI states — traders see execution and status changes accurately.
Core capabilities that move with me.
- Regulatory design architecture: ASIC, FCA, FINRA, ESMA — 150+ compliance components that absorbed 8 regulatory updates without structural rework.
- Information architecture for dense data: designed for traders processing 1,000+ data points per session. Complex data needs organisation, not simplification.
- Multi-product design system: one design language across 5 product lines and 3 engineering teams, zero redesign cycles for shared components.
- C-suite stakeholder alignment: capital-markets and investor materials for CFO/CEO audiences. Translating design rationale into ROI language is a core skill, not a bonus.
- Cross-functional influence: Legal said "no" to my first KYC redesign. I came back with a compliance-annotated spec Legal signed off and Engineering shipped in one sprint.
How the practice was built.
Immediate deep water
ASIC compliance from day one. Multi-asset trading mechanics, KYC/AML flows, leverage-disclosure architecture across 40+ countries. Not onboarding — deep water.
The layer that held
Built the compliance component architecture that absorbed every subsequent regulatory change without rework. Unified 5 disconnected codebases under one design language.
Role expanded, no title change
Capital-markets and investor materials, C-suite product-strategy input, design-system governance across 3 independent engineering teams. (Promotion to Senior effective January 2026.)
The questions that define regulated finance design don't change with whether the user is a retail trader or an institutional portfolio manager:
- How do you show real-time risk without cognitive overload?
- How do you design a disclosure hierarchy that satisfies regulators without breaking the flow?
- How do you scale a design system across products with divergent requirements and no central governance?
- How do you tell a PM their idea would violate a disclosure rule — and make them agree with you?
These are the questions I've been answering in production, at scale, for nearly five years.
Where my work maps — and where it doesn't yet.
Honest disclosure: I have no prior private-banking experience. The section below is my own research into the domain, not firsthand work — shown so you can see exactly where my production experience maps to private-banking constraints, and where it doesn't. The goal: relevant capabilities transfer on day one, not month six.
Relationship Managers
Power users managing 30–100 UHNW relationships at once — advisor dashboards, client activity feeds, compliance task queues, portfolio snapshots in one authenticated workspace.
Closest thing I've built: LogixPanel CRM — advisor-facing tool managing 100K+ trading accounts across regions. Structurally similar: role-based access, audit trails, workflow prioritisation.
UHNW Clients ($10M+ AUM)
Financially sophisticated but time-constrained — they don't want simplification, they want precision, trust signals, and experiences that honour the advisor relationship.
Closest thing I've built: Christie's real-estate platform for $50M+ buyers — same principle: digital tools enhance the broker relationship, they don't commoditise it.
Portfolio & Investment Counselors
Specialists translating multi-asset portfolios into client-facing reporting — performance attribution, risk decomposition, alternatives exposure — for wealthy but non-expert clients.
Closest thing I've built: TradingCup's investor dashboard — translating algorithmic data (Sharpe, max drawdown) into plain-language risk summaries via progressive disclosure.
Hypotheses based on research — I expect to challenge and refine these once I'm inside the actual domain.
Digital tools should make advisors more effective, not replace them. Every feature asks: does this strengthen or weaken the human relationship?
UHNW clients don't need dumbed-down UI — they need confidence in data accuracy. Every number sourced and timestamped. Ambiguity destroys trust at this level.
Role-based data access is the foundation, not a feature. The same RBAC I applied to LogixPanel scales to private-banking confidentiality.
My ASIC disclosure system (pre-tested, modular) would adapt to SEC/FINRA private-banking requirements — though I'd need to learn the specific regulatory nuances.
These are gaps in firsthand production experience, not in domain understanding. I've researched each — but research is not the same as having shipped it.
- Wealth reporting UI (performance attribution, risk decomposition across asset classes)
- Multi-asset portfolio visualisation (equities, fixed income, alternatives, derivatives in one view)
- UHNW self-service portals (document vault, proposal review, e-signature flows)
- Advisor CRM built for private-banking relationship cadence
- Product structure: separately managed accounts, alternatives, trust overlays
- How UHNW clients distinguish self-service vs advisor-mediated actions
- SEC/FINRA private-banking disclosure vs the ASIC retail framework I know
- Internal culture, workflow terminology, team structures at institutional firms
I joined my previous employer with no fintech background. Within 18 months I was leading compliance-architecture decisions across 40+ jurisdictions. That wasn't learning speed — it was systems thinking applied to an unfamiliar domain. These gaps are real and specific; the foundational systems work is already done.
Studied public UX patterns from wealth-management platforms and private-banking documentation — entity-switching UI, consolidated reporting layouts, advisor-dashboard patterns from public sources.
LogixPanel CRM (RBAC, audit trails, multi-account), TradingCup investor dashboard (risk data for non-experts), Christie's luxury platform (relationship-enhancing tools) — all map to private-banking constraints.
Shadow 2–3 Relationship Manager sessions before touching design. Map the gap between how advisors describe their workflow and how current tools support it. Fastest path to informed decisions.
Portfolio-down-15% scenario: show attribution with context, not just the loss. First-login architecture: establish trust before account numbers. Progressive disclosure for quarterly reports.
Confidence ≠ data volume: more metrics made allocation worse. The first-loss design problem: pre-allocation screens showing historical drawdown. Retail-scale challenges transfer directly to UHNW selection.
An AI explainability trail aligned to model-risk and predictive-analytics expectations. Confidence intervals over false precision; a draggable human-handoff threshold. The exact human-AI boundary institutional discretionary management requires.
87% Face ID adoption within 90 days (platform analytics) — authentication as trust signal. Context-specific hierarchy: a UHNW client at 7am wants net performance vs benchmark, not the full dashboard.
The opportunity-cost problem at $5M+: visceral visualisation shifts the mental model from savings to portfolio thinking. Impact first, then mechanism. Onboarding as belief transformation, not product tour.
I design for the emotional state of a UHNW client, not just the information state of the system — the difference between a portal that displays wealth and one that reinforces the advisory relationship.
Three bets, one unresolved tension.
This isn't brand recognition — it's a pattern-level read of how the dominant institutional terminals make specific design trade-offs, and what those trade-offs reveal about their user models. (Described by archetype, not by name.)
Command-line-first input bar, panel-based layout, typography-driven density (8–10px mono). Colour used only semantically; zero decoration.
Learnability sacrificed entirely for power-user density. Onboarding needs 40+ hours of training. The command syntax is an institutional-knowledge moat — opaque by design.
The opacity creates real problems for analysts with visual impairments and multi-lingual teams. A well-structured command palette (⌘K) could keep power-user speed while surfacing commands discoverably.
Customisable widget layout, more navigational affordances, a searchable component catalogue, lighter default density with power-user modes.
More usable for new analysts, worse for power desks trained on the incumbent's patterns. Wins in research-heavy buy-side firms; loses where raw speed and market-data depth matter most.
The customisable model creates a "blank canvas" problem — every install looks different. Role-based default layouts (PM / Risk Officer / Research Analyst presets) would cut first-run friction without losing flexibility.
Web-native, lighter visual language, a card/panel model familiar to modern SaaS users. Strong in fixed-income and FX screening; weaker in equities execution depth.
The web-first shift solved the legacy-desktop problem but created an identity in-between: modern-looking, but less dense than the incumbent and less focused than the workstation.
Card-based layouts create cross-asset correlation blindness — equities and FI on separate cards lose the contextual link multi-asset PMs need. A shared data canvas with semantic linking would restore it.
The pattern across all three
Every institutional terminal is in a slow design war between expert density and modern usability. No platform has resolved the tension — they've each just chosen a side.
The generational transition is accelerating it: analysts who grew up with modern SaaS tooling are joining desks that run dense legacy terminals. The mismatch between their ambient UX expectations and terminal interfaces is real friction — and a real design opportunity.
My thesis from this analysis
The answer isn't "make the dense terminal prettier." It's a system where density is always available but never required — a novice analyst operates at 40% density and a power trader at 100%, on the same data architecture. TradeX explores this with a 4-layer typography hierarchy and role-configurable panels.
This is a hypothesis, not a proven solution — I'd validate it by observing how analysts with 0–2 years of terminal experience navigate versus 10+ year veterans.