OCC
Streamlined data-heavy workflows across OCC’s Intraday P&L, Stress Testing and Liquidity Risk platforms, including a 0→1 redesign of Stress Testing.
Why the interface isn’t shown
This work involved sensitive financial systems in a regulated environment. I was not permitted to retain screenshots or interface artifacts, so this case study focuses on the problem, approach, collaboration and decisions I can discuss publicly.
Collaborator perspective
“Markian grasped complex concepts in an impressively short amount of time. Without his knowledge, our team wouldn’t have accomplished this company-wide effort.”
Problem statement
Risk teams don’t lack information. They need to see what matters across large amounts of interconnected data, under business, technical and regulatory constraints.
Improved the existing Intraday P&L application with clearer hierarchy, workflow and data interpretation
Redesigned and rebuilt Stress Testing from the ground up (0→1), alongside Liquidity Risk workflows
Onboarded UI developers and supported the work through implementation
Two workstreams
I was the only UX designer across two separate, highly technical projects, working directly with business systems analysts, product owners, risk leaders and executive directors.
My approach
Without screens to show, this is how the work moved: from expert knowledge to a structure the development team could build.
Design decisions
What I did. Spent significant time with SMEs, analysts, risk leaders and executives to learn not only what information had to appear, but how it related and how teams used it to make decisions.
Why it mattered. Simplifying a risk interface without understanding the system could easily remove context users depended on.
What I did. For Intraday P&L, I refined hierarchy, layouts, workflows, tables and visualization patterns so key information surfaced faster and related data felt connected.
Why it mattered. In a time-sensitive risk environment, usability is less about making a screen look simple and more about showing what deserves attention.
What I did. For Stress Testing & Liquidity Risk, I mapped relationships between data, workflows, system states and tasks, then turned them into an interaction model and implementation-ready UI, iterating as requirements evolved.
Why it mattered. The challenge wasn’t individual screens. It was a coherent structure for a complicated financial system.
Reflection
OCC pushed me to get comfortable entering a domain I knew very little about and learning quickly from the people who understood it best. It reinforced how important it is to understand the data, relationships and decisions behind an experience before trying to simplify it — especially when the information is complex and the stakes are high. I’ve carried that approach into every enterprise product I’ve worked on since.