Designing an internal treasury platform for traders at TD Bank
I designed the user journeys for VISION, TD's internal Treasury Reporting application — embedded with Agile developers and delivering Figma-to-React-ready flows in a regulated environment.
Overview
A working tool, not a showcase.
VISION is TD's internal application for Treasury Reporting — used by internal traders and external treasury clients to manage reporting functions. It's not a consumer product; it's a working tool for financial professionals who need speed and precision, not decoration.
Context
Internal tools carry a real cost when they're confusing.
Internal financial tools often get treated as an afterthought — built by whoever's available, patched together over years. VISION's users are traders working under time pressure, and a confusing flow has a real cost: slower reporting, more errors, more support tickets.
Constraints
Designing for two very different users, one regulated tool.
Regulated environment
Every design decision for a treasury reporting tool has to account for financial services compliance.
Two user types
Internal traders and external treasury clients use the application differently, with different needs and technical fluency.
Developer handoff
Designs needed to translate directly into React-ready components, not just look right in Figma.
Sprint cadence
Embedded in an Agile team meant designing at the speed of the sprint, not on a separate design-only timeline.
Process
Embedded, not handed a spec.
- Created the user journeys for internal clients and external traders using the Treasury Application.
- Embedded within Agile teams, working closely with developers and product owners sprint over sprint.
- Delivered Figma designs and Anima prototypes optimized for direct React integration by front-end teams.
- Facilitated UX workshops and stakeholder feedback sessions to validate flows before build.
- Applied visual hierarchy and typography principles to make a dense reporting tool easier to scan under pressure.
Key decisions
Separate journeys, faster handoff.
Two distinct journeys, not one generic flow
Mapped separate journeys for internal traders vs. external clients rather than forcing both into a single compromise flow.
Developer-ready handoff by default
Prioritized Figma + Anima prototypes built for direct React integration, shortening the gap between design and shipped code.
Structured workshops over one-off reviews
Ran scheduled UX workshops so stakeholder feedback landed before designs were locked, not after.
Where it landed
Shipped in a live, regulated environment.
- Shipped inside a live regulated financial services environment, not a sandbox or prototype-only engagement.
- Design-to-development handoff became faster and more predictable with React-ready prototypes.
- Alongside this role, I led TD's 200-member Design Book Club — a peer community across the broader design org.
Reflection
What I'd tell another designer facing this.
Internal tools rarely get design attention, which is exactly why they're an opportunity. A trader who trusts the tool moves faster; that trust gets built through the unglamorous work of hierarchy, consistency, and predictable interaction patterns.