Interface, and interaction design for enterprise decision management software.


My work is under NDA, therefore this is a high level overview on the context about the work I currently do.

Desktop to browser

The software I am working on is used for enterprise decision management and was initially developed for desktop. I translated some of the desktop patterns to work in browser. Altogether there are roughly 300 interfaces. One of the bigger design challenges among others was establishing consistency across screens that used inconsistent styling across and on screens.
DektoptoBrowser

Multiple environments

In my work I need to take into consideration that interfaces have to work consistently in multiple environments with various degrees of access to functionality.

Dev environment
DevEnironment

Enduser environment
User-env

Target audience

My target audience are engineers, developers, and data scientists.

Users

Things I design

Diagrams
Diagrams

Data points need to be visualized, so that the information can be easily understood and interpreted right away. Everything displayed must be meaningful, from color palettes, to the way punctuation marks in numbers are presented.

In some cases the diagrams require the ability to interact and manipulate the data displayed.

Icons
icons

Icons are used to make scanning and identifying functional areas within an interface easier. The icons can be on the level of a classic trashcan to symbolize “Delete” functionality, but the more challenging part is to create sets of icons that represent abstract concepts, and which are interpreted by different user groups the way they are intended.

Interactions
Interactions

Some interfaces require interactions with objects on the screen. These can be in various states, and sometimes you can do with one object something, which you can’t do with others. The challenge here is to get details, such as cursor states, object states, and various ways of input by hardware right, while also considering read-only and edit modes.

Portals
portals

Some of the functionality is intended only for very advanced users, whilst others get access to a trimmed down version, where they can use the features that they truly need, and not more. The challenge here is the inter-connectedness of features, and requires a good portion of outside-the-box thinking to make complex concepts work in a simplified way, where the system takes care of things under the hood.

Settings panels
Settings
Lots of the interfaces are panels where users can configure all sorts of functionality. The challenge here is to ensure that interface and interaction patterns, as well the terminology and language is consistent. As these have to work in different environments, this poses another challenge, as on the one hand all needs to be shown, while on the other hand, a trimmed down version needs to be displayed.

Toolbars
Toolbars
There are various toolbars for various editors. The challenge here is to make them consistent across all editors.

User interactions
User-interactions
Enduser facing portals are used by target users to collaborate in a team. The challenge here is to optimize the process and workflow for collaboration in such a way that things can get done.

Visual programming editors
VisualEditors
Visual editors á la Visio allow users to set up logic in such a way that functionality emerges. The challenge here is to get the interactions right for various ways of input and to make the visual representation a language that tells the use case at one glance.

Wizards
Wizards
Wizards guide users through the process of getting something done. The challenge here is to use them only when necessary, and to optimize content of inidividual steps in such a way that all makes sense.

Summary

The work I do is characterized by intense complexity and detail, involving multiple layers of dependencies, and vague feedback. Since 2012 I managed to gain an overview of what is there, how things are connected, and work on projects that are highly complex in nature.