Making investing part of an everyday wallet.

Mapping the constraints first.

Singtel Dash partnered with UOBAM to offer investing within the wallet. We adapted UOBAM’s existing product for Dash users.

The team was briefed by Dash’s product manager and the UOBAM team. I mapped the required checks, branches and exception states to surface all the constraints, so the team could review where an application could continue or had to stop.

We had no product-specific user research to work from, so my experience designing for Dash users helped me frame a working assumption: familiarity with a mobile wallet would not necessarily mean confidence with investing. I tried to prioritise Dash’s core users: people who might need help interpreting risk, returns and the movement of their money, but that assumption still needed testing with actual users.

Two gates needed explicit branches: US-person status determined whether an application could continue; Singpass MyInfo or manual registration determined how identity details were collected. Both know your customer (KYC) routes checked the ID against the Dash account before moving on to employment, source of funds, Common Reporting Standard (CRS) tax residency and the declaration. These checks were part of the onboarding requirements supplied to the team. Making those branches visible helped explain the journey to stakeholders and gave the team a defined outcome for each route.

Where the money is, and what to do next.

The same order, from sign-up to withdrawal.

I designed the same hierarchy throughout the user journey. After the risk questions, onboarding offered one recommended portfolio with the option to change it. This limited the initial comparison while adding options if users wanted an alternative. The dashboard was designed with the investment numbers and the main actions that can be taken always visible.

Moving money raised different questions: what the deposit options were and where users would receive their funds after withdrawal. Deposits showed each funding method’s minimum before amount entry. Withdrawals kept the destination visible, labelled the amount as indicative and allowed the user to check the details before confirmation. Those review steps were added deliberately to increase friction, giving users another opportunity to verify their intended action.

Handing over the whole journey.

The feature followed a waterfall process, with limited iteration once designs were sent to the offshore engineering team. The handoff covered flows, screen states and interaction rules using Dash’s design system that the team and I co-created. My colleague June Kang owned the UI. My responsibility was making the journey and its behaviour explicit.

Exceptions mattered as much to the experience as the happy path: an identity mismatch blocked progress, editing MyInfo details changed the registration route, and a withdrawal needed a review and pending state. We worked with the UOBAM team for compliance reviews, QA sign-off and dogfooding. Those internal checks supported delivery, but we didn’t have time to test the experience with customers.

Interactive prototype

Launched in December 2021.

Singtel and UOBAM announced Robo-Invest’s launch on 21 December 2021.

If I were to take the product forward, I’d focus on:

• Testing risk-question wording and comprehension of portfolio information with Dash users new to investing, then checking whether they can understand their holdings and what they’ve invested in.
• Building a funnel to measure conversion rates from risk assessment to submitted identity details and then first deposit, using the drop-offs to guide the next iteration.