Manufacturing

Materials Handling

YEar

2022-23

timeline

18 months

Team role

Design Lead

Designing a digital experience for managing materials handling equipment

The purpose of this project was to work with the client in analyzing their existing processes and content, and transferring it to a digital experience that informs customers. To do this, we designed and built an ecosystem of products that guides them from learning, to purchasing, to tracking and servicing equipment. This client had all of the data and content available - we just needed to organize and display it into a better digital experience.

Activities / deliverables

Staffing

Current State Assessment

User Interviews

Feature Prioritization

App Flows

Wireframes

Design System

Mockups

User Stories

Accessibility Documentation

User Testing

Design QA

Getting started

Thinking of a master plan

Teamwork
Staffing

Once the team began to expand, I began interviewing possible candidates. It was important to find designers that were not only best for the job, but best for each other as well. I carefully listened to each designer's past experiences, their strengths and the areas in which they were interested in growing. Then followed a small game of musical chairs as I reorganized talent into the roles that made the most sense for the success of the project. Each designer also had the opportunity to support in areas they were looking to grow, and take on leadership responsibilities as they established best practices within their areas of expertise.

Team org structure
Conceptualization
Experience Flows

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Concept Sketches

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Design System
Planning

Creating a design system for two workstreams meant constant communication between both design teams as well as getting approval on token updates by stakeholders. Even the smallest change to a molecule must be discussed to determine if it was an update to existing element or a snowflake.

Scalable Components

A shared atomic design system for multiple products is no easy feat, but it must be done. This particular design system required thoughtful execution and consistent communication across workstreams that would be using it.

Design System elements defined for two workstreams
Developer Documentation

We worked closely with our product team to capture user stories and acceptance criteria in Azure DevOps, and we added more annotations in Figma to ensure developers understood the intent of each component, interaction and screen.

Example of annotations for a single component

lessons learned

Key Takeaways

I can't be everything for everyone.

Creating a collaborative culture for designers to learn from each other rather gives everyone some autonomy over the process.

Governance can make or break your system.

All of our hard work means nothing if it is not maintained once the engagement ends. Discuss this early on.

Different time zones are not so bad.

Sometimes working early/late hours is necessary to build a connected team and a cohesive product.

Other projects

Only moms and stalkers scroll this far...

+ go back home +