Case Study 02

ERP system
for EDDE

Research and Design for Order management ERP system for EDDE

Introduction

Edde is a Southeast Asian company focused on providing high-quality electric motorcycles with a full end-to-end ownership journey. They aim to make electric mobility more accessible, convenient, and affordable for the region.

Industry

Electric Smart Mobility

Client

Edde 🇸🇬 🇮🇩

Project Type

User Research, Product Design, UX

Roles

Researcher, Designer

Tools

Project Overview

This project involved Creating ERP application for EDDE Smart Mobility, a company that offers a range of bikes and scooters for purchase through their mobile app and Showrooms in Indonesia. The aim of the project was to create a comprehensive internal ERP system to manage all bike orders, including customization options such as seat and body colors, different brands, floor boards, and helmet options. The project was completed over an eight-week period and involved four main parties: the product designer (myself), the product specialist, the product manager, and the development team.

Different modules of the ERP order management solution

UX Design Process

Employing a design thinking approach, the UX design process for this
project can be broken down into various stages.

Stage 1: Empathise

We started by understanding the project requirements and user needs. Through discussions with the product manager, testing the products, and analyzing the project roadmap, we gained a good grasp of the project’s complexities. Visual diagrams helped us see how the supply chain and user interactions worked.
User Groups
Given the project’s internal usage scope and the need to optimize resources, proto personas were developed based on initial assumptions. These personas will be validated in subsequent stages rather than conducting an exhaustive user research process. Below are the crafted personas for each user group:

User personas

Problem Validation

The subsequent step involved validating the created personas by engaging real users from each identified user group. Feedback was collected to prioritize issues, and a template was utilized to document users’ responses. The feedback from a representative individual in each user group was analyzed to identify the core problems that needed to be addressed in the application’s initial stage.

Stage 2: Define

Upon analyzing the collected data, we created a list of problems that needed attention. Carefully prioritizing these issues, we identified 8 key problems to be solved in this app.

To be solved list

Upon analyzing the collected data, we created a list of problems that needed attention. Carefully prioritizing these issues, we identified 8 key problems to be solved in this app.

Stage 3: Ideate

Solution Blueprint

To address these problems, we brainstormed and developed a solution blueprint after going through various ideas from team members:

And address the 8 problems on the to be solved list as follow

  1. Customer Details Recording:
    We will implement a user-friendly form for capturing essential customer information during the selling order process.
  2. Order Approval Process:
    To prevent errors, each selling order will require approval from the store manager before finalization.
  3. Sales Tracking:
    We will record all sales, including the salesperson’s name, to monitor performance and individual contributions.
  4. Detailed Sales Dashboard:
    A comprehensive dashboard will allow users to filter and analyze sales data for data-driven decision-making.
  5. App Accessibility Anywhere:
    The app will be internet-based, enabling users to access it remotely, reducing security concerns.
  6. Purchase Order Requests via App:
    Storekeepers can conveniently request purchasing orders directly through the app, eliminating the need for phone calls.
  7. Centralized Orders and Stocks Management:
    All inventory data will be centralized, facilitating efficient combined purchasing from suppliers.
  8. Accurate Employee Responsibilities:
    Distinct user role types will be established to assign responsibilities accurately, controlled by HR managers.

Stage 4: Prototype

Wireframing

The major app screens have been prototyped at the component level, ensuring a streamlined, user-friendly design. These images offer a clear visual representation of each screen, allowing for a detailed examination of individual components.

Key Screens in the Prototype

Login

The login flow is designed to be seamless and user-friendly, with clear instructions. Users will be allocated by HR personnel for their designated duties.

Login

Dashboard

The homescreen of the app has been designed with a minimalist approach, addressing problems 4 and 7. It provides users with a visualized summary of the inventory and guides them according to their position.
Dashboard

Orders

The order list displays all bike sales, filterable with different conditions. It also tracks the salesperson’s performance, addressing problem 3.
Orders

Order Details

Users can easily edit order details on this screen
Orders

Sales Order

This screen records customer and order details, which are sent for approval from the store manager, solving problems 1 and 2.
Orders

Order Approval

After creation, the order will be reviewed by the showroom manager, allowing for resubmission if rejected
Orders

Create and maintain user roles

This section is exclusively designed for the HR manager or company management responsible for allocating users to their respective duties. Here, they have the authority to add or remove users, manage login details, and activate user accounts, among other related tasks.
Orders

Prototyping the Screens

The major app screens have been prototyped at the component level, ensuring a streamlined, user-friendly design. These images offer a clear visual representation of each screen, allowing for a detailed examination of individual components.

Stage 5: Testing

Testing & Implementation

Once the prototype was finalised, the development team started implementing the design. We provided them with detailed design specifications, which included every interaction, layout, and component used in the prototype. Throughout the implementation phase, we held weekly meetings with the development team to discuss any issues that arose, and we made sure to test the system regularly.

As the implementation phase neared its end, we conducted a series of user tests to ensure that the system met the users’ needs and expectations. We invited a group of employees to test the system and provide feedback on their experience. We made changes to the design based on their feedback and retested until we were confident that the system was ready for launch.

Launch and Post-Launch

The system was launched successfully, and we monitored its performance closely to ensure that there were no issues. We also conducted a post-launch review to gather feedback from users and identify areas for improvement. We made a few small changes based on this feedback, but overall the system was well-received by users.

One of the main benefits of the new ERP system was the increased efficiency and accuracy in managing orders. The system allowed users to track orders from start to finish, which reduced errors and delays. The system also provided real-time inventory information, which helped users make better decisions and avoid stockouts.

Conclusion

Overall, this project was a great success. By following the UX process, we were able to create an ERP system that met the needs of Edde’s employees and improved the efficiency of their supply chain. The project demonstrated the importance of user research and testing in creating a product that meets users’ needs and expectations.