A glimpse of my work and their impact @HYPD

Throughout my tenure at HYPD, I've conceptualized and designed numerous features that not only benefited the company but also contributed to substantial revenue generation.

<aside> <img src="https://upload.wikimedia.org/wikipedia/commons/a/ab/Apple-logo.png" alt="https://upload.wikimedia.org/wikipedia/commons/a/ab/Apple-logo.png" width="40px" /> App Store →

</aside>

<aside> <img src="https://upload.wikimedia.org/wikipedia/commons/thumb/d/d0/Google_Play_Arrow_logo.svg/1200px-Google_Play_Arrow_logo.svg.png" alt="https://upload.wikimedia.org/wikipedia/commons/thumb/d/d0/Google_Play_Arrow_logo.svg/1200px-Google_Play_Arrow_logo.svg.png" width="40px" /> Google Play →

</aside>

Frame 1000003354.png

1) Order Page

This redesign marks one of my initial enhancements since joining HYPD. While it may seem like a standard feature, it addressed significant issues that were adversely affecting the business.

order details page 1.png

chimp-builder.png

Problems with the current design

  1. It was not dynamic, Developers needed to code the same page twice for web and mobile
  2. No cancellation button resulting in over 80% of user queries
  3. No product Suggestion.
  4. No CTAs for different states of the page

chimp-components.png

Solution for existing problems

  1. Dividing the page into smaller chunks and structuring the data based on the information that is normally perceived together.
  2. Adding Dynamic CTAs that will keep changing depending on the state.
  3. Added suggested products.

chimp-theme.png

Impact it had on business

  1. Reduced the user queries to 78%.
  2. 10% increase in sales
  3. 30% increase in product cancellation.(which was anyways up to 20%)
  4. Reduced development time and seamless user experience on all platforms.

Given the absence of technical constraints and a shift in business needs, we decided to redesign the page. Our approach involved organizing the data into groups and identifying which data can be modified dynamically based on the order's state.

We divided the data into 3 parts.

  1. Order details
  2. Order Status
  3. Contact details

The second step was to define the stages of an order.

By keeping the order detail block dynamic it was easier to change the data just inside that block from order confirmed > payment failed > On the way > canceled> delayed.

dynamic components.png

While it may seem that order cancellations briefly surged, it was a strategic decision made at the intersection of business requirements and user needs. Despite the initial uptick in cancellations, the long-term outcome was a notable enhancement in user experience, contributing to improved customer retention.

Later on, this same structure was used for the return & cancellation of the order, designing for the future resulted in reducing the time to design and implement.