← Back to Work

JPMorganAsset Pricing & Reference Data

Turning manual pricing work into shared infrastructure

Reducing repetitive price-sourcing work while making checks, challenges, and team knowledge easier to reuse.

An early, time-sensitive pricing day.

The pricing day started early and moved quickly. The team sourced, validated, and challenged prices across large volumes of financial instruments under tight morning deadlines.

Fixed-income sourcing depended heavily on manual work across multiple market-data sources. The process was repetitive, time-sensitive, and vulnerable to errors when information had to be retrieved, entered, checked, and rechecked by hand.

The manual sourcing path Time and opportunities for error accumulated through repeated retrieval and handling.
  1. Instrument / request
  2. Identify sourceSource switching
  3. Retrieve priceRepetition
  4. Enter / transfer resultManual handling
  5. Validate
  6. Investigate exception
  7. RepeatTime accumulates

Three intervention points.

Price sourcing

I automated parts of fixed-income price sourcing so prices could be pulled in bulk rather than retrieved instrument by instrument.

  • Bulk price retrieval for appropriate fixed-income workflows
  • Prepared inputs that reduced repeated manual entry
  • Automated handling of repetitive sourcing steps

Checks + controls

I added checks around the automated workflows so reducing manual work did not mean reducing scrutiny.

The checks helped surface exceptions for review instead of depending on repeated manual inspection.

Price-challenge knowledge

Pricing questions often required research before a price could be accepted or challenged. I created a shared tracker so once a question had been researched and resolved, the reasoning could be reused instead of rediscovered.

Prior pattern
ResolveForgetInvestigate again
Shared tracker
QuestionResearchResolutionShared recordReuse

The point was not just to make my own morning faster.

I shared workflows, controls, shortcuts, and process improvements with the wider team so useful changes became part of how the work could be done, rather than staying personal workarounds.

Personal efficiencyShared team utility

Two practical improvements.

Substantially faster sourcing
Targeted fixed-income sourcing workflow

Automating repetitive sourcing steps substantially reduced the time required for the targeted workflow.

Fewermanual errors
Automated fixed-income sourcing workflow

Reducing repeated manual handling also led to materially fewer errors in the automated workflow.

Where the work changed.

Before

  • Repeated manual sourcing
  • Repeated data entry
  • Repeated investigations
  • Useful knowledge often remained local

After

  • Bulk / automated sourcing where appropriate
  • Checks and controls around automation
  • Exceptions surfaced for review
  • Resolved price challenges reusable by the team

Automate repetition → preserve judgment

The useful automation was not the automation that removed people from the process. It was the automation that removed repetitive work while making the places that still required judgment easier to see.

Less time spent retrieving information.More structure around where human judgment was still needed.