01 / The problem
The first request was also the most sensitive.
HelloGold’s onboarding asked people to submit identification before reaching the dashboard. My work reconsidered that sequence as part of the onboarding and KYC experience.
The design question was about timing: could a person first understand the product, then encounter the document request in the context of the financial action it enabled?
02 / The flow
Move verification into a clearer context.
The revised direction separated account creation and product exploration from the point at which a customer chose to buy gold. The document request then had a visible purpose within the journey.
Verification remained a product and compliance constraint. The change concerned how the request was introduced, rather than removing it.
Earlier sequence
Create account → Submit identification → Enter dashboard
Revised direction
Create account → Explore dashboard → Choose to buy → Complete required verification
Historical sequence reconstructed from the written project account. This is an editorial flow diagram, not a client screen.
03 / Takeaway
Make the reason visible with the request.
Sensitive information has a place in a financial journey. The interface also has to explain why it is needed and what happens next. Here, the design contribution was to connect that request to a meaningful point in the experience.
Next project