Visual redesign

Role

UX Designer

Focus

Visual hierarchy

Company

MTEK

Product

Enterprise Software

Description

A visual redesign of MBrain; a Manufacturing Execution System (MES). We focused on improving visual hierarchy and workflow organization to make complex interfaces easier to understand.

Visual redesign

Role

UX Designer

Focus

Visual hierarchy

Company

MTEK

Product

Enterprise Software

Description

A visual redesign of MBrain; a Manufacturing Execution System (MES). We focused on improving visual hierarchy and workflow organization to make complex interfaces easier to understand.

Overview

From 2022–2025, I worked as a UX/UI Designer at MTEK.

Their product, MBrain, is a Manufacturing Execution System (MES) used to monitor, track, and manage production on the factory floor, from raw materials through to finished products.

MBrain’s interfaces often needed to present large amounts of information and support complex workflows. Over time, inconsistent grouping, unclear hierarchy, and uneven use of colour made them harder to scan and understand.

I focused on redesigning key areas to bring more order to the interface, making relationships between information clearer and using colour more purposefully to guide attention.

Challenge

Challenge

Because MBrain is complex, many workflows involved dense screens packed with nested information, competing actions, and hierarchical layers.

In some places, the visual design actually made things harder. For instance, in Process Builder, the selection highlight sometimes faded into the background, making it difficult to tell which area was active.

The challenge was to make these screens easier to read and navigate while preserving the complexity people needed to do their work.

Approach

Rather than applying one visual solution across every screen, I looked at how information and actions were structured within each workflow and identified where the hierarchy was breaking down.

I then used grouping, spacing, contrast, and colour to create clearer relationships between elements and give important information and actions more appropriate visual weight.

Project Examples

The examples below show how I applied these principles to strengthen visual hierarchy, improve scanability, and clarify complex workflows across the interface.

Improving workflow organization

The Process Builder, used to configure production workflows, packed a large number of controls into a relatively small space.

Testing highlighted several friction points, including closely placed controls in the step-design area and a long, uncategorized tool list that made individual tools harder to find.

Before

The long tool list on the right was difficult to scan. I planned to group the tools into collapsible categories, letting users open what they needed instead of scanning every option at once. This part of the redesign wasn't completed before I left the project.

After

More broadly, the redesign focused on making the existing complexity easier to navigate rather than removing functionality. I used clearer grouping, hierarchy, and colour to separate different parts of the interface and make actions easier to distinguish.

Improving information hierarchy

In MBrain nested tables were used to let users drill down from an order into related information, such as articles, variations, revisions, and bills of materials.

I was asked to make these relationships easier to see without losing the nested structure.

Nested levels were difficult to distinguish

Before

Exploring the hierarchy
Exploring the hierarchy

I explored different ways of making the nested relationships easier to follow.

Early concepts tested increasingly explicit use of colour and containment to show which information belonged to each level.

I explored different ways of making the nested relationships easier to follow.

Early concepts tested increasingly explicit use of colour and containment to show which information belonged to each level.

Case study image
Case study image
Case study image

Early explorations: testing different levels of visual separation

Refined Direction

I initially preferred stronger colour differentiation, but my team lead felt the more restrained treatment provided enough distinction for people who worked with these tables regularly. We ultimately moved forward with the subtler direction.

Colour still helped distinguish key levels, while the data itself remained visually quieter.

I initially preferred stronger colour differentiation, but my team lead felt the more restrained treatment provided enough distinction for people who worked with these tables regularly. We ultimately moved forward with the subtler direction.

Colour still helped distinguish key levels, while the data itself remained visually quieter.

After

Improving form organization

Some MBrain forms spread a large number of fields across wide horizontal layouts. This made it harder to see which pieces of information belonged together, while the main action could get lost among secondary ones.

I grouped the fields by their natural categories: Product Information, Machine Settings, and Batch Details, so related information sits together where it makes sense.

I shifted to a more vertical layout and gave each section more breathing room. This helps guide the eye down the form instead of forcing users to scan back and forth.

I also clarified the action hierarchy. Since Save is the primary action, it stands out, while Reset takes a quieter role.

Outcome

The redesign gave us better ways to handle some of MBrain’s most complex interfaces, including editing tools, layered tables, and forms.

I focused on grouping, hierarchy, colour, and action priority to make relationships and workflows easier to understand.

Not every idea made it into the product. Some stayed as explorations, and others were set aside as priorities shifted. The nested-table redesign, for example, was well received internally and documented for future reference, but it wasn’t built while I was at MTEK.

The redesign gave us better ways to handle some of MBrain’s most complex interfaces, including editing tools, layered tables, and forms.

I focused on grouping, hierarchy, colour, and action priority to make relationships and workflows easier to understand.

Not every idea made it into the product. Some stayed as explorations, and others were set aside as priorities shifted. The nested-table redesign, for example, was well received internally and documented for future reference, but it wasn’t built while I was at MTEK.

Reflections

This project changed how I think about complexity.

In enterprise products, simplifying an experience isn’t always about taking things away. Sometimes the information is essential, and the real challenge is giving that complexity enough structure to make sense.

Working with dense workflows, nested information, and forms taught me to pay closer attention to how grouping, hierarchy, and visual weight can make complex interfaces easier to navigate without losing what users need.

This project changed how I think about complexity.

In enterprise products, simplifying an experience isn’t always about taking things away. Sometimes the information is essential, and the real challenge is giving that complexity enough structure to make sense.

Working with dense workflows, nested information, and forms taught me to pay closer attention to how grouping, hierarchy, and visual weight can make complex interfaces easier to navigate without losing what users need.

Say hello!

I'm always happy to chat about UX, product design, or new opportunities!

Becka Design 2026©

Say hello!

I'm always happy to chat about UX, or new opportunities!

Say hello!

I’m always happy to chat about UX, or new opportunities!