Industrial Operations Platform
Guided workflows for digitizing production records inside an existing system
UX/UI Design + Frontend
3-person studio + client team
2026 · In production · Ongoing
Paper, Vue 3, Pinia, GitHub
Stakeholder discovery, UX/UI, Component system, Frontend
From manual records to guided workflows
Part of the operation still depended on notebooks and spreadsheets. Inconsistent names, incorrect quantities, and difficult-to-read entries forced an operations lead to interpret and correct information before using it.
The product already existed as a role-based SaaS. My work was not to redesign the entire platform, but to improve a critical part of it: the forms completed from tablets and phones in an industrial environment.
Reduce the burden without losing operational detail
The operations lead needed structured data for reporting. The people entering it needed a direct experience with less information visible at once and fewer opportunities to submit an invalid value.
The solution also had to fit an existing product and a short delivery window.
Simplifying the form did not mean removing information. It meant asking for it at the right moment.
What we knew—and what still needed validation
Initial direction came from conversations with the operations lead and ongoing client feedback. These inputs identified recurring inconsistencies in names and quantities.
Direct validation with operators is still in progress. For that reason, this case study does not claim a percentage improvement or that the new flow has eliminated errors.
Make progress visible and interruption recoverable
A staged flow
The team selected a multi-step approach over my initial vertical proposal, reducing how much information appears at once on mobile.
Validation before advancing
Each stage explains its purpose, validates required data, and preserves backward navigation before a final review.
Draft recovery
A shared composable stores the current step and form state locally so an accidental refresh does not restart the task.
One system across three forms
Shared headers, progress, validation, responsive patterns, and design tokens keep parallel workflows consistent.
Designing inside a product already in motion
The main technical challenge was joining an existing Vue codebase, learning its conventions, and delivering changes without disrupting modules owned by other people.
I implemented the three public forms with Vue 3 and shared composables, adapted them for desktop and mobile, and submitted the work through branches and pull requests reviewed by the technical lead.
Integrated workflows; impact still being measured
The three workflows are integrated into the system and their data supports the next reporting stage. The team continues collecting evidence to determine whether the structure reduces errors and completion time.
The verified result today is not a percentage. It is a functional operational experience that shipped and can now improve through real usage.
What I would carry into the next operational product
- →Understand the rules of an existing product before proposing new ones.
- →Let evidence and collaboration improve an initial design position.
- →Owning design and implementation closes interaction gaps that are often lost in handoff.
- →Define measurement before launch instead of reconstructing it afterward.
Moldsid — Digital Experience for Manufacturing
