Falcon: Instrument Data Management
Instrument Data Management is an application within Falcon, an institutional platform for managing Fixed-Income, Currencies, and Commodities, designed to streamline data querying, amendment, and maintenance for traders.
In this project, I collaborated closely with a Business Analyst (BA) to identify all potential use cases, distilled them into a clear user flow, and transformed complex business requirements into a structured, user-friendly interface.
Company
HSBC
Year
2023
Duration
2 months
My Contribution
User Journey
User Story
High Fidelity Prototype
Requirement Documentation
*For confidentiality purposes, names, data, and specific functionalities, have been modified or anonymised. The core process and outcomes remain accurate to reflect my contributions and learnings.
Trader
PRIMARY USER
Responsibility
Correct the wrong instrument data
Submit new instrument data for trading
Monitor the amended live data until it is correct from ION
Collaboration scenario
Submit the corrected instrument data to the Approver for approval
Chase the ION user for instrument data update
Challenge
There’s a huge amount of data (over 70 fields) per one instrument
Expectation
Quickly figure out the data that’s pending adjustment, pending adjustment cancellation or need to chase the ION user
Approver
SECONDARY USER
Responsibility
Review and approve/reject the data submitted from the trader
Collaboration scenario
Approve the instrument data proposed from the Trader
Challenge
There’s a huge amount of data (over 70 fields) per one instrument
Expectation
Quickly find the data that’s pending review from massive trading data
ION User
RELATED USER
Responsibility
Correct the instrument data from ION platfrom
Collaboration scenario
Receive reminder from the Trader to correct the data
Design document (Axure)
#1 Instrument Searcher
The search bar is designed for quick enquiry and access the data from database. To query the data, user need to select the type of instrument ID and type the ID number.
#2 Filters
Although I proposed using tabs to sort instruments by different statuses, the Product Owner preferred an earlier release for requirement validation. After discussion, we agreed to adopt the platform’s inherited filtering feature as a compromise for MVP1.
#3 Days Since Adjusted
By sorting the whole table by this column, the user can easily track the days since the data has been adjusted. Then, they can decide whether to generate a report to chase ION staff for data rectification.
#4 Updated Indicator
Helps the user to quickly figure out whether an instrument source data has been updated from ION since adjustment.
#1 Instrument Information
To properly use the limited space, we decide to move the uneditable, basic information to the top.
#2 Historical Data Display
Users might want to refer to historically adjusted data. To assist users focusing on the tasks while enabling the historical data enquiring requirement, I designed this toggle to expand/hide the past adjustments.
#3 Copy to Amend
As one instrument data includes over 70 fields. Proposing a new data from a blank row is not a productive choice.
Therefore, we enable users to start amending data from a duplicated row.
To find a field easier, it was suggested to further group the fields by business logic.
