Making investing understandable at scale

01 / Platform evolution

A product that kept widening its promise

The work began with mutual-fund journeys and expanded as Fisdom grew into a broader investment platform. Equities, derivatives, portfolio tracking, account opening, fund movement and partner-bank integrations all introduced their own rules. The design challenge was not to make every surface look alike. It was to make the platform feel coherent while preserving the depth each decision required.

Across five years, the role expanded with the product: from individual flows to shared patterns, design leadership, mentoring and finance education inside the team. Each release became an opportunity to make the next product decision less dependent on memory or interpretation.

02 / Investor confidence

Different investors need different kinds of confidence

A person opening their first investment account needs orientation and reassurance. An experienced trader needs speed, comparison and precise state changes. Both need to understand the consequence of an action before committing to it.

That distinction changed how screens were framed. Guidance moved closer to unfamiliar choices. Dense tools prioritised scanability and consistency. Confirmations explained what had happened and what could happen next. The work treated confidence as a product outcome created by hierarchy, language and feedback—not as a marketing layer added afterwards.

03 / Investment instruments

Designing the investing journey, not isolated screens

The former investment-instruments deep dive covered the end-to-end trading flow. Its strongest idea was continuity: an order form is only useful when it connects clearly to discovery, review, the portfolio view and the funds section that makes the transaction possible.

The order form brought price, quantity, order type and the final commitment into a deliberate sequence. The portfolio view shifted attention from a list of holdings to the state of a person’s positions. The funds section connected balances, linked bank accounts and transfers without making people reconstruct where money was moving.

04 / KYC evolution

Turning a paper-shaped process into a guided digital journey

KYC began as a sequence inherited from forms, documents and operational hand-offs. Simply placing that sequence on a phone would preserve the burden without preserving the context people once received from a person.

The redesigned journey separated preparation from action, explained why each item was required and made alternate document paths visible at the point of choice. Progress became meaningful rather than decorative. Errors were attached to the step a person could fix, and returning users could understand where to resume.

05 / Option chain

Density without encouraging reckless decisions

An option chain is dense because the market is dense. Removing essential variables would make the interface calmer but the decision poorer. The work instead created stable reading paths across calls, puts, strikes and Greeks, then kept the selected contract visible as a trader moved towards an action.

The design also resisted turning speed into pressure. Buy and sell actions remained explicit, a contract summary appeared before the next step, and switching between data views did not erase the current context. The goal was accessible information—not the false promise of effortless derivatives trading.

06 / Shared product system

Reuse the reasoning, not only the component

Shared foundations connected onboarding, order placement, portfolio tracking, GTT orders, screeners, IPOs and alerts. The most valuable reusable unit was often not a button or card, but a behaviour: how a pending state reads, how irreversible action is reviewed, how a number is formatted and how an exception is explained.

This made new product areas easier to discuss and reduced the number of one-off decisions passed to engineering. Components carried interaction rules and content expectations alongside their visual states.

07 / Bank integrations

One money movement, many operational realities

Bank connections introduced differences in authentication, timing, failure states and supported actions. The customer’s mental model, however, stayed simple: where is the money now, where is it going, and what should happen next?

The work established a consistent product frame around those variable rails. Account identity, available balance, transfer amount and completion state remained stable, while integration-specific instructions appeared only when needed.

08 / Finance education and leadership

Domain understanding became part of the design practice

The work grew beyond screen delivery. Finance workshops helped product and design colleagues understand instruments, terminology and the consequences behind user actions. Critiques could then focus on the quality of a decision rather than only the neatness of a layout.

Mentoring and shared review routines also made the system more resilient. The goal was not to make every designer imitate one solution. It was to give the team a stronger set of questions for evaluating the next one.

09 / Evidence

Outcomes will be published with their evidence

The existing case study contains performance, scale and satisfaction figures. They are not reproduced here while the underlying source, measurement period and publication permission are awaiting source and publication approval. The qualitative contribution above is supported by the existing project record; numerical outcomes will appear only after the Fisdom evidence pack is reviewed.

10 / Evolution

The lasting work was a clearer way to respond to change

Financial products do not become finished. Markets move, regulations change and people arrive with different expectations. Over time, Fisdom gained more than a collection of screens: it gained a connected product language and a team better equipped to use it.

That is the thread across the investment, KYC and option-chain work. Understand the consequential decision, make its context visible, then return the useful behaviour to the system.