GoCashmere

Gocashmere's information architecture is very similar to Repeat. We had agreed to re-use the same backend logic to save time and focus our efforts on marketing strategies. Besides the style changes, here are the main differences:
‍
First is the Landing Page. I've changed the structure to match a different intention. Since Go is a new brand, it should focus more in creating trust than pushing products to our visitors. The hero section will have prominent brand introduction video followed by some reels. Only then we'll we introduce the collections.
‍
The second is navigation. Since there will only be 30 products under five categories. I've suggested removing the category dropdown and inserting the categories into the navigation bar instead. It gives the visitors a better scope of what products are available. It also saves them one interaction when they want to access a category. It's crucial to lessen the number of steps and simplify the experience to improve engagement.
‍
The third is the banner design. We needed an early idea on how banners might look later on. Earlier on the project, the client described each product having one landscape photo. I wanted to utilise these and  proposed a multi-angle banner to showcase more of the product in a single viewing.

‍

After the design handoff, I created a brand guideline to ensure consistency throughout the front-end implementation. With the Project Manager, we've briefed the developers on the guidelines, the sequence of development, and the various page interactions. It's easier this time since Go's website architecture is similar to Repeat's. We just had to focus on key pages and style changes. Afterwards, I've created a separate Figma file for the corrections. Let's just say I've pissed off a couple of front-end developers that week *cries*.

‍

The photo shoot finished when the designs were handed to our developers. It ended up having 118 unique products that had seven images each. I was responsible to device a plan for sorting them out and creating a file system.
‍
I needed a way to work with Repeat's Creative Director and their Lead Designer. The photos will need to be spread out for easier comparison. Labels should also be accessible on the fly for easier tagging.
‍
Image sorting requirements:
- Sort for image carousel on product listing page.
- Sort images for social media use.
- Sort images for website banner use.
‍
I created a Figma file with the photos grouped per unique item. I added three indicators to present the three sort requirements. Since we're screen sharing for sorting, I arranged the images in a grid of 5 for optimal viewing on our screen dimension. We ended up spending only 3 hours going through every product. The clients were also stress-free afterward!

‍