top of page

Tarmac Logistics

Project | 05

Synopsis

Working within Keytree (SAP consulting, products, solutions and implementation) my task was to work with a SAP expert and provide UX design consultancy and hands on design to build out a POC advanced Axure prototype for Keytree's client Tarmac.

 

At the time Tarmac had an existing ordering, fulfilment and dispatch system that was vastly outdated. The software was built on a green screen interface technology that was in need of modernisation in order to have a better UX, up to date tech support, interoperable technology that could leverage the use of mobile tracking, and sensors within dispatch.

 

Initially, I worked with a Keytree SAP expert who was already introduced to Tarmac to get a basic understanding of the current user journeys and to understand the goals of the project. I spent some time studying the core user journeys for the system and designed some low fidelity wireframe screens to help kick off the design engagement with Tarmac.

 

The first session at Tarmac HQ served as a way for me to explain the design process and what I intended to provide for them and for me to understand more of the processes that happen outside of the ordering system. I used the wireframes and post it notes to annotate and capture insights and new features that they wanted to implement into a new design, with this information I went away and iterated on the design and shared remotely to gain feedback.

In parallel to the POC iterative design, I organised a design workshop at Tarmac HQ to capture deeper insights from depot staff. The workshop was designed to capture pain points and wish lists of the current solution and build out potential new feature requirements whilst avoiding adoption of the poor UX from the legacy systems. The workshop also served to test story epics identified by HQ senior staff to see how they would be received and adapted from their perspectives.

The findings from the workshop were translated into functional requirements and were reviewed by the senior stakeholders and given a priority for the POC. The high to mid-ranked requirements were built into the prototype.

Overall the prototype was designed with a light layer of visual design to provide some clarity, and would later serve as a basis for the visual design phase.  Whilst working on the prototype, I consulted with the SAP expert for feasibility to implement solutions on the platform.

Before the project could continue, all deign activity was frozen prior to Deloitte acquisition of Keytree.

Design Process

User Journey analysis

Workshops & discovery sessions

Requirements definition

Stakeholder engagement

Concept Sketching & Ideation

Tools used: Axure

Screen Samples
Concept Sketching & Ideation
IMG-3260 (1).jpg
User workshop at Tarmac HQ
DSC_1882.JPG
Epic Examples

Epic-2 | uc.3

Sales Office can Search Quotes

A sales team member can look at current quotes

for a customer to review configuration and

pricing offer and then subsequently create an

order.

Epic-2 | uc.4a

Sales Office can Search Quotes

A sales office team member can find search

existing orders for a customer, create or

maintain them and optionally plan the load for

the order for today or a following day. The data will be updated locally and synchronously with the backend ERP solution.

Epic-2 | uc.4b

Sales Office can view orders when ERP is not available [SCP Deployment]

In the event that the backend ERP solution is

not available the Sales Office will be able to

search and view Orders using the data made

available in the SCP tables.

bottom of page