Four years at an ASIC-regulated broker. Eight regulatory rewrites absorbed into a 150-component system, 100K+
traders across 40+ jurisdictions — I design the surfaces where a mis-labeled disclosure becomes a regulatory
finding, not a Slack thread.
Regulated trading platforms, $80M UHNW real estate, and
institutional B2B infrastructure. Each built under a different compliance framework, each serving a
different kind of professional.
ShippedLive client work — production deliverable
ConceptResearch concept — built on real production experience
01
Shipped · 4 Years · Live
Product
ACY Securities
One design system. 5 live platforms. Eight
regulatory updates. Zero structural reworks.
Lead designer across five product lines at an
ASIC-regulated broker — 100K+ active traders, 40+ jurisdictions, supporting $2B+ in daily trading
volume. Four years working directly with the CEO, CFO, Legal, and three engineering teams. I built a
150+ component system where teams ship without coming back to me for every edge case. KYC onboarding
drop-off fell from 73% to 45% (Mixpanel, 90 days post-launch) — that's more funded accounts, not just a
better task score. The system has absorbed 8 regulatory changes at 3–5 days each, against the 3–4 week
rebuilds that came before it.
Four years and counting: I work
directly with leadership on product direction. The design system has survived 8 regulatory updates, 3
engineering team changes, and expansion to 40+ countries — that durability is the return on building for
governance rather than aesthetics.
2024 — team restructured:
After the design team downsized, I maintained delivery across all 5 product lines by integrating AI into
the workflow — copy variants, asset resizing, code scaffolding. All UX decisions, compliance logic, and
governance stayed manual. The system's self-serve documentation made this possible.
Editorial Platform — I handled design,
development, and product decisions
Sole designer and product owner for Christie's
International Real Estate editorial platform — 9 months, five global offices, $5M–$80M property buyers.
I handled design, development, and stakeholder coordination end-to-end. The challenge: translating 260
years of print brand standards into a digital product without compromising a single weight, colour, or
whitespace ratio.
+20% Page Views (GA, 3-month post-launch)60% DB Query Reduction (47→18 queries/page)$5M–$80M UHNW Segment5 Global Offices · 1 Designer
Sole designer, developer, and product
owner. When the brief said "web engineer," I built the product. When the brief outgrew
engineering, I ran the product. Five offices, competing deadlines, one person — nine months.
FIX 4.4 documentation for institutional
clients — where a misconfigured message is a million-dollar position sizing error
Designed the documentation and onboarding system
for ACY's institutional FIX 4.4 API — the protocol that connects prime brokers, liquidity providers, and
institutional clients. Five different types of users (from product managers to market data engineers)
all need to understand the same system differently. I designed that experience. This work later became
the foundation for TradeX.
FIX 4.4 Protocol12+ Institutional Clients5-User TaxonomyB2B Prime Broker
Why this was hard: A
misconfigured FIX message doesn't show an error on screen — it quietly creates a million-dollar position
sizing mistake while the market keeps moving. The design target was self-serve integration: a hedge fund
engineer should be able to go from first API key to production order flow without a support ticket.
Documentation precise enough for developers, clear enough for business people — same system, completely
different needs. Integration time dropped from 3 weeks to 1 week; support tickets dropped 67%.
Shipped · Live
Platform · Tested with Real Traders
Finlogix
Real-Time Market Analytics · Modular Widget
System · ASIC Regulated
Trading analytics platform handling 1,000+
real-time data points. I designed a modular widget system so traders could arrange their workspace the
way they actually think — not the way a product manager assumed they should. Tested with 15 active
traders in controlled sessions. Order placement went from 8.2 seconds to 2.9 seconds. 67% built custom
layouts within 3 months (platform analytics, Q4 2023).
Order Placement 8.2s → 2.9s67% Custom Layout AdoptionTime-to-Insight −40% (n=15)n=15 Paired Usability Study
The research behind it:
Tested with 15 active traders in controlled sessions (paired within-subjects — each person tried both
old and new). Order placement went from 8.2s to 2.9s. The large effect isn't surprising — we
consolidated a 6-step flow into 2 steps, and the statistical analysis confirmed it was genuine, not
noise (p<0.001). The more useful finding was identifying which steps caused the delay: confirmation
modal and instrument search. That insight drove the redesign, not the aggregate number.
Authenticated Financial Platforms at Enterprise Scale
One design system at ACY Securities serves five product lines,
100K+ traders, and 40 regulated markets. Regulatory updates absorb in days because the system was built for
it — not retrofitted into it.
Three independent concept studies — built from public
regulatory frameworks (FINRA, SEC, FinCEN, FATF), competitor teardowns, and domain-expert consultations.
Fictional brands, original IP, no client overlap.
150+ production components built specifically for regulated
financial products. Some handle trading data (prices, orders, charts), some handle compliance requirements
(KYC, risk warnings, disclosures), and they all work across three information density levels — because a
trader and a compliance officer are reading the same data very differently.
What is your investment experience with leveraged products?
FINRA Rule 2111 · ASIC Suitability
FINRA Rule 2111 · suitability as UX challenge
◐ Light Mode
Best Execution ReportMiFID II
Order Execution Summary
INSTRUMENT
EUR/USD
VENUE
ACY Market
SPREAD
0.8 pips
Best Execution Policy✓ Applied
MiFID II Art.27 · RTS 28 · Dodd-Frank Title VII
MiFID II Art.27 best execution · RTS 28 annual execution quality reporting
Document UploadKYC
📎
Upload Identity Document
PDF, JPG or PNG · Max 5MB
✓ Passport✓ Driver's Licence⏳ Utility Bill
ASIC AML/CTF Act 2006 · FATF Rec. 10
KYC document verification · AML compliance flow
Regulatory AcceptanceLegal
Updated Product Disclosure Statement
ACY Securities has updated its PDS effective 1 April 2026 in response to ASIC
regulatory guidance CP 322.
I have read and accept the updated PDS and FSG
ASIC CP 322 · FSG s.942B
ASIC CP 322 · mandatory re-consent on regulatory update
HD · DarkHD
Trading Terminal
EUR/USD1.0869+0.20%
GBP/USD1.2741−0.14%
USD/JPY149.82+0.03%
XAU/USD2,318.4+0.83%
BTC/USD68,420+2.14%
4px padding · 11px · max density
Accessibility · DarkACC
WCAG AA+ / Vision Impaired
EUR/USD1.0869+0.20%
GBP/USD1.2741−0.14%
XAU/USD2,318.4+0.83%
14px+ type · 4.5:1 contrast · 44px touch
i18n · Darki18n
EN · 日本語 · 繁體中文
EUR/USD1.0869+0.20%
米ドル/円149.82+0.03%
英鎊/美元1.2741−0.14%
dir=ltr / dir=rtl · Unicode · CJK
3-language · RTL-safe · Unicode numerals
◐ Light Mode
HD · LightHD
Morning Brief / Report
EUR/USD1.0869+0.20%
GBP/USD1.2741−0.14%
USD/JPY149.82+0.03%
XAU/USD2,318.4+0.83%
BTC/USD68,420+2.14%
4px padding · 11px · max density
Print / ExportPDF
PDF / Regulatory Report
MARKET SNAPSHOT · 02 APR 2026
EUR/USD1.0869+0.20%
GBP/USD1.2741−0.14%
XAU/USD2,318.4+0.83%
Print-safe · ASIC statement format · greyscale-safe
Mobile · LightMOB
iOS / Android · Touch-Optimized
EUR/USD1.0869+0.20%
GBP/USD1.2741−0.14%
XAU/USD2,318.4+0.83%
44px min touch · 16px+ type · thumb-zone safe
Same component set · same data · 6 configurations — dark/light × density × context.
Switched via a single CSS class. Zero additional engineering cost per mode.
Regulatory requirements aren't legal hurdles — they're design
specifications. I translate constraints into reusable design systems, so teams ship faster on every
subsequent update.
ASIC (Australia)
How do you tell users their funds are at risk without
killing conversion? Leverage caps and disclosure rules forced honest hierarchy and clear copywriting.
FINRA / SEC Rules (US)
Designed suitability questionnaires to FINRA Rule 2111
and SEC disclosure standards: making required risk disclosures feel like user protection, not legal fine
print.
ESMA (EU)
Inducement bans as a creativity constraint: designing
engaging promotions when direct incentives are prohibited.
MiFID II Best Execution (EU)
How do you make trade execution transparency feel
like a feature, not a disclosure obligation? Best execution rules forced a rethink of the order
confirmation screen.
Dodd-Frank (US Derivatives)
US derivatives regulation that governs how trade data
is reported and disclosed. Every confirmation I design serves two audiences: the trader who just executed,
and the audit trail that regulators require.
WCAG 2.1 AA
Global accessibility standards for inclusive financial
terminals.
Constraint as Brief — What It Produced
150+
Reusable Design Components
KYC flows, best execution confirmations,
leverage warnings, consent gates — each built once, applied across ASIC, MiFID II, Dodd-Frank, and FCA
simultaneously.
~80%
Faster Regulatory Updates
When MiFID II Art.27 required trade execution
venue
disclosure (showing traders where and how their orders were filled), the update took 3 days — the pattern
already existed. Compliance patches, not rebuilds.
8+
Regulatory Updates Without Rewrites
ASIC CP 322 · FCA SCA · MiFID II Art.27 ·
Dodd-Frank VII · ESMA leverage caps · FATCA · KYC re-consent · PDS update — zero system rewrites.
Regulatory Compliance ArchitectureHow 150+ components enforce MiFID II · Dodd-Frank · ASIC · FCA · FINRA ·
WCAG 2.1 AA at the system level
COMPLIANCE STATUS BOARD
Last Audit: PASSEDViolations: 0--:--:--
JURISDICTION STATUS
KYC / AML PIPELINE
DISCLOSURE GATE STATUS
RISK & AUDIT METRICS
RECENT AUDIT TRAIL
Track Record
Five Years of Work. Here's What Actually Shipped.
Real outcomes from real products — what I owned, what I
measured, and what held up over time.
Measurable Outcomes
Architecture built for compliance change — 8+
regulatory updates shipped without system rewrites
MiFID II · Dodd-Frank VII · ASIC RG 268 · FCA COBS — 40+ countries · zero
downtime
System Scalability — One architecture serving 40+ countries,
flexible patterns built into the core from day one.
Design System Governance — Modular system adopted across 5+
product lines with documentation and engineering alignment.
Faster Design-to-Production — Clear handoff documentation
meant engineering teams could ship features without waiting for me to be involved in every step.
Built for Regulatory Change — MiFID II, Dodd-Frank, ASIC/FCA
requirements are all built as reusable components. When regulations changed, we shipped updates in
days instead of months.
My Design Role
Small team, five product lines — I built systems so
quality scales without any single person as a bottleneck
Design Direction: Set the design standards across 5 product
lines — interaction patterns, visual systems, and research practices that let engineering teams build
without needing my input on every detail.
Design System: Built 150+ components, interaction patterns,
animations, documentation, and developer handoff guides.
Working Across Teams: Worked directly with Legal on
regulatory needs, Product on roadmap priorities, Engineering on technical constraints, Marketing on
content, and leadership on strategic direction.
Leadership Materials: Designed investor briefings, board
decks, and strategic planning documents for the leadership team.
Verifiable Signals
Public References & Endorsements
8 LinkedIn Recommendations · Awwwards Nominee · Open Source · Data
Verification
KYC 47-field negotiation · ASIC 14-day directive shipped on time · Canvas
API unblocked
Legal vs. UX Trade-offs: When Legal required adding 47
disclosure fields to onboarding (ASIC/FCA compliance), data showed 73% drop-off. Built interactive
prototype. After 3-week C-suite mediation, Legal approved conditional implementation with audit trail.
Engineering Constraints: Canvas API animations caused
performance concerns. Ran joint profiling sessions, identified bottleneck (re-render loops).
Redesigned using requestAnimationFrame batching. Engineering validated and became design system
advocate.
Research Process
Data-Driven Decision Making
170+ Hotjar sessions · 15 user tests · 8.2s → 2.9s order placement (64%
faster)
Research Process: Built a 5-step research process using
Hotjar (170+ session recordings) to turn user behaviour data into evidence that convinced stakeholders
to act.
Testing with Real Users: Tested 3 design variants with 15
traders and found critical usability problems. After launch, order placement improved from 8.2s to
2.9s (64% faster).
Getting Buy-In: Used heatmap data (85% CTA visibility) to
convince leadership to invest in the design system.
Research Synthesis · ACY Order Flow
RedesignQ3 2023
① Observe
170+ Hotjar session recordings
② Hypothesize
3 competing variants drafted
③ Test
15 traders · moderated sessions
④ Synthesize
Affinity map · 8 clusters
⑤ Measure
Production telemetry post-launch
Finding 01
Traders abandoned confirmation step
when stop-loss field was not pre-filled — perceived as incomplete order.
→ Default SL/TP from last trade
Finding 02
85% of heatmap clicks on the "Sell"
CTA were hesitation taps — users re-read the price 2–3× before committing.
→ Live price lock with 3s timer
Outcome
64%
faster order placement
8.2s → 2.9s ·
Validated via production telemetry
Design Leadership
Making Design Work Without Me in the Room
From design lead to the person the CEO briefed on investor
materials and the CFO annotated in Figma for same-day sign-offs. That trust came from building systems —
governance, process, cross-functional workflows — not just components.
CEO + CFO · Direct
C-Suite Design Partnership
CEO briefed investor-facing work directly. CFO annotated in
Figma for same-day sign-off — no PM layer, no email rounds.
A 4-step review aligned to the engineering sprint. 30-60-90
onboarding so new hires understand finance, the system, and compliance — not just where Figma lives.
4-step reviewSprint-alignedEmpowerment over micromanagement
Cross-Functional
Governance That Survives
Legal reviews concepts before wireframes, copy before
prototypes, builds before handoff. I join engineering standups so specs match how they actually build.
What my colleagues actually said — 8 public LinkedIn
recommendations from my manager, people I managed, engineers I worked with, and leadership I collaborated
with.
Yung-Yu C. · Direct Report, Zerologix
"Empowers team members by providing opportunities to
lead new projects, favoring empowerment over micromanagement."
Sheng Wen C. · Cloud Data Architect · Different
Team
"Exceptional taste, technical creativity, and an
almost unsettling ability to ship beautiful work fast."
White Chen · Lead Software Engineer · Same Team
"I've worked with designers who throw designs over
the wall — Ed is not one of them. He'd join our standups, ask how we structure components, and adjust
his specs accordingly. That alone saved us a ton of back-and-forth."
The most valuable thing I do is reduce translation loss between
design, legal, and engineering. Legal speaks in regulation numbers. Engineers speak in components. Traders
speak in risk exposure. I speak all three — which means each group stops making expensive assumptions about
the others.
Different financial products need different design approaches. A retail trading app
optimises for speed and simplicity — and that's valid. But when I'm designing for institutional clients
managing real capital, or for platforms where a single UI error could trigger a regulatory violation, the
priority shifts: stability over novelty, trust over conversion tricks, and solutions tailored to each user's
risk tolerance rather than one template for everyone.
The best teams I've worked with don't treat design as decoration or compliance as a
checkbox. They treat them as the same conversation — what does the user need, what does the business
require, and how do we ship something that satisfies both without cutting corners? That's where I add the
most value.
Fit, not template
Right Solution for the Right Client
A retail app and a wealth dashboard serve different
people, different risks, different rules. I've designed both — and know when to drop one playbook for the
other.
Hard flow first
Build for What Comes Next
Start with the flow that has regulation, edge cases, and
real money. Get that right and the product won't need to be rebuilt for the next audit.
Day-one embed
In the Room from Day One
I sit in engineering standups and learn how they
structure components — so specs remove friction instead of adding to it. Same instinct with Legal, CFO,
Ops.
Systems not snowflakes
Systems That Scale with the Business
Every problem becomes a reusable pattern. The next
regulation change absorbs in days, not months — because the system was built to adapt.
Where I push back in fintech design
reviews
Simplicity is the right goal for
consumer apps. It is not the right goal for financial products. The right goal is clarity — and the
two are not the same. A "simplified" trading interface that removes a risk disclosure to reduce visual noise
has just created a compliance violation. A "streamlined" onboarding that skips a step to reduce friction may
have also skipped an ASIC audit requirement. I've pushed back on "make it simpler" many times. Not because
simpler is wrong — but because in regulated products, "simpler" without domain knowledge is just a way to
move the risk somewhere less visible.
I'm not trying to impress other designers. I want the team to
ship better, the business to grow safely, and the users to trust the product enough to keep using it.
Scope of Practice
Beyond the Screen
Investor materials for C-suite. Cross-functional governance
that survived 8 regulatory changes. Financial products running across 40+ markets. The work that never shows
up in a Figma file.
Cross-Cultural Design Leadership
Designing Across Markets: SF · Tokyo · Taipei
Worked across APAC and Western markets, dealing
with different regulatory frameworks (ASIC, FCA, FINRA) and different cultural expectations. Helped
distributed teams understand that localisation is about more than just translating text.
40+
Countries Supported
5+
Regulatory Jurisdictions
3
Time Zones Coordinated
AI-Augmented Design
How I Work with AI in Financial Product Design
I brief AI on the regulatory context — ASIC, FCA, MiFID II —
and then filter its output through five years of lived institutional experience. Claude drafts options; I
validate against compliance, business intent, and how real users actually work. Accessibility audits,
colour-blindness simulations, and edge-case testing happen before anything ships. The AI makes me faster.
The domain knowledge is what makes the output correct.
AI Direction Session
Live collaboration model · ACY Securities fintech case
Real collaboration model — Ed provides domain context and judgment, Claude generates, Ed filters
against lived fintech experience. This portfolio was built exactly this way.
Market Pulse
Simulated ·
Demo mode
Scripted · No live feed
AI Sentiment Indicators
Market Sentiment
Cautious Bullish
S&P 500 · VIX 17.4 · Put/Call 0.82
Fear / Greed Index
Greed
Momentum · Junk bond demand · Breadth
Macro Volatility
Moderate
VIX · MOVE index · EM spread
Asset Class Sentiment
Equities
64% bull
Fixed Income
59% bear
Commodities
72% bull
USD Index
55% bull
Crypto
81% bull
Economic Calendar — Next 5 Events
High
Mon 21:30
US Non-Farm Payrolls Exp: 185K
🇺🇸
High
Tue 02:00
Fed Chair Speech FOMC hawkish
risk
🇺🇸
Med
Tue 17:30
UK CPI YoY Exp: 2.8%
🇬🇧
High
Wed 21:30
US CPI MoM Exp: +0.3%
🇺🇸
Med
Thu 11:00
ECB Rate Decision Hold
expected
🇪🇺
AI-synthesised sentiment indicators — simulated data only. Not financial advice. Not connected to
live market feeds.
This panel demonstrates AI-assisted market intelligence UX design — gauge layouts, confidence
indicators, and calendar hierarchy for institutional trading contexts
UX Copy Generator
Ready · Demo
mode
Scripted · No API
Tone:
Generating...
Scripted outputs · Demonstrates AI-assisted copywriting workflow · Not connected to a live API
Persona Generator
Ready · Demo
mode
Scripted · No API
Scripted personas · Demonstrates AI-assisted research synthesis · Not connected to a live API
This portfolio was built with Claude. AI helps me work
faster — but every design decision comes from five years of shipping real products in regulated markets,
working with legal, engineering, and product teams every day.
"The best financial products feel obvious
in hindsight — not because they're simple, but because someone understood the business well enough to solve
problems before users ever noticed them."
Five years of designing for ASIC, FCA, and MiFID II markets taught me
something: in finance, the gap between "looks good in Figma" and "actually works in production" is
measured in regulatory risk and user trust. I close that gap by earning trust across functions — the CEO
briefs me directly on investor materials, the CFO annotates charts in my Figma files, Legal reviews my
compliance components before engineering builds them. That's a design lead who learned enough of
everyone's world to keep the whole team moving.
The Team Ships Faster with Me in It
Our lead engineer said it was "one of the smoothest cross-team
collaborations" he'd experienced. I join standups, adjust specs to match how engineers structure
components, and jump in on edge cases instead of saying "follow the mockup." Component misuse dropped from
~30% to under 8% (quarterly code review audits) after I introduced governance docs. The CFO's revision
cycle went from multi-day email rounds to same-day Figma sign-off after I onboarded him into the tool.
I Understand What the Business Actually Needs
When ASIC issued a 14-day compliance order, we responded in days because
the design system was already built for it — compliance logic lives in component variants, not page
layouts. When the CEO needed investor materials for a capital raise, he briefed me directly. When I
designed the institutional FIX 4.4 API portal, support tickets dropped 67% and integration time went from
3 weeks to 1. I think about what the business will need next year, not just this sprint.
I Know What Different Users Actually Need
40+ countries, three time zones, users ranging from first-time traders to
institutional desks managing $10M–$500M daily order flow. Each market has different expectations around
trust, risk disclosure, and information density. I've shipped for all of them — retail mobile apps (5.0★
App Store), institutional API portals, and multilingual campaigns in English, Arabic (RTL), Vietnamese,
and Japanese — not with one template, but with the right approach for each.
What I Build, the Whole Team Uses
150+ components across web, iOS, Android, and institutional products. The
architecture decision that matters: compliance logic — leverage warnings, disclosure thresholds, audit
trail markers — lives as component variants, not as page-level overrides. So when ASIC changes a leverage
cap or ESMA bans inducements, engineers update one component and the change propagates across all 5
platforms. Eight regulatory updates in 2 years, zero structural redesigns.
Let's Talk
Senior / Principal Product Design at institutional finance firms — where the design voice carries weight in
product, compliance, and engineering.
If your team builds for traders, RMs, compliance officers, or institutional clients in regulated markets, I'd
welcome the conversation.
