- A data exchange platform for supply chains

Building trust in risk data by enhancing visibility across the world's most complex supply chains.

Role: Product Designer, leading the end-to-end process to achieve my product team's goals. Part responsibility for a consistent platform with the other designers.

Product team: Linking (Synergy), responsible for the accurate Data exchange between members.

Primary tools: Figma, UserTesting, Dovetail, Miro, Jira, Confluence, Google Analytics.

Other tools: Qualtrics, Hotjar, Thoughtspot, Confluence, Intercom.

Timeframe: May 2022 - July 2024

Skip to section:

01 - Introduction

What is Sedex?

Sedex is a global leader in supply chain data exchange, empowering businesses to make responsible and ethical decisions by providing transparency into supplier networks. The platform focuses on enabling retailers and suppliers to assess risks and ensure compliance, offering critical insights into Environmental, Social, and Governance (ESG) metrics. With a growing user base and increasing complexities in supply chains, Sedex faced challenges in scaling its capabilities.

Problem Highlight

Sedex faced a major challenge in managing the growing complexity of supplier networks, which led to difficulties in navigation, data management, and maintaining effective communication across the platform. Users were struggling with inefficient visibility controls, cumbersome navigation, and outdated systems that failed to keep up with their needs. Our goal was to resolve these issues by creating a more intuitive, scalable platform that enhanced data visibility, improved workflows, and ultimately simplified the user experience.

Our goal

Our goal was to create a more intuitive and scalable platform, enhancing data visibility, improving navigation, and enabling more informed decision-making.

02 - The Challenge

Navigating Complexity and Improving Data Management

To familiarise myself with the platform and understand the journeys within my product team, I mapped out the entire new platform. This exercise provided a clear visual overview of the platform’s structure, highlighting key user interactions and potential areas for improvement.

The complexity of Sedex's user base was growing significantly. As more businesses joined the platform, the task of managing intricate supplier networks became more overwhelming for users. Our user research identified several pain points:

Initial findings

These challenges drove the redesign efforts, aiming to build a more user-centric, efficient, and flexible system.

03 - Discovery Phase

Extracting User Insights and Internal Expertise

The project kicked off with a deep discovery phase to ensure our redesign was firmly grounded in user needs. This included comprehensive user research activities designed to understand the intricacies of managing expanding supply chain networks. The key methods included:

The outcome of this discovery phase was a detailed problem statement, focusing on the need for more efficient navigation, better data management tools, and clear, scalable interfaces.

Research & Data Analysis

We took a blended approach of qualitative and quantitative research to validate our initial findings and inform the design direction:

Improtant Insights

Together, these insights demonstrated a need for more intuitive navigation, efficient visibility controls, better communication tools, and a scalable interface design to handle complex supply networks effectively. These guided the development of the three core design concepts to streamline and enhance the user experience.

04 - Concept Development

Simplifying Complexity

Before starting with wireframes, we focused on mapping out the early-stage user journeys and defining the "happy paths" for key user interactions. This phase was heavily influenced by the insights gathered during our research and discovery process. We used our understanding of user pain points, preferences, and behaviours to identify the most critical tasks and ensure each journey addressed users' core needs.

After mapping out early-stage user journeys and happy paths, guided by our research insights, I began sketching initial concepts aimed at addressing key user challenges. Once these concepts were drafted, I collaborated with the team to shortlist the ideas that seemed most promising in solving the identified issues. We chose the strongest concepts to move forward with and planned to validate them during our annual Sedex conference, where we could experiment and gather feedback from live members in real time, ensuring that our proposed solutions were tested directly with the end users in a realistic setting.

The insights from our research and discovery highlighted three core problems faced by users managing complex supplier relationships, lack of efficient data visibility, and difficulty navigating the existing outdated interface. To address these issues, I prototyped three key concepts—Tube Map, Tree List, and Supply Chain Top Sheet—each aimed at solving specific pain points:

Concepts validation

After gathering feedback from live testing and in-person research, we observed that preferences were split between two main visual approaches. This led us to rethink how to integrate the strengths of both designs into a cohesive solution.

