Tim Thompson's Portfolio Intelligentgolf EPOS

Design

The design of the system was based on a set of functional requirements that had been clearly defined from outset. However, due to a rapid development cycle, functionality was delivered in phases. The design in turn had to focus on the initial set of deliverables but I still needed to take a big picture view and anticipate how the interface could evolve to support the complete system.

I began by researching existing EPOS systems, listening to the frustrations and suggestions of users. I produced wireframe diagrams and user journeys to map out key tasks. Wireframes were then refined into graphic design mockups.

A number of mockups had to be produced to address the various tasks, for example:

• selecting product modifiers (eg allowing selection of multiple options and groups of options)
• ability to open multiple tabs and concurrent transactions
• integration with club membership services eg use of member discount cards
• offer refunds
• split bills
• x/z reads & till admin

Graphics & interaction

A modern, fluid feel was desired in contrast with the rudimentary 'Windows 95-esque' layouts of competing systems. I based the fit and feel on a modern flat design language. We also incorporated disciplined animated transitions to create a smooth sense of unity between the different panels, yet not to interfere with usability and speed of operation, paramount for a system to be used in a busy environment.

Front-end development

The rapid development lead initially to a rudimentary appearance for the live software - with nothing of the finesse of the mockups. A few weeks prior to its public launch, I stepped in and tidied up the front-end code to more closely match the designs. HTML5 & CSS3/SCSS was used throughout. To integrate with the development team, I learned the basics of Git and AngularJS. This was also the first project where I used Flexbox for layout. My participation on the front-end then continued for the remainder of my tenure, converting into code designs for new screens as the system evolved.

Usability testing

The rapid development and commercial requirements meant that clean processes couldn't always be adhered to, and I often had to improvise usability testing. After a prototype of the system had been launched, we sought feedback on usability from users, and rolled in changes as they were needed. With a live system now evolving, we were also able to test out new functionality on users prior to production releases.