✅ TL;DR

Challenge: Manual, inaccessible condition monitoring experience

My Role: Led end-to-end UX strategy, design, and delivery

Outcome:

• Cut setup time by 90%
• Reduced support tickets by 70%
• Shipped a self-service, no-code solution on time for IMTS
• Enabled MM to scale predictive maintenance and win customer trust

🚧 Before: A Broken Process Hiding in Plain Sight

When I was assigned to redesign MachineMetrics’ Condition Monitoring feature, I quickly realized this was more than a UX problem—it was a trust problem.

The feature existed, but only for the few technical power users who knew how to write YAML adapter scripts. Everyone else? They had to call support, wait days, and hope it worked.

There was:

• No central visibility.
• No way to track threshold breaches.
• No history, flexibility, or control.

“One person is the core expert. MM employees need to be involved. Not scalable.” — Internal Engineer

Operators didn’t even know their machines were running at 50% rapid override, inflating utilization numbers. Maintenance teams couldn’t get alerts on temperature spikes until after the damage. Production managers had no visibility into what was being monitored—or worse, what wasn’t.