Smarter Warehouse Yard Management solutions for Logistics

The primary stakeholder for this project was the Product Manager, who served as the main point of contact. Collaboration was smooth and effective, with frequent exchanges to keep the project aligned with user needs and product goals.

The Product Manager played a pivotal role in providing user insights based on webinars with potential customers, which informed the iterative changes in my designs.

Instead of having meetings, sometimes we used “Loom” recordings to each other, which saved a lot of time.

We knew the target audiences for this project. But we used “Jobs to be done” approach. And also listed out tasks which are essential for them in their everyday life. This approach works better, as we plan operations and jobs they have to do, to make it easier for them.

At first we drew assumptions about what they have to do. With confirmation later on from the research.

Throughout the project, to understand the journey, the flows we have to do. We used user flows for each feature, before doing any wireframes or design work. This approach helped us to understand logic, areas of improvement and how to make easier for people to complete their task.

Most of the work went into Wireframes stage. Since developers already had components in their front end from last projects, I could do wireframes and they implemented with their own. This approach was faster to launch, since time was sensitive. Also working on new kind of product from scratch, wireframes solution seems more efficient. UI work was planned sometime in the future.

In terms of development and consistency, improvements were suggested gradually in separate stages. Requirement was to keep it simple, as for this type of business user, interface has to be clean without “fireworks”.

However it was not sure when suggestions were supposed to be implemented, since it is built on Bootstrap and there was ongoing more important work at at a time for developers.

In order to keep track of components with development and new upcoming changes. I did audits of existing system, plus how my designs were implemented. This helped to communicate and be on the same page with everyone. To ensure implementation is good.

Developers are busy with their own ongoing tasks and forget previous implementations. After these audits with POs were added to roadmap to match with wireframes.

User testing played a crucial role in shaping the final solution. Many changes to the project were directly based on user feedback gathered during testing sessions. Additionally, the Product Manager conducted webinars with potential customers, using my prototypes to present our ideas. The insights from these webinars were invaluable in refining our approach.

Also we used prototype analytics to see how fast they are going and which areas they take time to think. The only thing we could have done better here - test even more. This product needed extensive data and testing. The user base was specific.

For smooth components handoff I created “One source of truth”. Components library where developer can take a look, and if any updates are made they are reflected there. Comprehensive library helps to maintain consistency and have overview of all components being made at one place.

For the styles, matching icons and re-usable components were created. In order to keep track of consistency. To ensure scalability of product line, I started by re-creating existing components from other areas of GoRamp and later on improved upon.