Go back to portfolio

Mars · Manufacturing

Mars: Breakdown Analysis, Expected to Save At Least €86 Million a Year

Designed Breakdown Analysis from the breakdown list to the confirmed root cause, the site mapping admin page, Downtime in speed mode, and the FMOS admin pages and KPI targets.

Role
UX Designer
Scope
Breakdown Analysis and FMOS factory tools
Focus
Manufacturing
Designer
Gideon Awolesi
Mars: Breakdown Analysis expected to save €86M a year case study cover

My contribution · Mars

Breakdown Analysis and FMOS factory tools

The product owner approved my interactive Breakdown Analysis prototype for testing with the European sites from January 2026. Breakdown Analysis is expected to save Mars at least €86 million a year.

€86M
expected yearly savings
172
prototype iterations
Jan 2026
approved for European site testing

What I owned

  1. 01Designed Breakdown Analysis in Mendix with the product owner and key users, then built it as an interactive prototype in 172 iterations.
  2. 02Designed the site mapping admin page and Downtime in speed mode for factories that measure cuts per minute.
  3. 03Looked after the Mars design system in 2026 and wrote a diagnostic and a governance proposal for it.

Clickable prototypes

Open the Mars prototypes

Each project has its own clickable prototype. Combine breakdowns into an analysis, map functional locations to lines, log downtime in speed mode, or set KPI targets.

Overview

About the project

  1. Role: Lead product designer at Mars from September 2023 to June 2026, on the Digital MAKE program for the European factories. I joined as the second UX designer, next to the designer who was already on the program. From early 2026, I was the only designer on these products, and I ran the knowledge transfer to the designer from the new delivery partner.
  2. What it is: Mars runs its European factories on a set of internal tools built in Mendix. FMOS, the Factory Mars Operating System, is the central one. Shift teams log their KPIs, downtime, and safety checks in it. BPS is the problem-solving tool: a deviation from a KPI gets actions, and if the team can't solve it at their level, it's escalated up the CP levels. Breakdown Analysis is the tool reliability engineers use to find the root cause of a machine breakdown. In 2025, it was still a Power Apps app, and Mars decided to rebuild it in Mendix next to BPS.
  3. Outcome: I designed screens across FMOS, BPS, and Breakdown Analysis, and I built an interactive Breakdown Analysis prototype that the product owner approved for testing with the European sites from January 2026. In 2026, I went back to the original screens and rebuilt the three products as one clickable coded prototype.

Project overview

  1. What Mars runs its factories on: Mars builds its factory apps in Mendix. FMOS, the Factory Mars Operating System, is the central one, where shift teams log their KPIs and run their CP meetings. BPS is the problem-solving tool for process deviations. Breakdown Analysis is the tool reliability engineers use to find the root cause of a technical machine breakdown. In 2025, Breakdown Analysis was still a Power Apps app, and Mars decided to rebuild it in Mendix next to BPS.
  2. What I did: I joined the Digital MAKE team in July 2025 as a UX designer, next to the designer who already owned the design system and the FMOS visuals. My first projects were in FMOS: the admin pages and the Downtime app. From October 2025, I owned the design of the new Breakdown Analysis app. After the other designer left the team in early 2026, I looked after the design system on my own, and when the delivery partner changed, I ran the knowledge transfer to the new partner's designer.
  3. Outcome: The BDA product owner approved my December 2025 Breakdown Analysis prototype, which took 172 iterations, for testing with European sites from January 2026. Breakdown Analysis is expected to save Mars at least €86 million a year.

Prototypes

These were separate projects, so each one has its own tab below. Four of them have an interactive prototype. The other three tabs cover work I supported, or work that a prototype wouldn't show well.

I built the prototypes in 2026 from the meeting notes and the original screens. Mars didn't commission them, and they run on sample data built on the real Slough lines and functional locations, so they aren't Mars's production software.

Breakdown Analysis

Interactive prototype: Open the prototype. Try this: Select the three Transfer conveyor 3 breakdowns and press Combine and start BDA, then work through the 5 Why to a root cause.

Reliability engineers and maintenance teams use Breakdown Analysis to analyse unplanned technical breakdowns, where a machine stops for more than 10 minutes, and to find the root cause. Process and production problems go to BPS instead. Under the regional standard, each site has to finish at least two analyses every 30 days. Each site sets a trigger point for each line, which decides if a breakdown is major or minor, and only the majors need a mandatory analysis.

The old version ran in Power Apps, live on 14 sites with 3 more testing it. Breakdowns came from SAP through the data lake with a one-day delay. Power Apps has a record limit, so breakdowns older than about five weeks were archived, and users lost that history. Major and minor breakdowns were in separate tables, and a minor breakdown had to be moved into the major table before anyone could analyse it, which caused database issues. Technicians had also asked to fill in BD page 1, the first page of the analysis, before the end of their shift.

