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.

The asset register in the Figma prototype: one row per asset, opening on active assets, with one security’s secondary listings nested under it.
The asset register in my Figma prototype, with one security’s other listings nested under 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.

The legacy Securities window: a small desktop list of access area, security name, user and updated date.
The window it replaced, at its real size. Test names are changed.

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.

A flip chart mapping securities accounts to safekeeping accounts, then to holding and transaction statements.Sticky notes covering a table, with notes such as tech savvy and manage people resources.Paper sketches of securities account screens taped to a window.

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.

An asset’s detail page: a summary, its primary and secondary listings, holdings, and an audit footer.
An asset’s page, with the identifiers on top and one row for each 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.

The add custom fields menu open beside the CUSIP field, with options to create a custom or SWIFT field.
The inline add, beside CUSIP in the create form.

Click through it

The same frames, joined up. Use the labels, or click through the screen itself.

The asset register, with secondary listings nested under the first asset and its row menu open.
One row per asset, opening on active assets. A security with more listings keeps them nested under it. The cards at the bottom are my notes for developers. Click the first row to open it. Full size
ISIN and CUSIP sit on the asset. Market, currency, SEDOL, Bloomberg ID and internal code sit on each listing. Its holdings and transactions are underneath, with who created, edited and approved it. Full size
The form follows the same model: general, identifiers, primary listing, secondary listings. Click the plus beside CUSIP. Full size
Added after a client walkthrough surfaced a need nobody had documented: internal codes and SWIFT fields, added inline, without leaving the form. Full size

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.

Aurora’s value date balances screen: search above a tree of accounts and dated balances.
Value date balances.
Aurora’s shared templates: a search screen with a side panel of the people a template is shared with.
A shared search template, with the people it’s shared with.