2.User Story

Priya is a software employee who recently relocated to Bangalore. She has 2 kids, Ritvik (8yrs) 4th standard, Aadya(5yrs) 1st standard. She got her kids admission through Edvantagepoint (product of Edqart) so her XYZ school tied-up with Edqart Merchandise services. Through the Edqart app, she is able to buy school products online. So she wants to buy a uniform for her newly joined kid. While she is traveling to her office in a cab she opens the Edqart website on a mobile browser.

She further explores the website and logs-in, as a first-time user she need not to signup with her details, since her mobile number already exists in the Edqart database, as during the admission she registered with Edqart service. Further, she needs to enter her mobile number and OTP and logs-in into the application. She can see XYZ school products and details. Thereafter she selects to see the Merchandise school’s specific products, she selects school uniform and checks sizes, price and adds to the cart. And to the same cart, she adds school bundle packages specific to class( Text and notebooks ) and some other stationery items. She proceeds with the payment. She receives the confirmation on her mobile. The product gets delivered to her doorstep within 2–3 days. Unfortunately, there is an issue with the product size so she raises an exchange request to replace the product and reorders with the new size. Then she receives the right product within 1–2 days, delivered by the representative.

Story Map

3. Journey Map

After defining the “bigger picture”, created a user flow for each of the personas to make this experience more specific to each of their goals. The point of this was to define the intended steps that each user might take through various pages and actions on the website in order to complete their goal. The first user persona I addressed in my user flows was Priya (Parent). Priya’s Journey (illustrated below) explores the website” EdQart“ and registers with the site.

She further explores the website and logs-in, as a first-time user she need not to signup with her details, since her mobile number already exists in the Edqart database, as during the admission she registered with Edqart service. Further, she needs to enter her mobile number and OTP and logs-in into the application. She can see XYZ school products and details. Thereafter she selects to see the Merchandise school’s specific products, she selects school uniform and checks sizes, price and adds to the cart. And to the same cart, she adds school bundle packages specific to class( Text and notebooks ) and some other stationery items. She proceeds with the payment. She receives the confirmation on her mobile. The product gets delivered to her doorstep within 2–3 days. Unfortunately, there is an issue with the product size so she raises an exchange request to replace the product and reorders with the new size. Then she receives the right product within 1–2 days, delivered by the representative.

Information Architecture (IA)

System Map

To give me a comprehensive overview of how a user might navigate through the website, I created a system map. The main goal of this was to gain a better understanding of the functionality and the breadth of the experience that the application should be providing users. I also used this to explore the different ways the website and physical store could be connected.

Ideate

Low fidelity wireframes

Ideate

Prototype

Design

Style Guide

Design

Visual Designs

UX Takeaways

Live Edqart

I really enjoyed the chance to work on the Edqart with such a truly amazing team! I learned a lot about both the new Business strategies new learnings and e-commerce UX.

Dare to experiment — Doing so in a real project single-handedly might sound scary, but fortune favors the brave!

EdQart — Hassel-Free-Delivery

← Back to home