A previous designer had started mockups in 2025 and didn't finish them. From October 2025, I owned the design of the new Mendix app. I ran weekly design sessions with the BDA product owner, who was the global owner of the tool, and a big part of the job was capturing his knowledge of the process in the design.

Breakdown Analysis, Breakdown Analysis, figure 1
Breakdown Analysis, Breakdown Analysis, figure 2

Research with the product owner and key users

From October 2025, I had access to the old tool in a test environment, and the product owner walked me through the process in the weekly sessions. Mars teams use the MSC-PM method, which ran in Excel, with BD page 1 for the information about the breakdown and BD page 2 for the analysis. The product owner asked me to keep the new flow simple and in line with that method.

On 27 October 2025, I ran a key-user session with two reliability engineers. One of them had been at Mars for 14 years and was on the team that set up the original BDA process. They asked to see who's leading each analysis, so the breakdown list got a BDA lead column. They also explained that they usually reject the unused major breakdowns once a year, in bulk.

Mars has more than 30 factories, so the product owner picked key users from the well-performing ones instead of asking every site. Besides that session and the product owner's reviews, there isn't a documented usability test from my time on the project.

Breakdown Analysis, Research with the product owner and key users, figure 1

How the analysis flow works

The analysis starts from the breakdown list, where major and minor breakdowns are in one table. Red marks a major breakdown and blue marks a minor one. From a row, the BDA lead can reject the breakdown with a mandatory comment, add it to an analysis that's already in progress, open BD page 1, or start the analysis straight away. The lead can also select several breakdowns on the same equipment and combine them into one analysis, and the latest breakdown becomes the leading one.

On BD page 1, the team writes the problem statement as a 5W2H and adds the breakdown details and pictures. A required field has a red exclamation mark that turns green once it's filled, and a confirmation shows when the page is complete. In the 5 Why analysis, the team starts from the problem and asks why, and each answer becomes the next question. A chain can go between three and five levels deep, and only the last why in a chain can be a root cause, because that's the rule in the method. An analysis can have more than one root cause.

Corrective actions are added only to the confirmed root causes. After that, the team answers the standard checkpoint questions, which are the same globally, and the site's own questions, on one page with collapsible groups. The last step is the check and finalise page, with the general breakdown information in the blue header and all the corrective actions listed.

Breakdown Analysis, How the analysis flow works, figure 1
Breakdown Analysis, How the analysis flow works, figure 2
Breakdown Analysis, How the analysis flow works, figure 3

The design decisions and the reasons for them

In the old process, people often assumed a root cause without checking it. So each why can have confirmation actions, which are checks to prove or disprove that answer. A why is confirmed once all its confirmation actions are confirmed, and if someone adds a new action after that, it goes back to unconfirmed. A confirmed root cause turns green, and a why that isn't confirmed yet stays blue.

Actions in Breakdown Analysis can't be rejected, unlike in BPS, because each one is a check that comes back with findings. An action can be a normal task or an SAP notification, which an RPA bot creates overnight. When the team switches SAP action to yes, the planner group becomes a mandatory field.

The product owner chose a side navigation over a top header, because the header took up too much vertical space, and the dashboard's three panels had to fit on a standard screen without scrolling. Editing happens in a panel that slides in from the right, and the list stays in view behind it. In March 2026, the team listed that sliding panel as a priority pattern for the other apps as well.

In December 2025, I merged the breakdown list and the BDA list into one table that shows both the breakdown numbers and the BDA numbers. The BDA started column became BDA status, with four values: Rejected, Not started, In progress, and Completed. This way, a rejected breakdown stays in the list with its status, instead of being deleted.

The same users work in FMOS and BPS on the days they run an analysis, so I kept the components in line with BPS and the FMOS look, with deep blue and straight corners. In November 2025, a developer reviewed the designs and confirmed they could be built on the BPS functionality and the Mars design system.

Breakdown Analysis, The design decisions and the reasons for them, figure 1
Breakdown Analysis, The design decisions and the reasons for them, figure 2

The prototype and what happened next

I started the prototype in Figma and then moved to Figma Make. I built a component library in code first, and then built each page from screenshots and detailed explanations, with no more than three screenshots in a prompt. The prototype took 172 iterations, from the breakdown list to the check and finalise page. I published it as a Figma Sites link, because colleagues in the US and the UK didn't have Figma access and still needed to click through it.

In early December 2025, the product owner went through the prototype page by page and approved it for testing with European sites from January 2026.

After the approval, I designed the admin pages, and in February 2026 the notifications and emails. That month, the product owner also asked for the equipment criticality from SAP, with A first, and for a repeating breakdown checkbox. Development of the new app was planned for the second quarter of 2026, and it hadn't started by March 2026.

Breakdown Analysis, The prototype and what happened next, figure 1
Breakdown Analysis, The prototype and what happened next, figure 2

Need this level of detail in your product?

Work through the hard product decisions early.

If you’re a product team, that can mean a focused design, system, or prototype project. If you’re hiring, it’s a chance to look closer at how I work across research, interfaces, and code.