G.P.O

CLIENT

IBM - GPO App

Services

UI/UX

Team

Jackie Torres – UI/UX Designer
Martin Linhart — Product Owner

Miguel Batis — Project Manager

Date

January, 2023

G.P.O

CLIENT

IBM - GPO App

Services

UI/UX

Team

Jackie Torres – UI/UX Designer
Martin Linhart — Product Owner

Miguel Batis — Project Manager

Date

January, 2023

G.P.O

CLIENT

IBM - GPO App

Services

UI/UX

Team

Jackie Torres – UI/UX Designer
Martin Linhart — Product Owner

Miguel Batis — Project Manager

Date

January, 2023

The G.P.O. (Global Purchase Order) desktop application aims to streamline the purchase order management process by providing users with a seamless dashboard experience.

The application will enable users to review and create purchase orders from sellers, as well as manage customer profiles efficiently. G.P.O. will serve as a centralized platform for businesses to facilitate purchasing transactions and maintain customer records effectively.

The G.P.O. (Global Purchase Order) desktop application aims to streamline the purchase order management process by providing users with a seamless dashboard experience.

The application will enable users to review and create purchase orders from sellers, as well as manage customer profiles efficiently. G.P.O. will serve as a centralized platform for businesses to facilitate purchasing transactions and maintain customer records effectively.

The Challenge

The Challenge

The Challenge

The G.P.O. team used to rely on manual methods for managing purchase orders and customer profiles, leading to a lot of complications, by addressing these issues through the development of the G.P.O. desktop application, the aim is to provide users with a more efficient, organized, and user-friendly solution for managing purchase orders and customer profiles.

  • Design and development of a desktop application with a modern and intuitive user interface.

  • Integration of functionalities for creating, editing, and tracking purchase orders.

  • Implementation of features for managing customer profiles, including contact details and purchase history.

  • Integration of security measures to protect sensitive data and ensure compliance with regulations.

  • Testing and quality assurance to ensure the stability and reliability of the application.

  • Documentation and user training materials to facilitate adoption and usage of the application.

The G.P.O. team used to rely on manual methods for managing purchase orders and customer profiles, leading to a lot of complications, by addressing these issues through the development of the G.P.O. desktop application, the aim is to provide users with a more efficient, organized, and user-friendly solution for managing purchase orders and customer profiles.

  • Design and development of a desktop application with a modern and intuitive user interface.

  • Integration of functionalities for creating, editing, and tracking purchase orders.

  • Implementation of features for managing customer profiles, including contact details and purchase history.

  • Integration of security measures to protect sensitive data and ensure compliance with regulations.

  • Testing and quality assurance to ensure the stability and reliability of the application.

  • Documentation and user training materials to facilitate adoption and usage of the application.

The G.P.O. team used to rely on manual methods for managing purchase orders and customer profiles, leading to a lot of complications, by addressing these issues through the development of the G.P.O. desktop application, the aim is to provide users with a more efficient, organized, and user-friendly solution for managing purchase orders and customer profiles.

  • Design and development of a desktop application with a modern and intuitive user interface.

  • Integration of functionalities for creating, editing, and tracking purchase orders.

  • Implementation of features for managing customer profiles, including contact details and purchase history.

  • Integration of security measures to protect sensitive data and ensure compliance with regulations.

  • Testing and quality assurance to ensure the stability and reliability of the application.

  • Documentation and user training materials to facilitate adoption and usage of the application.

The Process

The Process

The Process

The Solution

The Solution

The Solution


User Research

Identifying the pain points of the users was crucial for the developing a creation of the solution. After research, these were the crucial pain-point findings:


  • Time-consuming manual processes: Users currently rely on manual methods for managing purchase orders and customer profiles,
    leading to inefficiencies and wasted time.

  • Disorganized data management: Without a centralized system, users struggle to keep track of purchase orders, customer information, and communication with sellers, resulting in data fragmentation and errors.

  • Lack of visibility and tracking: Users find it difficult to monitor the status of purchase orders or track interactions with sellers and customers, leading to delays and misunderstandings.


  • Security concerns: Users are concerned about the security of sensitive business and customer data, especially if it is stored across multiple platforms or managed using outdated methods.


  • Limited collaboration and communication: Users may struggle to collaborate effectively with team members, sellers, and customers, leading to miscommunication and delays in decision-making.




User Research

Identifying the pain points of the users was crucial for the developing a creation of the solution. After research, these were the crucial pain-point findings:


  • Time-consuming manual processes: Users currently rely on manual methods for managing purchase orders and customer profiles,
    leading to inefficiencies and wasted time.

  • Disorganized data management: Without a centralized system, users struggle to keep track of purchase orders, customer information, and communication with sellers, resulting in data fragmentation and errors.

  • Lack of visibility and tracking: Users find it difficult to monitor the status of purchase orders or track interactions with sellers and customers, leading to delays and misunderstandings.


  • Security concerns: Users are concerned about the security of sensitive business and customer data, especially if it is stored across multiple platforms or managed using outdated methods.


  • Limited collaboration and communication: Users may struggle to collaborate effectively with team members, sellers, and customers, leading to miscommunication and delays in decision-making.




User Research

Identifying the pain points of the users was crucial for the developing a creation of the solution. After research, these were the crucial pain-point findings:


  • Time-consuming manual processes: Users currently rely on manual methods for managing purchase orders and customer profiles,
    leading to inefficiencies and wasted time.

  • Disorganized data management: Without a centralized system, users struggle to keep track of purchase orders, customer information, and communication with sellers, resulting in data fragmentation and errors.

  • Lack of visibility and tracking: Users find it difficult to monitor the status of purchase orders or track interactions with sellers and customers, leading to delays and misunderstandings.


  • Security concerns: Users are concerned about the security of sensitive business and customer data, especially if it is stored across multiple platforms or managed using outdated methods.


  • Limited collaboration and communication: Users may struggle to collaborate effectively with team members, sellers, and customers, leading to miscommunication and delays in decision-making.



