My Role

My role focused primarily on UI design, where I translated existing wireframes into polished, production-ready interfaces. While the core UX structure was already defined, I made targeted UX refinements throughout the process — improving clarity, hierarchy, and interaction patterns based on usability considerations. This allowed the final product to feel intuitive and purposeful, while staying aligned with the original user flows and technical constraints.

The Problem

On a factory floor, time matters.When a machine stops, engineers don’t open binders. They don’t search shared drives. They ask the person who’s “seen this before.”

The problem is — that person isn’t always there. Pelletech started with a simple observation: The most valuable knowledge in manufacturing lives in peoples heads.

It’s built over decades, shared in passing, learned the hard way. And when experienced engineers retire or move on, that knowledge often disappears with them.This wasn’t a technology problem It was a design problem.

The Gap Between Knowledge and Use

Manufacturing companies already have documentation — manuals, service reports, procedures — but it’s fragmented, outdated, and hard to use in the moment it’s needed. Engineers don’t want another system. They want answers. Fast. Pelletech asked a different question: What if accessing expert knowledge felt as natural as asking a colleague standing next to you?
That idea became the foundation for Expert Advisor.

Designing for the Real World

Expert Advisor wasn’t designed in a meeting room. It was designed around real constraints — noise, pressure, downtime, and hands-on work. The team made a deliberate choice: No complex workflows. No generic AI answers pulled from the internet. Instead, Expert Advisor would only speak using a company’s own knowledge — manuals, reports, procedures, and the unwritten experience of its people. Engineers could ask questions in plain language and get concise, relevant answers they could trust.The product didn’t try to replace experts.
It was designed to extend them.

Capturing What Usually Gets Lost

One of the hardest parts wasn’t retrieval — it was capture.Pelletech realised that if contributing knowledge felt like admin, it wouldn’t happen. So Expert Advisor was designed to accept knowledge in the way engineers naturally share it: quick notes, voice recordings, short videos, informal explanations.Over time, this turned scattered experience into a living knowledge layer — one that grows with every job, fault, and fix.

From Concept to Factory Floor

The product was validated in live environments, including Universal Pack UK, where decades of machine-specific knowledge sat with a small group of senior engineers.As Expert Advisor was introduced, that knowledge became accessible across teams and locations. Engineers could troubleshoot faster, rely less on specific individuals, and keep work moving — even when the “go-to” expert wasn’t available.The impact was tangible: reduced downtime, more confident teams, and knowledge that no longer walked out the door.

The Bigger Idea

Expert Advisor represents a shift in how industrial software is built. It’s not about adding more tools. It’s about removing friction. By designing around how people actually work — not how systems expect them to work — Pelletech created a product that fits quietly into the background, until the moment it’s needed most.In an industry built on experience, Expert Advisor makes sure that experience doesn’t disappear — it stays, learns, and keeps working.

The Outcome