Identifying Current Challenges + Solutions
The current website was live-coded and managed by a third party dev team. While this allowed lots of design flexibility, they had to be contacted whenever something needed updating and were far removed from our Design team’s daily work, processes, and information loops.
In using this system for years, it became clear that designers were spending too much time passing over assets, assessing design details that had already been stipulated during handoff, and waiting for revisions on incorrectly coded items. This inevitably caused delays and last-minute cramming to meet product and campaign launch deadlines.
Our proposed solution to the current (see below) process was a scalable, custom content building platform.
User Flow + Mapping
The Digital Art Director and Ecommerce team found a new Engineering/Development team to work with. We needed to present a clear picture to them so they’d have a strong understanding of our brand and goals.
We spent time documenting our challenges, prepared a full look at user paths + designs on the site, and laid out our desired outcome. We passed over existing use cases and assets so the new team could begin working through the build side and do testing before coming back to us with proposed components/modules.
Building the Design System
I assisted in the creation of necessary components, modules, and templates. I participated in many meetings with our teams in which we’d go over functionalities and how pieces were stacking on each other within the system. The meetings helped progress our wireframes and designs - we’d learn why the Devs made specific choices and give feedback on their UX/design effectiveness. This helped us iterate on structure and details to accommodate all our use cases.
With my in-depth knowledge of the subjects, I provided guidance on responsive/grid design + asset management. This allowed for all of the aspects we wanted included to be called out; the Devs/Engineers were well aware of our main goals and knew how to create many functionalities, but as expected, there were certain details that were clearer to our Design team.
For example, component + module positioning was built by applying a percentage option for both the X + Y axes so horizontal and vertical alignment could be adjusted to precise positions. While this would perhaps be useful in edge cases, we typically only needed right, left, or center alignment and consistency across breakpoints. A percentage changed visually across device sizes, so this option proved too customizable for most cases - we requested the addition of a right, left, and center quick-align option.
Reviews
We went through many review cycles - after Design + Dev had their conversations, we’d meet with the Ecommerce team for feedback on our decisions from a product/merchandizing perspective. It was occasionally challenging to get things aligned from all three angles, but constant collaboration allowed us to resolve these issues.
After months of testing and revising low-fi/hi-fi mock pages within Page Designer, we got the platform to launch-ready place. We’d learned a lot about how to create bespoke-looking pages that were simplified for an easy-to-use shopping experience.
Building the Landing Pages
I was asked to take on the Lead role of Primary Page Builder. Since I’d been close to both the design and build side of the project, we felt it would be most beneficial for me to manage this stage in order to: 1. suggest any updates to be implemented prior to launch and 2. gain a holistic view of the design process so I could eventually onboard others. It was undetermined who would be responsible for the page building role going forward since our designers had full workloads and someone else might be asked to join to handle this.
I built 13 product category landing pages from scratch in Page Designer, all for the January 2021 collection launch. There was a bit of a learning curve even though I’d spent so much time working through these designs - it felt different to make full pages with more complex UI than in our testing.
I gained an appreciation for the level of detail that was put into our project - although I’d used the builder many times at this point, it was a new experience using it solely to produce a clear, visually complete page that foundationally matched the desired design.
I had the background knowledge of how this had all been built, but tried to also view this through the lens of someone who was tasked with solely building a page to match a Figma design file they’d been given. This gave me insight into simplifications to reduce confusion and visual overwhelm when using the platform.