Polestar
Service Partner Portal
As the UX Designer, I led the design efforts for this project, collaborating with a cross-functional team that included developers, product owners (PO), product area managers (PAM), and other stakeholders. Our mission was to build minimum viable products (MVPs) that we could iterate upon based on user testing and feedback from real-world settings. The focus was on creating a portal that would seamlessly integrate into the workflows of partner service points, ensuring usability and minimizing the learning curve.
Methods & Tools
User Research
Shadowed technicians and interviewed staff at various service points to understand the current workflows, processes, and pain points they experienced.
Usability Testing
Conducted tests with service partners at multiple locations, utilizing their direct feedback to shape further iterations.
Figma
Developed detailed wireframes and interactive prototypes for testing and iteration.
Discovery
The first phase of the project was on-site research. We visited several service points, including tire hotels and partner workshops, to observe technicians in their daily work environment. This ethnographic approach allowed us to gain first-hand insight into the existing tools and workflows used by the partners. Since many service partners already used systems they were familiar with, we aimed to design a portal that complemented these systems, creating a familiar interface that minimized the onboarding effort.
Use Cases
Our research informed the development of several critical use cases for the portal:
Design Requirements
Tire Migration Tracking
Provide transparency of tire delivery and storage processes.
Access to Guidelines and Manuals
Include easily accessible reference material for various services, allowing partners to quickly find the information they need.
Integration with Existing Systems
The portal should feel familiar, with interaction patterns that align with the systems that partners were already using.
Ideation
During ideation, we worked on finding the optimal way to balance information density with usability. The portal had to present a lot of critical data, but it was also important that the information be accessible and actionable for service partners without feeling overwhelmed.
We explored different layouts, navigation options, and interaction patterns to determine how best to structure workflows, such as tire tracking and scheduling. Wireframes and prototypes were built in Figma, and iterated on in close collaboration with both developers and stakeholders to ensure technical feasibility and alignment with business goals.
Sketches and Wireframes
To bring our ideas to life, we began with sketches that helped us visualize user flows and potential layouts for the portal. These sketches provided a rough structure for how key features like tire tracking, service scheduling, and manual access could be organized on the screen.
Low-Fidelity Wireframes
Once the sketches were validated internally, we moved on to low-fidelity wireframes using Figma. The wireframes mapped out the layout and structure of the portal, including:
Prototype
After finalizing the wireframes, we created an interactive prototype in Figma. This mid-fidelity prototype allowed us to simulate the user experience, focusing on key interactions such as:
The prototype was then tested internally, with stakeholders and a small group of service partners, to validate that the flow and structure were intuitive.
Collaborate and Iterate
Collaboration was key throughout this phase. We conducted regular design reviews with stakeholders, developers, and product owners to gather feedback on the prototypes. This feedback loop was crucial in helping us identify areas for improvement and ensure that the design aligned with the overall project goals
Key iterations included:
User flow
The design process for the portal was centered around understanding and improving the current operational flow between Polestar, service partners, and customers. Below is an illustration of the current service process flow, which was instrumental in shaping our design:
Process Flow
This overview provides a clear foundation for understanding the existing system that our portal aimed to optimize. Each stage of the current process was analyzed to identify inefficiencies and opportunities for improvement, resulting in features within the Service Partner Portal that would streamline interactions and automate repetitive tasks.
Collect Feedback
Throughout the testing process, we gathered qualitative feedback from the participants. We noted where users struggled, such as confusing navigation paths, unclear icons, or difficulties in finding specific information. In particular, service partners highlighted challenges related to accessing certain features within the tire tracking flow and the complexity of managing multiple service appointments simultaneously.
Users also provided positive feedback, particularly on features that simplified their workflow, such as the integrated dashboard overview and the ability to update service statuses in real time.
Analyze and Iterate
Based on the feedback gathered during usability testing, we conducted a thorough analysis to identify recurring issues and points of friction. Key insights included:
After analyzing the feedback, we iterated on the design to resolve these pain points:
Based on the final testing and iteration cycles, we polished the design to ensure a high level of usability and alignment with partner expectations. We created high-fidelity mockups in Figma that showcased the portal across different screens and states, including mobile and desktop views. This ensured that the solution was optimized for consistent user experience across various devices, providing seamless access to all features and services.