09 · Projects
Murex
Voice Process – Trade entry on behalf of clients
The request
In the Murex platform, only clients could enter a trade request. Salespeople had no way to do it on their behalf, so clients were building their own solution for their sales teams. The request: an entry component built into the platform.
The solution
The form chains fields that depend on each other: counterparty, eligible products, configuration, then price and margin calculation. I made that sequence readable at every step, and brought out the information that matters on the phone: is the price still valid? It stays on screen from start to finish, to keep pace with a call.
Fields that depend on one another
The other challenge was the form's mechanics: almost every field depends on the one before it. Until the counterparty is chosen, nothing else can be entered. Once it is selected, only the financial products eligible for that counterparty are offered. Choosing the product and then configuring it (currency pair, direction, notional, expiry, strike) triggers the automatic calculation of the trader price, the sales margin and the final amount quoted to the client. That chain had to be readable: at every step, seeing what is already set, what is left to enter and what has just been recalculated.
Information hierarchy
Digging into it, I realised the most decisive piece of information is a very simple one: is the price still valid? Current, about to expire, or already expired. It is restated the same way from the top of the form to the bottom.
The most decisive piece of information is a very simple one: is the price still valid?
Keeping up with the pace of a phone call
The form has to keep up with a live call: capture the request, price it and confirm it while the client is still on the line. Nobody should have to wonder, mid-call, whether the amount they are about to quote still holds.
