Back to work

cInvest (Convoy DWM)

LiveMarbled wealth
ProblemThe DWM team needed to understand what users expected from digital wealth services and where opportunities sat vs. direct competitors.
My roleSenior Designer
CONTEXT

Digital wealth for Hong Kong

cInvest is an online fund supermarket by Convoy Finance Ltd, licensed for Type 1 (Dealing in Securities), Type 4 (Advising on Securities) and Type 9 (Asset Management). The Digital Wealth Management team wanted to understand what their users needed from the service and identify the opportunities worth going after.

01 · RESEARCH

Product research on top of market research

Convoy had commissioned the fundamental market research. On top of that, our team continued deeper product research: feature comparison of direct competitive products, the marketing approach of direct competitors, and a product-regulatory study specific to the Hong Kong market. The goal: get to the specifics behind the macro picture.

Further market research
Stacking deeper research on top of the vendor-supplied macro picture.
HMW clustering board
HMW clustering — from raw research to opportunity areas.
02 · JOURNEY

Ideal journey, real touchpoints

The insights from research fed a User Journey Map: thoughts, actions, needs and benefits of the user at each stage, stacked against every internal touchpoint that served that stage.

Creating a journey map as a deliverable helps both the product team and the business see the bigger picture. It lets us focus based on research, and it helped every internal stakeholder understand where they fit into the experience.

cInvest user journey map
Thoughts, actions, needs — mapped against every internal touchpoint.
03 · FLOWS

Define product scope with user flows

User flows forced the team to think through every consideration that might affect design decisions. Walking every step of a flow together meant no requirement, detail or interaction got forgotten. Even better: the diagram projected the final product’s shape, cutting down errors and iteration count right from the start.

Product scope definition
DWM service blueprint
Service blueprint — internal ops mapped against user-facing flow.
User flow sketches
Early flow sketches — walking every decision point together.
04 · UI

Storyboard before pixels

Storyboarded the core interactions before pushing pixels. The storyboard sits between flow and prototype — it lets the team agree on interaction beats and content structure before anyone commits to visual decisions.

cInvest storyboard final draft
05 · PROTOTYPE

Prototype with user stories

After defining the requirements, the flow showed the product’s structure like a blueprint; the prototype showed its first full-scale, functional form. Prototypes reduced development time by giving engineers a concrete target, gave stakeholders visuals to react to, and — most important — let the team weed out approaches that didn’t work before they cost real build time.

DWM phase 1 prototype — onboarding
DWM phase 1 prototype — core flow
DWM phase 1 prototype — detail
Prototype with user stories — first full-scale functional form.
06 · SYSTEM

A Lego kit for the whole app

For cInvest to stay extensible, it needed a design system. Standards for design and code, unifying both practices — the same instructions and Lego kit for everyone. Benefits: faster development, consistent layout, and reduced variance in user experience as more surfaces shipped.

cInvest colour theme and tokens
Colour theme as the first foundation — shared tokens across every surface.
See how I ship with agentsBack to work