Invoice Management Systems

This business event were held for several days to showcase the latest innovations in payment technology. Participants such as business owners or technology companies (fintech) from the Asia Pacific region were invited to the event.

Introduction

  • A working prototype demonstrating features from Visa’s upcoming new product
  • Fully-remote: Design in Malaysia, app development in Vietnam and deployed in Thailand (on-premise).
  • Project completed in less than 2 weeks (from idea, design execution to deployment at the physical event).
  • Apps are tested on-ground with actual users and usability issues are rectified immediately with Dev team on standby

Understand: Project Requirements

Design a product demo that will help Booth (also known as Pod) attendees to the event a high-level understanding on how the product (Invoice Management System) can benefit their business and partners. In order to determine and analyze the success of the experience after the event, attendees should also be allowed to share their feedback easily after engaging with the experience.

Understand: Challenges

With limited amount of information available on the product, the project demo will simulate a business transaction between three (3) different parties: Buyer, Supplier and Finance. There would be actions required from each user type for the transaction to complete successfully.

The demo will feature a scenario of order creation for a customisable Tuk-Tuk (three-wheeled taxi in Southeast Asia) design. The illustration were created earlier and I will need to adapt it into the product demo.

Define: Project Focus

With the main concerns outlined, I had distilled few key outcomes that will affect the design considerations:

Business outcome(s): Gauge and analyse interest from business partners on the technology innovations showcased during the event.

User outcome(s): Gain better understanding on the latest exciting development in payment technology and able to express thoughts or feeling on each of the technology or product showcase.

Research: Understanding The Context

Unlike the user journey for checking out from an E-commerce website which can be experienced by a single user at a time, the demo requires the three different users to perform actions on the after one another.

Without going into the granular details of the demo at the start of the project, the high-level pencil sketch was important for me to draw a better understanding of the relationship and roles between the different user within the system.

Details for Finance user was omitted during the early phase of the project (as it is still being finalised by project owner)

Design: Validate Early, Reduce Risks

With high-level structure confirmed with the rough sketch, the medium-fidelity wireframes were then created and used as a foundation for the Development team to get started immediately on the code architecture and planning.

The finalised wire-flows for the different roles within the product demo

The UI design process was expedited significantly as the wireframe addressed and aligned the project owner’s expectations on the demo.

Photos: At The Event

The product demo setup consists of three separate tablets that can be interacted individually. To ensure the experience are seamless when user is interacting with the demo (for example: no internet), the tablets are connected over local Wi-Fi (instead over the internet).

Role
  • Visual Design
  • Interaction Design
  • User Research
Year Completed

2017