Augury Overview page showcase board: health status charts, KPI cards, research to design, one page four questions, and turning repairs into reported value

Augury · Machine health

A retrieval brief became one page that answers four questions.

Augury monitors the health of industrial machines. I redesigned the Overview page so a site head can see how healthy the company is, where the risk is, how it changed, and which facility needs them, all driven by one filter.

Senior Product Designer 2022 Machine health analytics Web
Problem
The brief asked for data retrieval. Site heads needed answers they could trust at a glance.
Approach
Research recordings with the PM, then the flow, then the screens: one page, four questions, one filter.
Result
An Overview page where every number says what it is, when, and compared to what.

One page. Four questions. One filter.

  • 4Questions answered on one page
  • 3Research findings, each turned into a decision
  • 7Periods from one date menu
  • 1Filter that drives the whole page

Context

The brief asked for data. The page needed answers.

Augury puts sensors on industrial machines and diagnoses their health: Danger, Alarm, Monitor, Acceptable. The Overview page is where a customer lands: company stats, and a way to compare regions, branches, facilities and buildings.

The brief was to retrieve data. The product needed two modes on the same page: one for scanning the whole company at a glance, and one for investigating a single metric, period or facility.

Final Overview page: health status at the top, facilities ranked by machines in Alarm or Danger, one filter for the whole page
The final Overview page. Health first, then where the risk is, then which facility needs you.

Users

Site heads, responsible for every machine on site.

The page is built for the person who answers for a plant or a group of plants. They come in to check, not to explore, and they need to leave with a decision about where to look next.

Scan the company

How healthy are we right now, and is it better or worse than last period? The answer has to be readable before anything is pressed.

Compare facilities

Which facility needs me? Facilities ranked by machines in Alarm or Danger, against a standard they can trust.

Report the value

What did the repairs save? Cost and downtime avoided have to be filled in and counted, or the impact data stays empty.

Research

Three findings, three decisions on the page.

The product manager I worked with ran the user research. She shared the recordings with me, and we analyzed them together. Each finding became one decision, and each decision has a place on the page.

Research to design. What the user research found, and what changed on the page because of it.

User flow

Read and scan first. Ask more only when needed.

The flow starts from a default view a site head can read without touching anything. If the answer is not there, there are four ways to ask more: press a KPI, filter by date, switch tab, or pick a facility. Each one keeps the rest of the page in step, and any selection can be exported.

User flow. How a site head finds what matters, mapped from the original Figma flow.

Key decision

One filter drives the whole page.

A retrieval page asks the user to build a query before showing anything. Site heads needed the opposite: an answer first, then a way to narrow it.

The default

A data-retrieval page: set the filters, run the query, export the result and analyze it somewhere else.

The decision

Open on a default view that answers the first question. One filter, by KPI, date, tab or facility, then reshapes every section at once, and Back to default is always one press away.

One page, four questions. The same Health Status section, reshaped by a single press, date or facility.

Process

Research first, then the flow, then the screens.

01

Analyze the recordings

With the product manager, I went through the research recordings and pulled out where site heads got lost.

02

Map the user flow

I mapped how a site head reads the page and every way they ask more of it, with the decision points, in Figma.

03

Grayscale wireframes

The wireframes settled the structure: the facility list on the left, one date bar, and sections that all follow the same filter.

04

High-fidelity on the design system

The final screens use the tokens and components from Augury’s Figma files, with machine-health colors kept for status only.

Wireframes

Same page, from grayscale to the final design.

The wireframe fixed what the page shows and in which order. The final design kept the structure and added the brand, the health-status colors, and the Augury and company averages on every facility row.

Final Overview page: facility list ranked by machines in Alarm or Danger with Augury and company averages, tabs, date bar, Health Status KPIs and machine health over time

Overview page. Drag to compare the wireframe with the final design.

The solution

Every number says what it is, when, and compared to what.

01

Headlines that name their period

Current status and every chart title name the period and what the trend compares against, so a number is never read against the wrong month.

02

A KPI that explains itself

Pressing a KPI isolates it in the graph and explains it underneath. A value that is missing reads as -/- instead of a misleading zero.

03

Facilities against a standard

The facility list sorts by machines in Alarm or Danger and marks the Augury average and the company average on every row.

04

Repairs turned into reported value

A monthly email and one short dialog let a site head fill in cost and downtime avoided for each repair, and the totals update on the Overview page.

Turning repairs into reported value. One monthly email and one short dialog close the gap in the impact data.

Prototype

Try the Overview page.

A short session: press Machines in Danger, switch to this quarter, then open Bookmarks and fill in the value of a repair. Try the prototype to click through it yourself.

Rebuilt in 2026 from the original user flow, research and Figma files. The customer, facilities and numbers are invented.

Augury Overview · interactive prototype Open full screen

Reflection

A page earns trust when every number explains itself.

The brief asked for retrieval. Site heads needed a default view they could trust. Most of the confusion in the research was not about missing data. It was about numbers that did not say which period they covered or what they were compared against. Naming that on the page did more than any new chart.