User Flow


We created a clear and logical product structure to ensure that information is organized in a logical manner;

Based on the testing results we performed several iterations, implementing changes to optimize the product and provide a more efficient user experience;
As a result, we developed a user flow that is easy to understand and meets the expectations and needs of the users.






Wireframing


Through wireframing, we're able to iterate on various design concepts and refine our interface based on user feedback and usability testing.

By starting with low-fidelity wireframes, we can quickly explore different layout options and user flows, making adjustments as needed before

moving on to higher-fidelity designs. This iterative approach allows us to fine-tune our design and address any usability issues early in

the development process.



Design System


The IBM Design Language is the visual expression of IBM’s brand, including color, type scale, the grid, and more. Carbon translates

the design language into code for building digital experiences. My roles here was to make sure we used and correctly implemented the design system,

as well as oversee the development phase to make sure the guidelines were followed.

Carbon provides two type sets that support both productive and expressive moments. Primarily, productive was designed for product and expressive was designed for web pages, but there are opportunities to blend contrasting moments to provide clarity through hierarchy, and elevate the overall experience. We provided the users the option to switch between light and dark mode in the dashboard page.


User Flow


We created a clear and logical product structure to ensure that information is organized in a logical manner;

Based on the testing results we performed several iterations, implementing changes to optimize the product and provide a more efficient user experience;
As a result, we developed a user flow that is easy to understand and meets the expectations and needs of the users.






Wireframing


Through wireframing, we're able to iterate on various design concepts and refine our interface based on user feedback and usability testing.

By starting with low-fidelity wireframes, we can quickly explore different layout options and user flows, making adjustments as needed before

moving on to higher-fidelity designs. This iterative approach allows us to fine-tune our design and address any usability issues early in

the development process.



Design System


The IBM Design Language is the visual expression of IBM’s brand, including color, type scale, the grid, and more. Carbon translates

the design language into code for building digital experiences. My roles here was to make sure we used and correctly implemented the design system,

as well as oversee the development phase to make sure the guidelines were followed.

Carbon provides two type sets that support both productive and expressive moments. Primarily, productive was designed for product and expressive was designed for web pages, but there are opportunities to blend contrasting moments to provide clarity through hierarchy, and elevate the overall experience. We provided the users the option to switch between light and dark mode in the dashboard page.


User Flow


We created a clear and logical product structure to ensure that information is organized in a logical manner;

Based on the testing results we performed several iterations, implementing changes to optimize the product and provide a more efficient user experience;
As a result, we developed a user flow that is easy to understand and meets the expectations and needs of the users.






Wireframing


Through wireframing, we're able to iterate on various design concepts and refine our interface based on user feedback and usability testing.

By starting with low-fidelity wireframes, we can quickly explore different layout options and user flows, making adjustments as needed before

moving on to higher-fidelity designs. This iterative approach allows us to fine-tune our design and address any usability issues early in

the development process.



Design System


The IBM Design Language is the visual expression of IBM’s brand, including color, type scale, the grid, and more. Carbon translates

the design language into code for building digital experiences. My roles here was to make sure we used and correctly implemented the design system,

as well as oversee the development phase to make sure the guidelines were followed.

Carbon provides two type sets that support both productive and expressive moments. Primarily, productive was designed for product and expressive was designed for web pages, but there are opportunities to blend contrasting moments to provide clarity through hierarchy, and elevate the overall experience. We provided the users the option to switch between light and dark mode in the dashboard page.


User Testing


After the visual design was completed, I tested the prototype with five representative users to see how user-friendly the application was. The test was conducted over Webex video calls; Here's an overview of our user testing process:


  • Objectives — Before conducting user testing, we establish clear objectives and goals that align with the overall objectives of the G.P.O. app. This includes identifying specific aspects of the app to be tested, such as usability, navigation, and feature functionality.


  • Test Participants — We selected test participants who represent our target user demographic, including purchasing managers, sales representatives, and administrators.

  • Test Scenarios — We create realistic scenarios and tasks that simulate typical user interactions with the G.P.O. app. These scenarios were designed to test specific features, workflows, and user journeys within the app, allowing us to identify areas for improvement.

  • User Testing Sessions — User testing sessions are conducted either in-person or remotely, depending on logistical considerations. During the sessions, participants are asked to complete the predefined tasks while verbalizing their thoughts, observations, and any difficulties encountered. This qualitative feedback provides valuable insights into the user experience and usability of the app.

  • Feedback and Observations — We documented observations and feedback gathered from user testing sessions, including both positive aspects and areas for improvement. This feedback included usability issues, navigation challenges, feature requests, and overall user satisfaction.

  • Analyze Results — We analyzed the feedback and observations collected during user testing to identify common themes, patterns, and trends. This analysis helped us prioritize areas for improvement and determine steps to address identified issues.

  • Iterate and improve — Based on the findings from user testing, we iteratively refine the design and functionality of the G.P.O. app. This involved

    making adjustments to the user interface, optimizing workflows, and addressing any usability issues identified during testing.

  • Incorporate Feedback — By incorporating user feedback early and often, we ensured that the app met the needs and expectations of our users. In summary, user testing was a fundamental part of our development process, allowing us to validate design decisions, identify usability issues, and iteratively improve the user experience based on real user feedback.