01
Setting the direction
I facilitated discussions about the direction for accounts and co-created requirements directly with business stakeholders.
BackContact
Accounts
model that
ssccaalleess
model that
ssccaalleess
Accounts
model that
ssccaalleess
model that
ssccaalleess
Accounts
model that
ssccaalleess
model that
ssccaalleess
Client
StoneX | Fortune 50 | Fintech
Role
Senior UX Designer - Led this workstream
USERS
300,000
Shipped
Jan 2026
scope
Web & APP
Client
StoneX
Fortune 50 | Fintech
Role
Senior UX Designer
USERS
300,000
Shipped
Jan 2026
scope
Web & APP
Client
StoneX
Fortune 50 | Fintech
Role
Senior UX Designer
USERS
300,000
Shipped
Jan 2026
scope
Web & APP
context
The problem
I designed accounts model as part of building a unified StoneX platform.Before that, StoneX had 20 + legacy platforms, and accounts looked different in every one of them.
Clients relied on PDF statements instead of platforms - the reason was lack of trust and understanding of their own financial data.
This was where work on the platform began, so it had to scale for all domains (no pressure!)
context
The problem
I designed accounts model as part of building a unified StoneX platform.Before that, StoneX had 20 + legacy platforms, and accounts looked different in every one of them.
Clients relied on PDF statements instead of platforms - the reason was lack of trust and understanding of their own financial data.
This was where work on the platform began, so it had to scale for all domains (no pressure!)
context
The problem
I designed accounts model as part of building a unified StoneX platform.
Before that, StoneX had 20 + legacy platforms, and accounts looked different in every one of them.
Clients relied on PDF statements instead of platforms - the reason was lack of trust and understanding of their own financial data.
This was where work on the platform began, so it had to scale for all domains (no pressure!)
My role
I led design from discovery to final UX
02
Hands-on-work
I ran discovery (desk research, IDI, system explorations), and synthesis; Co-created requirements.
Designed for web & mobile app: from early concept to final designs and post-release enhancements.
Created platform-wide patterns, logic, early design system and detailed specs.
03
Close collaboration
I partnered with business, BA, engineering, data, product, research and UI designers.
I supported dev, ran QA documenting gaps, co-created research scenarios.
Pre -, during- and post-release collaboration for best results.
My role
I led design from discovery to final UX
01
Setting the direction
I facilitated discussions about the direction for accounts and co-created requirements directly with business stakeholders.
02
Hands-on-work
I ran discovery (desk research, IDI, system explorations), and synthesis; Co-created requirements.
Designed for web & mobile app: from early concept to final designs and post-release enhancements.
Created platform-wide patterns, logic, early design system and detailed specs.
03
Close collaboration
I partnered with business, BA, engineering, data, product, research and UI designers.
I supported dev, ran QA documenting gaps, co-created research scenarios.
Pre -, during- and post-release collaboration for best results.
outcomes
and trusted
Shipped,
Tests after release in Jan 2026 shown, that clients consistently pointed to improved clarity, shared understanding of data, and greater trust in the platform - the point of the workstream.
scaled
Built once,
The core account architecture was already scaled to FX Prime Brokerage and Digital Assets without redesign - new products plug into the same structure.
unified
One model,
Account model I created unified legacy models into one. Naming convention updated for key data points reduced confusion across brokers, clients, and internal teams and led to unification.
Key Decisions
Deciding what's important
Key Decisions
Deciding what's important
Key Decisions
Deciding what's important
The process
How I worked
The process
How I worked
The process
How I worked
Discovery
To move things forward, I ran interviews with brokers and multiple sessions with business & data teams to align on how the legacy platforms were actually used, what the data model were, what we could do, and what needed to be improved - there were no requirements to start from.
Impact went beyond discovery. I found that clients didn't trust the data because of inconsistent terminology - this changed data and dev teams thinking about how and where data was sourced and calculated. This also led to a commitment to unify the terminology. Also, the idea of portfolio-centric approach, was created as a result of this research.
After my changes, terminology was standardized. Data states were made explicit (availability, delays, access). Also, the platform was moved toward portfolio-centric setup, that supports client in their analysis and decisions.
Discovery
To move things forward, I ran interviews with brokers and multiple sessions with business & data teams to align on how the legacy platforms were actually used, what the data model were, what we could do, and what needed to be improved - there were no requirements to start from.
Impact went beyond discovery. I found that clients didn't trust the data because of inconsistent terminology - this changed data and dev teams thinking about how and where data was sourced and calculated. This also led to a commitment to unify the terminology. Also, the idea of portfolio-centric approach, was created as a result of this research.
After my changes, terminology was standardized. Data states were made explicit (availability, delays, access). Also, the platform was moved toward portfolio-centric setup, that supports client in their analysis and decisions.
Discovery
To move things forward, I ran interviews with brokers and multiple sessions with business & data teams to align on how the legacy platforms were actually used, what the data model were, what we could do, and what needed to be improved - there were no requirements to start from.
Impact went beyond discovery. I found that clients didn't trust the data because of inconsistent terminology - this changed data and dev teams thinking about how and where data was sourced and calculated. This also led to a commitment to unify the terminology. Also, the idea of portfolio-centric approach, was created as a result of this research.
After my changes, terminology was standardized. Data states were made explicit (availability, delays, access). Also, the platform was moved toward portfolio-centric setup, that supports client in their analysis and decisions.
Interviews with brokers across desks - a proxy for commercial clients we couldn't reach yet.
I did research synthesis including needs, pain points, value to be retrieved and key points for the new platform. I analyzed existing data in legacy platforms, dependencies, terminology and inconsistencies.
Design
for structure
I moved to the cross-account portfolio model and defined the information architecture for accounts, that scaled to other domains.
Impact: the information architecture became the shared foundation — later reused across other domains within the platform, such as Positions, Markets, Documents, and Funds.
Design
for structure
I moved to the cross-account portfolio model and defined the information architecture for accounts, that scaled to other domains.
Impact: the information architecture became the shared foundation — later reused across other domains within the platform, such as Positions, Markets, Documents, and Funds.
Design for structure
I moved to the cross-account portfolio model and defined the information architecture for accounts, that scaled to other domains.
Impact: the information architecture became the shared foundation — later reused across other domains within the platform, such as Positions, Markets, Documents, and Funds.
Design
for system logic
I defined one system logic for handling data states across the platform - data unavailability, delays, offline states, and API or Lightstreamer failures - so behavior stayed predictable instead of solved screen by screen.
Also, I created logic for routing - a fallback mechanism to avoid 404 error on user’s end.
I took care about asynchronous document download, to make sure it doesn’t stop the user when possible.
Impact: consistent error and data handling rules, reused by every team building the new platform.
Design
for system logic
I defined one system logic for handling data states across the platform - data unavailability, delays, offline states, and API or Lightstreamer failures - so behavior stayed predictable instead of solved screen by screen.
Also, I created logic for routing - a fallback mechanism to avoid 404 error on user’s end.
I took care about asynchronous document download, to make sure it doesn’t stop the user when possible.
Impact: consistent error and data handling rules, reused by every team building the new platform.
Design for system logic
I defined one system logic for handling data states across the platform - data unavailability, delays, offline states, and API or Lightstreamer failures - so behavior stayed predictable instead of solved screen by screen.
Also, I created logic for routing - a fallback mechanism to avoid 404 error on user’s end.
I took care about asynchronous document download, to make sure it doesn’t stop the user when possible.
Impact: consistent error and data handling rules, reused by every team building the new platform.
Design
for outcomes
I designed accounts for both web and mobile, from early concept through iterations to final screens, defining flows, states, interactions, permissions-based views, and designing the reusable components that became the first components in the new design system.
Impact: faster MVP delivery without future rework — the foundation other domains built on, cutting design and engineering effort across the platform
Design
for outcomes
I designed accounts for both web and mobile, from early concept through iterations to final screens, defining flows, states, interactions, permissions-based views, and designing the reusable components that became the first components in the new design system.
Impact: faster MVP delivery without future rework — the foundation other domains built on, cutting design and engineering effort across the platform
Design for outcomes
I designed accounts for both web and mobile, from early concept through iterations to final screens, defining flows, states, interactions, permissions-based views, and designing the reusable components that became the first components in the new design system.
Impact: faster MVP delivery without future rework — the foundation other domains built on, cutting design and engineering effort across the platform
Design
for teams, not just hand-off
I wrote detailed specs for dev covering states, behavior, and data sourcing, later used by QA, PM, and research. I supported devs directly, ran QA documenting bugs and fixes.
I also helped prepare usability test scenarios. Once live, I moved into new features as requirements kept coming in.
Impact: teams could build, extend, and validate without needing me for every decision.
Design
for teams, not just hand-off
I wrote detailed specs for dev covering states, behavior, and data sourcing, later used by QA, PM, and research. I supported devs directly, ran QA documenting bugs and fixes.
I also helped prepare usability test scenarios. Once live, I moved into new features as requirements kept coming in.
Impact: teams could build, extend, and validate without needing me for every decision.
Design for teams,
not just hand-off
I wrote detailed specs for dev covering states, behavior, and data sourcing, later used by QA, PM, and research. I supported devs directly, ran QA documenting bugs and fixes.
I also helped prepare usability test scenarios. Once live, I moved into new features as requirements kept coming in.
Impact: teams could build, extend, and validate without needing me for every decision.
Afterthoughts
What I learned
Afterthoughts
What I learned
Afterthoughts
What I learned
System-first
design enables scalability
Creating patterns and models early gives fast value in scalable components and structures teams can reuse and build on. But there are trade-offs: time spent on working these structures out instead of shipping UI fast, and some screens and communication that sometimes feel generic instead of expressing brand personality.
For this Account project, with new product, design, and dev teams joining constantly, that trade-off was worth it. But it's something to keep weighing, not decide once. In later stages it is worth double-checking if and where breaking the pattern can actually create real, measurable value.
System-first
design enables scalability
Creating patterns and models early gives fast value in scalable components and structures teams can reuse and build on. But there are trade-offs: time spent on working these structures out instead of shipping UI fast, and some screens and communication that sometimes feel generic instead of expressing brand personality.
For this Account project, with new product, design, and dev teams joining constantly, that trade-off was worth it. But it's something to keep weighing, not decide once. In later stages it is worth double-checking if and where breaking the pattern can actually create real, measurable value.
System-first design enables scalability
Creating patterns and models early gives fast value in scalable components and structures teams can reuse and build on.
But there are trade-offs: time spent on working these structures out instead of shipping UI fast, and some screens and communication that sometimes feel generic instead of expressing brand personality.
For this Account project, with new product, design, and dev teams joining constantly, that trade-off was worth it. But it's something to keep weighing, not decide once. In later stages it is worth double-checking if and where breaking the pattern can actually create real, measurable value.
Design must act
as system
governance
In high-ambiguity environments, with no clear roles or requirements, it's my job as a designer to help see the big picture and find the pieces to start real work from by setting patterns and rules others can build on.
You can't eat the whole cake at once. Taking it piece by piece is how you deliver value, and let others deliver it too.
Design must act
as system
governance
In high-ambiguity environments, with no clear roles or requirements, it's my job as a designer to help see the big picture and find the pieces to start real work from by setting patterns and rules others can build on.
You can't eat the whole cake at once. Taking it piece by piece is how you deliver value, and let others deliver it too.
Design must act as system
governance
In high-ambiguity environments, with no clear roles or requirements, it's my job as a designer to help see the big picture and find the pieces to start real work from by setting patterns and rules others can build on.
You can't eat the whole cake at once. Taking it piece by piece is how you deliver value, and let others deliver it too.
