Back

B2CFintechWebMobile

Transformed Service Centre-assisted options trading into a scalable self-serve investing capability

Multi-leg options trading interface

The desktop trading experience, alongside the mobile concept explored for a later release.

Impact at a glance

I helped turn a manual, Service Centre-assisted process into Qtrade’s first self-serve multi-leg options trading capability. The design brought contract selection and strategy building into one workflow, with an architecture designed to support up to four legs.

A platform gap that created risk, friction, and operational cost

Qtrade supported only single-leg options trading through a basic order form. Investors placing multi-leg strategies had to call the Service Centre, creating a fragmented experience across product and operations.

  • Advanced traders could not execute strategies independently
  • Service Centre teams manually placed complex trades
  • Manual workflows introduced delays and execution errors
  • The platform lacked expected tools like an options chain and strategy builder

This was not just a missing feature. It was a platform limitation that prevented Qtrade from supporting more advanced trading behaviour at scale.

Objective

  • Enable self-serve multi-leg options trading
  • Reduce operational dependency on Service Centre workflows
  • Prevent high-cost order entry errors
  • Support experienced traders without overwhelming others
  • Design a scalable foundation for future trading capabilities

My role

I led the design of a new trading capability, defining the workflow, interaction model, and scalable architecture across product, engineering, and trading stakeholders.

Understanding the system before designing the interface

This problem required understanding trading behaviour, internal workflows, and system constraints before designing screens.

  • Interviewed Service Centre reps to understand manual trade execution
  • Worked with trading SMEs to identify key strategies and constraints
  • Mapped internal systems that were not built for multi-leg logic
Manual workflow

Mapping internal workflows revealed where the product needed to replace operational dependency.

Mapping the trading workflow

I mapped the end-to-end task flow to understand how traders build and validate a strategy.

  • Identified key decision points and error risks
  • Aligned teams around the actual trading workflow
  • Separated UI decisions from system constraints
Task flow

Mapping traders’ decisions and the steps involved in building a multi-leg strategy.

Exploring the smallest viable change

I initially explored whether we could extend Qtrade's existing options trading form rather than build an entirely new experience. The idea was to add an options chain and let traders configure their first leg, then progressively add more legs to a strategy of up to four. This could potentially reduce development effort and accelerate time to market.

The early concepts focused on:

  • Adding contract selection to the existing trading experience
  • Building a strategy one leg at a time
  • Keeping selected legs visible as the order took shape
Early single-leg entry concept

First exploration: extending the existing options order form rather than replacing it.

Early step-by-step concept supporting up to four legs

A sequential flow for adding up to four legs, with navigation between each step.

Testing the approach with options traders

Testing the early concepts with options traders exposed a problem: while the flow could support multi-leg strategies, it required too many steps. Traders also pointed out that some order settings applied to the strategy as a whole, not to each leg.

The feedback made two issues clear:

  • Configuring each leg through separate steps slowed down strategy building
  • Repeating order-level decisions added work without helping traders make better choices

That challenged my assumption that the smallest change to the existing interface would also be the best experience. I needed to reconsider the interaction model.

Early usability testing concepts

Early concepts and workflow variations reviewed after trader feedback.

Reconsidering the interaction model

I returned to my competitive analysis, looking at Robinhood, Wealthsimple, Yahoo Finance, and Canadian financial institutions. Some experiences used traditional options chains with calls and puts side by side; others focused on the contract information traders use to make decisions. I also saw guided approaches that kept multiple legs on a single screen.

Internal trading specialists shared examples of professional trading applications where the options chain was the central workspace for evaluating contracts and constructing strategies.

Combined with trader feedback, this pointed to a different direction: make the options chain the centre of the experience, rather than one step in a longer form.

Revised options-chain concept

A revised concept placing the options chain and strategy summary on one screen.

Converging on an integrated trading experience

I explored a single-page layout that brought the key trading interactions together. The options chain sat on the left, where traders could evaluate contracts and select legs. On the right, a persistent panel showed their developing strategy and the settings needed to place the order.

This brought together:

  • Contract selection: Evaluate available contracts directly in the options chain
  • Strategy building: See and adjust selected legs in a live summary
  • Order configuration: Set order-level details without repeating them for every leg

Rather than removing complexity, I organized it around the decisions experienced traders needed to make. The result was a more connected approach with less back-and-forth between screens.

Integrated options trading layout

The integrated desktop layout brings contract selection and order details together.

Designing the interaction model

The core challenge was not designing an interface, but structuring a trading workflow that could support complex strategies while reducing risk and scaling across future capabilities.

  • Used an object-action model to structure the experience
  • Designed a modular system for building strategies leg-by-leg
  • Created a real-time feedback loop through a live strategy summary
Object action model

An object-action model used to define what traders could do with contracts and strategies.

Key design decisions and tradeoffs

  • Structured flexibility over full customization: Guided leg-by-leg construction reduced errors while maintaining control
  • Options chain as primary input: Selecting contracts directly reduced manual entry and aligned with trader expectations
  • Deferred advanced analytics: Excluded P&L graphs initially due to system constraints, focusing on order accuracy first
  • Scalable architecture over MVP simplicity: Designed for 4-leg strategies even though MVP supported only 2

Designing for confidence in high-risk decisions

This was also a behavioural design problem. The interface needed to support fast decisions without encouraging mistakes.

  • Progressive disclosure: Reduced cognitive overload
  • Feedback loops: Live strategy updates reinforced accuracy
  • Error prevention: Reduced reliance on manual entry
  • Review before commitment: Encouraged deliberate verification
Review screen

Order review concepts designed to help traders verify their strategy before submission.

Adapting the experience for mobile

Although the initial release focused on web, I also designed a mobile experience. The challenge was adapting a data-heavy trading workflow to a smaller screen while preserving the control traders needed to build and review a strategy.

The mobile concepts explored:

  • Using focused screens and bottom sheets for contract selection and trade actions
  • Revealing details progressively instead of crowding every control onto one screen
  • Giving traders a dedicated place to review selected legs and order details
Mobile Flow

Exploring how contract selection and order building could work on mobile.

Mobile Screens

Mobile screen concepts using bottom sheets and a dedicated order review experience.

Mobile implementation was deferred because of platform dependencies. The designs remain an exploration of how the same trading capability could work across web and mobile, not a shipped mobile experience.

Impact

  • Enabled Qtrade’s first self-serve multi-leg trading capability
  • Reduced reliance on manual Service Centre workflows
  • Reduced order entry errors in a high risk financial workflow
  • Shifted complex trading from operational dependency to product capability
  • Established a scalable foundation for future trading features

This work helped transition Qtrade from a service-supported trading model to a more scalable product driven experience.

Back to top