CASE STUDY · OPTIONS CLEARING CORPORATION · VIA EVIDEN
As Eviden’s UX designer across two OCC workstreams, I helped simplify data-heavy applications used to understand intraday performance, stress scenarios and liquidity risk.
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.
The challenge
Risk systems have the opposite of a typical product problem: there’s no lack of information. The challenge is presenting a large amount of interconnected data without obscuring what matters, under business, technical and regulatory constraints.
What I delivered
Role and responsibilities
Two workstreams
I was the only UX designer across two highly technical areas, working directly with business systems analysts, product owners, risk leaders and executive directors.
“Markian grasped complex concepts in an impressively short amount of time. Without his knowledge, our team wouldn’t have accomplished this company-wide effort.”
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 didSpent 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 matteredSimplifying a risk interface without understanding the system could easily remove context users depended on.
What I didFor Intraday P&L, I refined hierarchy, layouts, workflows, tables and visualization patterns so key information surfaced faster and related data felt connected.
Why it matteredIn a time-sensitive risk environment, usability is less about making a screen look simple and more about showing what deserves attention.
What I didFor 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 matteredThe challenge wasn’t individual screens. It was a coherent structure for a complicated financial system.
Reflection
[Two or three sentences in your words: what learning a new domain this quickly taught you, and how it shaped your approach to complex systems.]