Zwilling.com
Uniting a range of culinary brands into one brand, transforming e-commerce experience in 22 languages around the world connecting people with Zwilling

+50,000

New users within 3 months

52%

Increase in US sales

20.8%

Unique visitors

6.9%

Average order amounts up

34.9%

Increase in mobile users

21.5%

Increase in mobile conversions



Role: Lead Experience Designer
The Challenge

A full-scale digital transformation as one of the world’s oldest and most adored brands, Zwilling was in need of a full-scale digital transformation to bring together its deep history and impressive offering, with an emphasis on experience – to have the innovation of their products realized in their digital presence.

The Solution

Integrating brand and commerce into one compelling story, Isobar focused the entire strategy around the customer experience while keeping Zwilling’s rich history at the center of all executions, simultaneously bringing them into the 21st century. Using Salesforce Multi-Cloud Isobar led the experience design, creative, implementation and optimization of the new .com site for a global rollout across many countries and many languages.



Source: stats and vid stolen from agency site
Process and Deliverables

One go-to-place for design review, client approval, and asset hand-off. One of my responsibilities on this project was to support the Associate ESD Dir. creating a new delivery platform that housed everything related to the project with low effort.

So we created a destination where everything from workshop take-aways, IA, CX maps, initial wireframes, visual exploration, and final annotated visual design were published within a simple site structure.

This became the single source of truth, no more links in emails, messy dropbox folders, “v4-final-final-final.fileformat”. Etc.

It became a process and platform other projects at the agency adapted while allowing every project to make changes based on the specific project needs. In many ways I regard this as one of the big wins for this project.

“So nice that we just need to go to the same link every time...”
Primary focus

As the experience vision had been established with the client before my onboarding, I had the liberty to focus deeply on the interaction design of my primary focus areas.

This allowed me to collaborate closely with the visual designer and move fluidly from known requirements, design exploration, and prototyping when needed.

Different methods were applied to the different focus areas, eg. client workshop with analytics and wireframes for navigation, and prototyping with visual design assets for the buy button's "sticky behavior" on mobile.

Leading the design of
— Navigation

— Product Detail Page

— Cart & Checkout

— Account Page
Working With a Commerce Platform

Since the E-commerce system was Salesforce Commerce Cloud documentation were already existing, so a part of the work was identifying what out-of-the-box features to use and where to customize.

Work was carried out as a tight-knit team collaborating across strategy, copy, visual design, and experience design disciplines with client involvement twice a week.

The experience design role facilitated the conversations together with the team leading to client consensus.

In the interest of time we followed three steps
1

Assess the CMS documentation and understand the out-of-the-box features and share with the broader team.


2

Create quick sketches and sometimes lo-fi wireframes to use in conversation with team and client to establish consensus on when, where, and why to customize the e-com experience.


3

Super close collaboration with visual design since detailed wireframes were sometimes skipped in the interest of time. When visual design was signed off, the next key deliverable was annotated visuals so the off-shore dev team had proper documentation to use (see samples below).


This fast paced process was something I really enjoyed as it allowed me to move quickly between conversations & sketches to prototypes using the visual design assets.

Work Samples

Documenting consensus for client, dev. team, and QA.