top of page
Sarang
Shukla 

Kickstart Project

Background Research

A basic introduction about the CPO project was given to me and business process document with few screenshots of the old salesforce  application. After reading the documents i prepared my questions and emailed them to the BA, Project Manager and Product Owner. During our first call i asked questions about, user groups, their primary task what are the challenges they face with the current system to product owner as he himself is one of user (User Role - Supervisor) of the system. After having couple of discussions, I validated below pointers about the 'business problem' , with the product owner and kick started the project.

Proposed Solution
  • Personalised role specific dashboard.

  • A well defined Information Architecture.

  • Widgets for effective work distribution.

  • Online resource management system.

  • User and supplier communication through portal.

  • A separate application for supplier associates where they can view & process purchase orders.

After having the basic project understanding i came up with below target areas to that caters problem areas came out during discussions

  • Confusing System Navigation.

  • Poor Information Architecture.

  • No Personalisation.

Defining Problems

After having couple of meetings with stakeholders, i tried to sum up all the pain points on system level below are few of them.

  • No defined user role.

  • Scattered Information.

  • No data categorisation.

Defining Persona

I defined persona from user base to understand more about each type of users of the application

  • CPO Supervisor

  • CPO Associate

  • CPO Admin

CPO Team

  • Supplier Associate

Vendors

User Base
  • Primary User.
    Around 300 Organisational Employee CPO Team (Centralised Parts Ordering) who are responsible to create and maintain purchase order lifecycle end to end until the product gets delivered.

  • Secondary User.
    Supplier or Vendor these are the people who receive purchase order and process it. which include lot of coordination from generate invoice, requesting payment and delivering the order.

Stakeholder Interview
  • Lot of followup between supplier & CPO Team .

  • Hard to track documentation/notes .

  • Manager struggle to keep a track on associates activity.

  • Conflicts within team related to ownership of task and work assignment is tricky.

Since, product owner himself is one of the end user, So, I consider him as one of the primary stakeholder i got important insights on the end user pain points, ,different user roles in system, technical limitations and wht are the plan to over come in future etc.

 

Below are some of the main points came out of the discussion

Case Introduction

Project Vision

A modern style system which can improve productivity by assisting users in many ways to manage purchase order created in the system to buy trucks auto parts from different vendors.

About Client

Penske is one of the top 3 trucking company in USA and Canada which lease trucks to individuals and business as per the need.

The Design Problem

​Creating a robust ERP application which can provide a holistic experience to the Penske Parts Ordering team of 1800 associates and supervisors, where supervisors can manage the team and track individuals productivity and associates can create, manage and track payment of purchase order by following a defined process flow and to implement an effective communication channel with vendors. 

  • To understand and map the end to end lifecycle of purchase order.

  • To manage +5000 purchase orders and tasks efficiently.

  • There was no defined system flow and process was scattered all over (digitally and manually)

  • Managing the doc's and communication with +1000 suppliers on a daily basis.

My Role
My Team
  • UX/UI Design + BA Support.

  • Followed and enhanced design system.

  • Conducting UX grooming session before the start of each sprint with development and testing team.

  • Assisting BA in writing acceptance criteria of user story.

  • Defining the scope of user story.

  • UX Audit to make sure development meets the UX/UI standards prior to every client demo.

  • UX research , wire-framing, prototyping. Visual mockups following brand guidelines.

Design Delivery Lead (Myself)

Developers

Testers

Automation Tester

BA

1
1
3
6
1

Purchase Order Management

Increased 50% productivity by reducing the turn around time of purchase order completion life cycle. Migrated services from salesforce to a fully functional modern website to enhance the usability of web portal, developed holistic UX approach to effectively manage the purchase order of truck’s auto-parts for one of the top 3 truck leasing company in United States.

I started brainstorming session with BA and Product Owner and we went through the notes taken during the interviews and we started jotting down the user pain points and aims.  after the review session with clients i made few changes and we finalise the personas.

User
Persona

As is Journey
To be Journey

By collecting all the insights from the interview with the supervisor and with

some brainstorming with in the team i created  AS IS and TO BE Journey .

Customer Journey

By having multiple discussion with the product owner, i try to understand the daily task of the user and what are the critical steps in the process. Created the process flow and users flows to map down the "user and system decisions", "call to Actions", "Confirmation Popups" and how information will flow on different screen in a logical manner.

Flow
Diagrams

Created information architecture to have a clear understanding of navigation of the new system and to make sure user will have the right and important feature upfront, Assist user to achieve the task and find the right set of data without confusion.

Information
Architecture

I began the design process with low-fidelity sketches and wireframes to accelerate decision-making through visualisation without losing time. My sketches were based on the initial user interviews, the business goal, and the heuristic evaluation. After couple of iterations and design review we finalise the IA user flow and wireframes.

Wireframs

  • Since it was ERP system and clients wanted to see more data, I created 16 column layout grid to accommodate information and data in a minimal way.

  • Enhanced and maintained design system.

  • Followed PrimeNG UI Library Kit

Design System

Followed and enhanced the design system as per style guidelines

After couple of wireframe iterations we finalised the logical flow and I proceeded with UI design the final screens in Figma, by following the brand guidelines and the design system.

Visual Design

Usability Testing

Conducted usability testing at every stage on Figma prototype, followed by a testing session with the selected users on developed application before the MVP release with parts ordering team and vendors to get the user insights and to find the usability problem if any. 

1. Defining Tasks
2. Facilitate
4. Test Report
3. Observe

I prepared a set of task based question that covers major use cases to complete the purchase order. 

Participants were briefed about the test and sessions were recorded with their consent. Scenarios were given to observe.

During the sessions navigation, content, presentation & interactions of the user with application were thoroughly observed.

Created the final UT Report that consists of findings, observations, recommendation and the level of severity.

Usability Testing Process
Participant Segmentation

Associates

Potential

8

Vendors

3

Novince

Supervisors

5

Experts

Government Digital Services

B2B & B2C

2019 

GDS

EV Charging Station Monitoring

Product Design

2022 - 2023

B2B 

App To Control Eye Mask

A digital campaign to raise funds in-order to continue research and to build an eye-wear product which can cure seasonal affective disorder by improving sleep quality.

Website for marketing and raising funds to build the product.

B2C

2023

Product Design

View Other Case Studies

Mapping With Design Process

MATARIALISE
EXPLORE
UNDERSTAND

Empathise

Business Goal

& Requirenment

Problem

Statement

Stakeholder 

Interview

Competitive 

Benchmarking

Define

Information

Architecture

Pain Points

 & User Aims

Persona and

user Journey

User Flow

& Task Flow

Ideate

Paper Sketch/

LowFie Wireframe

Highfie

Wireframe

Design 

Iteration

User

Testing

Prototype

Functional

Prototype

Visual

Design

Design System

Visual Assets

Mockups / Design Documentation

Test

Design Iterations

for Improvements

Design

Discussion

User Testing

& AB Testing

Feedback

Analysis

Impliment

DevGromming Session

UX/UI Audit of Development

Development

Support

Design Asset

Preparation

bottom of page