top of page

RollKall Invoicing

Project Overview

In this project, I will guide you through my process of designing RollKall's new invoices. The goal of this project is to create a new invoice with streamlined features, improved UI, and fewer steps for coordinators to send multiple invoices in one session.

Responsibilities: 

  • UX Research (interviews and heuristic evaluation)

  • UX Design (user flow and usability testing)

  • UI Design (high fidelity mockups)

Role: Lead Designer

Length of project: 8 weeks

Company: RollKall

EMPATHY

Imagine going to a grocery store to buy a red and a green apple, but the red apple is on one side of the store and the green apple is on the other. When you go to pay, you have to use cash for the red apple and a credit card for the green one. It's frustrating and inconvenient, right? That is an analogy of what t coordinators are feeling when using RollKall's invoicing,

Project Brief

Currently, the RollKall platform offers two types of invoices; while they differ in features, they share the same goal of being sent to the client and paid for. Sending invoices has been a frustrating and time consuming process for our LEA coordinators and this invoicing framework causes issues internally at RollKall. 

DISCOVERY

User interviews, User Persona, Heuristic Evaluation

RollKall's invoicing issues have been known, they just haven't been fixed, so I needed to find ways to improve it. This started with gathering user feedback. Based on user interviews, identifying the personas and conducting a heuristic evaluation I was able to gain insights to the following research objectives.

  1. Get an understanding of how coordinators use our invoicing?

  2. Identify the coordinator's pain points with our invoicing?

  3. Gather user input on tools that might make their invoicing tasks easier.

Group 7669.png
Group 538.png
Group 541.jpg

Key Findings

  • Limited Customization: Coordinators wish there was an easier way to select which contacts would be receiving the invoice.

  • Feature Parity: It would make the coordinator's invoicing tasks much easier and faster if there were only one invoice type that had the features of both invoices and one method to send them to clients.

  • Inconsistent UI: Ensure that the invoice summary page, client emails, and PDFs have a consistent look

Solution

Create a streamlined user interface and one user flow that speeds up the process of sending both invoice types to clients.

Research Objectives

  • Understand my user's invoicing process

  • Identify my user's pain points

  • Identify what my users found useful and useless on the invoicing interface pages

User Interviews and Heuristic Evaluations

During my interviews I observed the LEA coordinators as they demonstrated how they send invoices to clients, which helped me realize how time-consuming the process is for them. I recorded their suggestions for how to speed up the process. Additionally, the coordinators identified which user interface components would enhance their experience, such as"

bottom of page