UX Design

Bildschirmfoto 2019-04-01 um 16.15.51.png

UX Project by

Designer Tin Nguyen

Developer Ken Tschopp

Designer Simon Wirth

Designer Stefanie Meier



Involved Partner

Küng AG

Portmann Meier

My Role

Research / Interview / Wireframes / Prototyping / Usability Tests


Illustrator / Sketch / Adobe XD / Axure


3 weeks

borm banner.jfif


BORM-INFORMATIK AG develops enterprise resource planning systems for wood processing companies. In order to be able to offer their mobile customers an even better user experience, they decided to find out how they could transfer their operating concept, which is primarily optimized for the desktop, to the mobile version.

Building on this, we made conceptual considerations.  The mobile version does not represent the entire range of functions of Borm Live/Business (Desktop version). We focused on the most necessary functions which should be able to be carried out on the go aswell using useful features the smartphone has to offer: GPS, Map, voice recording, taking photos and so on. We did not approach the problem with the technical feasibility in mind, Instead we tried to focus on the tasks and goals of the users.

1. Analysis

In advance we studied the product range of BORM-INFORMATIK AG and its competitors intensively. In order to understand the tasks, goals and work processes of the users, we also conducted interviews with several Borm employees. The ERP system is also used by BORM in their own company, which is why these interviews gave us an instructive first insight into user needs.



After our preparation we were ready to visit BORM directly at their headquarter in Steinhausen, Zug to finally meet them. We were able to see in which environment they work and who the involved people are.



I held several interviews with different stakeholders and quickly learned about the most important features, insights and the pain points they encounter when interacting with clients using the mobile version.

Bildschirmfoto 2019-03-25 um 16.05.31.png

Key Insights

Unsere Lösung ist noch sehr Maus/Tastaturlastig

Gewisse Dinge kann man nur am PC einsehen… z.B. welches Feld wurde von wem geändert

Wir sind sehr Techniklastig; wir sind Funktions -und Informationsgeil

Kunden wollen eher weg von Customizable Interfaces

So viele Funktionen wie nötig, aber auch so wenige wie gehen

Alle Daten werden immer möglichst zusammen erfasst. Jede Information wird nur einmal erfasst

2. Specification

The answers from the interviews were compiled and analyzed. Based on the analysis, we have defined the first user groups and requirements. We were then able to compile these into larger topic groups. The first functions that our prototype should cover could be derived from these topic groups.


User groups

Primary user groups


Project Manager 


Secondary user groups




3. Design

After evaluating our results we discussed and formulated our first design principles from which final sketches on paper and then the first touchable prototype in the prototyping tool Axure emerged.



Many sketches were made on paper to define the functions and then later on implemented.

konzept 2.png


The clickable prototype was made in Axure.


4. Evaluation

Through observations during testings and the requirements of our customer different design principles ideas were defined.

Design principle 1

Start on the smartphone, finish on the desktop. It can happen that an entry on the smartphone has to be made relatively quickly. For example, the recording of a potential customer at a trade fair, or a quick note during a conversation. These uncategorized entries can then be completed on the desktop application.

Design principle 2

Personalization through usage, instead of customizing in advance. Customers tend to move away from customizable interfaces. Accordingly, we have designed so that no entire modules can be individually adapted. Rather, the content adapts itself to the needs of the user based on user behaviour.

Usability testing

Usability testing with BORM-INFORMATIK and their clients at their place were made with our prototypes.

Bildschirmfoto 2019-03-25 um 16.03.49.png

Affinity map

We created an affinity map as a group to identify themes from our usability testings and thus optimizing our prototype to a second version we then tested.



We prioritized the topics and functions in a Roadmap.  Instead of adding strict deadlines, we put the topics in order of importance. (A roadmap is a strategic plan that defines a goal or outcome and also serves as a communication tool.)

1. Time recording

According to our findings, we come to the conclusion that time recording represents the greatest added value, since all employees in the company are confronted with time recording. It is essential that this can be done quickly, easily and from anywhere. The first approach here would be to include this function first in any MVP.

2. Contact search

Everyone wants to be able to find and recall a customer information regardless of location.

3. Record and save contact

Many people find it useful to record contacts and edit them on site, or to save them temporarily and edit them later.

4. Notes

Many see potential in the “Capture Notes” function, which is why the question arises as to how these should be weighted.

5. Project overview

Project overview is a central function for many, a lot of work is about projects and is searched for.

6. ToDo list

Another built-in ToDo list still needs to be done and an integration & synchronization with other servers