The local people in Australia have very limited access to the product we would like to offer. Some competitor products like A and B are not widely used in the local market. Our target audience is seeking an easier and more common way to purchase the product we offer.
Users: we want our users can access to our products on the market easily.
Business: we want the usage of the application to boost and the coverage of merchants and shoppers to expand.
At the beginning of the project, we focused on studying our user groups and conducting competitor analysis. It was the stage that we were trying to discover the possible features our systems could have. We made assumptions like how difficult our users could access the product we offer currently and what is our competitors' target audience.
I was provided with some product documents and had a kick-off meeting with our team to discuss the scope. I started from there and did some competitive analysis and requirements analysis.
Here is the site/mind map I created with the information architecture well structured.
Based on the requirements documents and the site map, I made the sketches and wireframes of our product to validate my design ideas.
Here is the first version of the wireframe.
As our target audience is local Australians, the design style has to be modern and simple. The main principle of the design is that the product has to be super easy to use. We tried our best to reduce the complexity of the system. The information has to be displayed very clearly, and the user flow is smooth and straightforward.
One of the optimized flows example is the sign-up flow. The first iteration of the flow required our users to input their details such as username, email address, phone number, and password. But I soon found that those steps were too trivial, and even the users who log in through 3rd party platform would be required to input their username or email address. The users might lose patience before they finish the process. So I discussed with the team and removed the input of some unnecessary information.
Here is the Sign-up flow diagram.
While the research and design process are vital parts of a project, the dev hand-off should not be neglected. The reality is no matter how great the design is, if something wrong happens between the design-dev collaboration, the result might not be good. Here is a peek at the design system and hand-off structure.
Worked also as a software tester, I have made the requirements into detail and well-documented. Requirements documentation helped us to sync the understanding of our product. All my teammates were satisfied with the results.