Linear Version (Tube map):

Tree View Version:

05 - Tree View Concept

Evolved into Tree List

We began by mapping out the existing user journeys to identify areas where users experienced friction—often referred to as "unhappy paths." These paths revealed key pain points, such as difficulties in navigating large supplier networks and confusion about hierarchical relationships among suppliers. Understanding these challenges allowed us to pinpoint opportunities to significantly improve the user experience.

To ensure that our approach was feasible from both a design and technical perspective, we worked closely with the development team before diving into design sketches. Together, we conducted data architecture exercises to help developers understand the existing data structure, which played a crucial role in how we planned to integrate new designs seamlessly. This close collaboration ensured that the technical and design teams were fully aligned on requirements from the start.

We also created user stories to make sure we were considering the user experience in a holistic manner. These user stories described tasks from the user’s point of view and helped ensure that every feature and design decision was guided by real user needs and intended behaviours.

With user insights and technical understanding, I sketched concepts to address the identified pain points. After multiple iterations, we reached a final design that balanced user needs with platform capabilities, resulting in the Tree View—a hierarchical visualization that organized complex supplier relationships in an approachable way.

Validating the Tree List concept

As we moved into testing, feedback indicated that users needed even greater control and flexibility when navigating their networks. They wanted the ability to easily move between a high-level overview and specific details. In response, the Tree View evolved into the Tree List—a more dynamic and flexible version that allowed users to expand or collapse different nodes, providing both broad overviews and in-depth information when needed.

Our rapid iteration process involved close collaboration with developers to use Material UI components, ensuring we could move quickly without sacrificing quality. These development exercises, paired with user story mapping, were instrumental in aligning the entire team to deliver a design solution that addressed user needs while being technically practical to implement.

Metrics of Success:

06 - Tube Map Concept

Evolved into Link Summary Page

The reason for developing the Tube Map Concept was to give users the opportunity to zoom into more detailed data about their supply chain. From the full network shown in the Tree List, we wanted to enable users to dive deeper into specific supply pathways, allowing them to see the detailed data they needed to understand and take action on.

The Tube Map provided a high-level visualisation inspired by transport maps, helping users understand how goods flowed across their supply chain. This approach was effective in simplifying complex, multi-layered relationships into a more digestible form, making it easier for users to grasp the overall structure.

How did we come to this conclusion?

As we gathered feedback, it became clear that users needed both this broader overview and the ability to manage specific details of individual relationships. This insight led to the evolution of the Tube Map into the Link Summary Page, which allowed users to focus on individual supplier connections and manage data visibility more effectively.

We followed the same iterative process as the Tree List concept to refine and validate the Link Summary Page. This approach ensured that the final design was both user-friendly and aligned with technical requirements.

Metrics of Success:

07 - Growing the Design System

Contributing to the Larger Ecosystem

With this project, I advocated for the use of atomic components in our Design System and Storybook libraries. This approach ensured that the components we created were modular, reusable, and adaptable, benefiting both current and future projects.

I also led efforts to train the team about design tokens and semantic tokens, helping them understand how these tokens could create a more flexible and consistent design system. By introducing tokens, we laid the foundation for a more scalable and adaptive approach to maintaining and extending the visual language of our platform.

The components designed for the Tree List and Link Summary Page were incorporated into Sedex’s broader design system:

  • Reusable Components: These new elements enriched the Components Library, providing a foundation for future projects across the product teams. This helped create consistency in the platform and allowed other teams to build on a unified design language.

Outcome:

08 - Key Results and Impact

Metrics that Matter

The redesign significantly enhanced user experience and improved overall efficiency across the platform. Our key metrics and performance indicators (KPIs) included:

09 - Key Takeaways

What did I lear?

The team

What disciplines did I collaborate with? Notable mentions:

Adding to the previously introduced members, we also have those working in multiple teams who've made noteworthy contributions to Synergy.

Our team has experienced changes in personnel over the course of the project. Some members have left, while others have joined during this time.

Thank you!

LinkedInDribblevaggosdesign@gmail.com

©Evangelos Angelis ️