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>
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.
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.
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.
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.