Aurora
If you’d like to learn more, please get in touch.
Owned Aurora’s product design for over a year at Smartstream. One example is its new securities module, shown here: I co-led a two-day workshop in Vienna with development, QA, product and documentation, then designed it.
Context
Aurora is Smartstream’s reconciliations and payments product. Its securities launch needed a register that banks and hedge funds could trust for securities data, so I redesigned how a security is created, found and read. I handed it off with user flows and logic documentation.
Problem
One security can list on several markets, in several currencies, under several identifiers. The legacy screens scattered those across rows and screens, so people moved back and forth between records to understand a single asset. That slowed routine work and raised the risk of errors, and it got worse as the securities module grew.
Workshop
I co-led a two-day workshop in Vienna with development, QA, product and documentation. We mapped how different users work with securities data day to day, then turned those workflows into system structures. It showed the system was organised around how data was stored, when people think in terms of assets.
Decisions
One record per asset, with its listings nested
People look for the asset first and the market second. ISIN and CUSIP belong to the asset; market, currency, SEDOL, Bloomberg ID and internal code belong to each listing. The screen now follows that model, instead of a separate row for every listing.
Active assets by default
Daily work happens on active assets, so that’s where the screen opens. Inactive ones are one tab away, and nothing is hidden.
Identifiers people can extend
An unscripted client walkthrough during a design review surfaced a need nobody had documented: custom identifiers, especially internal codes and SWIFT. The requirements described a fixed set of fields. I added an inline add, and updated the create flow for primary and secondary listings.
Click through it
The same frames, joined up. Use the labels, or click through the screen itself.

Constraints
Strict compliance requirements, a launch date, and no tolerance for breaking existing workflows or terminology. The interface had to get simpler for operational users without simplifying the data underneath, for technical users too.
More of Aurora
I owned the product’s design for over a year, so securities wasn’t the only part. Two others: value date balances, and search templates people can share.










