Simplifying leveraged crypto trading
What began as a guide inside the trading page became a separate Easy Margin feature proposed by the CEO. I led the team’s exploration of a simpler trading flow, with a central concern: making a trade easier must not make its consequences feel invisible.
What changed?
leverage adoption
18% is the author-confirmed reporting figure. The historical PDF retains the original 23% figure; the underlying report is not available here to reconcile the calculations.
position completion
Reported increase in position completion.
confusion-related tickets
Reported decrease in confusion-related tickets.
The problem & the evidence
Where the problem came from
Support tickets and liquidation complaints showed the gap between interest in trading and familiarity with crypto markets. Our first response was a guide on the existing page. When the CEO suggested making the experience a feature of its own, we initially pushed back: we worried that another mode would confuse traders.
- Support tickets
- Liquidation complaints
- Usability sessions
- Analytics + Metabase
- Research methods
- Usability testing included 10 professional traders, plus people interested in trading recruited through Support after reviewing their trading volume. The size of the second group is not recorded here.
- Results documentation
- The clearest recalled finding was the mismatch between submitting an order and its execution. The design response is documented below; no post-change test result or A/B lift is claimed for that response.
- How it was measured
- Analytics and Metabase tracked adoption, migration, position completion, and support-ticket changes across the population treated as traders. A separate 500-person cohort was used for the recalled liquidation result; it is not the denominator for all the headline metrics.
- A/B testing
Case-specific A/B results are not documented.
Measurement context
Exact reporting windows, baseline rates, and the definition of position completion are not documented here. The 500-person comparison involved trading activity and volume, but its full method is no longer recalled. The results are reported observations, not a controlled causal estimate.
Change the entry point, not the trading engine
The original case contrasts professional configuration with a simpler directional intention: price up or price down. Easy Margin organized more than seven configuration variables into three intent-driven actions, while retaining the infrastructure underneath.
From contract configuration to directional intent
Extracted from PDF page 3. The original diagram contrasts contract, leverage, margin, liquidation, and position concepts with an Up/Down entry into controlled exposure.
A simpler surface with controls underneath
The PDF describes a parallel layer over the existing engine: intent mapping, automatic structuring, embedded controls, and unlock logic. The interface exposed direction, leverage, estimated P&L, stop-loss buffering, and one-tap close. The diagram is a conceptual service model, not an implementation specification.
The Easy Leverage abstraction layer
Extracted from PDF page 4: existing trading infrastructure, the abstraction layer, risk guardrails, and the retail interface. The labels describe the original case’s model.
Access to higher leverage was earned
Higher tiers were not available by default. As clarified in my account of the project, trading volume, product usage, and user level affected access. This original screen makes volume thresholds visible, helping explain why the slider did not offer every level immediately.
Volume-based leverage thresholds
Embedded screen extracted from PDF page 8. The visible thresholds range from 30x to 60x; sample balances in this capture are interface content, not performance results.
Decisions & leading the team
Question the feature before simplifying it
The CEO originated the idea of a standalone feature. Our initial objection was confusion between trading modes. The difficult question was not how many controls to remove, but how to avoid an experience so effortless that the user wonders whether a real trade has happened.
Shared constraints, independent exploration
After the decision meetings, I brought the whole team into the exploration. I also explained the problem individually, keeping the overall brief stable and leaving the details open, to avoid anchoring everyone on one solution. The final direction emerged from roughly ten design explorations.
Submission is not execution
In testing, people expected the position to open immediately after submission. The execution delay made them feel that the price they received differed from the one shown. We decided to label the displayed values as estimates and introduce an explicit “opening position” state.
Controlled growth had a cost
The original PDF records higher fees than standard margin, restricted leverage tiers, and UI constraints imposed by the risk engine. It attributes the additional overhead to protection buffering, automatic structuring, exposure mapping, and simulation. The tradeoff was controlled participation rather than unrestricted volume.
A separate 500-person cohort
I recall a 30% reduction in liquidations in a smaller cohort of 500 people. The comparison considered trading activity and volume, but I cannot reconstruct the exact baseline, period, or calculation. This figure is kept separate from the trader-wide metrics above.
Screens & design decisions
Easy Leverage trading flow
Original screen extracted from PDF page 5: direction first, a leverage slider, order amount, and estimated profit/loss. These estimates are distinct from the final execution price.
Professional leveraged trading mode
Original screen extracted from PDF page 2: chart, market depth, order types, and detailed position inputs. Compare the configuration density with the guided entry beside it.
My direct work
- Led team exploration of the CEO’s feature proposal, including the initial concerns about trader confusion.
- Kept a shared brief while giving team members room to explore independently; roughly ten designs informed the final direction.
- Used usability findings to clarify estimated values and the delay between submission and position opening.
What I learned
Simplicity can go too far. If an action feels effortless but the user cannot tell what happened, the interface has removed understanding along with the work.
More on the decisions
From an on-page guide to a separate feature
We first considered a guide within the trading page. The CEO proposed a standalone feature instead. We initially objected because another mode might confuse traders. The resulting work kept the underlying trading infrastructure and explored a clearer entry into it.
Direction, exposure, consequence
The guided entry organized direction, leverage, and amount around the existing engine. Access to higher leverage depended on trading volume, product use, and user level. The original interface shows volume-based thresholds; this was not simply an unrestricted slider.
Show what happens after submission
Usability sessions exposed an expectation of instant position opening. When execution took time, users objected to the difference between the displayed estimate and the opened position. We decided to make the estimate explicit and show an opening-position state.