Crowdsourcing Supply Chain Transparency
My Role
UX/UI Designer
Project Manager
Team
UX Designer - Christian Marschner
UX Designer - Ori Nevares
Skills
UI/UX Design
Project Management
Cross Team Collaboration
Results
• e2e ideation, prototyping, and testing of critical customer request to facilitate data sharing amongst the worlds largest chemical producers.
• User centred leadership amongst cross-functional product team
Timeline
Mar 2022 - Jun 2022 (4 mos)
Preview
A portal to request and share industry material data to collaboratively understand the worlds supply chains.
1
Blockchain Mass Balance
Leveraging blockchain to create digital twins of companies materials and improve supply chain transparency.
2
Request Missing Data
Companies can request material data from others to understand their full products lifecycle and environmental impact.
3
Collaborative Transparency
All sharing records are added to the blockchain ledger helping to illuminate the worlds supply chain and improve our environmental impact.
The Design Process
Background
Greentoken by SAP is an early stage startup within the companies incubator SAP.IO. The product leverages a blockchain ledger to act as a mass balance calculator to improve supply chain transparency and ensure environmental regulation is adhered to.
The Problem
Each company in a supply chain has valuable information about their materials, however, there is no channel for them to request and share this information with one another resulting in a gap in understanding.
The Goal
How might we help facilitate companies in sharing their unique material data with one another?
Our Approach
Stakeholder interviews and an inspiration board to inform a rapid ideation process and development handoff.
Stakeholder Interviews
1 hour semi-structured interviews were conducted to understand the current landscape and design requirements.
Inspiration Board
Similar existing patterns and design solutions were researched and gathered to inform our initial concepts.
Key Insights
The research data was synthesized and analyzed into themes which resulted 4 key insights informing the design direction.
Sensitive Data
Certain data is protected under patents or non-disclosure agreements so its visibility needs to be controlled.
Back and Forth
Data requests may require clarification and supporting communication so two way channels should be supported.
Multiple Requests
Users may need to request multiple data points and supply multiple data points. A request management area will be needed to organize all these options.
Supporting Information
Users may need to provide certification for the data requests so the ability to upload documents needs to be supported.
Concept Ideation
Initial ideas were mocked up in lo fidelity sketches with the following decisions building from the key insights.
Mid Fidelity
After an internal design team review the leading ideas were taken forward to mid-fidelity mockups and prepared for feedback from product management and development.
Design Solution
After a final client and product management review the prototypes were refined to high fidelity screens and prepared for development handoff.
Development Handoff
Final screens were assembled, annotated, and prototyped to support development.
Impact
3
Key Customers Retained
We were able to research, design, test and implement this complex e2e feature within 4 months resulting in the company retaining three essential customers.
#1
Feature Priority
This feature was essential functionality to help the company move towards its larger north star of creating a transparent and collaborative supply chain trace.
Reflections
Ownership Model
This feature did not have a Product Manager role like other features. This created a void for defining feature requirements and scope. This resulted in a vague understanding throughout the team and a lot of redundant design iterations based on adding and removing features. Identifying this scenario in the future and then leading alignment exercises would help alleviate the impact of this for future work.
Continuous Dev Collaboration
For this feature we knew who the assigned developer would be so we were able to involve them early in the ideation phases. This proved to be essential for a seamless development handoff as they had extensive knowledge of the features nuances since the start. Repeating this process in the future would be greatly beneficial.
Website design and content by Ori Nevares