sushizo-splash.jpg

Sushi Zo

Sushi Zo Website Redesign

sushizo-home.jpg

Brief

Sushi Zo Website. Making it intuitive to use, modernized, and aesthetically pleasing. For this project, I collaborated with a team of 4 UX designers and 4 developers to create a new website for the Sushi Zo company.

Our solution was this cleaner and elegant, responsive version of the Sushi Zo website!



 

 
 

Client

Sushi Zo

Responsibilities

Feature Prioritization, Low-Fidelity Sketches, High-Fidelity Wireframes & Prototype, UI Specifications Document, Presentation ( 2 Weeks project )

Tools

Sketch, InVision, Trello, Slack, Keynote, Google Drive

 
 

 
 

Role

Lead Product Designer/ Scrum Master

For this project, we had a team of 4 designers and 4 developers over the course of 2 weeks. As the lead product designer for this project, I focused on the desktop experience, with another designer on my team taking the lead on the mobile experience. As scrum master, I ran our working sessions with the developers, ensured deadlines were met, and managed all communication between the two teams. 

Scope

The Sushi Zo website redesign was an exercise in branding and UI redesign. For this engagement, we did not go through an entire UX process from soup to nuts. Instead, we focused on following design best practices and simplifying Sushi Zo's digital presence. We held a design studio with the developers so that they could experience the design process more fully and so that we could incorporate their feedback into the designs. 

What we did.


My team and I redesigned the website for Sushi Zo and updated the branding. We took their website and simplified the user experience, making the website easier to navigate and understand. We made our updated version mobile responsive. 

 
 

 

Inspiration

Sushi-Zo.png
 

 

The Handoff

To ensure that our developers had all of the information that they needed, we created a style guide and uploaded all of our screens into Zeplin. Within Zeplin, we were able to add extra information, such as intended animations, links, and comments. This gave our developers a trusted source for all information.

Key Learnings

This project highlighted the value of clear communication and setting roles and responsibilities from the outset of a project. While it was awesome to include the developers in our design studio, and have them see first-hand what happens when designers start a project, it immediately became apparent that the design team needed to explain the intended goal of design studio and how the many ideas that get generated get combined to become a singular set of screens.

 
 

Zeplin Styleguide shared with developers