Supply Chain Marketplace
Problem Context
Currently this organization had 15 existing tools in usage by various members of the Supply Chain (SC) ecosystem and were adding more solutions to their toolkit.
Current Limitations
1. Numerous tools and non-standard KPIs across different functions, regions, and segments. Each solution is executed in silo despite overlaps
2. Different personas are not being addressed with specific level of insights
For example: It takes time for a Director level person to navigate through the solutions and dig out the relevant insights
3. Language currently used in the tools is often complex and hard to understand, thus misleading the users.
VP Global Supply
"I love it! Assuming money is not a problem, when can I start using it?"
Europe, SC Director
"This fulfills everything I asked for. The experience is very simple and intuitive yet the information is comprehensive.."
Head of Advanced Analytics
"The team was incredibly collaborative and I learnt how to think design, which was a great learning experience as well."
My role and learnings
In this project I was wearing multiple hats - Project manager (for the first month), Design Lead and Sr. Design Researcher. I was collaborating with three UI designers, the domain (SC) expert as well as the tech team (Senior Engineer + DevOps) for feasibility checks.
My biggest learning was to create an environment which was built on trust, constant communication and sharing of different perspectives across the team (internal +client). This helped create ownership of various components in the process as well as stakeholders becoming champions of the solution proposed.
Through this project I learnt the importance of scoping. The number of people allocation from team (domain, tech, design) were understaffed which led to bottle necks and minor delays which could have been avoided.
For example, we initially scoped the project for 1 UX designer and did not include any tech experts. By the time we were in the first week of the design phase, we quickly realized our error and added 2 more UI/UX designers to the team and 2 data engineers to help check the feasibility of the solution.